Table Of Contents
Prerequisites for L2VPN Pseudowire Switching
Restrictions for L2VPN Pseudowire Switching
Information About L2VPN Pseudowire Switching
How L2VPN Pseudowire Switching Works
How Packets Are Manipulated at the L2VPN Pseudowire Switching Aggregation Point
How to Configure L2VPN Pseudowire Switching
Configuration Examples for L2VPN Pseudowire Switching
L2VPN Pseudowire Switching in an Inter-AS Configuration: Example
Feature Information for L2VPN Pseudowire Switching
L2VPN Pseudowire Switching
First Published: April 20, 2005Last Updated: November 20, 2009This feature module explains how to configure L2VPN Pseudowire Switching, which extends Layer 2 Virtual Private Network (L2VPN) pseudowires across an interautonomous system (inter-AS) boundary or across two separate Multiprotocol Label Switching (MPLS) networks. The feature supports ATM and time-division multiplexing (TDM) attachment circuits (ACs) and Ethernet ACs.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for L2VPN Pseudowire Switching" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for L2VPN Pseudowire Switching
•
Restrictions for L2VPN Pseudowire Switching
•
Information About L2VPN Pseudowire Switching
•
How to Configure L2VPN Pseudowire Switching
•
Configuration Examples for L2VPN Pseudowire Switching
•
Feature Information for L2VPN Pseudowire Switching
Prerequisites for L2VPN Pseudowire Switching
For the Cisco 12000 series routers, the L2VPN Pseudowire Switching feature for Any Transport over MPLS (AToM) is supported on the following engines:
•
E2
•
E3
•
E4+
•
E5
•
E6
For engines that do not support this feature, the packets are sent to the software and forwarded through the slow path.
Note
Engines E1 and E4 do not support L2VPN Pseudowire Switching, even in the slow path.
Restrictions for L2VPN Pseudowire Switching
•
L2VPN Pseudowire Switching is supported with AToM.
•
Only static, on-box provisioning is supported.
•
Sequencing numbers in AToM packets are not processed by L2VPN Pseudowire Switching. The feature blindly passes the sequencing data through the xconnect packet paths, a process that is called transparent sequencing. The endpoint provider-edge (PE) to customer-edge (CE) connections enforce the sequencing.
•
You can ping the adjacent next-hop PE router. End-to-end label switched path (LSP) pings are not supported.
•
Do not configure IP or Ethernet interworking on a router where L2VPN Pseudowire Switching is enabled. Instead, configure interworking on the routers at the edge PEs of the network.
•
The control word negotiation results must match. If either segment does not negotiate the control word, the control word is disabled for both segments.
•
AToM Graceful Restart is negotiated independently on each pseudowire segment. If there is a transient loss of the label distribution protocol (LDP) session between two AToM PE routers, packets continue to flow.
•
Per-pseudowire quality of service (QoS) is not supported. Traffic engineering (TE) tunnel selection is supported.
•
Attachment circuit interworking is not supported.
Information About L2VPN Pseudowire Switching
To configure the L2VPN Pseudowire Switching feature, you should understand the following concepts:
•
How L2VPN Pseudowire Switching Works
•
How Packets Are Manipulated at the L2VPN Pseudowire Switching Aggregation Point
How L2VPN Pseudowire Switching Works
L2VPN Pseudowire Switching allows the user to extend L2VPN pseudowires across two separate MPLS networks or across an inter-AS boundary, as shown in Figure 1 and Figure 2.
L2VPN Pseudowire Switching connects two or more contiguous pseudowire segments to form an end-to-end multihop pseudowire. This end-to-end pseudowire functions as a single point-to-point pseudowire.
As shown in Figure 2, L2VPN Pseudowire Switching enables you to keep the IP addresses of the edge PE routers private across inter-AS boundaries. You can use the IP address of the Autonomous System Boundary Routers (ASBRs) and treat them as pseudowire aggregation (PE-agg) routers. The ASBRs join the pseudowires of the two domains.
L2VPN Pseudowire Switching also enables you to keep different administrative or provisioning domains to manage the end-to-end service. At the boundaries of these networks, PE-agg routers delineate the management responsibilities.
Figure 1 L2VPN Pseudowire Switching in an Intra-AS Topology
Figure 2 L2VPN Pseudowire Switching in an Inter-AS Topology
How Packets Are Manipulated at the L2VPN Pseudowire Switching Aggregation Point
Switching AToM packets between two AToM pseudowires is the same as switching any MPLS packet. The MPLS switching data path switches AToM packets between two AToM pseudowires. The following list explains exceptions:
•
The outgoing virtual circuit (VC) label replaces the incoming VC label in the packet. New Internal Gateway Protocol (IGP) labels and Layer 2 encapsulation are added.
•
The incoming VC label time-to-live (TTL) field is decremented by one and copied to the outgoing VC label TTL field.
•
The incoming VC label EXP value is copied to the outgoing VC label EXP field.
•
The outgoing VC label "Bottom of Stack" S bit in the outgoing VC label is set to 1.
•
AToM control word processing is not performed at the L2VPN Pseudowire Switching aggregation point. Sequence numbers are not validated. Use the Router Alert label for LSP Ping; do not require control word inspection to determine an LSP Ping packet.
How to Configure L2VPN Pseudowire Switching
Use the following procedure to configure L2VPN Pseudowire Switching on each of the PE-agg routers. In this configuration, you are limited to two neighbor commands after entering the l2 vfi command.
Prerequisites
•
This procedure assumes that you have configured basic AToM L2VPNs. This procedure does not explain how to configure basic AToM L2VPNs that transport Layer 2 packets over an MPLS backbone. For information on the basic configuration, see Any Transport over MPLS.
•
For interautonomous configurations, ASBRs require a labeled interface.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
l2 vfi name point-to-point
4.
neighbor ip-address vcid [encapsulation mpls | pw-class pw-class-name]
5.
exit
6.
exit
7.
show mpls l2transport vc [vcid [vc-id | vc-id-min vc-id-max]] [interface name [local-circuit-id]] [destination ip-address | name] [detail]
8.
show vfi [vfi-name]
9.
ping [protocol] [tag] {host-name | system-address}
DETAILED STEPS
Examples
The following example displays output from the show mpls l2transport vc command:
Router# show mpls l2transport vcLocal intf Local circuit Dest address VC ID Status------------- -------------------------- --------------- ----- ----MPLS PW 10.0.1.1:100 10.0.1.1 100 UPMPLS PW 10.0.1.1:100 10.0.1.1 100 UPThe following example displays output from the show vfi command:
Router# show vfiVFI name: test, type: point-to-pointNeighbors connected via pseudowires:Router ID Pseudowire ID10.0.1.1 10010.0.1.1 100Configuration Examples for L2VPN Pseudowire Switching
This section provides the following configuration example:
•
L2VPN Pseudowire Switching in an Inter-AS Configuration: Example
L2VPN Pseudowire Switching in an Inter-AS Configuration: Example
Two separate autonomous systems are able to pass L2VPN packets, because the two PE-agg routers have been configured with L2VPN Pseudowire Switching. This example configuration is shown in Figure 3.
Figure 3 L2VPN Pseudowire Switching in an Interautonomous System
Additional References
Related Documents
Related Topic Document TitleAny Transport over MPLS
Pseudowire redundancy
High availability for AToM
L2VPN interworking
Layer 2 local switching
PWE3 MIB
Pseudowire Emulation Edge-to-Edge MIBs for Ethernet and Frame Relay Services
Packet sequencing
Standards
Standard Titledraft-ietf-pwe3-control-protocol-14.txt
Pseudowire Setup and Maintenance using LDP
draft-martini-pwe3-pw-switching-01.txt
Pseudo Wire Switching
MIBs
RFCs
Technical Assistance
Feature Information for L2VPN Pseudowire Switching
Table 1 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Releases 12.2(28)SB or 12.2(33)SRB or a later release appear in the table
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2005-2009 Cisco Systems, Inc. All rights reserved.



