All MIBs › MPLS-L3VPN-STD-MIB › mplsL3VpnNumVrfRouteMaxThreshCleared
mplsL3VpnNumVrfRouteMaxThreshCleared
Module: MPLS-L3VPN-STD-MIB
OID (symbolic): MPLS-L3VPN-STD-MIB::mplsL3VpnNumVrfRouteMaxThreshCleared
OID (numeric): 1.3.6.1.2.1.10.166.11.0.6
Node type: NOTIFICATION-TYPE
Description:
This notification is generated only after the number of routes contained by the specified VRF exceeds or attempts to exceed the maximum allowed value as indicated by mplsVrfMaxRouteThreshold, and then falls below this value. The emission of this notification informs the operator that the error condition has been cleared without the operator having to query the device.
Note that mplsL3VpnVrfConfRteMxThrshTime denotes the interval at which the mplsNumVrfRouteMaxThreshExceeded notification will be reissued after the maximum value has been exceeded (or reached if mplsL3VpnVrfConfMaxRoutes and mplsL3VpnVrfConfHighRteThresh are equal) and the initial notification has been issued. Therefore, the generation of this notification should also be emitted with this same frequency (assuming that the error condition is cleared). Specifically, if the error condition is reached and cleared several times during the period of time specified in mplsL3VpnVrfConfRteMxThrshTime, only a single notification will be issued to indicate the first instance of the error condition as well as the first time the error condition is cleared. This behavior is intended to prevent continuous generation of notifications by an agent in the event that routes are continually added and removed to/from a VRF after it has reached its maximum value. The default value is 0. If this value is set to 0, the agent should issue a notification whenever the maximum threshold has been cleared.
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-L3VPN-STD-MIB::mplsL3VpnNumVrfRouteMaxThreshCleared snmptrap -v2c -c public <manager> '' 1.3.6.1.2.1.10.166.11.0.6
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]:57239->[192.168.30.10]:162]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (289048983) 33 days, 10:54:49.83 SNMPv2-MIB::snmpTrapOID.0 = OID: MPLS-L3VPN-STD-MIB::mplsL3VpnNumVrfRouteMaxThreshCleared
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.2 | mgmt | BKTEL-HFC862-BASE-MIB |
| 1.3.6.1.2.1 | mib_2 | CHECKPOINT-MIB-2 |
| 1.3.6.1.2.1.10 | transmission | CHECKPOINT-MIB-2 |
| 1.3.6.1.2.1.10.166 | mplsStdMIB | MPLS-TC-STD-MIB |
| 1.3.6.1.2.1.10.166.11 | mplsL3VpnMIB | MPLS-L3VPN-STD-MIB |
| 1.3.6.1.2.1.10.166.11.0 | mplsL3VpnNotifications | MPLS-L3VPN-STD-MIB |
| 1.3.6.1.2.1.10.166.11.0.6 | mplsL3VpnNumVrfRouteMaxThreshCleared | MPLS-L3VPN-STD-MIB |