The following restrictions apply for fault propagation:
This feature is supported only on the 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C.
This feature is supported only for an Epipe service. It is not supported for a VPLS or R-VPLS service.
The Epipe service can be configured with two access SAPs, or two access-uplink SAPs, or one access SAP and one access-uplink SAP. SDP bindings (spoke-SDP) are not supported:
On the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C, the SAPs in the Epipe service can be configured on access, access-uplink, or hybrid ports or LAGs.
On the 7210 SAS-Dxp and 7210 SAS-K 2F1C2T, the SAPs in the Epipe service can be configured on access or access-uplink ports or LAGs.
All supported encapsulation can be used with access, access-uplink, and hybrid ports. That is, unlike LLF, which provides similar capability but only for null SAPs, this feature is not restricted to only null-encapsulated ports.
A MEP (Up or Down) with defect-oper-group enabled can be configured on one of the SAPs of the Epipe service:
The Down MEP, which is used to track service uplink connectivity, must be configured on a different port, and not the port to which the fault is propagated. That is, the Down MEP with defect-oper-group configured and the port with monitor-oper-group configured must not be the same.
The Up MEP used to track service uplink connectivity must be configured on the same port to which the fault is propagated. That is, the Up MEP with defect-oper-group configured and the port with the monitor-oper-group configured must be the same. In this case, it is mandatory for the user to enable config>service>epipe>sap>ignore-oper-down so that the Up MEP can continue to process the CFM messages received from the remote end. When an Up MEP is used, the fault must not be propagated to the other local endpoint in an Epipe service because it is likely to block all communications with the remote endpoint of an Epipe service.
The defect-oper-group configuration can only track the fault state of a single MEP. Multiple MEPs are not supported. Consequently, only a single uplink can be tracked in an Epipe service.
The monitor-oper-group command can be configured on any port or LAG other than the one on which the CFM defect-oper-group command is configured. It does not need to be restricted to the port or LAG that has a SAP configured in the same Epipe service, even though this is the most common use case. Allowing the configuration of the monitor-oper-group command on any port allows the user to have one service to track multiple services between the same two endpoints and propagate the fault to all the service ports that use the same uplink or path for service connectivity to the same remote endpoint.