VPLS Configuration Example with BGP Signaling
The example in this section shows how to configure the VPLS topology illustrated in Figure 121. The example includes the commands for configuring VPLS on both the local E-series router (VE 1) and the remote E-series router (VE 2).
![]()
Topology Overview of VPLS with BGP Signaling
The sample topology in Figure 121 includes two VPLS domains, VPLS A and VPLS B. VPLS A connects CE 1, at the edge of Customer A's Boston site, with CE 3, at the edge of Customer A's Chicago site. Similarly, VPLS B connects CE 2, at the edge Customer B's Boston site, with CE 4, at the edge of Customer B's Chicago site.
The E-series routers in the topology, VE 1 and VE 2, each participate in both the VPLS A domain and the VPLS B domain. The example configures a total of four separate VPLS instances, one for each VPLS domain in which the VE router participates. The instances for the VPLS A domain are named vplsA, and the instances for the VPLS B domain are named vplsB.
For each VPLS instance, an Ethernet or bridged Ethernet network interface provides a connection to the associated CE device. Each VPLS instance maintains its own set of forwarding tables and filters to learn the network topology, in a manner that is similar to a bridge group used for transparent bridging.
Each VE router in the sample topology also has an ATM core-facing interface that connects it to the provider (P) router in the service provider core. You must configure MPLS LSPs on the core-facing interfaces to connect VE 1 and VE 2 through the P router across the service provider core. Finally, you must configure BGP on both VE 1 and VE 2 to provide signaling for both VPLS domains.
After you configure the bridging, MPLS, and BGP components of VPLS, the router automatically generates a VPLS virtual core interface for each VPLS instance. The VPLS virtual core interface represents all of the MPLS tunnels from the router to the remote VE device.
Configuration on VE 1 (Local VE Router)
Use the following commands on the local VE router (VE 1) to configure the VPLS topology shown in Figure 121.
! Configure VPLS instance vplsA.host1(config)#bridge vplsA vpls transport-virtual-router defaulthost1(config)#bridge vplsA vpls site-range 10host1(config)#bridge vplsA vpls site-name boston site-id 1host1(config)#bridge vplsA vpls rd 100:11host1(config)#bridge vplsA vpls route-target both 100:1!! Configure VPLS instance vplsB.host1(config)#bridge vplsB vpls transport-virtual-router defaulthost1(config)#bridge vplsB vpls site-range 20host1(config)#bridge vplsB vpls site-name boston site-id 1host1(config)#bridge vplsB vpls rd 100:12host1(config)#bridge vplsB vpls route-target both 100:2!! Configure Fast Ethernet interface 3/0 between VE 1 and CE 1,! and assign it to vplsA as a trunk interface.host1(config)#interface fastEthernet 3/1host1(config-if)#bridge-group vplsA subscriber-trunkhost1(config-if)#exit!! Configure bridged Ethernet interface 2/0.12 between VE 1 and CE 2,! and assign it to vplsB as a trunk interface.host1(config)#interface atm 2/0.12 point-to-pointhost1(config-subif)#atm pvc 12 0 12 aal5snap 0 0 0host1(config-subif)#encapsulation bridge1483 mac-address 0090.1a40.9991host1(config-subif)#bridge-group vplsB subscriber-trunkhost1(config-if)#exit!! Configure a loopback interface on VE 1 and assign it an IP address.host1(config)#interface loopback 0host1(config-if)#ip address 10.1.1.1 255.255.255.255host1(config-if)#exit!! Assign the router ID for VE 1 using the IP address of the loopback interface.host1(config)#ip router-id 10.1.1.1!! Enable MPLS on the default virtual router.host1(config)#mpls!! Configure ATM core-facing interface 2/0.100 between VE 1 and the P router,! and assign it an IP address.host1(config)#interface atm 2/0.100 point-to-pointhost1(config-subif)#atm pvc 100 1 100 aal5snap 0 0 0host1(config-subif)#ip address 192.168.1.1 255.255.255.0!! Enable MPLS, LDP, and topology-driven LSPs on the core-facing interface.host1(config-subif)#mplshost1(config-subif)#mpls ldphost1(config-subif)#exit!! Configure BGP signaling.host1(config)#router bgp 100host1(config-router)#neighbor 10.2.2.2 remote-as 100host1(config-router)#neighbor 10.2.2.2 update-source loopback 0host1(config-router)#neighbor 10.2.2.2 next-hop-selfhost1(config-router)#address-family l2vpn signalinghost1(config-router-af)#neighbor 10.2.2.2 activatehost1(config-router-af)#neighbor 10.2.2.2 next-hop-selfhost1(config-router-af)#exit-address-familyhost1(config-router)#address-family vpls vplsAhost1(config-router-af)#exit-address-familyhost1(config-router)#address-family vpls vplsBhost1(config-router-af)#exit-address-familyhost1(config-router)#exitConfiguration on VE 2 (Remote VE Router)
Use the following commands on the remote VE router (VE 2) to configure the VPLS topology shown in Figure 121.
! Configure VPLS instance vplsA. The route target (100:1)! matches the route target configured for vplsA on VE 1.host2(config)#bridge vplsA vpls transport-virtual-router defaulthost2(config)#bridge vplsA vpls site-range 10host2(config)#bridge vplsA vpls site-name chicago site-id 2host2(config)#bridge vplsA vpls rd 100:21host2(config)#bridge vplsA vpls route-target both 100:1!! Configure VPLS instance vplsB. The route target (100:2)! matches the route target configured for vplsB on VE 1.host2(config)#bridge vplsB vpls transport-virtual-router defaulthost2(config)#bridge vplsB vpls site-range 20host2(config)#bridge vplsB vpls site-name chicago site-id 2host2(config)#bridge vplsB vpls rd 100:22host2 (config)#bridge vplsB vpls route-target both 100:2! Configure Fast Ethernet interface 3/5 between VE 2 and CE 3,! and assign it to vplsA as a trunk interface.host2(config)#interface fastEthernet 3/5host2(config-if)#bridge-group vplsA subscriber-trunkhost2(config-if)#exit!! Configure bridged Ethernet interface 2/0.21 between VE 2 and CE 4,! and assign it to vplsB as a trunk interface.host2(config)#interface atm 2/0.21 point-to-pointhost2(config-subif)#atm pvc 21 0 21 aal5snap 0 0 0host2(config-subif)#encapsulation bridge1483 mac-address 0090.1a40.9992host2(config-subif)#bridge-group vplsB subscriber-trunkhost2(config-if)#exit!! Configure a loopback interface on VE 2 and assign it an IP address.host2(config)#interface loopback 0host2(config-if)#ip address 10.2.2.2 255.255.255.255host2(config-if)#exit!! Assign the router ID for VE 2 using the IP address of the loopback interface.host2(config)#ip router-id 10.2.2.2!! Enable MPLS on the default virtual router.host2(config)#mpls!! Configure ATM core-facing interface 3/1.100 between VE 2 and the P router,! and assign it an IP address.host2(config)#interface atm 3/1.100 point-to-pointhost2(config-subif)#atm pvc 100 1 100 aal5snap 0 0 0host2(config-subif)#ip address 192.168.2.2 255.255.255.0!! Enable MPLS, LDP, and topology-driven LSPs on the on the core-facing interface.host2(config-subif)#mplshost2(config-subif)#mpls ldphost2(config-subif)#exit!! Configure BGP signaling.host2(config)#router bgp 100host2(config-router)#neighbor 10.1.1.1 remote-as 100host2(config-router)#neighbor 10.1.1.1 update-source loopback 0host2(config-router)#neighbor 10.1.1.1 next-hop-selfhost2(config-router)#address-family l2vpn signalinghost2(config-router-af)#neighbor 10.1.1.1 activatehost2(config-router-af)#neighbor 10.1.1.1 next-hop-selfhost2(config-router-af)#exit-address-familyhost2(config-router)#address-family vpls vplsAhost2(config-router-af)#exit-address-familyhost2(config-router)#address-family vpls vplsBhost2(config-router-af)#exit-address-familyhost2(config-router)#exit