CISCO-IETF-PPVPN-MPLS-VPN-MIB

        This MIB is an extension of the MPLS-VPN-MIB.  It contains a new
notification, mplsNumVrfRouteMaxThreshCleared, which was added with 
MPLS-VPN-MIB-DRAFT-05.
    
Source file
CISCO-IETF-PPVPN-MPLS-VPN-MIB
Last revised
Identity
ciscoMplsVpnMIB
Base OID
1.3.6.1.4.1.9.10.999
Imported Objects
CISCO-SMI ciscoExperiment
MPLS-VPN-MIB mplsVpnVrfConfHighRouteThreshold mplsVpnVrfPerfCurrNumRoutes
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page)
SNMPv2-SMI MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page)
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-IETF-PPVPN-MPLS-VPN-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-IETF-PPVPN-MPLS-VPN-MIB::ciscoMplsVpnMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-IETF-PPVPN-MPLS-VPN-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-IETF-PPVPN-MPLS-VPN-MIB::ciscoMplsVpnMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (6)
.1.3.6.1.4.1.9.10.999
.1.3.6.1.4.1.9.10.999.0
.1.3.6.1.4.1.9.10.999.1
.1.3.6.1.4.1.9.10.999.2
.1.3.6.1.4.1.9.10.999.2.1
.1.3.6.1.4.1.9.10.999.2.2
Dependencies (10) 4 direct · 6 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Conformance Groups (1)
Objects required for CISCO MPLS VPN notifications.
.1.3.6.1.4.1.9.10.999.2.2.1
Compliance Statements (1)

OID .1.3.6.1.4.1.9.10.999.2.1.1
Compliance statement for agents that support the CISCO
MPLS VPN MIB.
Required groups
Notifications / Traps (1)
NameOIDDescription
.1.3.6.1.4.1.9.10.999.0.1
This notification is generated only after the number of routes
contained by the specified VRF reaches 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.