L3VPN_1.3.6.1.4.1.2011.5.25.145.19.3.3 hwL3vpnIpv6PrefixThresholdExceed

Trap Buffer Description

The number of IPv6 prefixes in the VPN instance exceeded the threshold. (VpnInstanceName=[VpnInstanceName], PrefixCount=[PrefixCount], Threshold=[Threshold])

The number of IPv6 route prefixes in a VPN instance exceeded the value calculated using the formula .

In VS mode, this trap is supported only by the admin VS.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Event
Trap Severity	Warning
Mnemonic Code	hwL3vpnIpv6PrefixThresholdExceed
Trap OID	1.3.6.1.4.1.2011.5.25.145.19.3.3
MIB	HUAWEI-RM-EXT-MIB
Alarm ID	This is an event trap and does not involve alarm ID.
Alarm Name	This is an event trap and does not involve alarm name.
Alarm Type	This is an event trap and does not involve alarm type.
Raise or Clear	This is an event trap and does not involve alarm generation or clearance.
Match trap	-

Trap Buffer Parameters

Parameter	Description
VpnInstanceName	Name of a VPN instance.
PrefixCount	Current number of IPv6 route prefixes in the VPN instance.
Threshold	Alarm threshold for the number of IPv6 route prefixes in the VPN instance.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.145.9.3	hwIpv6PrefixLimitVpnName	-
1.3.6.1.4.1.2011.5.25.145.9.1	hwCurIpv6PrefixNum	-
1.3.6.1.4.1.2011.5.25.145.9.2	hwIpv6PrefixLimitValue	-

Impact on the System

This alarm has no adverse impact on the system.

Possible Causes

Cause 1: A large number of IPv6 routes were added to the routing table in the VPN instance.

Cause 2: The alarm threshold for the number of IPv6 route prefixes in the VPN instance was reduced.

Procedure

1. Run the display ipv6 routing-table vpn-instance-name statistics command to check the total number of private network prefixes and the number of routes that each protocol adds to the IPv6 routing table. Run the display ipv6 routing-table limit command to check the total number of VPN route prefixes and the limit on the number of VPN route prefixes. Check whether the number of configured VPN route prefixes exceeds the alarm threshold.

If yes, go to Step 2.
If no, go to Step 3.

2. Run the prefix limit {alert-percent | simply-alert} command to reconfigure a proper alarm threshold for route prefixes or delete redundant VPN routes. Then, check whether the alarm persists.

If yes, go to Step 3.
If no, go to Step 4.

3. Collect log and configuration information, and contact technical support.

4. End.