Use this command to statically configure 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.
Use these commands to statically configure a new MPLS Ethernet PW for the specified VPLS or VPWS. Both the outgoing (MPLS ingress) and incoming (MPLS egress) PW labels must be specified. You must similarly 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.
Network administrators can use this command to modify the current configuration of a PW for the specified ces_mpls_name. The incoming_pw_label must be locally unique and is allocated out of the static label space. The outgoing_pw_label can be any value and must match the peer‘s configured incoming PW label.
For CES services created for use with MPLS, the “Type: Static/Signaled” line in the CES section of the output will show “N/A” until a PW is configured, since this the PW type is not known until the peer is added to the CES. The PW section of the output includes a “PW Signaling” line that will display “LDP” or “None (Static)”, depending on the PW configuration.
Since the configured labels can be changed while the current labels are in-use, there is a small window where the configured labels and in-use labels are different. If you issue the show ces detail command during this window, an extra line is output to indicate the extra information.
The non-detail version of this command includes a peer flag that indicates the signaling protocol, if any, for a PW/peer. An “L” indicates LDP is used to signal the PW. A “T” indicates that no signaling is done, and therefore, this is a static PW.
The detail version of this command now displays a “PW Signaling” line that displays “LDP” or “None (Static)”, depending on the PW configuration. The “Local PW Status” shows “--” instead of “Not Signaled”, since the PW status is not currently signaled. For informational purposes, any local faults are still shown.
The “Remote PW Status” and “Remote I/F MTU” always show “--”.Since the configured labels can be changed while the current labels are in-use, there is a small window where the configured labels and in-use labels are different. If you issue the show l2vpn detail command during this window, an extra line is output to indicate this extra information.
This command displays the label ranges on the current running system, including configurable and non-configurable ranges. The output also includes hardware resource usage to provide a better picture about the MPLS hardware utilization and capacity.
Print
this page
Email this topic
Feedback
View PDF
Download EPUB