NoteThis command has been replaced with the following command: . This command is still supported for backward compatibility, but it will be removed from a future release, so we recommend that you start using the new command.
Configures a VPLS or H-VPLS peer for the node you are configuring.
|vpls_name||Specifies the VPLS 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.|
|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.|
|primary||Specifies that the peer is an H-VPLS core node and configures a primary H-VPLS connection to that core node.|
|secondary||Specifies that the peer is an H-VPLS core node and configures a secondary H-VPLS connection to that core node.|
|spoke||Specifies that the peer is a H-VPLS spoke node.|
Up to 32 core nodes can be configured for each VPLS. H-VPLS spoke nodes can peer with core nodes. Nodes can belong to multiple VPLS instances. The ipaddress parameter identifies the VPLS node that is the endpoint of the VPLS PW.
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 .
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.
The following command adds a connection from the local core switch to the core switch at 22.214.171.124:
configure vpls vpls1 add peer 126.96.36.199
The following command adds a connection from the local core switch to the spoke switch at 188.8.131.52:
configure vpls vpls1 add peer 184.108.40.206 spoke
The following command adds a primary connection from the local spoke switch to the core switch at 220.127.116.11:
configure vpls vpls1 add peer 18.104.22.168 core primary
This command was first available in ExtremeXOS 11.6.
Support for H-VPLS was first available in ExtremeXOS 12.1.
This command is available only on the platforms that support MPLS as described in the Switch Engine 32.2 Feature License Requirements document.