Configures a VPLS, H-VPLS, or VPWS peer for the node you are configuring.
|vpls_name||Specifies the VPLS for which you are configuring a peer.|
|vpws_name||Specifies the VPWS for which you are configuring a peer.|
|ipaddress||Specifies the IP address of the peer node.|
|core||Specifies that the peer is a core node. This option applies only to VPLS peers.|
|full-mesh||Specifies that the peer is a core full-mesh node. This is the default setting if neither the core or spoke options are specified. This option applies only to VPLS peers.|
|primary||Specifies that the peer is an H-VPLS core node and configures a primary H-VPLS connection to that core node. This option applies only to H-VPLS peers.|
|secondary||Specifies that the peer is an H-VPLS core node and configures a secondary H-VPLS connection to that core node. This option applies only to H-VPLS peers.|
|spoke||Specifies that the peer is a H-VPLS spoke node. This option applies only to H-VPLS peers.|
Each VPLS or H-VPLS node supports up to 64 peers, and each VPWS supports one peer. H-VPLS core nodes can peer with other core nodes and/or spoke nodes. H-VPLS spoke nodes can peer with core nodes but not with other spoke nodes.
VPLS core nodes must be configured in a full-mesh with other core nodes. Thus, all core nodes in the VPLS must have a configured PW to every other core node serving this VPLS. By default, the best LSP is chosen for the PW. The underlying LSP used by the PW can be configured by specifying the named LSP using the CLI command configure l2vpn [vpls vpls_name | vpwsvpws_name] peeripaddress [add | delete] mpls lsplsp_name.
H-VPLS spoke nodes establish up to two point-to-point connections to peer with core nodes. If both primary and secondary peers are defined for a spoke node, the spoke node uses one of the peers for all communications. If both peers are available, the spoke node uses the connection to the primary peer. If the primary peer connection fails, the spoke node uses the secondary peer. If the primary peer later recovers, the spoke node reverts back to using the primary peer.
VPWS nodes establish a point-to-point connection to one peer.
The l2vpn keyword was introduced in ExtremeXOS Release 12.4 and is required when configuring a VPWS peer. For backward compatibility, the l2vpn keyword is optional when configuring a VPLS peer. 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 command adds a connection from the local core switch to the core switch at 184.108.40.206:
configure l2vpn vpls vpls1 add peer 220.127.116.11
The following command adds a connection from the local core switch to the spoke switch at 18.104.22.168:
configure l2vpn vpls vpls1 add peer 22.214.171.124 spoke
The following command adds a primary connection from the local spoke switch to the core switch at 126.96.36.199:
configure l2vpn vpls vpls1 add peer 188.8.131.52 core primary
The following command adds a VPWS connection from the local node to the peer switch at 184.108.40.206:
configure l2vpn vpws vpws1 add peer 220.127.116.11
This command was first available in ExtremeXOS 11.6.
Support for H-VPLS was first available in ExtremeXOS 12.1.
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.2 Feature License Requirements document.