CISCO-ETHER-CFM-MIB

        This MIB module defines the managed objects 
and notifications for Ethernet Connectivity 
Fault Management (CFM).
        
CFM is an end-to-end per service instance Ethernet layer 
Operations, Administration and Management (OAM) protocol. 
        
CFM events include: 
        
- Maintenance End-Point (MEP) coming up: establishing 
  connectivity
        
- Maintenance End-Point going down: losing connectivity
        
- Maintenance End-Point unknown: unexpected
        
- Maintenance End-Point missing: expected but not reachable
        
- Continuity Check Configuration Error: collision in MEP IDs
        
- Continuity Check Loop: forwarding loop in network
        
- Continuity Check Cross-connect: cross-connected 
  forwarding path.
        
The following acronyms are used in this module:
        
- MEP: Maintenance End Point
        
- MEPID: Maintenance End Point Identifier
        
- CC: Continuity Check
        
- CCDB: Continuity Check Database
        
- SVLAN: Service Provider Virtual Local Area Network
        
- VLAN: Virtual Local Area Network
        
- CLI: Command Line Interface.
        
- OAM: Operations Administration and Management.
    
Source file
CISCO-ETHER-CFM-MIB
Last revised
Identity
ciscoEtherCfmMIB
Base OID
1.3.6.1.4.1.9.9.461
Imported Objects
CISCO-SMI ciscoMgmt
Q-BRIDGE-MIB VlanId
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Gauge32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC MacAddress TEXTUAL-CONVENTION (no object page) TimeStamp
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-ETHER-CFM-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-ETHER-CFM-MIB::ciscoEtherCfmMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-ETHER-CFM-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-ETHER-CFM-MIB::ciscoEtherCfmMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (28)
ciscoEtherCfmMIB.1.3.6.1.4.1.9.9.461
.1.3.6.1.4.1.9.9.461.0
.1.3.6.1.4.1.9.9.461.0.0
.1.3.6.1.4.1.9.9.461.1
.1.3.6.1.4.1.9.9.461.1.1
cEtherCfmMaxEventIndexUnsigned32.1.3.6.1.4.1.9.9.461.1.1.1
cEtherCfmEventTable.1.3.6.1.4.1.9.9.461.1.1.2
cEtherCfmEventEntry.1.3.6.1.4.1.9.9.461.1.1.2.1
cEtherCfmEventDomainIndexUnsigned32.1.3.6.1.4.1.9.9.461.1.1.2.1.1
cEtherCfmEventLclMepCountSNMPv2-SMIGauge32.1.3.6.1.4.1.9.9.461.1.1.2.1.10
cEtherCfmEventLclIfCountSNMPv2-SMIGauge32.1.3.6.1.4.1.9.9.461.1.1.2.1.11
cEtherCfmEventRmtMepidCfmMepid.1.3.6.1.4.1.9.9.461.1.1.2.1.12
cEtherCfmEventRmtMacAddressSNMPv2-TCMacAddress.1.3.6.1.4.1.9.9.461.1.1.2.1.13
cEtherCfmEventRmtPortStateEnumeration.1.3.6.1.4.1.9.9.461.1.1.2.1.14
cEtherCfmEventRmtServiceIdOctetString.1.3.6.1.4.1.9.9.461.1.1.2.1.15
cEtherCfmEventCodeEnumeration.1.3.6.1.4.1.9.9.461.1.1.2.1.16
Enumeration.1.3.6.1.4.1.9.9.461.1.1.2.1.17
cEtherCfmEventSvlanQ-BRIDGE-MIBVlanId.1.3.6.1.4.1.9.9.461.1.1.2.1.2
cEtherCfmEventIndexUnsigned32.1.3.6.1.4.1.9.9.461.1.1.2.1.3
cEtherCfmEventDomainNameSNMP-FRAMEWORK-MIBSnmpAdminString.1.3.6.1.4.1.9.9.461.1.1.2.1.4
cEtherCfmEventTypeEnumeration.1.3.6.1.4.1.9.9.461.1.1.2.1.5
cEtherCfmEventLastChangeSNMPv2-TCTimeStamp.1.3.6.1.4.1.9.9.461.1.1.2.1.6
cEtherCfmEventServiceIdOctetString.1.3.6.1.4.1.9.9.461.1.1.2.1.7
cEtherCfmEventLclMepidCfmMepid.1.3.6.1.4.1.9.9.461.1.1.2.1.8
cEtherCfmEventLclMacAddressSNMPv2-TCMacAddress.1.3.6.1.4.1.9.9.461.1.1.2.1.9
.1.3.6.1.4.1.9.9.461.2
.1.3.6.1.4.1.9.9.461.2.1
.1.3.6.1.4.1.9.9.461.2.2
Dependencies (18) 6 direct · 12 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
Type Definitions (1)
Unsigned32 range: 0..8191
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.461.2.1.1
Compliance statement for agents that support the Ethernet
CFM MIB.
Required groups
Notifications / Traps (8)
NameOIDDescription
.1.3.6.1.4.1.9.9.461.0.0.1
This notification is generated in the following cases:

- when a remote MEP first comes up, that is when we receive
a CC message from that MEP for the first time.

- when the device receives a CC message from a MEP for which
it has an expired CCDB entry.

- when a CC message is received for a remote MEP for which
the device already has a CCDB entry and the port-state in
the received CC message is different from the cached
previous state.
.1.3.6.1.4.1.9.9.461.0.0.2
This notification is generated when a remote MEP goes down;
i.e. the entry in CCDB corresponding to this MEP times out
or the device receives a CC message with zero hold-time.
.1.3.6.1.4.1.9.9.461.0.0.3
This notification is generated when a device receives a CC
message with the service ID not matching the one locally
configured for the VLAN in question.
.1.3.6.1.4.1.9.9.461.0.0.4
This notification is generated when a device receives a CC
message with the same MEPID and MAC address as those of
the device itself, indicating that there is a forwarding
loop and that the device is receiving its own CC messages.
.1.3.6.1.4.1.9.9.461.0.0.5
This notification is generated when a device receives a CC
message with the same MEPID but different MAC address as
those of the device itself, indicating that there is a
mis-configuration in the network where a remote device
has the same MEPID configured.
.1.3.6.1.4.1.9.9.461.0.0.6
This notification is generated when an expected
(configured) MEP does not come up during the cross-check
start timeout interval.
.1.3.6.1.4.1.9.9.461.0.0.7
This notification is generated when an unexpected MEP
comes up.
.1.3.6.1.4.1.9.9.461.0.0.8
This notification is generated when all the MEPs belonging
to a customer service instance come up before the expiration of
the cross-check start timeout interval.