Endpoint X is operationally up if at least one of its objects is operationally up. It is down if all of its objects are operationally down.
If the SAP in endpoint X transitions locally to the down state or received a SAP down notification by the SAP-specific OAM signal, the node must send T-LDP SAP down status bits on the Y endpoint ICB spoke-SDP only. Ethernet SAP does not support SAP OAM protocol. All other SAP types cannot exist on the same endpoint as an ICB spoke-SDP because a non-Ethernet SAP cannot be part of an MC-LAG instance.
If the ICB spoke-SDP in endpoint X transitions locally to down state, the node must send T-LDP SDP-binding down status bits on this spoke-SDP.
If the ICB spoke-SDP in endpoint X receives T-LDP SDP-binding down status bits or pseudowire not forwarding status bits, the node saves this status and takes no further action. The saved status is used for active transmit endpoint object selection.
If all objects in endpoint X perform any or all of the following operations, the node must send status bits of SAP down over all ‟Y” endpoint spoke-SDPs, including the ICB:
transitioned locally to down state
received a SAP down notification by remote T-LDP status bits or by SAP-specific OAM signal
received SDP-binding down status bits
received PW not forwarding status bits
Endpoint Y is operationally up if at least one of its objects is operationally up. It is down if all its objects are operationally down.
If a spoke-SDP in endpoint Y, including the ICB spoke-SDP, transitions locally to down state, the node must send T-LDP SDP-binding down status bits on this spoke-SDP.
If a spoke-SDP in endpoint Y, including the ICB spoke-SDP, performed any or all of the following operations, the node saves this status and takes no further action:
received T-LDP SAP down status bits
received T-LDP SDP-binding down status bits
received PW not forwarding status bits
The saved status is used for selecting the active transmit endpoint object.
If all objects in endpoint Y, except the ICB spoke-SDP, performed any or all of the following operations, the node must send status bits of SDP-binding down over the X endpoint ICB spoke-SDP only:
transitioned locally to the down state
received T-LDP SAP down status bits
received T-LDP SDP-binding down status bits
received PW not forwarding status bits
If all objects in endpoint Y performed any or all of the following operations, he node must send status bits of SDP-binding down over the X endpoint ICB spoke-SDP, and must send a SAP down notification on the X endpoint SAP by the SAP-specific OAM signal if applicable:
transitioned locally to down state
received T-LDP SAP down status bits
received T-LDP SDP-binding down status bits
received PW not forwarding status bits
An Ethernet SAP does not support signaling status notifications.