Ethernet-CFM redundancy

Ethernet-CFM redundancy description

When you configure Ethernet-CFM redundancy, you can link MEPs to the state of the resiliency mechanism that is supported in MC-LAGs. The state of the MEP does not affect the state of resiliency mechanism.

Ethernet-CFM redundancy is configured at the NE level. When you configure Ethernet-CFM redundancy, the state of a MEP is the same as the state of the SAP, LAG, or MC-LAG with which it is associated. For example, if the redundant MC-LAG is in standby state, the MEP is also in standby state. When a MEP is in standby state, the MEP is idle, CCMs are not exchanged, and the MEP does not respond to CFM tests.

Note: The MEP, SAP, and LAG must reside within an MC-LAG that has Ethernet-CFM redundancy configured. See To create an MC LAG group to configure MC-LAGs.

When Ethernet-CFM redundancy is configured and the active state of an MC-LAG changes, the MC-LAG Inactive state on the MEP changes and any defects on the MEP are flagged.

The state of MEPs, SAPs, and LAGs that are configured for Ethernet-CFM redundancy appears in the MC-LAG Inactive field. The status of MC-LAGs that are configured for Ethernet-CFM redundancy appears in the Is Active field.

In addition to configuring Ethernet-CFM redundancy at the NE level, you can configure Ethernet-CFM redundancy on tunnel MEPs. See To modify NE properties to configure Ethernet-CFM redundancy at the NE level. See To modify a LAG to configure Ethernet-CFM redundancy on a tunnel MEP.