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.
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.
cEtherCfmCcMepDown
.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.
cEtherCfmCcCrossconnect
.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.
cEtherCfmCcLoop
.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.
cEtherCfmCcConfigError
.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.
cEtherCfmXCheckMissing
.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.
cEtherCfmXCheckUnknown
.1.3.6.1.4.1.9.9.461.0.0.7
This notification is generated when an unexpected MEP
comes up.
cEtherCfmXCheckServiceUp
.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.