SR Vpls

Chapter 16
VPLS Configuration
This chapter provides an overview of Virtual Private LAN Services (VPLS) and describes the tasks and
commands used to configure VPLS features through the SmartEdge® OS.
For information about the tasks and commands used to monitor, troubleshoot, and administer VPLS, see
the “VPLS Operations” chapter in the Routing Protocols Operations Guide for the SmartEdge OS.
This chapter includes the following sections:
• Overview
• Configuration Tasks
• Configuration Examples
• Command Descriptions
Overview
VPLS enables networks at separate geographical locations to communicate with each other across a WAN
as if they were directly attached to each other in a LAN. The WAN becomes transparent, which is achieved
by creating VPLS pseudo-wires.
A pseudo-wire is a mechanism that emulates the attributes and function of Ethernet connectivity over a
WAN. Any required switching functionality or service translation is outside the scope of the pseudo-wire
and of the transport network. Pseudo-wires are carried over Multiprotocol Label Switching (MPLS) tunnels
on the network.
MPLS signaling protocols are used to automatically provision a service on a pseudo-wire end-to-end, so
you can provision a pseudo-wire by pointing to its two endpoints, and MPLS automatically negotiates the
path.
VPLS Configuration 16-1

Configuration Tasks
Figure 16-1 displays the network topology for a typical VPLS configuration.
Figure 16-1 Typical VPLS Network Topology
Customer edge (CE) routers, which are on the edge of geographically separate customer networks, are
connected by Ethernet to provider edge (PE) routers on an MPLS provider network. A pseudo-wire is
established for each pair of CE routers that are to be connected into a virtual private LAN. For example,
the PW1 pseudo-wire is used to connect the CE1 and CE3 routers, and the PW2 pseudo-wire is used to
connect the CE2 and CE4 routers.
To create pseudo-wires, a VPLS-enabled bridge must first be configured on each PE router, and then
peering (neighbor) sessions can be established across that bridge. The pseudo-wire is the circuit across
which the peering session occurs. A VPLS-enabled bridge can have multiple peering sessions.
Configuration Tasks
Note In this section, the command syntax in the task tables displays only the root command; for the
complete command syntax, see the full description for the command in the “Command
Descriptions” section.
Before VPLS can be configured, the following conditions must be met:

• MPLS core backbone configuration is up and running.
For more information on configuring MPLS, see Chapter 13, “MPLS Configuration.”
• Label Distribution Protocol (LDP) targeted discovery has been enabled between PE peers.
For more information on configuring LDP targeted discovery, see the “Targeted LDP” section in
Chapter 15, “LDP Configuration.”
To configure VPLS, perform the tasks described in the following sections:
• Configuring a Bridge Profile
• Configuring a VPLS Profile
• Configuring a VPLS-Enabled Bridge
16-2 Routing Protocols Configuration Guide

Configuration Tasks
Configuring a Bridge Profile

You can assign a named bridge profile to a neighbor. When the subscriber circuit is bound to a bridged
interface, the attribute values in the named bridge profile assigned to the neighbor override those in the
default bridge profile for the circuit, unless the circuit is also assigned a named bridge profile.
To configure a bridge profile, perform the tasks described in Table 16-1. Enter all commands in bridge
profile configuration mode, unless otherwise noted. For more information about the commands used to
configure a bridge profile, see the “Bridging Configuration” chapter in the Ports, Circuits, and Tunnels
Configuration Guide for the SmartEdge OS.
Table 16-1 Configure a Bridge Profile
Task Root Command Notes
Create a named or default bridge profile and access bridge profile Enter this command in global configuration mode.
bridge profile configuration mode.
Set the rate and burst tolerance for broadcast traffic broadcast rate-limit
on any VPLS pseudo-wire circuit to which you
assign this bridge profile.
Specify the maximum number of medium access mac-limit

control (MAC) addresses for the VPLS pseudo-wire
circuit to which you assign this bridge profile.
Set the rate and burst tolerance for multicast traffic multicast rate-limit
on any VPLS pseudo-wire circuit to which you
assign this bridge profile.
Set the rate and burst tolerance for traffic to unknown-dest rate-limit
unknown destinations on any VPLS pseudo-wire
circuit to which you assign this bridge profile.
Configuring a VPLS Profile

A VPLS profile contains one or more neighbors, with each neighbor defining the attributes necessary to
establish a separate peer instance (pseudo-wire) to a remote PE device. When a VPLS profile is assigned
to a VPLS-enabled bridge, the bridge uses the neighbors in the profile to establish the peer instances and
enable bridging over the pseudo-wires.
To configure a VPLS profile (with one or more neighbors), perform the tasks described in Table 16-2. Enter
all commands in VPLS profile neighbor configuration mode, unless otherwise noted.
Table 16-2 Configure a VPLS Profile
Create a new VPLS profile, or select an existing vpls profile Enter this command in global configuration mode.
one for modification, and enter VPLS profile VPSL profiles are used to configure one or more
configuration mode. neighbors to which a VPLS instance can establish peering
connections. All neighbors configured within a VPLS
profile are referenced by the VPLS profile name. The
VPLS profile name is unique in the system.
The VPLS profile is referenced from the VPLS instance
configuration. Multiple VPLS instances can apply (share)
the same VPLS profile. If a profile is updated then all
instances of its usage use the changed attributes.
Conflicts arising due the updated VPLS profile in the
VPLS instances does not result in rejecting the VPLS
profile or the updates; the individual VPLS instances
handle these conditions.

Configuration Tasks
Table 16-2 Configure a VPLS Profile (continued)
Create a new neighbor, or select an existing one for neighbor Enter this command in VPLS profile configuration mode.
modification, and enter VPLS profile neighbor The neighbor is identified by the IP address of the remote
configuration mode. PE device. It is used along with the pseudo-wire ID from
the VPLS instance configuration to establish a
pseudo-wire between the local and remote PE devices.
Multiple peering sessions (created by VPLS profiles) can
be established to the same PE device; different profiles
can reference the same remote PE IP address.
Assign an existing named bridge profile to the bridge profile For more information about this command, see the
neighbor. “Bridging Configuration” chapter in the Ports, Circuits, and
Tunnels Configuration Guide for the SmartEdge OS.
Enable circuit statistics for VPLS circuits. counters When enabled, packet receive and transmit statistics are
collected for each pseudo-wire circuit associated with this
neighbor.
Use the no form of this command to disable circuit
statistics for VPLS circuits.
Associate a description with the neighbor. description This command does not affect the neighbor, but is used
only as a note in the configuration. The neighbor is
identified by the IP address of the remote PE device.
Set the local mode of operation for the neighbor local-mode This command applies only if a spoke connection type is
connection. configured for the neighbor. With a spoke connection type,
one end of the connection must be set to MTU-s mode
and the other must be set to PE-rs mode.
For proper VPLS operation ensure that the local mode at
both ends is set correctly.
Configure a native virtual LAN (VLAN) tag for native-vlan-tag The native VLAN tag value is configurable on the
transporting untagged 802.1Q permanent virtual SmartEdge OS to enable interoperability with the native
circuit (PVC) traffic across a pseudo-wire. VLAN tag used by other devices in the network.
When the native VLAN tag is configured for a pseudo-wire
instance:
1. All untagged ingress packets are prepended with the
configured native VLAN tag.
2. All ingress packets with a VLAN tag value of 0 have
that tag value re-written to the configured native VLAN
tag value. The original dot1q bits are not preserved.
3. At egress, when a packet is received over a
pseudo-wire, the VLAN tag is removed if its value
matches the native VLAN tag value associated with
the pseudo-wire. If the pseudo-wire is configured with
a different native VLAN tag value, or is not configured,
then the packet retains its VLAN tag.
Only one native VLAN tag per pseudo-wire is supported.
Set the connection type used between the local and pe-type Currently, hub and spoke connection types are supported.
remote PE devices. For proper VPLS peering, both ends of the peer must be
configured with the same connection type.
Specify the pseudo-wire encapsulation type. pw-encap Ethernet or Ethernet VLAN encapsulation can be
specified.

Configuration Tasks
Table 16-2 Configure a VPLS Profile (continued)
Configure pseudo-wire labels for a static pw-label When the pseudo-wire labels are configured, the
pseudo-wire. pseudo-wire is not signaled using a targeted LDP session
to the neighbor. Instead, a static mapping for the
pseudo-wire is created using the specified pseudo-wire
labels. A pseudo-wire label can be used only once. Trying
to configure a pseudo-wire label that is already in use
causes the pw-label command to be rejected.
Pseudo-wire labels must be configured on both ends of
the VPLS peering session for the static pseudo-wire to
operate properly.
Static pseudo-wires (inner tunnels) can be configured in
either static or signalled outer tunnels, including static,
LDP and RSVP LSPs and GRE tunnels.
When the outer tunnel is broken or when no next hop to
the peer exists, the static pseudo-wire is marked down,
and a standby pseudo-wire is used if it has been
configured.
MAC flush TLVs sent using the clear vpls mac-flush
command (in exec mode) can be sent over both signaled
and static pseudo-wires.
Use the no form of this command to delete the
pseudo-wire labels.
Enable a neighbor as a standby neighbor for a standby-for A neighbor can serve as a standby for only one primary
primary neighbor. neighbor. This method of configuring a standby neighbor
to reference a primary neighbor allows for establishing the
primary and standby pseudo-wires using independent
sets of attributes.
Before a standby neighbor can be enabled, the following
conditions must be met:
• A spoke connection type must be set for the neighbor.
• Local mode must be set to MTU-s.
• No other standby neighbor in the VPLS profile can
reference the same primary neighbor IP address.
Configuring a VPLS-Enabled Bridge

A VPLS-enabled bridge is used to establish peer instances to neighbors.
To configure a VPLS-enabled bridge, perform the tasks described in Table 16-3. Enter all commands in
VPLS configuration mode, unless otherwise noted.
Table 16-3 Configure a VPLS-Enabled Bridge
Create a bridge or select one for modification and bridge Enter this command in context configuration mode.
enter bridge configuration mode. For more information about this command, see the
“Bridging Configuration” chapter in the Ports, Circuits, and
Tunnels Configuration Guide for the SmartEdge OS.
Enable VPLS on a bridge and enter VPLS vpls Enter this command in bridge configuration mode.
configuration mode.
Disable the operation of an enabled VPLS instance. disable If the VPLS instance has been disabled, you can use the
no form of this command to enable it.

Configuration Examples
Table 16-3 Configure a VPLS-Enabled Bridge (continued)
Apply an existing VPLS profile to a VPLS instance. profile When a VPLS profile is applied, a VPLS peer instance is
created for each neighbor defined in the profile, and a
pseudo-wire connection is established using the attributes
defined for the neighbor.
A VPLS profile must be configured using the vpls profile
command (in global configuration mode) before it can be
applied.
Multiple VPLS profiles can be applied to the same VPLS
instance. If two or more profiles reference the same
neighbor (same IP address), then the neighbor from the
first profile is used. The same profile cannot be applied
multiple times even if the pseudo-wire IDs are different.
Configure a default pseudo-wire number for use pw-id The default pseudo-wire number is used for VPLS profiles
with all the pseudo-wires signaled by the VPLS that do not have a pseudo-wire ID (number or name)
instance. specified.
Remote PE devices use the pseudo-wire ID and the local
IP address to identify the pseudo-wire and the associated
VPLS instance.
A VPLS instance can have only one default pseudo-wire
ID, either a number or a name. If a default pseudo-wire ID
(name or number) has been configured for a VPLS
instance and a new one is configured, the previous
pseudo-wire ID is replaced with the new one.
Configure a default pseudo-wire name for use with pw-name The default pseudo-wire name is used for VPLS profiles
all the pseudo-wires signaled by the VPLS instance. that do not have a pseudo-wire ID (number or name)
specified.
Remote PE devices use the pseudo-wire ID and the local
IP address to identify the pseudo-wire and the associated
VPLS instance.
A VPLS instance can have only one default pseudo-wire
ID, either a number or a name. If a default pseudo-wire ID
(name or number) has been configured for a VPLS
instance and a new one is configured, the previous
pseudo-wire ID is replaced with the new one.
The VPLS configuration examples assume that the following conditions are true:
• MPLS core backbone configuration is up and running.
For more information on configuring MPLS, see Chapter 13, “MPLS Configuration.”
• LDP targeted discovery has been enabled between PE peers.
For more information on configuring LDP targeted discovery, see the “Targeted LDP” section in
Chapter 15, “LDP Configuration.”
The following configuration example creates a VPLS bridge to two VPLS neighbors. This configuration is
broken down into the following sections:
• Bridge Profile
• VPLS Profile
• VPLS-Enabled Bridge

Bridge Profile
The following configuration example creates two bridge profiles, 100Mbps-bc and 120Mbps-mc. The
100Mbps-bc bridge profile sets a rate limit of 125 Mbps (12,500 kbps) for broadcast traffic on the
VPLS pseudo-wire circuit to which this bridge profile is assigned. The 120Mbps-mc bridge profile sets a
rate limit of 150 Mbps (15,000 kbps) for multicast traffic on the VPLS pseudo-wire circuit to which this
bridge profile is assigned. The attributes of these bridge profiles will be applied to VPLS neighbor
configurations.
[local]Redback#config
[local]Redback(config)#bridge profile 100Mbps-bc
[local]Redback(config-bridge-profile)#broadcast rate-limit 12500000
[local]Redback(configb-bridge-profile)#exit
[local]Redback(config)#bridge profile 120Mbps-mc
[local]Redback(config-bridge-profile)#multicast rate-limit 15000000
[local]Redback(config-bridge-profile)#end
VPLS Profile
The following configuration example creates a VPLS profile, vprofile1, and two neighbors,
64.10.192.112 and 110.32.164.5. The attributes from the bridge profile, 100Mbps-bc, are applied
to the neighbor given the description, dallas-to-nyc. The attributes from the bridge profile,
120Mbps-mc, are applied to the neighbor given the description, dallas-to-sfo. The neighbor
attributes in this bridge profile will be applied to VPLS-enabled bridge instance.
[local]Redback(config)#vpls profile vprofile1
[local]Redback(config-vpls-profile)#neighbor 64.10.192.112
[local]Redback(config-vpls-profile-neighbor)#description dallas-to-nyc
[local]Redback(config-vpls-profile-neighbor)#bridge-profile 100Mbps-bc
[local]Redback(config-vpls-profile-neighbor)#exit
[local]Redback(config-vpls-profile-neighbor)#description dallas-to-sfo
[local]Redback(config-vpls-profile-neighbor)#bridge-profile 120Mbps-mc
[local]Redback(config-vpls-profile-neighbor)#end
VPLS-Enabled Bridge
The following configuration example creates a VPLS-enabled bridge instance, truecom.net, configures
a default pseudo-wire number, 100, for this instance, and applies the attributes from the VPLS profile,
vprofile1, to this instance.
[local]Redback(config)#context local
[local]Redback(config-ctx)#bridge truecom.net
[local]Redback(config-bridge)#vpls
[local]Redback(config-vpls)#pw-id 100
[local]Redback(config-vpls)#profile vprofile1
[local]Redback(config-vpls)#end

Command Descriptions
This section describes the syntax and usage guidelines for the commands used to configure VPLS features.
The commands are presented in alphabetical order.
counters pw-encap
description pw-id
disable pw-label
local-mode pw-name
native-vlan-tag standby-for
neighbor vpls
pe-type vpls profile
profile

counters
counters
no counters
Purpose
Enables circuit statistics for Virtual Private LAN Services (VPLS) circuits.
Command Mode
VPLS profile neighbor configuration
Syntax Description
This command has no keywords or arguments.
Default
VPLS pseudo-wire circuit counters are disabled.
Usage Guidelines
Use the counters command to enable circuit statistics for VPLS circuits.
When enabled, packet receive and transmit statistics are collected for each pseudo-wire circuit associated
with this neighbor.
Use the show circuit counters vpls command (in any mode) to display packet counter information for
VPLS circuits. For more information about the show circuit counters vpls command, see the “VPLS
Operations” chapter in the Routing Protocols Operations Guide for the SmartEdge OS.
Use the no form of this command to disable circuit statistics for VPLS circuits.
Examples
The following example enables circuit statistics for VPLS circuits:
[local]Redback(config)#vpls profile foo
[local]Redback(config-vpls-profile-neighbor)#counters
[local]Redback(config-vpls-profile-neighbor)#
Related Commands
description pe-type
local-mode pw-encap
neighbor

description
description text
no description
Purpose
Associates a description with a neighbor.
Command Mode
Syntax Description
text Description of the neighbor (63 characters maximum).
Default
None
Usage Guidelines
Use the description command to associate a description with a neighbor. This command does not affect
the neighbor, but is used only as a note in the configuration.
Note The neighbor is identified by the IP address of the remote provider edge (PE) device.
Use the no form of this command to remove a description from the neighbor. Because there can be only
one description for a neighbor, when you use the no form of this command, it is not necessary to include
the text argument.
Examples
The following example provides the description, test-peer, for the neighbor, 10.10.10.1:
[local]Redback(config-vpls-profile-neighbor)#description test-peer
Related Commands
counters pe-type
local-mode pw-encap
neighbor

disable
disable
no disable
Purpose
Disables the operation of an enabled Virtual Private LAN Services (VPLS) instance.
Command Mode
VPLS configuration
Syntax Description
Default
VPLS instances are enabled.
Usage Guidelines
Use the disable command to disable the operation of an enabled VPLS instance. When the VPLS instance
is disabled, the following actions occur:
• The bridge continues to learn medium access control (MAC) addresses and forwards traffic on all the
associated bridge circuits.
• All pseudo-circuits associated with the pseudo-wires are marked down.
Use the no form of this command to enable a previously disabled VPLS instance.
Examples
The following example disables the VPLS instance on the to-pe4 bridge:
[local]Redback(config-ctx)#bridge to-pe4
[local]Redback(config-vpls)#disable
[local]Redback(config-vpls)#
The following example enables the previously disabled VPLS instance on the to-pe4 bridge:
[local]Redback(config-vpls)#no disable

Related Commands
profile
pw-id
pw-name
vpls

local-mode
local-mode {mtu-s | pe-rs}
{no | default} local-mode
Purpose
Sets the local mode of operation for the neighbor connection.
Command Mode
Syntax Description
mtu-s Sets the local mode to multitenant unit switch (MTU-s). This mode is used
when the local router is participating in hierarchical Virtual Private LAN
Services (VPLS) by using a pseudo-wire connected to a core provider edge
routers (PE-rs) device, and when the local VPLS instance does not have a
mesh of pseudo-wire to all the core PE devices.
pe-rs Sets the local mode to PE-rs. This mode is used at a core VPLS PE device
that is providing hierarchical VPLS connectivity to other MTU-s routers.
Default
The PE-rs mode is set.
Usage Guidelines
Use the local-mode command to set the local mode of operation for the neighbor connection. This
command applies only if a spoke connection type is configured for the neighbor. With a spoke connection
type, one end of the connection must be set to MTU-s mode and the other must be set to PE-rs mode.
Note For proper VPLS operation, ensure that the local mode at both ends is set correctly.
Use the no or default form of this command to return the local mode of operation to PE-rs.
Examples
The following example sets the local mode to mtu-s:
[local]Redback(config-vpls-profile-neighbor)#local-mode mtu-s

Related Commands
counters
description
native-vlan-tag
neighbor
pe-type
pw-encap
standby-for

native-vlan-tag
native-vlan-tag value
no native-vlan-tag
Purpose
Configures a native virtual LAN (VLAN) tag for transporting untagged 802.1Q permanent virtual circuit
(PVC) traffic across a pseudo-wire.
Command Mode
Syntax Description
value Native VLAN tag value. The range of values is 1 to 4,095.
Default
The native VLAN tag is not configured.
Usage Guidelines
Use the native-vlan-tag command to configure a native VLAN tag for transporting untagged 802.1Q PVC
traffic across a pseudo-wire.
The native VLAN tag value is configurable on the SmartEdge OS to enable interoperability with the native
VLAN tag used by other devices in the network.
When the native VLAN tag is configured for a pseudo-wire instance:
1. All untagged ingress packets are prepended with the configured native VLAN tag.
2. All ingress packets with a VLAN tag value of 0 have that tag value re-written to the configured native
VLAN tag value. The original dot1q bits are not preserved.
3. At egress, when a packet is received over a pseudo-wire, the VLAN tag is removed if its value matches
the native VLAN tag value associated with the pseudo-wire. If the pseudo-wire is configured with a
different native VLAN tag value, or is not configured, then the packet retains its VLAN tag.
Note Only one native VLAN tag per pseudo-wire is supported.
Use the no form of this command to remove the native VLAN tag configuration.
Examples
The following example configures a native VLAN tag with a tag value of 23.
[local]Redback(config-vpls-profile-neighbor)#native-vlan-tag 23

Related Commands
counters
description
local-mode
neighbor
pe-type
pw-encap
standby-for

neighbor
neighbor ip-addr
{no | default} neighbor ip-addr
Purpose
Creates a new neighbor, or selects an existing one for modification, and enters Virtual Private LAN
Services (VPLS) profile neighbor configuration mode.
Command Mode
VPLS profile configuration
Syntax Description
ip-addr Neighbor IP address, in the form A.B.C.D.
Default
None
Usage Guidelines
Use the neighbor command to create a new neighbor, or select an existing one for modification, and enter
VPLS profile neighbor configuration mode.
The neighbor is identified by the IP address of the remote provider edge (PE) device. It is used along with
the pseudo-wire ID from the VPLS instance configuration to establish a pseudo-wire between the local and
remote PE devices. Multiple peering sessions (created by VPLS profiles) can be established to the same PE
device; different profiles can reference the same remote PE IP address.
Use the no or default form of this command to remove a configured neighbor.
Examples
The following example creates a new VPLS neighbor with the IP address, 10.10.10.1:
Related Commands
counters pe-type
description pw-encap
local-mode standby-for
native-vlan-tag

pe-type
pe-type {hub | spoke}
{no | default} pe-type
Purpose
Specifies the connection type used between the local and remote provider edge (PE) devices.
Command Mode
Syntax Description
hub Hub connection type. This connection type is used if the Virtual Private
LAN Services (VPLS) topology is enabled using a full mesh of
pseudo-wire. Packets received on a hub link pseudo-wire are not forwarded
on other hub connections (split horizon).
spoke Spoke connection type. This connection type is used for enabling
hierarchical VPLS topologies between multitenant unit switch (MTU-s) and
PE routers (PE-rs), or when a full mesh of pseudo-wires is not used.
Forwarding in unrestricted on spoke links.
Default
The hub connection type is used.
Usage Guidelines
Use the pe-type command to specifies the connection type used between the local and remote PE devices.
Currently, hub and spoke connection types are supported. For proper VPLS peering, both ends of the peer
must be configured with the same connection type.
Use the no or default form of this command to specify the default connection type.
Examples
The following example sets the connection type to spoke:
[local]Redback(config-vpls-profile-neighbor)#pe-type spoke

Related Commands
counters
description
local-mode
native-vlan-tag
neighbor
pw-encap
standby-for

profile
profile prof-name [pw-id pw-num | pw-name pw-name]
no profile prof-name
Purpose
Applies an existing Virtual Private LAN Services (VPLS) profile to a VPLS instance.
Command Mode
VPLS configuration
Syntax Description
prof-name Name of the VPLS profile that contains the neighbor attributes for
establishing the pseudo-wires (maximum 40 characters).
pw-id pw-num Optional. Pseudo-wire number. The value of the pw-num argument is a
4-byte number. The remote provider edge (PE) device uses the pseudo-wire
number and the local IP address to identify the pseudo-wire and the
associated VPLS instance.
pw-name pw-name Optional. Pseudo-wire name. The remote PE device uses the pseudo-wire
name and the local IP address to identify the pseudo-wire and the associated
VPLS instance.
Default
None
Usage Guidelines
Use the profile command to apply an existing VPLS profile to a VPLS instance. When a VPLS profile is
applied, a VPLS peer instance is created for each neighbor defined in the profile, and a pseudo-wire
connection is established using the attributes defined for the neighbor.
A VPLS profile must be configured using the vpls profile command (in global configuration mode) before
it can be applied.
Use the pw-id pw-num construct or pw-name pw-name construct to optionally specify a pseudo-wire ID
(number or name) to signal the ID for pseudo-wires to the neighbor defined in the profile. If a pseudo-wire
ID is not configured for a VPLS profile, then the VPLS instance-level default pseudo-wire ID is used.
Multiple VPLS profiles can be applied to the same VPLS instance. If two or more profiles reference the
same PE (same IP address), then the neighbor from the first profile is used. The same profile cannot be
applied multiple times even if the pseudo-wire IDs are different.
Use the no form of this command to delete a VPLS profile.
Examples

The following example applies the foo VPLS profile to the VPLS instance on the to-pe4 bridge:
[local]Redback(config-vpls)#profile foo pw-id 20
Related Commands
disable
pw-id
pw-name
vpls
vpls profile

pw-encap
pw-encap {ether | vlan}
{no | default} pw-encap
Purpose
Specifies the pseudo-wire encapsulation type.
Command Mode
Syntax Description
ether Specifies the encapsulation type as Ethernet encapsulation.
vlan Specifies the encapsulation type as Ethernet virtual LAN (VLAN)

encapsulation.
Default
The default pseudo-wire encapsulation type is Ethernet encapsulation.
Usage Guidelines
Use the pw-encap command to specify the pseudo-wire encapsulation type.
Use the no or default form of this command to specify the default encapsulation type.
Examples
The following example specifies the pseudo-wire encapsulation type as Ethernet VLAN encapsulation:
[local]Redback(config-vpls-profile-neighbor)#pw-encap vlan
Related Commands
counters
description
local-mode
native-vlan-tag
neighbor
pe-type
standby-for

pw-id
pw-id pw-num
no pw-id pw-num
Purpose
Configures a default pseudo-wire number for use with all the pseudo-wires signaled by the Virtual Private
LAN Services (VPLS) instance.
Command Mode
VPLS configuration
Syntax Description
pw-num Default pseudo-wire number, used to identify the pseudo-wire endpoints
when signaling using Label Distribution Protocol (LDP). Valid values are 1
to 4,294,967,295.
Default
None
Usage Guidelines
Use the pw-id command to configure a default pseudo-wire number for use with all the pseudo-wires
signaled by the VPLS instance. The default pseudo-wire number is used for VPLS profiles that do not have
a pseudo-wire ID (number or name) specified.
Remote provider edge (PE) devices use the pseudo-wire ID and the local IP address to identify the
pseudo-wire and the associated VPLS instance.
A VPLS instance can have only one default pseudo-wire ID, either a number or a name. If a default
pseudo-wire ID (name or number) has been configured for a VPLS instance and a new one is configured,
the previous pseudo-wire ID is replaced with the new one.
Use the no form of this command to remove the default pseudo-wire number.
Examples
The following example configures the default pseudo-wire number, 1234, for use with all the pseudo-wires
signaled by the VPLS instance:
[local]Redback(config-vpls)#pw-id 1234

Related Commands
disable
profile
pw-name
vpls

pw-label
pw-label in in-label-num out out-label-num
no pw-label
Purpose
Configures pseudo-wire labels for a static pseudo-wire.
Command Mode
Syntax Description
in in-label-num Number of the incoming (ingress) pseudo-wire label. The range of values
is 4,096 to 65,535.
out out-label-num Number of the outgoing (egress) pseudo-wire label. The range of values is
4,096 to 65,535.
Default
No pseudo-wire labels are configured.
Usage Guidelines
Use the pw-label command to configure pseudo-wire labels for a static pseudo-wire. When the
pseudo-wire labels are configured, the pseudo-wire is not signaled using a targeted LDP session to the
neighbor. Instead, a static mapping for the pseudo-wire is created using the specified pseudo-wire labels.
A pseudo-wire label can be used only once. Trying to configure a pseudo-wire label that is already in use
causes the pw-label command to be rejected. Pseudo-wire labels must be configured on both ends of the
VPLS peering session for the static pseudo-wire to operate properly.
Note Static pseudo-wires (inner tunnels) can be configured in either static or signalled outer tunnels,
including static, LDP and RSVP LSPs, and GRE tunnels.
When the outer tunnel is broken or no next hop to the peer exists, the static pseudo-wire is marked down,
and a standby pseudo-wire is used if it has been configured.
Note MAC flush TLVs sent using the clear vpls mac-flush command (in exec mode) can be sent over
both signaled and static pseudo-wires.
Use the no form of this command to delete the pseudo-wire labels.
Examples

The following example creates ingress and egress pseudo-wire labels, with the values 5000 and 15000,
respectively, for a static pseudo-wire to the VPLS profile neighbor, 10.10.10.1:
[local]Redback(config-vpls-profile-neighbor)#pw-label in 5000 out 15000
Related Commands
neighbor
profile
vpls

pw-name
pw-name pw-name
no pw-name pw-name
Purpose
Configures a default pseudo-wire name for use with all the pseudo-wires signaled by the Virtual Private
LAN Services (VPLS) instance.
Command Mode
VPLS configuration
Syntax Description
pw-name Name of the default pseudo-wire, used to identify the pseudo-wire
endpoints when signaling using Label Distribution Protocol (LDP).
Default
None
Usage Guidelines
Use the pw-name command to configure a default pseudo-wire name for use with all the pseudo-wires
signaled by the VPLS instance. The default pseudo-wire name is used for VPLS profiles that do not have
a pseudo-wire ID (number or name) specified.
Remote provider edge (PE) devices use the pseudo-wire ID and the local IP address to identify the
pseudo-wire and the associated VPLS instance.
A VPLS instance can have only one default pseudo-wire ID, either a number or a name. If a default
pseudo-wire ID (name or number) has been configured for a VPLS instance and a new one is configured,
the previous pseudo-wire ID is replaced with the new one.
Use the no form of this command to remove the default pseudo-wire name.
Examples
The following example configures the default pseudo-wire name, pw-foo, for use with all the
pseudo-wires signaled by the VPLS instance:
[local]Redback(config-vpls)#pw-name pw-foo

Related Commands
disable
profile
pw-id
vpls

standby-for
standby-for ip-addr
{no | default} standby-for
Purpose
Enables a neighbor as a standby neighbor for a primary neighbor.
Command Mode
Syntax Description
ip-addr IP address, in the form A.B.C.D, of the primary neighbor for which the
standby neighbor is being configured.
Default
No standby neighbor is configured.
Usage Guidelines
Use the standby-for command to enable a neighbor as a standby neighbor for a primary neighbor. A
neighbor can serve as a standby for only one primary neighbor. This method of configuring a standby
neighbor to reference a primary neighbor allows for establishing the primary and standby pseudo-wires
using independent sets of attributes.
Before a standby neighbor can be enabled, the following conditions must be met:
• A primary neighbor must be configured in the same profile.
• A spoke connection type must be set for the neighbor.
• Local mode must be set to multitenant unit switch (MTU-s).
• No other standby neighbor in the Virtual Private LAN Services (VPLS) profile can reference the same
primary neighbor IP address.
Use the no or default form of this command to disable a neighbor from being a standby neighbor for a
primary neighbor.
Examples
The following example creates a standby neighbor, 10.10.10.1, for the primary neighbor, 20.20.5.5:
[local]Redback(config-vpls-profile-neighbor)#standby-for 20.20.5.5

Related Commands
counters
description
local-mode
native-vlan-tag
neighbor
pe-type
pw-encap

vpls
vpls
no vpls
Purpose
Enables Virtual Private LAN Services (VPLS) on a bridge and enters VPLS configuration mode.
Command Mode
bridge configuration
Syntax Description
Default
VPLS is not enabled on the bridge.
Usage Guidelines
Use the vpls command to enable VPLS on a bridge and enter VPLS configuration mode.
Use the no form of this command to disable VPLS on the bridge.
Examples
The following example enables VPLS on the to-pe4 bridge and enter VPLS configuration mode:
Related Commands
disable
profile
pw-id
pw-name

vpls profile
vpls profile prof-name
no vpls profile prof-name
Purpose
Creates a new Virtual Private LAN Services (VPLS) profile, or selects an existing one for modification,
and enters VPLS profile configuration mode.
Command Mode
global configuration
Syntax Description
prof-name Name of the VPLS profile (maximum of 40 characters).
Default
None
Usage Guidelines
Use the vpls profile command to create a new VPLS profile, or select an existing one for modification, and
enter VPLS profile configuration mode. VPLS profiles are used to configure one or more neighbors to
which a VPLS instance can establish peering connections. All neighbors configured within a VPLS profile
are referenced by the VPLS profile name, which is unique in the system.
The VPLS profile is referenced from the VPLS instance configuration. Multiple VPLS instances can apply
(share) the same VPLS profile. If a profile is updated, then all instances of its usage use the changed
attributes. Conflicts arising, due to the updated VPLS profile in the VPLS instances, do not result in
rejecting the VPLS profile or the updates; the individual VPLS instances handle these conditions.
Examples
The following example creates the foo VPLS profile and enter VPLS profile configuration mode:
[local]Redback(config-vpls-profile)#
Related Commands
neighbor
profile

SR Vpls

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SR Vpls

Uploaded by

Copyright:

Available Formats

Chapter 16

VPLS Configuration 16-1

Figure 16-1 Typical VPLS Network Topology

Before VPLS can be configured, the following conditions must be met:

16-2 Routing Protocols Configuration Guide

Configuring a Bridge Profile

Table 16-1 Configure a Bridge Profile

Task Root Command Notes

Specify the maximum number of medium access mac-limit

Configuring a VPLS Profile

Table 16-2 Configure a VPLS Profile

Task Root Command Notes

VPLS Configuration 16-3

Table 16-2 Configure a VPLS Profile (continued)

Task Root Command Notes

16-4 Routing Protocols Configuration Guide

Table 16-2 Configure a VPLS Profile (continued)

Task Root Command Notes

Configuring a VPLS-Enabled Bridge

Table 16-3 Configure a VPLS-Enabled Bridge

Task Root Command Notes

VPLS Configuration 16-5

Table 16-3 Configure a VPLS-Enabled Bridge (continued)

Task Root Command Notes

16-6 Routing Protocols Configuration Guide

VPLS Configuration 16-7

16-8 Routing Protocols Configuration Guide

VPLS Configuration 16-9

16-10 Routing Protocols Configuration Guide

VPLS Configuration 16-11

16-12 Routing Protocols Configuration Guide

VPLS Configuration 16-13

16-14 Routing Protocols Configuration Guide

Note Only one native VLAN tag per pseudo-wire is supported.

VPLS Configuration 16-15

16-16 Routing Protocols Configuration Guide

VPLS Configuration 16-17

16-18 Routing Protocols Configuration Guide

VPLS Configuration 16-19

16-20 Routing Protocols Configuration Guide

VPLS Configuration 16-21

vlan Specifies the encapsulation type as Ethernet virtual LAN (VLAN)

16-22 Routing Protocols Configuration Guide

VPLS Configuration 16-23

16-24 Routing Protocols Configuration Guide

Use the no form of this command to delete the pseudo-wire labels.

VPLS Configuration 16-25

16-26 Routing Protocols Configuration Guide

VPLS Configuration 16-27

16-28 Routing Protocols Configuration Guide

VPLS Configuration 16-29

16-30 Routing Protocols Configuration Guide

VPLS Configuration 16-31

16-32 Routing Protocols Configuration Guide

You might also like