Table Of Contents
Implementing MPLS Layer 2 VPNs
Contents
Prerequisites for Implementing MPLS L2 VPN on Cisco IOS XR Software
L2VPN: Feature Overview
L2VPN Concepts
Virtual Circuit Connection Verification on L2VPN
Ethernet over MPLS
Ethernet Port Mode
VLAN Mode
QinQ Mode
QinAny Mode
ATM over MPLS
Quality of Service
High Availability
How to Configure L2VPN
L2VPN Prerequisites
Configuring Static Point-to-Point XConnects
Configuring Dynamic Point-to-Point XConnects
Configuring Virtual Circuit Connection Verification
Configuring Virtual Circuit Connection Verification for a Static Pseudowire
Configuring Virtual Circuit Connection Verification on a Dynamic Pseudowire
Configuring L2VPN Quality of Service in Port Mode
Configuring L2VPN Quality of Service in VLAN Mode
Configuration Examples for L2VPN
L2VPN Interface Configuration: Example
Point-to-Point Xconnects Configuration: Examples
L2VPN Quality of Service: Example
Additional References
Related Documents
Standards
MIBs
RFCs
Technical Assistance
Implementing MPLS Layer 2 VPNs
This module provides the conceptual and configuration information for MPLS Layer 2 virtual private networks (VPNs) on Cisco IOS XR software.
Note 
For more information about MPLS Layer 2 VPN on the Cisco IOS XR software and for descriptions of the commands listed in this module, see the "Related Documents" section of this module. To locate documentation for other commands that might appear while executing a configuration task, search online in the Cisco IOS XR software master command index.
Feature History for Implementing MPLS Layer 2 VPN on Cisco IOS XR Software Configuration Module
Release
|
Modification
|
Release 3.4.0
|
This feature was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
|
Release 3.4.1
|
The following features were documented in this release:
•Virtual Circuit Connection Verification (VCCV) on L2VPN was added.
•Layer 2 VPN (L2VPN) Quality of Service (QoS) was added for Ethernet over MPLS (EoMPLS) on the Cisco CRS-1.
•Both QinQ mode and QinAny mode were added for EoMPLS on the Cisco XR 12000 Series Router.
•L2VPN was added on ATM interfaces for the Cisco XR 12000 Series Router.
|
Contents
•Prerequisites for Implementing MPLS L2 VPN on Cisco IOS XR Software
•L2VPN: Feature Overview
•How to Configure L2VPN
•Configuration Examples for L2VPN
•Additional References
Prerequisites for Implementing MPLS L2 VPN on Cisco IOS XR Software
The following prerequisites are required to configure L2 VPN on your network:
•You must be in a user group associated with a task group that includes the proper task IDs for MPLS L2 VPN commands.
•For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
L2VPN: Feature Overview
This section includes the following subsections:
•L2VPN Concepts
•Virtual Circuit Connection Verification on L2VPN
•Ethernet over MPLS
•ATM over MPLS
•Quality of Service
•High Availability
L2VPN Concepts
Layer 2 (L2) VPN emulates the behavior of a local area network (LAN) across an internet protocol (IP) or MPLS-enabled IP network allowing Ethernet devices to communicate with each other as if they were connected to a common LAN segment.
Internet service providers (ISPs) would like to replace their Frame Relay (FR) or Asynchronous Transfer Mode (ATM) infrastructures with an IP infrastructure. Accordingly, there is a need for to provide standard ways of using an IP infrastructure to provide a serviceable L2 interface to customers, specifically, to provide standard ways of using an IP infrastructure to provide virtual circuits between pairs of customer sites.
Building a L2VPN system requires coordination between the ISP and the customer. The ISP provides L2 connectivity; the customer builds a network using data link resources obtained from the ISP. In an L2VPN service, the ISP does not require information about a the customer's network topology, policies, routing information, point-to-point links, or if the network has point-to-point links from other ISPs.
What the ISP does require are provider edge (PE) routers with the following capabilities:
•Encapsulation of L2 protocol data units (PDU) into layer 3 packets
•Inter-connection of any-to-any L2 transports
•Emulation of L2 quality-of-service (QoS) over a packet switch network
•Ease of configuration of the L2 service
•Support for different types of tunneling mechanisms (MPLS, L2TPv3, IPSec, GRE, and others)
•L2VPN process databases include all information related to circuits and their connections.
Virtual Circuit Connection Verification on L2VPN
Virtual Circuit Connection Verification (VCCV) is an L2VPN Operations, Administration, and Maintenance (OAM) feature that allows network operators to run IP-based provider edge (PE)-to-PE keepalive protocol across a specified pseudowire to ensure that the pseudowire data path forwarding does not contain any faults. The disposition PE receives VCCV packets on a control channel, which is associated with the specified pseudowire. The control channel type and connectivity verification type, which are used for VCCV, are negotiated when the pseudowire is established between the PEs for each direction.
Two types of packets can arrive at the disposition egress:
•Type 1—Specifies normal Ethernet over MPLS (EoMPLS) data packets.
•Type 2—Specifies VCCV packets.
Because each of the supported packets requires different handling, the disposition egress code is able to distinguish between these packets. The code checks the status of bit #28 in a control word, which is always present for VCCV packets but not necessary for data packets.
Cisco IOS XR software supports Label Switched Path (LSP) VCCV type 1, which uses an inband control word if enabled during signaling. The VCCV echo reply is sent as IPv4 that is the reply mode is IPv4. The reply is forwarded as IP, MPLS, or a combination of both.
VCCV pings counters that are counted in MPLS forwarding on the egress side. However, on the ingress side, they are sourced by the route processor (RP) and do not count as MPLS forwarding counters.
Ethernet over MPLS
Ethernet over MPLS (EoMPLS) provides a tunneling mechanism for Ethernet traffic through an MPLS-enabled Layer 3 (L3) core and encapsulates Ethernet protocol data units (PDUs) inside MPLS packets (using label stacking) to forward them across the MPLS network.
Ethernet over MPLS is presented in the following sections:
•Ethernet Port Mode
•VLAN Mode
•QinQ Mode
•QinAny Mode
Ethernet Port Mode
In Ethernet port mode, both ends of pseudowire (PW) are connected to Ethernet ports. In this mode, the port is tunneled over PW or, using local switching (also known as AC-to-AC cross-connect) switches packets or frames from one AC to another AC attached to the same PE node.
Note In Cisco IOS XR software, an AC is a logical link that connects the CE to the PE .
The pseudowire is always a Type 5 virtual connection (VC).
On the ingress provider edge, the network service provider passes the packets to the pseudowire termination point, adds the MPLS labels to the packets, and sends the packets over the pseudowire.
Figure 13 provides an example of Ethernet port mode at work.
Figure 13 Ethernet Port Mode Packet Flow
VLAN Mode
VLAN mode provides Ethernet VLAN-to-VLAN connectivity. In VLAN mode, each VLAN on a customer-end to provider-end link can be configured as a separate L2VPN connection, using either VC type 4 or VC type 5. VC type 5 is the default mode.
On Type 4 VCs, on the ingress provider edge, the VLAN tag maps to a particular pseudowire and the packet is placed on the pseudowire with the VLAN tag untouched.
On Type 5 VCs, on the ingress provider edge that is receiving packets from the customer edge, the network service provider strips off the customer edge VLAN tag before placing the packets on the pseudowire. On the egress provider edge, the network service provider pushes the VLAN tag onto the protocol stack before it sends the packet to the customer edge.
Figure 14 VLAN Mode Packet Flow
As illustrated in Figure 14, the Ethernet PE associates an internal VLAN-tag to the Ethernet port for switching the traffic internally from the ingress port to the PW; however, before placing the traffic into the PW, it removes the internal VLAN tag. At the egress VLAN PE, the PE associates a VLAN tag to the frames coming off of the PW and after switching the traffic internally, it sends out the traffic off of an Ethernet trunk port. Since the port is in trunk mode, the VLAN PE doesn't remove the VLAN tag and forwards the frames through the port with the added tag.
QinQ Mode
Note The QinQ mode is supported only on the Cisco XR 12000 Series Router.
In QinQ mode, each customer edge VLAN is carried by a service provider VLAN. Ideally, in QinQ mode, the pseudowire should be a Type 5 virtual connection (VC), but Type 4 virtual connections (VCs) are also supported.
On each Ethernet provider edge network, both the customer edge VLAN (inner) and the service provider VLAN (outer) are configured. Both the customer edge VLAN tag and the service provider VLAN tag are service delimiting.
On a Type 4 virtual connection (VC):
•On an ingress provider edge network:
–The service provider inserts a service provider tag onto the packet. Pseudowire termination uses the service provider tag to find the VC on which to send the packet, and pops the tag before placing the packet on the pseudowire.
•On an egress provider edge network:
–Pseudowire termination pushes a locally significant service provider tag onto the packet before passing the packet to the network service provider. The network service provider uses this tag to find the customer edge, and pops the tag before sending the packet to the customer edge.
On a Type 5 virtual connection (VC):
•On an ingress provider edge network:
–The ingress provider edge pops the VLAN tag and passes the packet to pseudowire termination.
•On an egress provider edge network:
–Pseudowire termination pushes the customer edge VLAN (inner) tag and the service provider VLAN (outer) tag before passing the packet to the network service provider. The network service provider uses the service provider VLAN (outer) tag to determine the customer edge and pops the tag before sending the packet over the pseudowire.
QinAny Mode
Note The QinAny mode is supported only on the Cisco XR 12000 Series Router.
In the QinAny mode, the service provider VLAN (outer) tag is configured on both the ingress and the egress nodes of the provider edge VLAN. The QinAny mode is similar to the QinQ mode using a Type 5 virtual connection (VC), except that the customer edge VLAN (inner) tag is carried in the packet when it is sent over the pseudowire. This is because the customer edge VLAN (inner) tag is not known through the configuration.
ATM over MPLS
ATM over MPLS (AToM) provides a tunneling mechanism for ATM traffic through an MPLS-enabled Layer 3 (L3) core. Cisco IOS XR software supports a point-to-point end-to-end service, where two ATM circuits are connected together.
ATM over MPLS is supported on the following ATM interface elements:
•ATM ports (also known as ATM port mode)
•ATM Layer 2 Subinterfaces with a PVC
•ATM Layer 2 Subinterfaces with a PVP
Cisco IOS XR software supports a point-to-point end-to-end service, where two ATM circuits are connected together. Switching can take place in two ways:
•AC-to-PW—Traffic reaching the PE is tunneled over a pseudowire (and conversely, traffic arriving over the PW is sent out over the AC). This is the most common scenario.
•Local switching—Traffic arriving on one AC is immediately sent out of another AC without passing through a pseudowire.
Note For detailed information about configuring an L2VPN network, see the "Implementing MPLS Layer 2 VPNs" module of the Cisco IOS XR Multiprotocol Label Switching Configuration Guide.
Quality of Service
Using L2VPN technology, you can assign a quality of service (QoS) level to both Port and VLAN modes of operation.
Table 5 lists the supported quality of service (QoS) policy actions on Layer 2 interfaces on the Cisco CRS-1 router.
Table 5 QoS Policy Actions on Layer 2 VPN
Policy Action
|
Imposition Ingress
|
Imposition Egress
|
Disposition Ingress
|
Disposition Egress
|
match criteria
|
any
source-address mac
cos
vlan
|
any
access-group
protocol
exp
|
any
access-group
protocol
exp
|
any
destination-address mac
cos
vlan
qos-group
discard-class
|
policer type (color-blind only)
|
1R2C
1R3C
2R3C
|
1R2C
1R3C
2R3C
|
1R2C
1R3C
2R3C
|
1R2C
1R3C
2R3C
|
policer conform-action
exceed-action
violate-action
|
drop
transmit
set discard-class
set mpls exp imposition
|
drop
transmit
set discard-class
set mpls exp topmost
|
drop
transmit
set discard-class
set mpls exp topmost
|
drop
transmit
set discard-class
set cos
|
shape
|
yes
|
yes
|
yes
|
yes
|
marking
|
set mpls exp imposition
set-qos group
set discard-class
|
set cos
set mpls exp topmost
set qos-group
set discard-class
|
set mpls exp topmost
set qos-group
set discard-class
|
set cos
|
random-detect
|
default
discard-class
cos
|
default
discard-class
exp
|
default
discard-class
exp
|
default
discard-class
cos
|
queue-limit
|
yes
|
yes
|
yes
|
yes
|
L2VPN technology requires that QoS functionality on PE routers be strictly layer2 payload-based on the edge-facing interfaces (also know as Attachment Circuits). Figure 15 illustrates layer-2 and layer-3 QoS service policies in a typical L2VPN network.
Figure 15 L2VPN QoS Feature Application
Figure 16 shows four packet processing paths within a provider edge device where a QoS service policy can be attached. In an L2VPN network, packets are received and transmitted on the edge-facing interfaces as L2 packets and transported on the core-facing interfaces as MPLS (EoMPLS) or IP (L2TPv3) packets.
Figure 16 L2VPN QoS Reference Model
High Availability
L2VPN has control plane in both route processors and line cards, as well as forwarding plane elements in the line cards (LCs). The availability of L2VPN meets the requirements listed here:
•A control plane failure in either the RP or the LC will not affect the circuit forwarding path.
•The RP control plane supports fail-over without affecting the LC control and forwarding planes.
•L2VPN integrates with existing LDP graceful restart mechanism.
How to Configure L2VPN
This section describes the tasks required to implement L2VPN:
•Configuring Static Point-to-Point XConnects
•Configuring Dynamic Point-to-Point XConnects
•Configuring Virtual Circuit Connection Verification
•Configuring L2VPN Quality of Service in Port Mode
•Configuring L2VPN Quality of Service in VLAN Mode
Note The tasks in this section use ethernet for the configuration examples; however, they apply equally to ATM.
L2VPN Prerequisites
Before you can implement MPLS L2VPN on a connection, you must create and configure an attachment circuit (AC) to host L2VPN, as described in one of the following chapters:
•To configure an AC on an Ethernet port, see the "Configuring Ethernet Interfaces on Cisco IOS XR Software" module of the Cisco IOS XR Interface and Hardware Component Configuration Guide.
•To configure an AC on a VLAN, see the "Configuring 802.1Q VLAN Interfaces on Cisco IOS XR Software" module of the Cisco IOS XR Interface and Hardware Component Configuration Guide.
•To configure an AC on an ATM interface, see the "Configuring ATM Interfaces on Cisco IOS XR Software" module of the Cisco IOS XR Interface and Hardware Component Configuration Guide.
Note, also, that L2VPN is supported only on the following interfaces:
•Ethernet: L2VPN is supported on ethernet ports and VLANs.
•ATM: L2VPN is supported on ATM ports, Permanent Virtual Circuits (PVCs), and Permanent Virtual Paths (PVPs).
Configuring Static Point-to-Point XConnects
Perform this task to configure static point-to-point xconnects.
Please note the following points about xconnects:
•An xconnect is uniquely identified with the pair; accordingly, the xconnect name must be unique within a group.
•A segment (either an attachment circuit or pseudowire) is globally unique and can only belong to a single xconnect.
•A static VC local label is from 16 to 16,000 and is globally unique (that is, it can be used in one pseudowire only).
•No more than 16,000 xconnects can be configured per router.
Note Static pseudowire connections do not use LDP for signalling.
SUMMARY STEPSPoint-to-Point Xconnects Configuration
1. configure
2. l2vpn
3. xconnect group group name
4. p2p xconnect name
5. interface type-instance
6. neighbor A.B.C.D pw-id pseudowire ID pw-static-label local value remote value
7. end
or
commit
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
configure
Example:
RP/0/RP0/CPU0:router# configure
|
Enters the configuration mode.
|
Step 2
|
l2vpn
Example:
RP/0/RP0/CPU0:router(config)# l2vpn
|
Enters L2VPN configuration mode.
|
Step 3
|
xconnect group group name
Example:
RP/0/RP0/CPU0:router(config-l2vpn)# xconnect
group grp_1
|
Enters the name of the xconnects group.
|
Step 4
|
p2p xconnect name
Example:
RP/0/RP0/CPU0:router(config-l2vpn-xconnect)#
p2p vlan1
|
Enters a name for the point-to-point xconnect.
|
Step 5
|
interface type-instance
Example:
RP/0/RP0/CPU0:router(config-l2vpn-xconnect-p2p)
# interface GigabitEthernet0/0/0/0.1
|
Specifies the interface type instance. The choices are:
•GigabitEthernet: GigabitEthernet/IEEE 802.3 interfaces
•TenGigE: TenGigabitEthernet/IEEE 802.3 interfaces
|
Step 6
|
neighbor A.B.C.D pw-id pseudowire ID
pw-static-label local label remote label
Example:
RP/0/RP0/CPU0:router(config-l2vpn-xconnect-p2p)
# neighbor 2.2.2.2 pw-id 2000 pw-static-label
local 17 remote 18
|
Configures the pseudowire segment for the xconnect.
Optionally, you can disable the control-word or set the transport-type to "ethernet" or "vlan".
|
Step 7
|
end
or
commit
Example:
RP/0/RP0/CPU0:router(config-l2vpn-xconnect-p2p)
# end
or
RP/0/RP0/CPU0:router(config-l2vpn-xconnect-p2p)
# commit
|
Saves configuration changes.
•When you enter the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)? [cancel]:
–Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.
–Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.
–Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.
•When you enter the commit command, the system saves the configuration changes to the running configuration file and remains within the configuration session.
|
Configuring Dynamic Point-to-Point XConnects
Perform this task to configure dynamic point-to-point xconnects.
Note For dynamic xconnects, LDP must be up and running.
SUMMARY STEPS
1. configure
2. l2vpn
3. xconnect group group name
4. p2p xconnect name
5. interface type-instance
6. neighbor A.B.C.D pw-id pseudowire ID
7. end
or
commit
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
configure
Example:
RP/0/RP0/CPU0:router# configure
|
Enters the configuration mode.
|
Step 2
|
l2vpn
Example:
RP/0/RP0/CPU0:router(config)# l2vpn
|
Enters L2VPN configuration mode.
|
Step 3
|
xconnect group group name
Example:
RP/0/RP0/CPU0:router(config-l2vpn)# xconnect
group grp_1
|
Enters the name of the xconnects group.
|
Step 4
|
p2p xconnect name
Example:
RP/0/RP0/CPU0:router(config-l2vpn-xconnect)#
p2p vlan1
|
Enters a name for the point-to-point xconnect.
|
Step 5
|
interface type-instance
Example:
RP/0/RP0/CPU0:router(config-l2vpn-xconnect-p2p)
# interface GigabitEthernet0/0/0/0.1
|
Specifies the interface type instance. The choices are:
•GigabitEthernet: GigabitEthernet/IEEE 802.3 interfaces
•TenGigE: TenGigabitEthernet/IEEE 802.3 interfaces
|
Step 6
|
neighbor A.B.C.D pw-id pseudowire ID
Example:
RP/0/RP0/CPU0:router(config-l2vpn-xconnect-p2p)
# neighbor 2.2.2.2 pw-id 2000
|
Configures the pseudowire segment for the xconnect.
Optionally, you can disable the control-word or set the transport-type to "ethernet" or "vlan".
|
Step 7
|
end
or
commit
Example:
RP/0/RP0/CPU0:router(config-l2vpn-xconnect-p2p)
# end
or
RP/0/RP0/CPU0:router(config-l2vpn-xconnect-p2p)
# commit
|
Saves configuration changes.
•When you enter the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)? [cancel]:
–Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.
–Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.
–Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.
•When you enter the commit command, the system saves the configuration changes to the running configuration file and remains within the configuration session.
|
Configuring Virtual Circuit Connection Verification
This section presents the following procedures on how to configure VCCV:
•Configuring Virtual Circuit Connection Verification for a Static Pseudowire
•Configuring Virtual Circuit Connection Verification on a Dynamic Pseudowire
You can use the ping mpls pseudowire command to ping over the MPLS pseudowire. You can configure the VCCV control channel with the pseudowire to verify specific virtual circuits.
Configuring Virtual Circuit Connection Verification for a Static Pseudowire
Perform this task to configure VCCV for a static pseudowire.
SUMMARY STEPS
1. configure
2. l2vpn
3. xconnect group group name
4. p2p {xconnect-name}
5. neighbor {A.B.C.D} {pw-id value} [pw-static-label local label remote value] [control-word {disable | enable}] [vccv disable]
6. end
or
commit
7. show l2vpn xconnect [detail | group | interface | neighbor | state | summary | type | unresolved]
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
configure
Example:
RP/0/RP0/CPU0:router# configure
|
Enters the configuration mode.
|
Step 2
|
l2vpn
Example:
RP/0/RP0/CPU0:router(config)# l2vpn
RP/0/RP0/CPU0:router(config-l2vpn)#
|
Enter L2VPN configuration mode.
|
Step 3
|
xconnect group group name
Example:
RP/0/RP0/CPU0:router(config-l2vpn)# xconnect group
customerX
RP/0/RP0/CPU0:router(config-l2vpn-xconnect)#
|
Specifies the group to which the xconnects belong using a free-format string.
|
Step 4
|
p2p {xconnect name}
Example:
RP/0/RP0/CPU0:router(config-l2vpn-xconnect)# p2p
vlan1
RP/0/RP0/CPU0:router(config-l2vpn-xconnect-p2p)#
|
Enters a name for the point-to-point xconnect.
|
Step 5
|
neighbor {A.B.C.D} {pw-id value} [pw-static-label
local label remote value] [control-word {disable |
enable}][vccv disable]
Example:
RP/0/RP0/CPU0:router(config-l2vpn-xconnect-p2p)#
neighbor 10.1.1.2 pw-id 3000 pw-static-label local
5000 control-word enable vccv disable
|
Configures a static pseudowire to have the VCCV disable option.
|
Step 6
|
end
or
commit
Example:
RP/0/RP0/CPU0:router(config-l2vpn-xconnect-p2p)# end
or
RP/0/RP0/CPU0:router(config-l2vpn-xconnect-p2p)#
commit
|
Saves configuration changes.
•When you enter the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)? [cancel]:
–Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.
–Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.
–Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.
•When you enter the commit command, the system saves the configuration changes to the running configuration file and remains within the configuration session.
|
Step 7
|
show l2vpn xconnect [detail | group | interface |
neighbor | state | summary | type | unresolved]
Example:
RP/0/RP0/CPU0:router# show l2vpn xconnect detail
|
Displays brief information on configured xconnects.
•Use the detail keyword to verify that VCCV is disabled.
|
Configuring Virtual Circuit Connection Verification on a Dynamic Pseudowire
Perform this task to configure VCCV for a dynamic pseudowire.
SUMMARY STEPS
1. configure
2. l2vpn
3. xconnect group group name
4. p2p {xconnect-name}
5. neighbor {A.B.C.D} {pw-id value} [control-word {disable | enable}] [vccv disable]
6. end
or
commit
7. show l2vpn xconnect [detail | group | interface | neighbor | state | summary | type | unresolved]
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
configure
Example:
RP/0/RP0/CPU0:router# configure
|
Enters the configuration mode.
|
Step 2
|
l2vpn
Example:
RP/0/RP0/CPU0:router(config)# l2vpn
RP/0/RP0/CPU0:router(config-l2vpn)#
|
Enter L2VPN configuration mode.
|
Step 3
|
xconnect group group name
Example:
RP/0/RP0/CPU0:router(config-l2vpn)# xconnect group
customerX
RP/0/RP0/CPU0:router(config-l2vpn-xconnect)#
|
Specifies the group to which the xconnects belong using a free-format string.
|
Step 4
|
p2p {xconnect name}
Example:
RP/0/RP0/CPU0:router(config-l2vpn-xconnect)# p2p
vlan1
RP/0/RP0/CPU0:router(config-l2vpn-xconnect-p2p)#
|
Enters a name for the point-to-point xconnect.
|
Step 5
|
neighbor {A.B.C.D} {pw-id value} [control-word
{disable | enable}][vccv disable]
Example:
RP/0/RP0/CPU0:router(config-l2vpn-xconnect-p2p)#
neighbor 10.1.1.2 pw-id 3000 control-word enable
vccv disable
|
Configures a dynamic pseudowire to have the VCCV disable option.
|
Step 6
|
end
or
commit
Example:
RP/0/RP0/CPU0:router(config-l2vpn-xconnect-p2p)# end
or
RP/0/RP0/CPU0:router(config-l2vpn-xconnect-p2p)#
commit
|
Saves configuration changes.
•When you enter the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)? [cancel]:
–Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.
–Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.
–Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.
•When you enter the commit command, the system saves the configuration changes to the running configuration file and remains within the configuration session.
|
Step 7
|
show l2vpn xconnect [detail | group | interface |
neighbor | state | summary | type | unresolved]
Example:
RP/0/RP0/CPU0:router# show l2vpn xconnect detail
|
Displays brief information on configured xconnects.
•Use the detail keyword to verify that VCCV is disabled.
|
Configuring L2VPN Quality of Service in Port Mode
This procedure describes how to attach a QoS policy in L2VPN Port mode. (For VLAN mode, see "Configuring L2VPN Quality of Service in VLAN Mode" section.)
SUMMARY STEPS
1. configure
2. interface type-instance.subinterface
3. l2transport
4. service-policy [input | output] [policy-map-name]
5. end
or
commit
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
configure
Example:
RP/0/RP0/CPU0:router# configure
|
Enters the configuration mode.
|
Step 2
|
interface type-instance.subinterface
Example:
RP/0/RP0/CPU0:router(config)# interface
GigabitEthernet0/0/0/0.1
|
Specifies the interface attachment circuit.
|
Step 3
|
l2transport
Example:
RP/0/RP0/CPU0:router(config-if)# l2transport
|
Configures an interface or connection for Layer 2 switching.
|
Step 4
|
service-policy [input | output]
[policy-map-name]
Example:
RP/0/RP0/CPU0:router(config-if)# service-policy
input servpol1
|
Attaches a QoS policy to an input or output interface to be used as the service policy for that interface.
|
Step 5
|
end
or
commit
Example:
RP/0/RP0/CPU0:router(config-rsvp-if)# end
or
RP/0/RP0/CPU0:router(config-rsvp-if)# commit
|
Saves configuration changes.
•When you enter the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)? [cancel]:
–Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.
–Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.
–Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.
•When you enter the commit command, the system saves the configuration changes to the running configuration file and remains within the configuration session.
|
Configuring L2VPN Quality of Service in VLAN Mode
This procedure describes how to attach a QoS policy in VLAN mode. For Port mode, see "Configuring L2VPN Quality of Service in Port Mode" section.
SUMMARY STEPS
1. configure
2. interface type-instance.subinterface l2transport
3. service-policy [input | output] [policy-map-name]
4. end
or
commit
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
configure
Example:
RP/0/RP0/CPU0:router# configure
|
Enters the configuration mode.
|
Step 2
|
interface type-instance.subinterface
l2transport
Example:
RP/0/RP0/CPU0:router(config)# interface
GigabitEthernet0/0/0/0.1 l2transport
|
Configures an interface or connection for Layer 2 switching.
Note In VLAN Mode, you must enter the l2transport keyword on the same line as the interface.
|
Step 3
|
service-policy [input | output]
[policy-map-name]
Example:
RP/0/RP0/CPU0:router(config-if)# service-policy
input servpol1
|
Attaches a QoS policy to an input or output interface to be used as the service policy for that interface.
|
Step 4
|
end
or
commit
Example:
RP/0/RP0/CPU0:router(config-rsvp-if)# end
or
RP/0/RP0/CPU0:router(config-rsvp-if)# commit
|
Saves configuration changes.
•When you enter the end command, the system prompts you to commit changes:
Uncommitted changes found, commit them before exiting (yes/no/cancel)? [cancel]:
–Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.
–Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.
–Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.
•When you enter the commit command, the system saves the configuration changes to the running configuration file and remains within the configuration session.
|
Configuration Examples for L2VPN
In the following example, two traffic classes are created and their match criteria are defined. For the first traffic class called class1, ACL 101 is used as the match criterion. For the second traffic class called class2, ACL 102 is used as the match criterion. Packets are checked against the contents of these ACLs to determine if they belong to the class.
This section includes the following configuration examples:
•L2VPN Interface Configuration: Example
•Point-to-Point Xconnects Configuration: Examples
•L2VPN Quality of Service: Example
L2VPN Interface Configuration: Example
The following example shows
interface GigabitEthernet0/0/0/0.1 l2transport
Point-to-Point Xconnects Configuration: Examples
This section includes configuration examples for both static and dynamic p2p xconnects on an ATM interface.
Static Config
The following example shows
xconnect group vlan_grp_1
neighbor 2.2.1.1 pw-id 1 pw-static-label local 17 remote 18
Dynamic Config
The following example shows
xconnect group vlan_grp_1
L2VPN Quality of Service: Example
The following example shows
service-policy [input | output] [policy-map-name]
Additional References
For additional information related to implementing traffic engineering, refer to the following references:
Related Documents
Related Topic
|
Document Title
|
Cisco IOS XR L2VPN command reference document
|
MPLS Virtual Private Network Commands on Cisco IOS XR Software
|
Cisco CRS-1 router getting started material
|
Cisco IOS XR Getting Started Guide
|
Information about user groups and task IDs
|
Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide
|
Standards
|
|
Title
|
Technical Assistance Center (TAC) home page, containing 30,000 pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.
|
—
|
MIBs
RFCs
RFCs
|
Title
|
RFC 4447
|
Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP), April 2006
|
RFC 4448
|
Encapsulation Methods for Transport of Ethernet over MPLS Networks, April 2006
|
Technical Assistance
Description
|
Link
|
The Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.
|
http://www.cisco.com/techsupport
|
Feedback
