FPE-Based PW-port Operational State

The FPE-based PW-port operational state is driven by the ability of the stitching service (see the following notes) to forward traffic. This includes the stitching service’s operational status and, if the external PW is TLDP signaled, the PW status bits. The operational flag for a non-operational PW-port is set to stitchingSvcTxDown.

Transitioning of the PW-port into down state because of a PXC failure (for example, physical port fails), brings the stitching service down with the following result:

In case of TLDP-signaled PW, the psnIngressFault and psnEgressFault PW status bits is propagated to the remote end, indicating that the local stitching service is down.
In case of EVPN, the EVPN route is withdrawn, indicating that the local stitching service is down.
In case of BGP-VPWS, the BGP-VPWS the ‛D’ bit of the Layer 2 Information Extended Community flag field is set, indicating that the local stitching service is down.

Note:

The stitching service in this context is an Epipe service in vc-switching mode for BGP-VPWS or TLDP signaled PW, as follows:

configure
      service epipe <epipe-id> customer <cust-id> vc-switching [create]
            pw-port <pw-port-id> fpe <fpe-id>
            spoke-sdp <sdp-id:vc-id> [create]
                  or 
            bgp-vpws
                  :

Note:

The stitching service in this context is an Epipe service in a non-vc-switching mode for EVPN, as follows:

configure
      service epipe <epipe-id> customer <cust-id> create
            pw-port <pw-port-id> fpe <fpe-id>
            bgp-evpn
                  :