L3VPN_1.3.6.1.4.1.2011.5.25.145.33.1 hwIpv4RouteExceed

Trap Buffer Description

The number of IPv4 routes in the VPN instance exceeded the maximum value. (VPN instance name=[vpnName], number of existing routes=[current], maximum value=[max])

The number of IPv4 routes in the VPN instance exceeded the maximum number that is allowed.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Critical
Mnemonic Code	hwL3vpnIpv4RouteExceed
Trap OID	1.3.6.1.4.1.2011.5.25.145.33.1
MIB	HUAWEI-RM-EXT-MIB
Alarm ID	0x00F1021c
Alarm Name	hwL3vpnIpv4RouteExceed
Alarm Type	qualityOfServiceAlarm
Raise or Clear	Raise
Match trap	L3VPN_1.3.6.1.4.1.2011.5.25.145.33.2 hwIpv4RouteExceedClear

Trap Buffer Parameters

Parameter	Description
vpnName	VPN instance name.
current	Current number of IPv4 routes in the VPN instance.
max	Maximum number of IPv4 routes in the VPN instance.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.145.31.3	hwIpv4RouteLimitVpnName	-
1.3.6.1.4.1.2011.5.25.145.31.1	hwCurIpv4RouteNum	-
1.3.6.1.4.1.2011.5.25.145.31.2	hwIpv4RouteLimitValue	-

Impact on the System

If the number of VPN IPv4 routes exceeds the upper threshold, the excessive routes cannot be added to the VPN instance's routing table, causing these routes to be lost and some traffic to be interrupted.

Possible Causes

Cause 1: The number of received VPN IPv4 routes exceeded the upper threshold of the VPN instance multiplied by the maximum number allowed.

Cause 2: The limit on the maximum number of routes allowed in the IP address family of the VPN instance was reduced.

Procedure

1. Run the display ip routing-table limit command to check the configured limit on the maximum number of routes allowable in the VPN instance and the current total number of routes.

2. Run the display ip routing-table statistics command to check whether redundant VPN routes exist in the VPN instance.

If so, go to Step 3.
If not, go to Step 4.

3. Delete the redundant VPN routes and then check whether the alarm persists.

If so, go to Step 4.
If not, go to Step 6.

4. Run the display this command in the VPN instance view to check the routing-table limit configuration. Check whether the number of routes in the VPN instance reaches the upper threshold.

If so, the alarm is informational only, and no action is required. To clear the alarm, run the routing-table limit number { alert-percent | simply-alert } command to reconfigure a proper limit on the maximum number of routes. Then go to Step 6.
If not, go to Step 5.

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

6. End.