IPI-DOT1AG-CFM-NVO3-TRAP-MIB

        IPI NVO3 CFM CCM FaultAlarm Trap MIB. 
    
Source file
IPI-DOT1AG-CFM-NVO3-TRAP-MIB
Last revised
Identity
dot1agCfmNVO3trapMib
Base OID
1.3.6.1.4.1.36673.121
Imported Objects
IEEE8021-CFM-MIB dot1agCfmMaIndex dot1agCfmMdIndex dot1agCfmMepEntry dot1agCfmMepIdentifier Dot1agCfmRemoteMepState
IPI-MODULE-MIB ipi
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Integer32 mib-2 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC MacAddress RowStatus TimeStamp TruthValue
Net-SNMP examples using the ipinfusion 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 'IPI-DOT1AG-CFM-NVO3-TRAP-MIB' -M '/opt/observium/mibs/ipinfusion:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'IPI-DOT1AG-CFM-NVO3-TRAP-MIB::dot1agCfmNVO3trapMib'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'IPI-DOT1AG-CFM-NVO3-TRAP-MIB' -M '/opt/observium/mibs/ipinfusion:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'IPI-DOT1AG-CFM-NVO3-TRAP-MIB::dot1agCfmNVO3trapMib'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (8)
.1.3.6.1.4.1.36673.121
.1.3.6.1.4.1.36673.121.0
.1.3.6.1.4.1.36673.121.1
.1.3.6.1.4.1.36673.121.1.1
.1.3.6.1.4.1.36673.121.1.2
.1.3.6.1.4.1.36673.121.1.3
Unsigned32
.1.3.6.1.4.1.36673.121.1.4
.1.3.6.1.4.1.36673.121.1.5
Dependencies (22) 5 direct · 17 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
Notifications / Traps (1)
NameOIDDescription
.1.3.6.1.4.1.36673.121.0.1
A MEP has a persistent defect condition. A notification
(fault alarm) is sent to the management entity with the OID
of the MEP that has detected the fault.

The management entity receiving the notification can identify
the system from the network source address of the
notification, and can identify the MEP reporting the defect
by the indices in the OID of the dot1agCfmMepHighestPrDefect
variable in the notification:

dot1agCfmMdIndex - Also the index of the MEP's
Maintenance Domain table entry
(dot1agCfmMdTable).
dot1agCfmMaIndex - Also an index (with the MD table index)
of the MEP's Maintenance Association
network table entry
(dot1agCfmMaNetTable), and (with the MD
table index and component ID) of the
MEP's MA component table entry
(dot1agCfmMaCompTable).
dot1agCfmMepIdentifier - MEP Identifier and final index
into the MEP table (dot1agCfmMepTable).