ETH-CSF considerations and limitations

• Hitless failover is not supported.
• ETH-CSF can be supported only with Down MEPs for point-to-point Ethernet applications. MEPs should be in the Up state and not in a faulty or failed state.
• ETH-CSF frames are transmitted only when the Down MEP (both source and remote) is in the Up state and the transmissions cease case of a MEP failure.
• A client port that is associated with a Down MEP can be either a physical interface or a port-channel interface. No other type of interface is supported.
• There can be only one physical or port-channel interface that is associated with an Down MEP. It is not allowed to associate a physical interface that is already a port-channel member as a client port to an Down MEP. No two physical or port-channel interfaces can be associated with a single Down MEP.
• All available physical interfaces on a device can be associated as client ports to different Down MEPs with a one-to-one mapping.
• When a client interface is configured with a port-channel interface, the timeout before RMEP sends C-LOS messages back to the MEP when its client interface link is down is 3.5 times the configured tx-interval.

Note

Because 8 k MEPs can be created on the device, practically all of the available client ports can be associated with different MEPs with a one-to-one mapping. Therefore, the scale is the same as that for the number of MEPs that can be created.