Adds or deletes a named LSP as a specified PW for the specified Layer 2 VPN peer.
|vpls_name||Identifies the VPLS within the switch (character string).|
|vpws_name||Identifies the VPWS within the switch (character string).|
|ipaddress||Specifies the IP address for the peer node that is the endpoint of the PW-LSP. This option applies only to VPLS peers.|
|add||Permits addition of up to four RSVP-TE LSPs to the VPLS peer.|
|delete||Removes the LSP specified by the lsp_name parameter from the PW-LSP aggregation list.|
|lsp_name||Removes the specified lsp.|
If all the named LSPs are deleted from the configured Layer 2 VPN peer, VPLS or VPWS attempts to use the best-routed path LSP, if one exists. The delete portion of this command cannot be used to remove a named LSP that was selected by the switch as the best LSP. If no LSPs exist to the peer, Layer 2 VPN connectivity to the peer is lost. Currently, the VPLS or VPWS PW uses only one LSP.
The l2vpn keyword was introduced in ExtremeXOS Release 12.4 and is required when configuring a VPWS instance. For backward compatibility, the l2vpn keyword is optional when configuring a VPLS instance. However, this keyword will be required in a future release, so we recommend that you use this keyword for new configurations and scripts.
The following examples add and remove a named LSP:
configure l2vpn vpls vpls1 peer 18.104.22.168 add mpls lsp “to-olympic4" configure l2vpn vpls vpls1 peer 22.214.171.124 delete mpls lsp “to-olympic4"
The following example adds a named LSP for a VPWS peer:
configure l2vpn vpws vpws1 peer 126.96.36.199 add mpls lsp “to-olympic5"
This command was first available in ExtremeXOS 11.6.
The l2vpn and vpws keywords were first available in ExtremeXOS 12.4.
This command is available only on the platforms that support MPLS as described in the Switch Engine 32.3 Feature License Requirements document.