The example in this section shows how to configure the VPLS topology illustrated in Figure 122. The example includes the commands for configuring VPLS on both the local E-series router (PE 1) and the remote E-series router (PE 2).
Figure 122: Topology for VPLS Configuration Example with BGP Signaling
The sample topology in Figure 122 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, PE 1 and PE 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 PE 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 PE 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 PE 1 and PE 2 through the P router across the service provider core. Finally, you must configure BGP on both PE 1 and PE 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.
Use the following commands on the local PE router (PE 1) to configure the VPLS topology shown in Figure 122.
- ! Configure VPLS instance vplsA.
- host1(config)#bridge vplsA vpls transport-virtual-router
default
- host1(config)#bridge vplsA vpls site-range
10
- host1(config)#bridge vplsA vpls site-name
boston site-id 1
- host1(config)#bridge vplsA vpls rd 100:11
- host1(config)#bridge vplsA vpls route-target
both 100:1
- !
- ! Configure VPLS instance vplsB.
- host1(config)#bridge vplsB vpls transport-virtual-router
default
- host1(config)#bridge vplsB vpls site-range
20
- host1(config)#bridge vplsB vpls site-name
boston site-id 1
- host1(config)#bridge vplsB vpls rd 100:12
- host1(config)#bridge vplsB vpls route-target
both 100:2
- !
- ! Configure Fast Ethernet interface 3/0 between PE 1 and
CE 1,
- ! and assign it to vplsA as a trunk interface.
- host1(config)#interface fastEthernet 3/1
- host1(config-if)#bridge-group vplsA subscriber-trunk
- host1(config-if)#exit
- !
- ! Configure bridged Ethernet interface 2/0.12 between PE
1 and CE 2,
- ! and assign it to vplsB as a trunk interface.
- host1(config)#interface atm 2/0.12 point-to-point
- host1(config-subif)#atm pvc 12 0 12 aal5snap
0 0 0
- host1(config-subif)#encapsulation bridge1483
mac-address 0090.1a40.9991
- host1(config-subif)#bridge-group vplsB subscriber-trunk
- host1(config-if)#exit
- !
- ! Configure a loopback interface on PE 1 and assign it
an IP address.
- host1(config)#interface loopback 0
- host1(config-if)#ip address 10.1.1.1 255.255.255.255
- host1(config-if)#exit
- !
- ! Assign the router ID for PE 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 PE
1 and the P router,
- ! and assign it an IP address.
- host1(config)#interface atm 2/0.100 point-to-point
- host1(config-subif)#atm pvc 100 1 100 aal5snap
0 0 0
- host1(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)#mpls
- host1(config-subif)#mpls ldp
- host1(config-subif)#exit
- !
- ! Configure BGP signaling.
- host1(config)#router bgp 100
- host1(config-router)#neighbor 10.2.2.2 remote-as
100
- host1(config-router)#neighbor 10.2.2.2 update-source
loopback 0
- host1(config-router)#neighbor 10.2.2.2 next-hop-self
- host1(config-router)#address-family l2vpn
signaling
- host1(config-router-af)#neighbor 10.2.2.2
activate
- host1(config-router-af)#neighbor 10.2.2.2
next-hop-self
- host1(config-router-af)#exit-address-family
- host1(config-router)#address-family vpls vplsA
- host1(config-router-af)#exit-address-family
- host1(config-router)#address-family vpls vplsB
- host1(config-router-af)#exit-address-family
- host1(config-router)#exit
Use the following commands on the remote PE router (PE 2) to configure the VPLS topology shown in Figure 122.
- ! Configure VPLS instance vplsA. The route target (100:1)
- ! matches the route target configured for vplsA on PE 1.
- host2(config)#bridge vplsA vpls transport-virtual-router
default
- host2(config)#bridge vplsA vpls site-range
10
- host2(config)#bridge vplsA vpls site-name
chicago site-id 2
- host2(config)#bridge vplsA vpls rd 100:21
- host2(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 PE 1.
- host2(config)#bridge vplsB vpls transport-virtual-router
default
- host2(config)#bridge vplsB vpls site-range
20
- host2(config)#bridge vplsB vpls site-name
chicago site-id 2
- host2(config)#bridge vplsB vpls rd 100:22
- host2 (config)#bridge vplsB vpls route-target
both 100:2
- ! Configure Fast Ethernet interface 3/5 between PE 2 and
CE 3,
- ! and assign it to vplsA as a trunk interface.
- host2(config)#interface fastEthernet 3/5
- host2(config-if)#bridge-group vplsA subscriber-trunk
- host2(config-if)#exit
- !
- ! Configure bridged Ethernet interface 2/0.21 between PE
2 and CE 4,
- ! and assign it to vplsB as a trunk interface.
- host2(config)#interface atm 2/0.21 point-to-point
- host2(config-subif)#atm pvc 21 0 21 aal5snap
0 0 0
- host2(config-subif)#encapsulation bridge1483
mac-address 0090.1a40.9992
- host2(config-subif)#bridge-group vplsB subscriber-trunk
- host2(config-if)#exit
- !
- ! Configure a loopback interface on PE 2 and assign it
an IP address.
- host2(config)#interface loopback 0
- host2(config-if)#ip address 10.2.2.2 255.255.255.255
- host2(config-if)#exit
- !
- ! Assign the router ID for PE 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 PE
2 and the P router,
- ! and assign it an IP address.
- host2(config)#interface atm 3/1.100 point-to-point
- host2(config-subif)#atm pvc 100 1 100 aal5snap
0 0 0
- host2(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)#mpls
- host2(config-subif)#mpls ldp
- host2(config-subif)#exit
- !
- ! Configure BGP signaling.
- host2(config)#router bgp 100
- host2(config-router)#neighbor 10.1.1.1 remote-as
100
- host2(config-router)#neighbor 10.1.1.1 update-source
loopback 0
- host2(config-router)#neighbor 10.1.1.1 next-hop-self
- host2(config-router)#address-family l2vpn
signaling
- host2(config-router-af)#neighbor 10.1.1.1
activate
- host2(config-router-af)#neighbor 10.1.1.1
next-hop-self
- host2(config-router-af)#exit-address-family
- host2(config-router)#address-family vpls vplsA
- host2(config-router-af)#exit-address-family
- host2(config-router)#address-family vpls vplsB
- host2(config-router-af)#exit-address-family
- host2(config-router)#exit
 | Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |