Contents
The L2VPN Pseudowire Redundancy feature enables you to configure your network to detect a failure in the network and reroute the Layer 2 (L2) service to another endpoint that can continue to provide service. This feature provides the ability to recover from a failure either of the remote provider edge (PE) router or of the link between the PE and customer edge (CE) routers. This feature also provides the ability to set up multiple backup pseudowires.
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 Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
L2VPNs can provide pseudowire resiliency through their routing protocols. When connectivity between end-to-end PE routers fails, an alternative path to the directed LDP session and the user data can take over. However, there are some parts of the network where this rerouting mechanism does not protect against interruptions in service. The figure below shows those parts of the network that are vulnerable to an interruption in service.
The L2VPN Pseudowire Redundancy feature provides the ability to ensure that the CE2 router in the figure above can always maintain network connectivity, even if one or all the failures in the figure occur.
The L2VPN Pseudowire Redundancy feature enables you to set up backup pseudowires. You can configure the network with redundant pseudowires (PWs) and redundant network elements, which are shown in the three figures below.
The figure below shows a network with redundant pseudowires and redundant attachment circuits.
The figure below shows a network with redundant pseudowires, attachment circuits, and CE routers.
The figure below shows a network with redundant pseudowires, attachment circuits, CE routers, and PE routers.
The L2VPN Pseudowire Redundancy feature enables you to configure a backup pseudowire in case the primary pseudowire fails. When the primary pseudowire fails, the PE router can switch to the backup pseudowire. You can have the primary pseudowire resume operation after it comes back up.
Note |
In Cisco IOS XE Release 2.3, only one backup pseudowire is supported. In Cisco IOS XE Release 2.4 and later releases, up to three backup pseudowires are supported. |
The successful transmission of the Layer 2 frames between PE routers is due to the configuration of the PE routers. You set up the connection, called a pseudowire, between the routers.
The pseudowire-class configuration group specifies the characteristics of the tunneling mechanism, which are:
You must specify the encapsulation mplscommand as part of the pseudowire class for the AToM VCs to work properly. If you omit the encapsulation mplscommand as part of the xconnectcommand, you receive the following error:
% Incomplete command.
Perform this task to configure a pseudowire class.
In Cisco IOS XE Release 2.3, only one backup pseudowire is supported. In Cisco IOS XE Release 2.4 and later releases, up to three backup pseudowires are supported. Use the following steps to configure a single backup pseudowire.
For each transport type, the xconnectcommand is configured slightly differently. The following configuration steps use Ethernet VLAN over MPLS, which is configured in subinterface configuration mode. See Any Transport over MPLS to determine how to configure the xconnect command for other transport types.
In Cisco IOS XE Release 2.4 and later releases, up to three backup pseudowires are supported. You can assign priorities to the backup pseudowires to specify which pseudowire to use first if the primary pseudowire fails. Use the following steps to configure multiple backup pseudowires.
Note |
In Cisco IOS XE Release 2.4, the L2VPN Pseudowire Redundancy: Multiple Backup Pseudowires feature supports only ATM interfaces. > |
To force the router switch over to the backup or primary pseudowire, you can enter the xconnect backup force switchover command in privileged EXEC mode. You can specify either the interface of the primary attachment circuit (AC) to switch to or the IP-address and VC ID of the peer router.
A manual switchover can be made only if the interface or peer specified in the command is actually available and the xconnect will move to the fully active state when the command is entered.
Step 1 | show mpls l2transport vc In this example, the primary attachment circuit is up. The backup attachment circuit is available, but not currently selected. The show output displays as follows: Example: Router# show mpls l2transport vc Local intf Local circuit Dest address VC ID Status ------------- ----------------------- --------------- ---------- ---------- Fe0/0/0.1 Fe VLAN 101 10.0.0.2 101 UP Fe0/0/0.1 Fe VLAN 101 10.0.0.3 201 STANDBY Router# show mpls l2transport vc detail Local interface: fe0/0/0.1 up, line protocol up, fe VLAN 101 up Destination address 10.0.0.2 VC ID: 101, VC status UP . . . Local interface: fe0/0/0.1 down, line protocol down, fe VLAN 101 down Destination address 10.0.0.3 VC ID: 201, VC status down . . . |
Step 2 | show xconnect all In this example, the topology is Attachment Circuit 1 to Pseudowire 1 with a Pseudowire 2 as a backup: Example: Router# show xconnect all Legend: XC ST=Xconnect State, S1=Segment1 State, S2=Segment2 State UP=Up, DN=Down, AD=Admin Down, IA=Inactive, NH=No Hardware XC ST Segment 1 S1 Segment 2 S2 ------+---------------------------------+--+---------------------------------+-- UP pri ac fe0/0/0(FastEthernet) UP mpls 10.55.55.2:1000 UP IA sec ac fe0/0/0(FastEthernet) UP mpls 10.55.55.3:1001 DN In this example, the topology is Attachment Circuit 1 to Attachment Circuit 2 with a Pseudowire backup for Attachment Circuit 2: Example: Router# show xconnect all Legend: XC ST=Xconnect State, S1=Segment1 State, S2=Segment2 State UP=Up, DN=Down, AD=Admin Down, IA=Inactive, NH=No Hardware XC ST Segment 1 S1 Segment 2 S2 ------+---------------------------------+--+---------------------------------+-- UP pri ac Se6/0/0:150(FR DLCI) UP ac Se8/0:150(FR DLCI) UP IA sec ac Se6/0/0:150(FR DLCI) UP mpls 10.55.55.3:7151 DN |
Step 3 | xconnect logging redundancy In addition to the show mpls l2transport vccommand and the show xconnect command, you can use the xconnect logging redundancy command to track the status of the xconnect redundancy group: Example: Router(config)# xconnect logging redundancy When this command is configured, the following messages will be generated during switchover events: Activating the primary member: Example: 00:01:07: %XCONNECT-5-REDUNDANCY: Activating primary member 10.55.55.2:1000 Activating the backup member: Example: 00:01:05: %XCONNECT-5-REDUNDANCY: Activating secondary member 10.55.55.3:1001 |
The following sections show the L2VPN Pseudowire Redundancy feature examples. These configuration examples show how the L2VPN Pseudowire Redundancy feature can be configured with the AToM (like-to-like) and L2VPN Interworking features.
Each of the configuration examples refers to one of the following pseudowire classes:
pseudowire-class mpls encapsulation mpls
pseudowire-class mpls-ip encapsulation mpls interworking ip
The following example shows a High-Level Data Link Control (HDLC) attachment circuit xconnect with a backup pseudowire:
interface Serial4/0/0 xconnect 10.55.55.2 4000 pw-class mpls backup peer 10.55.55.3 4001 pw-class mpls
The following example shows a Frame Relay attachment circuit xconnect with a backup pseudowire:
connect fr-fr-pw Serial6/0/0 225 l2transport xconnect 10.55.55.2 5225 pw-class mpls backup peer 10.55.55.3 5226 pw-class mpls
The following example shows a Fast Ethernet attachment circuit xconnect with L2VPN IP interworking and a backup pseudowire:
interface FastEthernet0/0/0 xconnect 10.55.55.2 1000 pw-class mpls-ip backup peer 10.55.55.3 1001 pw-class mpls-ip
The following example shows an Fast Ethernet VLAN attachment circuit xconnect with L2VPN IP interworking and a backup pseudowire:
interface FastEthernet1/0/0.1 encapsulation dot1Q 200 no ip directed-broadcast xconnect 10.55.55.2 5200 pw-class mpls-ip backup peer 10.55.55.3 5201 pw-class mpls-ip
Description |
Link |
---|---|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 1 | Feature Information for L2VPN Pseudowire Redundancy |
Feature Name |
Releases |
Feature Information |
---|---|---|
L2VPN Pseudowire Redundancy |
Cisco IOS XE Release 2.3 |
This feature enables you to set up your network to detect a failure in the network and reroute the Layer 2 service to another endpoint that can continue to provide service. The following commands were introduced or modified: backup delay (L2VPN local switching), backup peer, show xconnect, xconnect backup force-switchover, xconnect logging redundancy. |
L2VPN Pseudowire Redundancy: Multiple Backup Pseudowires |
Cisco IOS XE Release 2.4 |
This feature enables multiple backup pseudowires. The following command was modified: backup peer. |
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 and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.