EasyManua.ls Logo

Extreme Networks ExtremeWare - Configure Mpls Vpls Add Peer

Extreme Networks ExtremeWare
2254 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
configure mpls vpls add peer
ExtremeWare Software 7.3.0 Command Reference Guide 1817
configure mpls vpls add peer
config mpls vpls <vpls_name> add peer [<ipaddress> | <host_name>]
[core-to-core | spoke-to-core {primary | secondary} | core-to-spoke {vpls |
tls {vcid <vcid>} {dot1q ethertype <hex_number>}] {lsp <lsp_name>}
Description
Configures a VPLS peer for the specified vpls_name.
Syntax Description
Default
N/A.
Usage Guidelines
This command configures a VPLS peer for the specified vpls_name. Up to 32 peers may be configured
for each VPLS. Peers may belong to multiple VPLS instances. The
ipaddress
parameter identifies the
peer node that is the endpoint of the VC-LSP. The ipaddress should be configured with a 32-bit prefix
on the peer node. When the peer node is also an Extreme switch, then either OSPF/ISIS must also be
enabled on the VLAN that the ipaddress is assigned, or the peer switch must be configured to distribute
direct routes into the OSPF/ISIS domain. Note that the export command should be used when the
tunnel LSP needs to cross OSPF area boundaries or when ESRP is enabled on the VLAN that the
ipaddress is assigned. If the VPLS peer is specified using the
host_name
parameter, the DNS client
must be configured so that the host_name can first be resolved to an IP address.
Per node, each peer relationship for each VPLS must be configured. The peer relationships are defined
as either a core-to-core, core-to-spoke, or spoke-to-core. This relationship implicitly defines the packet
flooding behavior for the VC-LSP set up to the configured peer.
A VPLS peer relationship defined as
core-to-core
indicates that the peer is a member of a fully
meshed VPLS core peer group. Flood traffic received from a core node by the core node is forwarded to
spoke nodes only.
A VPLS peer relationship defined as
spoke-to-core
specifies the spoke connectivity from a spoke
node to a core node. Flood traffic received by a spoke node from a core node is forwarded to the local
egress interface. The
spoke-to-core
keyword may optionally be qualified with the redundant
configuration mode. The core node is either the primary or secondary VPLS peer. One primary core
vpls_name Identifies the VPLS within the switch (character string)
ipaddress Specifies the IP address for the peer node that is the endpoint of the VC-LSP
host_name Specifices the peer host name.
core-to-core Specifies the VPLS peer relationship which represents a member of a fully
meshed VPLS core peer group.
spoke-to-core Specifies the spoke connectivity from a spoke node to a core node.
core-to-spoke Specifies the spoke connectivity from the core node to the spoke node.
vcid Specifies an option for VC-LSP between the core and spoke.
tps Specifies an option for VC-LSP between the core and spoke.
hex_number Specifies the ethertype for dot1q

Table of Contents

Related product manuals