L3VPN_1.3.6.1.2.1.10.166.11.0.6 L3VPN_MIB_TRAP_THRESH_CLEARED

Trap Buffer Description

The number of routes in the VPN instance fell below the maximum value(Excluding maximum). (VpnInstanceName=[VpnInstanceName], VpnInstanceRouteCount=[VpnInstanceRouteCount], MaxValue=[MaxValue])

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Critical
Mnemonic Code	L3V_TRAP_THRE_EXCEED
Trap OID	1.3.6.1.2.1.10.166.11.0.6
MIB	MPLS-L3VPN-STD-MIB
Alarm ID	0x09110001
Alarm Name	L3V_TRAP_THRE_EXCEED
Alarm Type	qualityOfServiceAlarm
Raise or Clear	Clear
Match trap	L3VPN_1.3.6.1.2.1.10.166.11.0.4 L3VPN_MIB_TRAP_THRESH_EXCEED

Trap Buffer Parameters

Parameter	Description
VpnInstanceName	Indicates the name of a VPN instance. If a VPN instance name is "_public_", the alarm cause is that the number of public network route prefixes exceeds the maximum limit.
VpnInstanceRouteCount	Indicates the number of existing route prefixes.
MaxValue	Indicates that the maximum number of route prefixes allowed.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.2.1.10.166.11.1.3.1.1.3	mplsL3VpnVrfPerfCurrNumRoutes	-
1.3.6.1.2.1.10.166.11.1.2.2.1.10	mplsL3VpnVrfConfHighRteThresh	mplsL3VpnVrfName

Impact on the System

After the number of public network route prefixes fell below the maximum limit, public network routes can be received normally. After the number of VPN route prefixes fell below the maximum limit, VPN routes can be received normally.

Possible Causes

Cause 1: The number of public network route prefixes reached the maximum limit, and then it fell below the maximum limit.

Cause 2: The maximum limit for public network route prefixes was adjusted higher using the ip prefix-limit command.

Cause 3: The number of VPN route prefixes reached the maximum limit, and then it fell below the maximum limit.

Cause 4: The maximum limit for VPN route prefixes was adjusted higher using the prefix limit command.

Procedure

This alarm message is informational only, and no action is required.