Interface And Hardware Component Configuration Guide For Cisco Ncs 5500 Series Routers, Ios Xr Release - Cisco NCS 5500 Series Configuration Manual

Configuring Ethernet OAM
• A configured numeric identifier for the MEP (the MEP ID). Each MEP in the service must be configured
with a different MEP ID.
• Dynamic Remote MEPs are not supported for MEPs with less than 1min interval. You must configure
MEP CrossCheck for all such MEPS.
• Sequence numbering is not supported for MEPs with less than 1 minute interval.
• A Remote Defect Indication (RDI). Each MEP includes this in the CCMs it is sending, if it has detected
a defect relating to the CCMs it is receiving. This notifies all the MEPs in the service that a defect has
been detected somewhere in the service.
• The interval at which CCMs are being transmitted.
• CCM Tx/Rx statistics counters are not supported for MEPs with less than1 minute intervals.
• Sender TLV and Cisco Proprietary TLVs are not supported for MEPs with less than 1min intervals.
• The status of the interface where the MEP is operating—for example, whether the interface is up, down,
STP blocked, and so on.
Note
These defects can be detected from received CCMs:
• Interval mismatch—The CCM interval in the received CCM does not match the interval that the MEP
is sending CCMs.
• Level mismatch—A MEP has received a CCM carrying a lower maintenance level than the MEPs own
level.
• Loop—A CCM is received with the source MAC address equal to the MAC address of the interface
where the MEP is operating.
• Configuration error—A CCM is received with the same MEP ID as the MEP ID configured for the
receiving MEP.
• Cross-connect—A CCM is received with an MAID that does not match the locally configured MAID.
This generally indicates a VLAN misconfiguration within the network, such that CCMs from one service
are leaking into a different service.
• Peer interface down—A CCM is received that indicates the interface on the peer is down.
• Remote defect indication—A CCM is received carrying a remote defect indication.
Note
Out-of-sequence CCMs can also be detected by monitoring the sequence number in the received CCMs from
each peer MEP. However, this is not considered a CCM defect.
The status of the interface (up/down) should not be confused with the direction of any
MEPs on the interface (Up MEPs/Down MEPs).
This defect does not cause the MEP to include a remote defect indication in the CCMs
that it is sending.
Interface and Hardware Component Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.1.x
Ethernet CFM
33