Configures L2VPN VPWS service over MPLS Static PW.
Specifies the VPWS for which you are configuring a peer.
Specifies the peer IP address.
Specifies the IP address of the peer node.
Specifies the static pseudowire transmit label.
Specifies the name of the egress label.
Specifies the static PW receive label.
Specifies the name of the ingress label.
Use this command to statically configure a new MPLS Ethernet PW for the specified VPWS. You must specify the outgoing (MPLS ingress) and incoming (MPLS egress) PW labels. Similarly, you must configure the peer with a static PW that has the reverse PW label mappings.
Locally, the incoming_pw_label must be unique and is allocated out of the static label space. The outgoing_pw_label must match the peer‘s configured incoming PW label.
Just like a signaled PW, a static PW can optionally be configured to use any type of tunnel LSP: LDP, RSVP-TE, or Static. In the case of RSVP-TE and LDP, those protocols must be configured and enabled and an LSP must be established before traffic can be transmitted over the static PW.
For Static LSPs, only the MPLS ingress LSP (or outgoing LSP) is specified. Unlike signaled PWs, there is no end-to-end PW communication that is used to verify that the PW endpoint is operational, and in the case of static LSPs, that the data path to the PW endpoint is viable. In the event of a network fault, if a secondary RSVP-TE LSP is configured or the routing topology changes such that there is an alternate LDP LSP, the static PW will automatically switch LSPs in order to maintain connectivity with the PW endpoint. Static LSPs can be protected proactively by configuring BFD to verify the static LSPs IP next hop connectivity. Optionally, the underlying LSP for the PW can be explicitly specified using a named LSP. When a named LSP is explicitly specified, only the specified named LSP is used to carry the PW. In the event that a specified named LSP is withdrawn, the VPLS/VPWS remains operationally down until the named LSP is restored.
Since VC Status signaling is not supported, the VC Status “standby” bit cannot be used to allow support for PW redundancy and H-VPLS. Consequently, only “core full-mesh” PWs are allowed to have statically configured labels.
The following command configures VPWS service for VPWS1 on peer 22.214.171.124:
configure vpws vpws1 add peer 126.96.36.199
This command was first available in ExtremeXOS 15.4.
This command is available on all platforms that support MPLS as described in the Switch Engine 32.3 Feature License Requirements document.