RM_1.3.6.1.4.1.2011.5.25.145.19.3.1 hwL3vpnIpv6PrefixExceed
Description
The number of IPv6 prefixes in the VPN instance exceeded the maximum value. (VpnInstanceName=[VpnInstanceName], PrefixCount=[VpnInstanceRouteCount], MaxValue=[MaxValue])
The number of IPv6 route prefixes in a VPN instance exceeded the maximum number that is allowed.
Attributes
Attribute |
Description |
|---|---|
Alarm or Event |
Alarm |
Trap Severity |
Critical |
Mnemonic Code |
hwL3vpnIpv6PrefixExceed |
Trap OID |
1.3.6.1.4.1.2011.5.25.145.19.3.1 |
Alarm ID |
0x70122013 |
Alarm Type |
qualityOfServiceAlarm |
Raise or Clear |
Raise |
Match trap |
RM_1.3.6.1.4.1.2011.5.25.145.19.3.2 hwL3vpnIpv6PrefixExceedClear |
Parameters
VB
Impact on the System
If more IPv6 routes are added, they will be discarded. As a result, traffic may be interrupted.
Possible Causes
Cause 1:
A large number of IPv6 routes were added to the routing table.
Cause 2:
The maximum number of IPv6 route prefixes in the VPN instance was reduced.
Procedure
- Run the display ipv6 routing-table vpn-instance vpn-instance-name statistics command to check the total number of IPv6 route prefixes in the VPN instance and the number of routes of each routing protocol that are added to the IPv6 routing table. Then, run the display ipv6 routing-table limit command to check whether the number of IPv6 route prefixes in the VPN instance exceeds the configured maximum number.
- Delete unneeded IPv6 VPN routes or run the ipv6 prefix limit number { alert-percent [ route-unchanged ]| simply-alert } command to increase the maximum number. Then, check whether the alarm persists.
- Collect trap, log, and configuration information, and contact technical support personnel technical support personnel.
- End.
