BGP_1.3.6.1.4.1.2011.5.25.177.11.2.1 RPKISESSIONROAEXCEED

Trap Buffer Description

The number of ROAs received from the session exceeded the alarm number. (InstanceId=[InstanceId], SessionRemoteAddrType=[SessionIPAddrType], SessionRemoteAddr=[SessionIPAddr], MaxROANum=[RpkiLimitNum])

The number of ROA entries that the device received from an RPKI session exceeded the alarm upper threshold.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Critical
Mnemonic Code	hwRpkiSessionROAExceed
Trap OID	1.3.6.1.4.1.2011.5.25.177.11.2.1
MIB	HUAWEI-BGP-VPN-MIB
Alarm ID	0x083b2000
Alarm Name	hwRpkiSessionROAExceed
Alarm Type	communicationsAlarm
Raise or Clear	Raise
Match trap	BGP_1.3.6.1.4.1.2011.5.25.177.11.2.2 RPKISESSIONROAEXCEEDCLEAR

Trap Buffer Parameters

Parameter	Description
InstanceId	Instance ID
SessionIPAddrType	Session address type
SessionIPAddr	Session address
RpkiLimitNum	Maximum number of ROA entries that a device is allowed to receive from an RPKI session

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.177.11.1.1.1.4	hwRpkiSessionRoaLimitNum	hwRpkiSessionVrfName hwRpkiSessionType hwSessionIPAddr

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.177.11.1.1.1.4

hwRpkiSessionRoaLimitNum

hwRpkiSessionVrfName

hwRpkiSessionType

hwSessionIPAddr

Impact on the System

If alert-only is not specified in the rpki-limit command, the session will be disconnected.
If alert-only is specified in the rpki-limit command, services will not be affected.

Possible Causes

The number of ROA entries that the device receives from an RPKI session exceeded the configured limit.

Procedure

1. Run the display rpki session verbose command to check whether the number of ROA entries that the device receives from an RPKI session exceeds the configured limit.

If the number of ROA entries that the device receives from an RPKI session exceeds the configured limit, go to Step 2.
If the number of ROA entries that the device receives from an RPKI session has not exceeded the configured limit, go to Step 6.

2. Check whether the configured limit is too low.

If the configured limit is too low, go to Step 5.
If the configured limit meets the requirements on the live network, go to Step 3.

3. Check logs and contact maintenance personnel of the peer device to determine whether all the data received from the peer device is necessary.

If all the data received from the peer device is necessary, go to Step 5.
If not all the data received from the peer device is necessary, go to Step 4.

4. Ask the maintenance personnel of the peer device to delete the unnecessary ROA data and then check whether the trap is cleared. If the trap persists, go to Step 6.

5. Increase the limit on the number of ROA entries that the device is allowed to receive from an RPKI session and then check whether the trap is cleared. If the trap persists, go to Step 6.

6. Collect alarm information and configuration information, and then contact technical support personnel.