Professional Documents
Culture Documents
MPLS BGP Loop Prev
MPLS BGP Loop Prev
If customer use the same AS number between his sites, the BGP loop
prevention mechanism disallows customer sites having identical AS
numbers to be linked by another AS number. In other words, routing
updates from one site would be dropped when the other site receives
them; therefore, connectivity cannot be established between the sites
without additional configuration on the Service provider PE routers.
Topology Diagram:
This configuration scenario demonstrates BGP PE-CE routing for VPN
sites using same BGP AS numbers. The above topology shows Customer A
is using BGP AS 65001 for Site-1 and 65001 at Sites 2.
When you use BGP AS Override functionality, PE2 router will replace AS
65001 in the AS-PATH with its own AS number, which is 1 and send it to
CE2 as shown below in diagram:
Configuration Overview:
Basic Configuration:
PE1 Router: PE2 Router: P Router CE1 Router CE2 Router
! ! ! !
ip cef
interface
ip address ip address ip address ip address
FastEthernet0/0
172.16.1.1 172.16.1.2 10.1.1.2 192.168.1.2
255.255.255.255 255.255.255.255 255.255.255.252 255.255.255.252
ip address
192.168.1.6
! ! mpls ip !
255.255.255.252
network network
10.1.1.1 10.1.1.6
0.0.0.0 area 0 0.0.0.0 area 0
network network
172.16.1.1 172.16.1.2
0.0.0.0 area 0 0.0.0.0 area 0
! !
no no
synchronization synchronization
neighbor neighbor
172.16.1.2 172.16.1.1
remote-as 1 remote-as 1
no auto-summary neighbor
172.16.1.1
! update-source
Loopback0
address-family
vpnv4 no auto-summary
neighbor !
172.16.1.2
activate address-family
vpnv4
neighbor
172.16.1.2 neighbor
send-community 172.16.1.1
extended activate
exit-address- neighbor
family 172.16.1.1
send-community
! extended
mpls ldp
router-id
Loopback0
We have BGP vpnv4 neighbors hip up between PE1 and PE2 can be verify
as shown below:
PE2#conf t
PE2(config)#ip vrf Cust_A
PE2(config-vrf)#description Customer-A
PE2(config-vrf)# rd 1:100
PE2config-vrf)# route-target both 1:100
PE2(config-vrf)#exit
PE2(config)#int fa0/0
PE2(config-if)#ip vrf forwarding Cust_A
PE2(config-if)#ip add 192.168.1.5 255.255.255.252
PE2(config-if)#exit
Configure per VRF BGP routing for Cust_A under the BGP routing process
on PE1 and PE2 and under the BGP VRF routing context mention the
remote BGP CE neighbors and activated as shown below.
PE1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
PE1(config)#router bgp 1
PE1(config-router)#address-family ipv4 vrf Cust_A
PE1(config-router-af)#neighbor 192.168.1.2 remote-as 65001
PE1(config-router-af)#neighbor 192.168.1.2 activate
PE1(config-router-af)#exit
PE2#conf t
Enter configuration commands, one per line. End with CNTL/Z.
PE2(config)#router bgp 1
PE2(config-router)#address-family ipv4 vrf Cust_A
PE2(config-router-af)#nei 192.168.1.6 remote-as 65001
PE2(config-router-af)#nei 192.168.1.6 activate
PE2(config-router-af)#exit
PE1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
PE1(config)#router bgp 1
PE1(config-router)#address-family ipv4 vrf Cust_A
PE1(config-router-af)#neighbor 192.168.1.2 as-override
PE1(config-router-af)#exit
PE2#conf t
Enter configuration commands, one per line. End with CNTL/Z.
PE2(config)#router bgp 1
PE2(config-router)#address-family ipv4 vrf Cust_A
PE2(config-router-af)#neighbor 192.168.1.6 as-override
PE2(config-router-af)#exit
Verification of BGP PE-CE Routing
Implemention:
Check the routing table of VRF Cust_A must show routes learn from
neigboring PE