L3VPN_1.3.6.1.2.1.10.166.11.0.3 mplsL3VpnVrfRouteMidThreshExceeded
Description
L3VPN/4/L3V_TRAP_MID_EXCEED:OID [oid] The number of routes in the VPN instance exceeded the middle threshold. (VpnInstanceName=[octet], VpnInstanceRouteCount=[gauge], MidThresholdValue=[gauge])
The number of routes contained by the specified VRF exceeds the value indicated by mplsL3VpnVrfMidRouteThreshold.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.2.1.10.166.11.0.3 |
Warning |
qualityOfServiceAlarm(3) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
VpnInstanceName |
Indicates the name of a VPN instance. |
VpnInstanceRouteCount |
Indicates the number of existing routes or prefixes. |
MidThresholdValue |
Indicates that the alarm threshold of routes or prefixes. |
Impact on the System
When the total number of VPN routes or prefixes exceeds the alarm threshold, routes can still be installed to the routing table. That is, the routes are not discarded and traffic is not interrupted for the moment.
Possible Causes
1. The total number of the VPN routes in the VPN routing table exceeds the alarm threshold of VPN routes specified in the routing-table limit command, and is smaller than the maximum number of routes.
2. The total number of the VPN route prefixes in the VPN routing table exceeds the alarm threshold of VPN route prefixes specified in the prefix limit command, and is smaller than the maximum number of route prefixes.
Procedure
- Run the display ip routing-table limit vpn-instance vpn-instance-name command to check whether the number of routes or prefixes in the VPN instance exceeds the upper limit.
- Analyze the source of each route and check whether the
number of existing routes or prefixes in the VPN instance meets the
requirements.
If so, go to Step 4.
If not, go to Step 3.
- Check whether the number of routes or prefixes still exceeds
the alarm threshold after redundant VPN routes are deleted.
If so, go to Step 5.
If not, go to Step 6.
- Enter the VPN instance view and run the display this command
to view the configuration of the routing-table
limit command and the prefix limit command. Then, check whether the set alarm threshold of VPN
routes is proper.
If so, go to Step 5.
If not, run the routing-table limit number { alert-percent | simply-alert } or prefix limit number { alert-percent | simply-alert } command to set a proper alarm threshold of routes or prefixes. Then, go to Step 6.
- Collect alarm information and configuration information, and then contact technical support personnel.
- End.
Previous
