VPLS Autodiscovery: BGP Based
Available Languages
Table Of Contents
Prerequisites for VPLS Autodiscovery: BGP Based
Restrictions for VPLS Autodiscovery: BGP Based
Information About VPLS Autodiscovery: BGP Based
How the VPLS Autodiscovery: BGP Based Feature Works
How Enabling VPLS Autodiscovery Differs from Manually Configuring VPLS
Show Commands Affected by VPLS Autodiscovery: BGP Based
How to Configure VPLS Autodiscovery: BGP Based
Enabling VPLS Autodiscovery: BGP Based
Configuring BGP to Enable VPLS Autodiscovery
Customizing the VPLS Autodiscovery Settings
Configuration Examples for VPLS Autodiscovery: BGP Based
VPLS Autodiscovery: BGP Based: Basic Example
Feature Information for VPLS Autodiscovery: BGP Based
VPLS Autodiscovery: BGP Based
First Published: February 19, 2007Last Updated: February 19, 2007VPLS Autodiscovery enables each Virtual Private LAN Service (VPLS) provider edge (PE) router to discover which other PE routers are part of the same VPLS domain. VPLS Autodiscovery also automatically detects when PE routers are added to or removed from the VPLS domain. You no longer need to manually configure the VPLS and maintain the configuration when a PE router is added or deleted. VPLS Autodiscovery uses the Border Gateway Protocol (BGP) to discover the VPLS members and to set up and tear down pseudowires in the VPLS.
Finding Feature Information in This Module
Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the "Feature Information for VPLS Autodiscovery: BGP Based" section.
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
Prerequisites for VPLS Autodiscovery: BGP Based
•
•
•
•
•
Prerequisites for VPLS Autodiscovery: BGP Based
Before configuring VPLS Autodiscovery, perform the Cisco 7600 router-specific tasks listed in the section called "Virtual Private LAN Services on the Optical Service Modules" in the Cisco 7600 Series Router IOS Software Configuration Guide, 12.2SR.
Restrictions for VPLS Autodiscovery: BGP Based
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
–
–
Information About VPLS Autodiscovery: BGP Based
To understand VPLS Autodiscovery, you should understand the following concepts:
•
•
•
How the VPLS Feature Works
VPLS allows Multiprotocol Label Switching (MPLS) networks to provide multipoint Ethernet LAN services, also known as Transparent LAN Services (TLS). All customer sites in a VPLS appear to be on the same LAN, even though those sites might be in different geographic locations.
How the VPLS Autodiscovery: BGP Based Feature Works
VPLS Autodiscovery enables each VPLS PE router to discover the other PE routers that are part of the same VPLS domain. VPLS Autodiscovery also tracks when PE routers are added to or removed from the VPLS domain. The autodiscovery and signaling functions use BGP to find and track the PE routers.
BGP uses the L2VPN Routing Information Base (RIB) to store endpoint provisioning information, which is updated each time any Layer 2 VFI is configured. Prefix and path information is stored in the L2VPN database, allowing BGP to make decisions on the best path. When BGP distributes the endpoint provisioning information in an update message to all its BGP neighbors, the endpoint information is used to configure a pseudowire mesh to support L2VPN-based services.
The BGP autodiscovery mechanism facilitates the configuration of L2VPN services, which are an integral part of the Cisco IOS Virtual Private LAN Service (VPLS) feature. VPLS enables flexibility in deploying services by connecting geographically dispersed sites as a large LAN over high-speed Ethernet in a robust and scalable IP MPLS network. For more information about BGP and the L2VPN address family in relation to VPLS Autodiscovery, see the following documents:
•
•
How Enabling VPLS Autodiscovery Differs from Manually Configuring VPLS
With VPLS Autodiscovery, you no longer need to manually set up the VPLS. The commands you use to set up VPLS Autodiscovery are similar to those you use to manually configure a VPLS, as shown in Table 1. VPLS Autodiscovery uses neighbor commands in L2VPN address family mode to distribute endpoint information to configure a pseudowire.
When you configure VPLS Autodiscovery, you enter the l2vfi autodiscovery command. This command allows the VFI to learn and advertise the pseudowire endpoints. As a result, you no longer need to enter the neighbor (VPLS) command in L2 VFI configuration mode.
However, the neighbor (VPLS) command is still supported with VPLS Autodiscovery in L2 VFI command mode. You can use the neighbor (VPLS) command to allow PE routers that do not participate in the autodiscovery process to join the VPLS. You can also use the neighbor (VPLS) command with PE routers that have been configured using the Tunnel Selection feature. You can also use the neighbor (VPLS) command in hierarchical VPLS configurations that have U-PE routers that do not participate in the autodiscovery process and have split-horizon forwarding disabled.
Show Commands Affected by VPLS Autodiscovery: BGP Based
VPLS Autodiscovery changes the following show commands:
•
•
•
How to Configure VPLS Autodiscovery: BGP Based
To configure VPLS Autodiscovery, perform the following tasks:
•
•
•
Enabling VPLS Autodiscovery: BGP Based
Perform the following task to enable each VPLS PE router to discover the other PE routers that are part of the same VPLS domain.
Prerequisites
Before configuring VPLS Autodiscovery, perform the Cisco 7600 router-specific tasks listed in the " "Virtual Private LAN Services on the Optical Service Modules" section in the Cisco 7600 Series Router IOS Software Configuration Guide, 12.2SR.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring BGP to Enable VPLS Autodiscovery
In Cisco IOS Release 12.2(33)SRB, the BGP L2VPN address family was introduced with a separate L2VPN RIB that contains endpoint provisioning information for VPLS Autodiscovery. BGP learns the endpoint provisioning information from the L2VPN database which is updated each time a Layer 2 virtual forwarding instance (VFI) is configured. When BGP distributes the endpoint provisioning information in an update message to all its BGP neighbors, the endpoint information is used to configure a pseudowire mesh to support aL2VPN-based services.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
DETAILED STEPS
Customizing the VPLS Autodiscovery Settings
Several commands allow you to customize the VPLS environment. You can specify identifiers for the VPLS domain, the route distinguisher, the route target, and the PE router. Perform the following steps to customize these settings.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
DETAILED STEPS
What To Do Next
Perform the steps in "Configuring BGP to Enable VPLS Autodiscovery" section.
Configuration Examples for VPLS Autodiscovery: BGP Based
The following example shows the configuration of a network using VPLS Autodiscovery:
•
VPLS Autodiscovery: BGP Based: Basic Example
Figure 1 show a basic configuration of VPLS Autodiscovery.
Figure 1 Basic VPLS Autodiscovery Configuration
PE1
l2 router-id 10.1.1.1l2 vfi auto autodiscoveryvpn id 100!pseudowire-class mplsencapsulation mpls!interface Loopback1ip address 10.1.1.1 255.255.255.255!interface Ethernet0/0description Backbone interfaceip address 192.168.0.1 255.255.255.0mpls ip!router ospf 1log-adjacency-changesnetwork 10.1.1.0 0.0.0.255 area 0network 172.16.0.0 0.0.0.255 area 0!router bgp 1no bgp default ipv4-unicastbgp log-neighbor-changesbgp update-delay 1neighbor 10.1.1.2 remote-as 1neighbor 10.1.1.2 update-source Loopback1neighbor 10.1.1.3 remote-as 1neighbor 10.1.1.3 update-source Loopback1!address-family ipv4no synchronizationno auto-summaryexit-address-family!address-family l2vpn vplsneighbor 10.1.1.2 activateneighbor 10.1.1.2 send-community extendedneighbor 10.1.1.3 activateneighbor 10.1.1.3 send-community extendedexit-address-familyPE2
l2 router-id 10.1.1.2l2 vfi auto autodiscoveryvpn id 100!pseudowire-class mplsencapsulation mpls!interface Loopback1ip address 10.1.1.2 255.255.255.255!interface Ethernet0/0description Backbone interfaceip address 192.168.0.2 255.255.255.0mpls ip!router ospf 1log-adjacency-changesnetwork 10.1.1.0 0.0.0.255 area 0network 172.16.0.0 0.0.0.255 area 0!router bgp 1no bgp default ipv4-unicastbgp log-neighbor-changesbgp update-delay 1neighbor 10.1.1.1 remote-as 1neighbor 10.1.1.1 update-source Loopback1neighbor 10.1.1.3 remote-as 1neighbor 10.1.1.3 update-source Loopback1!address-family ipv4no synchronizationno auto-summaryexit-address-family!address-family l2vpn vplsneighbor 10.1.1.1 activateneighbor 10.1.1.1 send-community extendedneighbor 10.1.1.3 activateneighbor 10.1.1.3 send-community extendedexit-address-familyPE3
l2 router-id 10.1.1.3l2 vfi auto autodiscoveryvpn id 100!pseudowire-class mplsencapsulation mpls!interface Loopback1ip address 10.1.1.3 255.255.255.255!interface Ethernet0/0description Backbone interfaceip address 192.168.0.3 255.255.255.0mpls ip!router ospf 1log-adjacency-changesnetwork 10.1.1.0 0.0.0.255 area 0network 172.16.0.0 0.0.0.255 area 0!router bgp 1no bgp default ipv4-unicastbgp log-neighbor-changesbgp update-delay 1neighbor 10.1.1.1 remote-as 1neighbor 10.1.1.1 update-source Loopback1neighbor 10.1.1.2 remote-as 1neighbor 10.1.1.2 update-source Loopback1!address-family ipv4no synchronizationno auto-summaryexit-address-family!address-family l2vpn vplsneighbor 10.1.1.1 activateneighbor 10.1.1.1 send-community extendedneighbor 10.1.1.2 activateneighbor 10.1.1.2 send-community extendedexit-address-familyAdditional References
The following sections provide references related to the VPLS Autodiscovery: BGP Based feature.
Related Documents
Virtual Private LAN Services on the
Cisco 7600 series router"Virtual Private LAN Services on the Optical Service Modules" in the
Cisco 7600 Series Router IOS Software Configuration Guide, 12.2SRL2 VPNs on the Cisco 7600 router
Configuration information for Layer 2 VPNs on the Cisco 7600 router is included in the following documents:
•
•
•
•
Cisco 7600 Series Router SIP, SSC, and SPA Software Configuration Guide•
Cisco 7600 Series Router SIP, SSC, and SPA Software Configuration Guide•
Standards
MIBs
RFCs
RFC 3916
Requirements for Pseudo-wire Emulation Edge-to-Edge (PWE3)
RFC 3981
Pseudo Wire Emulation Edge-to-Edge Architecture
Technical Assistance
Command Reference
This section documents new and modified commands only.
auto-route-target
To enable the automatic generation of a route target (RT), use the auto-route-target command in L2 VFI configuration mode. To remove the automatically generated RTs, use the no form of this command.
auto-route-target
no auto-route-target
Syntax Description
This command has no arguments or keywords.
Command Default
The VPLS Autodiscovery feature automatically generates an RT, so you do not need to enter this command when you configure the feature.
Command Modes
L2 VFI configuration
Command History
Usage Guidelines
This command works with the l2 vfi autodiscovery command, which automatically creates route targets. The no version of the command allows you to remove the automatically generated route targets. You cannot enter this command if route targets have not been automatically created yet.
Examples
The following example removes automatically generated route targets:
no auto-route-targetRelated Commands
l2 router-id
To specify a router ID for the provider edge (PE) router to use with Virtual Private LAN Services (VPLS) Autodiscovery pseudowires, use the l2 router-id command in L2 VFI configuration mode. To revert to the MPLS global router ID, use the no form of this command.
l2 router-id ip-address
no l2 router-id ip-address
Syntax Description
Defaults
The Layer 2 router ID is set to the Multiprotocol Label Switching (MPLS) global router ID.
Command Modes
L2 VFI configuration
Command History
Usage Guidelines
You can configure an arbitrary value in the IP address format for each router. However, each router ID must be unique.
The Layer 2 router ID is used in the forward equivalence class (FEC) 129 encoding for pseudowire signaling It is also used in the network layer reachability information (NLRI) for peer discovery.
Examples
The following example specifies a Layer 2 router ID:
l2 router-id 10.1.1.1Related Commands
l2 vfi autodiscovery
Enables the VPLS PE router to automatically discover other PE routers that are part of the same VPLS domain.
l2 vfi autodiscovery
To enable the Virtual Private LAN Service (VPLS) provider edge (PE) router to automatically discover other PE routers that are part of the same VPLS domain, use the l2 vfi autodiscovery command in global configuration mode. To disable VPLS autodiscovery, use the no form of this command.
l2 vfi vfi-name autodiscovery
no l2 vfi vfi-name autodiscovery
Syntax Description
vfi-name
Specifies the name of the virtual forwarding instance. The virtual forwarding instance (VFI) identifies a group of pseudowires that are associated with a virtual switching instance (VSI).
Command Default
Layer 2 VFI autodiscovery is not enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
VPLS Autodiscovery enables each VPLS PE router to discover other PE routers that are part of the same VPLS domain. VPLS Autodiscovery also automatically detects when PE routers are added to or removed from the VPLS domain. Beginning with Cisco IOS Release 12.2(33)SRB, you no longer need to manually configure the VPLS neighbors and maintain the configuration when a PE router is added or deleted. However, you can still perform manual VPLS configuration even when you enable VPLS Autodiscovery.
Examples
The following example enables VPLS Autodiscovery on a PE router:
l2 vfi vfi2 autodiscoveryRelated Commands
neighbor (VPLS)
To specify the type of tunnel signaling and encapsulation mechanism for each Virtual Private LAN Service (VPLS) peer, use the neighbor command in L2 VFI manual configuration mode. To disable a split horizon, use the no form of this command.
neighbor remote-router-id vc-id {encapsulation encapsulation-type | pw-class pw-name} [no-split-horizon]
no neighbor remote-router-id
Syntax Description
Defaults
Split horizon is enabled.
Command Modes
L2 VFI manual configuration
Command History
Usage Guidelines
In a full-mesh VPLS network, keep split horizon enabled to avoid looping.
With the introduction on VPLS Autodiscovery, the remote router ID no longer needs to be the LDP router ID. The address you specify can be any IP address on the peer, as long as it is reachable. When VPLS Autodiscovery discovers peer routers for the VPLS, the peer router addresses might be any routable address.
Examples
This example shows how to specify the tunnel encapsulation type:
Router(config-vfi)# l2 vfi vfi-1 manualRouter(config-vfi)# vpn 1Router(config-vfi)# neighbor 172.16.10.2 4 encapsulation mplsThis example shows how to disable the Layer 2 split horizon in the data path:
Router(config-vfi)# l2 vfi vfi-1 manualRouter(config-vfi)# vpn 1Router(config-vfi)# neighbor 172.16.10.2 4 encapsulation mpls no-split-horizonRelated Commands
rd (VPLS)
To specify the route distinguisher (RD) to distribute endpoint information in a Virtual Private LAN Service (VPLS) configuration, use the rd command in L2 VFI configuration mode. To remove the manually configured RD and return to the automatically generated RD, use the no form of this command.
rd {autonomous-system-number:nn | ip-address:nn}
no rd {autonomous-system-number:nn | ip-address:nn}
Syntax Description
Command Default
VPLS Autodiscovery automatically generates a route distinguisher using the Border Gateway Protocol (BGP) autonomous system number and the configured virtural forwarding instance (VFI) Virtual Private Network (VPN) ID.
Command Modes
L2 VFI configuration
Command History
Usage Guidelines
VPLS Autodiscovery automatically generates a route distinguisher using the BGP autonomous system number and the configured VFI VPN ID. You can use this command to change the automatically generated route distinguisher.
The same RD value cannot be configured in multiple VFIs.
There are two formats for configuring the route distinguisher argument. It can be configured in the autonomous-system-number:network-number format, or it can be configured in the IP address:network-number format.
An RD is either:
•
•
You can enter an RD in either of these formats:
16-bit-autonomous-system-number:32-bit-number
For example, 101:3.32-bit-IP-address:16-bit-number
For example, 192.168.122.15:1.Examples
The following example shows a configuration using VPLS Autodiscovery that sets the RD to an IP address of 10.4.4.4 and a network address of 70:
l2 vfi SP2 autodiscoveryvpn id 200vpls-id 10.4.4.4:70rd 10.4.5.5:7The following example shows a configuration using VPLS Autodiscovery that sets the RD to an autonomous system number of 2 and a network address of 3:
l2 vfi SP2 autodiscoveryvpn id 200vpls-id 10.4.4.4:70rd 2:3Related Commands
l2 vfi autodiscovery
Enable a VPLS PE router to automatically discover other PE routers that are part of the same VPLS domain.
route-target (VPLS)
To specify a route target (RT) for a Virtual Private LAN Service (VPLS) virtual forwarding instance (VFI), use the route-target command in L2 VFI configuration mode. To revert to the automatcially generated route target, use the no form of this command.
route-target [import | export | both] {autonomous-system-number:nn | ip-address:nn}
no route-target {import | export | both} {autonomous-system-number:nn | ip-address:nn}
Syntax Description
Defaults
VPLS Autodiscovery automatically generates a route target using the lower 6 bytes of the route distinguisher (RD) and VPLS ID.
Command Modes
L2 VFI configuration
Command History
Usage Guidelines
The same route target cannot be configured in multiple VFIs.
The route target specifies a target VPN extended community. Like a route distinguisher, an extended community is composed of either an autonomous system number and an arbitrary number or an IP address and an arbitrary number. You can enter the numbers in either of these formats:
16-bit-autonomous-system-number:32-bit-number
For example, 101:3.32-bit-IP-address:16-bit-number
For example, 192.168.122.15:1.Examples
The following example shows a VPLS Autodiscovery configuration that configures route-target extended community attributes for VFI SP1:
l2 vfi SP1 autodiscoveryvpn id 100vpls-id 5:300rd 4:4route-target 10.1.1.1:29Related Commands
show mpls l2transport vc
To display information about Any Transport over MPLS (AToM) virtual circuits (VCs) and static pseudowires that have been enabled to route Layer 2 packets on a router, use the show mpls l2transport vc command in privileged EXEC mode.
show mpls l2transport vc [vcid vc-id | vcid vc-id-min vc-id-max] [interface name [local-circuit-id]] [destination ip-address | name] [detail]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If you do not specify any keywords or arguments, the command displays a summary of all the VCs.
Examples
The output of the commands varies, depending on the type of Layer 2 packets being transported over the AToM VCs.
The following sample output shows information about the interfaces and VCs that have been configured to transport various Layer 2 packets on the router:
Router# show mpls l2transport vcLocal intf Local circuit Dest address VC ID Status------------- ------------------ --------------- ---------- ----------Se5/0 FR DLCI 55 10.0.0.1 55 UPAT4/0 ATM AAL5 0/100 10.0.0.1 100 UPAT4/0 ATM AAL5 0/200 10.0.0.1 200 UPAT4/0.300 ATM AAL5 0/300 10.0.0.1 300 UPTable 2 describes the fields shown in the display.
The following example shows information about the NSF/SSO and graceful restart capability. The SSO portion indicates when checkpointing data has either been sent (on active) or received (on standby). When SSO data has not been successfully sent or has been released, the SSO information is not shown.
Router# show mpls l2transport vc detailLocal interface: Fa5/1/1.2 down, line protocol down, Eth VLAN 2 upDestination address: 10.55.55.2, VC ID: 1002, VC status: downOutput interface: Se4/0/3, imposed label stack {16}Preferred path: not configuredDefault path: activeTunnel label: imp-null, next hop point2pointCreate time: 02:03:29, last status change time: 02:03:26Signaling protocol: LDP, peer 10.55.55.2:0 downMPLS VC labels: local 16, remote unassignedGroup ID: local 0, remote unknownMTU: local 1500, remote unknownRemote interface description:Sequencing: receive disabled, send disabledSSO Descriptor: 10.55.55.2/1002, local label: 16SSM segment/switch IDs: 12290/8193, PWID: 8193VC statistics:packet totals: receive 0, send 0byte totals: receive 0, send 0packet drops: receive 0, send 0The following example shows information provided when an AToM static pseudowire has been provisioned and the show mpls l2transport vc detail command is used to check the configuration. The Signaling protocol field specifies Manual, because a directed control protocol such as Label Distribution Protocol (LDP) cannot be used to exchange parameters on static pseudowires. The Remote interface description field seen for nonstatic pseudowire configurations is empty, because remote information is exchanged using signaling between the PEs and this is not done on static pseudowires.
Router# show mpls l2transport vc detailLocal interface: Et1/0 up, line protocol up, Ethernet upDestination address: 10.1.1.2, VC ID: 100, VC status: upOutput interface: Et2/0, imposed label stack {10003 150}Preferred path: not configuredDefault path: activeNext hop: 10.0.0.2Create time: 00:18:57, last status change time: 00:16:10Signaling protocol: ManualMPLS VC labels: local 100, remote 150Group ID: local 0, remote 0MTU: local 1500, remote 1500Remote interface description:Sequencing: receive disabled, send disabledVC statistics:packet totals: receive 219, send 220byte totals: receive 20896, send 26694packet drops: receive 0, send 0Table 3 describes the significant fields shown in the display.
The following example shows the command output of the show mpls l2transport vc detail command with when VPLS Autodiscovery has configured the VPLS pseudowires. The output that is specific to VPLS Autodiscovery is show in bold.
Router# show mpls l2transport vc detailLocal interface: VFI my_test VFI upMPLS VC type is VFI, interworking type is EthernetDestination address: 10.3.3.1, VC ID: 123456, VC status: upNext hop PE address: 10.55.55.2Output interface: Et3/0, imposed label stack {17 19}Preferred path: not configuredDefault path:Next hop: 10.1.0.2Create time: 2d05h, last status change time: 2d05hSignaling protocol: LDP, peer 10.55.55.2:0 upMPLS VC labels: local 21, remote 19AGI: type 1, len 8, 0000 3333 4F4E 44C4Local AII: type 1, len 4, 0909 0909 (10.9.9.9)Remote AII: type 1, len 4, 0303 0301 (10.3.3.3)Group ID: local 0, remote 0MTU: local 1500, remote 1500Remote interface description:Sequencing: receive disabled, send disabledVC statistics:packet totals: receive 22611, send 22611byte totals: receive 2346570, send 2853581packet drops: receive 0, send 0Table 4 describes the fields shown in the display.
Related Commands
show vfi
To display information related to the virtual forwarding instance (VFI), use the show vfi command in privileged EXEC mode.
show vfi [vfi-name ]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
This example shows an example of VFI status. The virtual circuit (VC) ID in the output represents the Virtual Private Network (VPN) ID; the VC is identified by the combination of the destination address and the VC ID.
Router# show vfi VPLS-2VFI name: VPLS-2, state: upVPN ID: 100Local attachment circuits:Vlan2Neighbors connected via pseudowires:Peer Address VC ID Split-horizon10.1.1.1 2 Y10.1.1.2 2 Y10.2.2.3 2 NTable 5 describes the significant fields shown in the output.
For the VPLS Autodiscovery feature, the command output of the show vfi command includes autodiscovery information, as shown in the following example:
Router# show vfiLegend: RT= Route-target, S=Split-horizon, Y=Yes, N=NoVFI name: VPLS1, state: up, type: multipointVPN ID: 10, VPLS-ID: 9:10RD: 9:10, RT: 10.10.10.10:150Local attachment circuits:Ethernet0/0.2Neighbors connected via pseudowires:Peer Address VC ID Discovered Router ID S10.7.7.1 10 10.7.7.1 Y10.7.7.2 10 10.1.1.2 Y10.7.7.3 10 10.1.1.3 Y10.7.7.4 10 10.1.1.4 Y10.7.7.5 10 - YVFI name: VPLS2 state: up, type: multipointVPN ID: 11, VPLS-ID: 10.9.9.9:2345RD: 10:11, RT: 10.4.4.4:151Local attachment circuits:Ethernet0/0.3Neighbors connected via pseudowires:Peer Address VC ID Discovered Router ID S10.7.7.1 11 10.7.7.1 Y10.7.7.2 11 10.1.1.5 YTable 6 describes the significant fields in the output related to VPLS Autodiscovery.
Related Commands
show xconnect
Displays information about xconnect attachment circuits and pseudowires.
show xconnect
To display information about xconnect attachment circuits and pseudowires, use the show xconnect command in privileged EXEC mode.
show xconnect {all | interface interface | peer ip-address {all | vcid vcid} | rib} [detail]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The show xconnect command can be used to display, sort, and filter basic information about all xconnect attachment circuits and pseudowires.
You can use the show xconnect command output to help determine the appropriate steps to take to troubleshoot an xconnect configuration problem. More specific information about a particular type of xconnect can be displayed using the commands listed in the "Related Commands" table.
Examples
The following example shows show xconnect all command output in the brief (default) display format:
Router# show xconnect allLegend: XC ST=Xconnect State, S1=Segment1 State, S2=Segment2 StateUP=Up, DN=Down, AD=Admin Down, IA=Inactive, NH=No HardwareXC ST Segment 1 S1 Segment 2 S2------+---------------------------------+--+---------------------------------+--UP ac Et0/0(Ethernet) UP mpls 10.55.55.2:1000 UPUP ac Se7/0(PPP) UP mpls 10.55.55.2:2175 UPUP pri ac Se6/0:230(FR DLCI) UP mpls 10.55.55.2:2230 UPIA sec ac Se6/0:230(FR DLCI) UP mpls 10.55.55.3:2231 DNUP ac Se4/0(HDLC) UP mpls 10.55.55.2:4000 UPUP ac Se6/0:500(FR DLCI) UP l2tp 10.55.55.2:5000 UPUP ac Et1/0.1:200(Eth VLAN) UP mpls 10.55.55.2:5200 UPUP pri ac Se6/0:225(FR DLCI) UP mpls 10.55.55.2:5225 UPIA sec ac Se6/0:225(FR DLCI) UP mpls 10.55.55.3:5226 DNIA pri ac Et1/0.2:100(Eth VLAN) UP ac Et2/0.2:100(Eth VLAN) UPUP sec ac Et1/0.2:100(Eth VLAN) UP mpls 10.55.55.3:1101 UPUP ac Se6/0:150(FR DLCI) UP ac Se8/0:150(FR DLCI) UPTable 7 describes the significant fields shown in the display.
The following example shows show xconnect all command output in the detailed display format:
Router# show xconnect all detailLegend: XC ST=Xconnect State, S1=Segment1 State, S2=Segment2 StateUP=Up, DN=Down, AD=Admin Down, IA=Inactive, NH=No HardwareXCST Segment 1 S1 Segment 2 S2------+---------------------------------+--+---------------------------------+--UP ac Et0/0(Ethernet) UP mpls 10.55.55.2:1000 UPInterworking: ip Local VC label 16Remote VC label 16pw-class: mpls-ipUP ac Se7/0(PPP) UP mpls 10.55.55.2:2175 UPInterworking: ip Local VC label 22Remote VC label 17pw-class: mpls-ipUP pri ac Se6/0:230(FR DLCI) UP mpls 10.55.55.2:2230 UPInterworking: ip Local VC label 21Remote VC label 18pw-class: mpls-ipIA sec ac Se6/0:230(FR DLCI) UP mpls 10.55.55.3:2231 DNInterworking: ip Local VC label unassignedRemote VC label 19pw-class: mpls-ipUP ac Se4/0(HDLC) UP mpls 10.55.55.2:4000 UPInterworking: none Local VC label 18Remote VC label 19pw-class: mplsUP ac Se6/0:500(FR DLCI) UP l2tp 10.55.55.2:5000 UPInterworking: none Session ID: 34183Tunnel ID: 62083Peer name: pe-iou2Protocol State: UPRemote Circuit State: UPpw-class: l2tpUP ac Et1/0.1:200(Eth VLAN) UP mpls 10.55.55.2:5200 UPInterworking: ip Local VC label 17Remote VC label 20pw-class: mpls-ipUP pri ac Se6/0:225(FR DLCI) UP mpls 10.55.55.2:5225 UPInterworking: none Local VC label 19Remote VC label 21pw-class: mplsIA sec ac Se6/0:225(FR DLCI) UP mpls 10.55.55.3:5226 DNInterworking: none Local VC label unassignedRemote VC label 22pw-class: mplsIA pri ac Et1/0.2:100(Eth VLAN) UP ac Et2/0.2:100(Eth VLAN) UPInterworking: none Interworking: noneUP sec ac Et1/0.2:100(Eth VLAN) UP mpls 10.55.55.3:1101 UPInterworking: none Local VC label 23Remote VC label 17pw-class: mplsUP ac Se6/0:150(FR DLCI) UP ac Se8/0:150(FR DLCI) UPInterworking: none Interworking: noneThe additional fields displayed in the detailed output are self-explanatory.
For VPLS Autodiscovery, issuing the show xconnect command with the rib keyword provides Routing Information Base (RIB) detail, as shown in the following:
Router# show xconnect ribLocal Router ID: 10.9.9.9Legend: O=Origin, P=Provisioned, TID=Target ID, B=BGP, Y=Yes, N=NoO P VPLS/VPWS-ID TID Next-Hop Route-Target-+-+---------------------+------------+---------------+---------------------B Y 10:123 10.7.7.7 10.7.7.7 10:123B N 10:123 10.7.7.8 10.7.7.8 10:123B Y 10.100.100.100:1234 10.0.0.2 10.2.2.2 10.111.111.111:1234510.3.3.3 10.8.8.8:34510.4.4.4B Y 128.100.100.100:1234 10.13.1.1 10.1.1.1 10.111.111.111:12345Table 8 describes the significant fields shown in the display.
For VPLS Autodiscovery, issuing the show xconnect command with the rib and detail keywords provides more information about the routing information base, as shown in the following example:Router# show xconnect rib detailLocal Router ID: 10.9.9.9VPLS-ID 10:123, TID 10.7.7.7Next-Hop: 10.7.7.7Hello-Source: 10.9.9.9Route-Target: 10:123Incoming RD: 10:10Forwarder: vfi VPLS1Origin: BGPProvisioned: YesVPLS-ID 10:123, TID 10.7.7.8Next-Hop: 10.7.7.8Hello-Source: 10.9.9.9Route-Target: 10:123Incoming RD: 10:11Forwarder: vfi VPLS1Origin: BGPProvisioned: NoVPLS-ID 10.100.100.100:1234, TID 0.0.0.2Next-Hop: 10.2.2.2, 10.3.3.3, 10.4.4.4Hello-Source: 10.9.9.9Route-Target: 10.111.111.111:12345, 10.8.8.8:345Incoming RD: 10:12Forwarder: vfi VPLS2Origin: BGPProvisioned: YesVPLS-ID 10.100.100.100:1234, TID 10.13.1.1Next-Hop: 10.1.1.1Hello-Source: 10.9.9.9Route-Target: 10.111.111.111:12345Incoming RD: 10:13Forwarder: vfi VPLS2Origin: BGPProvisioned: YesTable 9 describes the significant fields shown in the display.
Related Commands
vpls-id
To assign an identifier to the Virtual Private LAN Service (VPLS) domain, use the vpls-id command in L2 VFI configuration mode. To revert to the default VPLS ID, use the no form of this command.
vpls-id {autonomous-system-number:nn | ip-address:nn}
no vpls-id {autonomous-system-number:nn | ip-address:nn}
Syntax Description
Command Default
The VPLS ID is generated automatically by VPLS Autodiscovery.
Command Modes
L2 VFI configuration
Command History
Usage Guidelines
VPLS Autodiscovery automatically generates a VPLS ID using the Border Gateway Protocol BGP autonomous system number and the configured VFI VPN ID. You can use the vpls-id command to change the automatically generated VPLS ID.
The Label Distribution Protocol (LDP) uses the VPLS ID when signaling VPLS autodiscovered neighbors. The VPLS ID identifies the VPLS domain.
Only one VPLS ID can be configured per virtual forwarding instance (VFI), and the same VPLS ID cannot be configured in multiple VFIs on the same provider edge (PE) router.
The manually configured VPLS ID replaces the internally generated VPLS ID. The manually configured VPLS ID also changes the automatically generated route target (RT).
The vpls-id command defines the attachment group identifier (AGI) for the VPLS domain. Therefore, all provider edge (PE) routers in the same VPLS domain must use the same VPLS ID.
For interautonomous system configurations, you must manually configure the VPLS ID instead of using the automatically generated VPLS ID, because all PE routers do not share the same autonomous system number.
Examples
The following example sets the VPLS ID to the autonomous system and network number 5:300:
vpls-id 5:300The following example sets the VPLS ID to IP address and network number 10.4.4.4:70:vpls-id 10.4.4.4:70Related Commands
xconnect
To bind an attachment circuit to a pseudowire, and to configure an Any Transport over MPLS (AToM) static pseudowire, use the xconnect command in one of the supported configuration modes. To restore the default values, use the no form of this command.
xconnect peer-ip-address vc-id encapsulation {l2tpv3 [manual] | mpls [manual]} [pw-class pw-class-name] [sequencing {transmit | receive | both}]
no xconnect
Syntax Description
Command Default
The attachment circuit is not bound to the pseudowire.
Command Modes
Connect configuration
Interface configuration
l2transport configuration (for ATM)Command History
Usage Guidelines
The combination of the peer-ip-address and vcid arguments must be unique on the router. Each xconnect configuration must have a unique combination of peer-ip-address and vcid configuration.
Note
The same vcid value that identifies the attachment circuit must be configured using the xconnect command on the local and remote PE router. The VC ID creates the binding between a pseudowire and an attachment circuit.
With the introduction of VPLS Autodiscovery in Cisco IOS Release 12.2(33)SRB, the remote router ID need not be the LDP router ID. The address you specify can be any IP address on the peer, as long as it is reachable. When VPLS Autodiscovery discovers peer routers for the VPLS, the peer router addresses might be any routable address.
Note
For L2TPv3, to manually configure the settings used in the attachment circuit, use the manual keyword in the xconnect command. This configuration is called a static session. The router is placed in xconnect configuration mode, and you can then configure the following options:
•
•
•
•
For L2TPv3, if you do not enter the encapsulation l2tpv3 manual keywords in the xconnect command, the data encapsulation type for the L2TPv3 session is taken from the encapsulation type configured for the pseudowire class specified with the pseudowire-class pw-class-name command.
The pw-class keyword with the pw-class-name value binds the xconnect configuration of an attachment circuit to a specific pseudowire class. In this way, the pseudowire class configuration serves as a template that contains settings used by all attachment circuits bound to it with the xconnect command.
Software prior to Cisco IOS Release 12.2(33)(SRB) configured pseudowires dynamically using Label Distribution Protocol (LDP) or another directed control protocol to exchange the various parameters required for these connections. In environments that do not or cannot use directed control protocols, the xconnect command allows provisioning an AToM static pseudowire. Use the manual keyword in the xconnect command to place the router in xconnect configuration mode. MPLS pseudowire labels are configured using the mpls label and (optionally) mpls control-word commands in xconnect configuration mode.
Examples
The following example configures xconnect service for an Ethernet interface by binding the Ethernet circuit to the pseudowire named 123 with a remote peer 10.0.3.201. The configuration settings in the pseudowire class named vlan-xconnect are used.
Router(config)# interface Ethernet0/0.1Router(config-if)# xconnect 10.0.3.201 123 pw-class vlan-xconnectThe following example enters xconnect configuration mode and manually configures L2TPv3 parameters for the attachment circuit:
Router(config)# interface Ethernet 0/0Router(config-if)# xconnect 10.0.3.201 123 encapsulation l2tpv3 manual pw-class ether-pwRouter(config-if-xconn) l2tp id 222 111Router(config-if-xconn) l2tp cookie local 4 54321Router(config-if-xconn) l2tp cookie remote 4 12345Router(config-if-xconn) l2tp hello l2tp-defaultsThe following example enters xconnect configuration mode and manually configures an AToM static pseudowire. The example shows the configuration for only one side of the connection; the configurations on each side of the connection must be symmetrical.
Router# configure terminalRouter(config)# interface Ethernet1/0Router(config-if)# no ip addressRouter(config-if)# xconnect 10.131.191.252 100 encapsulation mpls manual pw-class mplsRouter(config-if-xconn)# mpls label 100 150Router(config-if-xconn)# exit
Router(config-if)# exit
Related Commands
Feature Information for VPLS Autodiscovery: BGP Based
Table 10 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Cisco IOS software images are specific to a Cisco IOS software release, a feature set, and a platform. Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Note
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.
© 2007 Cisco Systems, Inc. All rights reserved.
Feedback