Types of CCM defects that have been detected.
The possible defects are:
• Remote Defect re ceived—The last CCM
received from the peer had the RDI bit set.
• Loop (our MAC received)—CCMs were
received from a peer with the same MAC
address as the local MEP.
• Config (our ID received)—CCMs were received
from a peer with the same MEP ID as the local
MEP.
• Cross-connect (wrong MAID)—The last CCM
received from the peer contained a
domain/service identified that did not match the
locally configured domain/service identifier.
• Peer port down—The last CCM received from
the peer contained an Interface Status indicating
that the interface on the peer was not up.
• Wrong interval—The last CCM received
contained a CCM interval that did not match
the locally configured CCM interval.
• Wrong level—The last CCM received was for
a lower level than the level of the local MEP.
• Timed out—No CCMs have been received
within the loss time.
• Missing (cross-check)—Cross-check is
configured and lists this peer MEP, but no
CCMs have been received within the loss time.
• Unexpected (cross-check)—Cross check is
configured for this service and does not list this
peer MEP, but CCMs have been received from
it within the loss time.
CCM defects detected
Number of CCMs received in total, by defect type.CCMs received
How long ago the last CCM was received, and a full
decode of its contents. Any unknown TLVs are
displayed in hexadecimal.
Last CCM received
Offload status of received CCM handling.Offload status
Cisco ASR 9000 Series Aggregation Services Router Interface and Hardware Component Command Reference,
Release 5.3.x
344
Ethernet OAM Commands on the Cisco ASR 9000 Series Router
show ethernet cfm peer meps
To Next Page
Loading...
Need help?
General
