All MIBs › MPLS-VPN-MIB › mplsNumVrfRouteMaxThreshExceeded
mplsNumVrfRouteMaxThreshExceeded
Module: MPLS-VPN-MIB
OID (symbolic): MPLS-VPN-MIB::mplsNumVrfRouteMaxThreshExceeded
OID (numeric): 1.3.6.1.3.118.0.4
Node type: NOTIFICATION-TYPE
Description:
This notification is generated when the number of routes contained by the specified VRF reaches or attempts to exceed the maximum allowed value as indicated by mplsVrfMaxRouteThreshold. In cases where mplsVpnVrfConfHighRouteThreshold is set to the same value as mplsVpnVrfConfMaxRoutes, mplsVpnVrfConfHighRouteThreshold need not be exceeded; rather, just reached for this notification to be issued.
Note that mplsVpnVrfConfRouteMaxThreshTime denotes the interval at which the this notification will be re-issued after the maximum value has been exceeded (or reached if mplsVpnVrfConfMaxRoutes and mplsVpnVrfConfHighRouteThreshold are equal) and the initial notification has been issued. This value is intended to prevent continuous generation of notifications by an agent in the event that routes are continually added to a VRF after it has reached its maximum value. The default value is 10 minutes. If this value is set to 0, the agent should only issue a single notification at the time that the maximum threshold has been reached, and should not issue any more notifications until the value of routes has fallen below the configured threshold value.
What is mplsNumVrfRouteMaxThreshExceeded?
This notification fires when the number of routes in a VRF (Virtual Routing and Forwarding) instance reaches or exceeds the maximum allowed threshold defined by mplsVrfMaxRouteThreshold. It alerts operators that the VRF is at or over capacity. Network administrators rely on this notification to trigger scaling actions or investigate unexpected route proliferation in MPLS VPN deployments.
Examples
Send this trap to an SNMP manager — replace <manager> with the IP or hostname of your monitoring server (SNMPv2c):
snmptrap -v2c -c public <manager> '' MPLS-VPN-MIB::mplsNumVrfRouteMaxThreshExceeded snmptrap -v2c -c public <manager> '' 1.3.6.1.3.118.0.4
Listen for incoming traps on the manager host (-f keeps it in the foreground, -Lo prints to stdout — useful for testing):
snmptrapd -f -Lo -c /dev/null authCommunity log public
Example snmptrapd log entry:
zoo11-linux.zoo [UDP: [192.168.30.111]:57898->[192.168.30.10]:162]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (399781930) 46 days, 6:30:19.30 SNMPv2-MIB::snmpTrapOID.0 = OID: MPLS-VPN-MIB::mplsNumVrfRouteMaxThreshExceeded
SNMPv3 example:
snmptrap -v3 -l authPriv -u snmpv3user -a SHA -A "AuthPass1" -x AES -X "PrivPass1" <manager> '' MPLS-VPN-MIB::mplsNumVrfRouteMaxThreshExceeded
OID Breakdown
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | BIANCA-BRICK-PPP-MIB |
| 1.3.6 | dod | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1 | internet | BIANCA-BRICK-PPP-MIB |
| 1.3.6.1.3 | experimental | DASAN-DHCP-MIB |
| 1.3.6.1.3.118 | mplsVpnMIB | MPLS-VPN-MIB |
| 1.3.6.1.3.118.0 | mplsVpnNotifications | MPLS-VPN-MIB |
| 1.3.6.1.3.118.0.4 | mplsNumVrfRouteMaxThreshExceeded | MPLS-VPN-MIB |