The L2VPN Advanced VPLS feature introduces the following enhancements to Virtual Private LAN Services:
Ability to load-balance traffic across multiple core interfaces using equal cost multipaths (ECMP)
Support for redundant provide edge switches
Command line interface enhancements to facilitate configuration of the L2VPN Advanced VPLS feature
The L2VPN Advanced VPLS feature uses Virtual Switch System (VSS) and Flow Aware Transport (FAT) pseudowires to achieve PE redundancy and load-balancing. The following sections explain the concepts and configuration tasks for this feature.
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 Advanced VPLS.
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 Advanced VPLS
This feature requires that you understand how VPLS works. For information about VPLS, see
VPLS Overview
in the Cisco 7600 Series Ethernet Services Plus (ES+) and Ethernet Services Plus T (ES+T) Line Card Configuration Guide.
Configuring the L2VPN Advanced VPLS feature works with MPLS Traffic Engineering tunnels with explicit paths and Generic Routing Encapsulation (GRE tunnels) with static routes to the tunnel destination. For information and configuration steps for MPLS traffic engineering and GRE tunnels, see the following documents:
This features requires two Cisco 6500 series routers be configured as a virtual switch system.
This features requires nonstop forwarding and stateful switchover.
Restrictions for L2VPN Advanced VPLS
Theping and traceroute commands that support the Any Transport over MPLS Virtual Circuit Connection Verification (VCCV) feature are not supported over FAT pseudowires.
The VPLS Autodiscovery feature is not supported with the L2VPN Advanced VPLS feature.
In Cisco IOS Release 12.2(33)SXI4, the following types of configurations are supported:
MPLS core with configuration of PE routers through the neighbor command under transport vpls mode.
MPLS core with configuration of PE routers through MPLS traffic engineering tunnels using explicit paths.
IP core with configuration of PE routers through MPLS over GRE tunnels.
Other configuration methods, including using the route-via command, BGP autodiscovery, or explicit VLAN assignment to a PE egress port, are not supported.
Load-balancing is not supported in the core routers when the core uses IP to transport packets.
The maximum number of links per bundle is limited to eight.
The maximum number of port channels is limited to 32.
The maximum number of VPLS neighbors is limited to 60 minus the number of neighbors configured with the load-balanceflow command.
In Cisco IOS Release 12.2(33)SXI4, the L2VPN Advanced VPLS feature is supported on the Cisco Catalyst 6500 series switches with Supervisor 720-10GE engine.
The L2VPN Advanced VPLS feature supports the following line cards and shared port adapters (SPAs):
7600-SIP-400 (core facing)
Gigabit and 10-gigabit Ethernet SPAs (2X1GE-V1, 2X1GE-V2 and 1X10GE-V2 SPA)
Packet over Sonet (POS) SPAs (2XOC3, 4XOC3, 1XOC12 and 1XOC48 )
Information About L2VPN Advanced VPLS
To configure the L2VPN Advanced VPLS feature, you should understand the following concepts:
FAT pseudowires are used to load-balance traffic in the core when equal cost multipaths are used. The MPLS labels add an additional label to the stack, called the flow label, which contains the flow information of a VC. For more information about FAT pseudowires, see PWE3 Internet-Draft Flow Aware Transport of MPLS Pseudowires
(draft-bryant-filsfils-fat-pw).
Virtual Switch Systems
Two Cisco 6500 series switches can be connected to form one logical switch. One switch is designated as the master, while the other is the slave. The two switches are connected by a virtual switch link (VSL). The two switches are used for link redundancy, load-balancing, and failover.
Enabling Load-Balancing with ECMP and FAT Pseudowires
The following steps explain how to enable load-balancing at the provider edge (PE) routers and on the core routers.
To enable load-balancing on the edge routers, issue the load-balanceflow command. The load-balancing rules are configured through the port-channelload-balance command parameters.
To enable core load-balancing, issue the flow-labelenable command on both PE routers. You must issue the load-balanceflow command with the flow-labelenable command.
SUMMARY STEPS
1.enable
2.configureterminal
3.pseudowire-classname
4.encapsulationmpls
5.load-balanceflow
6.
flow-label enable
7.
end
DETAILED STEPS
Command or Action
Purpose
Step 1
enable
Example:
Router> enable
Enables privileged EXEC mode.
Enter your password if prompted.
Step 2
configureterminal
Example:
Router# configure terminal
Enters global configuration mode.
Step 3
pseudowire-classname
Example:
Router(config)# pseudowire-class class1
Establishes a pseudowire class with a name that you specify and enters pseudowire class configuration mode.
Step 4
encapsulationmpls
Example:
Router(config-pw)# encapsulation mpls
Specifies the MPLS tunneling encapsulation type.
Step 5
load-balanceflow
Example:
Router(config-pw)# load-balance flow
Enables load-balancing on ECMPs.
Step 6
flow-label enable
Example:
Router(config-pw)# flow-label enable
Enables the imposition and disposition of flow labels for the pseudowire.
Step 7
end
Example:
Router(config-pw)# end
Exits pseudowire class configuration mode and enters privileged EXEC mode.
Enabling Port-Channel Load-Balancing
The following task explains how to enable port channel load-balancing, which sets the load-distribution method among the ports in the bundle. If the port-channelload-balance command is not configured, load-balancing occurs with default parameters.
SUMMARY STEPS
1.enable
2.configureterminal
3.port-channelload-balancemethod
4.
exit
DETAILED STEPS
Command or Action
Purpose
Step 1
enable
Example:
Router> enable
Enables privileged EXEC mode.
Enter your password if prompted.
Step 2
configureterminal
Example:
Router# configure terminal
Enters global configuration mode.
Step 3
port-channelload-balancemethod
Example:
Router(config)# port-channel load-balance src-mac
Specifies the load distribution method among the ports in a bundle.
Step 4
exit
Example:
Router(config)# exit
Exits global configuration mode and enters privileged EXEC mode.
Explicitly Specifying the PE Routers As Part of Virtual Ethernet Interface Configuration
There are several ways to specify the route through which traffic should pass.
Explicitly specify the PE routers as part of the virtual Ethernet interface configuration
Configure an MPLS Traffic Engineering tunnel
Configure a GRE tunnel
The following task explains how to explicitly specify the PE routers as part of the virtual Ethernet interface configuration.
Configuring L2VPN Advanced VPLS--Explicitly Specifying Peer PE Routers Example
The following example shows how to create two VPLS domains under VLANs 10 and 20. Each VPLS domain includes two pseudowires to peer PE routers 10.2.2.2 and 10.3.3.3. Load-balancing is enabled through the load-balanceflow and flow-labelenable commands.
Configuring L2VPN Advanced VPLS--Using MPLS over GRE Tunnels Example
The following example shows the creation of two VPLS domains under VLANs 10 and 20. Each VPLS domain includes two pseudowires to peer PEs 10.2.2.2 and 10.3.3.3. The pseudowires are MPLS over GRE tunnels because the core is IP.
pseudowire-class cl1
encap mpls
load-balance flow
!
port-channel load-balance src-mac
!
int tunnel 1
tunnel mode gre ip
mpls ip
tunnel source 10.1.1.1
tunnel destination 10.2.2.2
!
int tunnel 2
tunnel mode gre ip
mpls ip
tunnel source 10.1.1.1
tunnel destination 10.3.3.3
!
interface virtual-ethernet 1
transport vpls mesh
neighbor 10.2.2.2 pw-class cl1
neighbor 10.3.3.3 pw-class cl1
switchport
switchport mode trunk
switchport trunk allowed vlan 10, 20
ip route 10.2.2.2 255.255.255.255 Tunnel1
ip route 10.2.2.2 255.255.255.255 Tunnel2
Additional References
The following sections provide references related to the L2VPN Advanced VPLS feature.
Virtual Private LAN Services (VPLS) Using Label Distribution Protocol (LDP) Singling
Technical Assistance
Description
Link
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.
To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.
Access to most tools on the Cisco Support 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 Advanced VPLS
Feature Name
Releases
Feature Information
L2VPN Advanced VPLS
12.2(33)SXI4
L2VPN Advanced VPLS feature uses Virtual Switch System (VSS) and Flow Aware Transport (FAT) pseudowires to achieve PE redundancy and load-balancing.
In 12.2(33)SXI4, this feature was introduced on the Cisco 6500 series router.
The following commands were introduced:
flow-labelenable,
interfacevirtual-ethernet,
load-balanceflow,
neighbor(VPLStransportmode),
showinterfacevirtual-ethernet, and
transportvplsmesh.