Statically configures a new MPLS TDM PW for the specified CES.
| ces_name |
Specifies the circuit emulation service (CES). |
| ipaddress |
Specifies an IP address. |
| fec-id-type pseudo-wire |
Defines the FEC ID type for this peer. |
| pw_id |
Specifies the pseudowire ID. |
| static-pw |
Specifies that the transmit and receive labels are going to be statically configured. |
| transmit-label |
Specifies the static pseudowire transmit label. |
| outgoing_pw_label |
Specifies the outgoing static label. The outgoing_pw_label must match the peer‘s configured incoming PW label. |
| receive-label |
Specifies the label that you apply to the static PW on egress . |
| incoming_pw_label |
Specifies the egress label. |
| lsp |
Specifies the Label Switch Path through the network. |
| lsp_name |
Specifies the name of the LSP. |
N/A.
This command statically configures a new MPLS TDM PW for the specified CES. Both the outgoing (MPLS ingress) and incoming (MPLS egress) PW labels must be specified. The peer must be similarly configured 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.
Optionally, you can configure the PW 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 CES remains operationally down until the named LSP is restored.
The following command adds a static pseudowire to:
configure iproute add 10.1.1.0/24 lsp lsp598
This command was first available in ExtremeXOS 15.4.
This command is available on the E4G-200 and E4G-400 platforms.
Print
this page
Email this topic
Feedback
View PDF
Download EPUB