MEPs and MIPs filter CCMs from higher and lower domain levels as described in the following table.
Table 6. Continuity Check Message Processing
Frames at
Frames from
UP-MEP Action
Down-MEP Action MIP Action
Less than my level
Bridge-relay side or
Wire side
Drop
Drop
Drop
My level
Bridge-relay side
Consume
Drop
Add to MIP-DB and
forward
My level
Wire side
Drop
Consume
add to MIP-DB and
forward
Greater than my
level
Bridge-relay side or
Wire side
Forward
Forward
Forward
All the remote MEPs in the maintenance domain are defined on each MEP. Each MEP then expects a
periodic CCM from the configured list of MEPs. A connectivity failure is then defined as:
• Loss of three consecutive CCMs from any of the remote MEP, which indicates a network failure.
• Reception of a CCM with an incorrect CCM transmission interval, which indicates a configuration
error.
• Reception of a CCM with an incorrect MEP ID or MAID, which indicates a configuration or cross-
connect error. This error could happen when different VLANs are cross-connected due to a
configuration error.
• Reception of a CCM with an MD level lower than the receiving MEP, which indicates a configuration
or cross-connect error.
• Reception of a CCM containing a port status/interface status TLV, which indicates a failed bridge or
aggregated port.
The continuity check protocol sends fault notifications (Syslogs, and SNMP traps, if enabled) whenever
you encounter any of the these errors.
Enabling CCM
To enable CCM, use the following commands.
1.
Enable CCM.
ECFM DOMAIN mode
no ccm disable
The default is
Disabled
.
2.
Configure the transmit interval (mandatory). The interval specified applies to all MEPs in the domain.
ECFM DOMAIN mode
ccm transmit-interval
seconds
The default is
10 seconds
.
802.1ag
103
Summary of Contents for S4820T
Page 1: ...Dell Configuration Guide for the S4820T System 9 8 0 0 ...
Page 282: ...Dell 282 Control Plane Policing CoPP ...
Page 622: ...Figure 81 Configuring Interfaces for MSDP 622 Multicast Source Discovery Protocol MSDP ...
Page 623: ...Figure 82 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 623 ...
Page 629: ...Figure 86 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 629 ...
Page 630: ...Figure 87 MSDP Default Peer Scenario 3 630 Multicast Source Discovery Protocol MSDP ...
Page 751: ...10 11 5 2 00 00 05 00 02 04 Member Ports Te 1 2 1 PIM Source Specific Mode PIM SSM 751 ...
Page 905: ...Figure 112 Single and Double Tag First byte TPID Match Service Provider Bridging 905 ...
Page 979: ...6 Member not present 7 Member not present Stacking 979 ...
Page 981: ...storm control Storm Control 981 ...
Page 1103: ...Figure 134 Setup OSPF and Static Routes Virtual Routing and Forwarding VRF 1103 ...