MPLS Lab 011 CE-PE Routing Using eBGP
Image requirements:
VIRL: IOSv 15.7
EVE-NG: Cisco vIOS Router vios-15.6
GNS3: vios-adventerprisek9-m.vmdk.SPA.156-2.T
Description:
BGP will be routing protocol of choice for a new service with another customer, this contract will be including the installation of L3 MPLS VPN services at the three remote locations, client expecting completion of the work as soon as possible, bring your excellent skills, obtained from the previous experience to this project, implement the configuration of VRF, CE-PE routing using eBGP, and MP-BGP protocol.
Topology:
Download Lab: EVE-NG | GNS3
Scenario:
Another contract has been signed, this client needs to use eBGP as the mechanism to exchange routes between the ISP and its private networks, there are three locations needed to be interconnected over the MPLS cloud, the same standard procedure has to be implemented, configuring the VRF, exchange routes with the client, redistribute into BGP VPNv4 tables and finally verify the proper operation of the service.
Lab tasks:
1. Configure VRF CE1 on all PE routers connected to the customer's locations.
2. Assign VRF CE1 to the G0/3 interfaces on the PE routers.
3. Exchange prefixes between PE and CE routers using the eBGP routing protocol.
4. Redistribute routes between the BGP VPNv4 and eBGP routing structures.
5. Verify that customers' sites able to communicate with each other.
Lab procedure:
Task1: Implement VRFs named CE1 at PE2, PE3, PE4.
Configuration:
PE2(config)#vrf definition CE1
PE2(config-vrf)#rd 2000:2000
PE2(config-vrf)#address-family ipv4 unicast
PE2(config-vrf-af)#route-target export 2000:2000
PE2(config-vrf-af)#route-target import 2000:2000
PE2(config-vrf-af)# exit
Complete the same configuration on the remaining LSRs.
Verification:
PE2# show vrf brief
PE2# show vrf detail CE1
Task2: Assign VRF CE1 to the G0/3 interfaces on the PE routers.
Configuration:
PE2(config)#interface g0/3
PE2(config-if)#vrf forwarding CE1
PE2(config-if)#ip address 10.150.0.2 255.255.255.252
PE2(config-if)#exit
Verification:
PE2#show ip route vrf CE1
Routing Table: CE1
10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C 10.150.0.0/30 is directly connected, GigabitEthernet0/3
L 10.150.0.2/32 is directly connected, GigabitEthernet0/3
Task3: Exchange prefixes between PE and CE routers using the eBGP routing protocol.
Configuring nodes PE2 and CE1-A:
PE2(config)#router bgp 64500
PE2(config-router)#address-family ipv4 unicast vrf CE1
PE2(config-router-af)#neighbor 10.150.0.1 remote-as 65000
CE1-A(config)#router bgp 65000
CE1-A(config-router)#neighbor 10.150.0.2 remote-as 64500
CE1-A(config-router)#network 10.150.0.0 mask 255.255.255.252
CE1-A(config-router)#network 10.155.0.0 mask 255.255.255.0
CE1-A(config-router)#
Complete a similar configuration on the remaining LSRs and CE routers.
Autonomous system per customer site:
Verification:
PE2#show bgp vrf CE1 all summary
PE2#show bgp vrf CE1
Task4: Redistribute routes between the BGP VPNv4 and eBGP routing structures.
Actually this happens automatically as soon as you enabled BGP neighborship between the CE and PE routers, routes from BGP VPNv4 table go into BGP table for routing instance CE1 and vise versa, then what prefixes go over MPLS cloud completely controlled by CE nodes unless there is some kind of routing policy implemented at the ISP site.
Verification:
PE2#show bgp vpnv4 unicast vrf CE1
PE2#show bgp vrf CE1 all summary
PE2#show bgp vrf CE1
PE2#show ip route vrf CE1
Task5: Verify that customers' sites able to communicate with each other.
CE1-A#show bgp ipv4 unicast summary
BGP router identifier 10.155.0.1, local AS number 65000
BGP table version is 11, main routing table version 11
6 network entries using 864 bytes of memory
6 path entries using 480 bytes of memory
3/3 BGP path/bestpath attribute entries using 456 bytes of memory
2 BGP AS-PATH entries using 48 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 1848 total bytes of memory
BGP activity 6/0 prefixes, 8/2 paths, scan interval 60 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
10.150.0.2 4 64500 29 28 11 0 0 00:21:50 4
CE1-A#
CE1-A#show bgp ipv4 unicast
BGP table version is 11, local router ID is 10.155.0.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter,
x best-external, a additional-path, c RIB-compressed,
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found
Network Next Hop Metric LocPrf Weight Path
*> 10.150.0.0/30 0.0.0.0 0 32768 i
*> 10.150.0.4/30 10.150.0.2 0 64500 65002 i
*> 10.150.0.8/30 10.150.0.2 0 64500 65001 i
*> 10.155.0.0/24 0.0.0.0 0 32768 i
*> 10.160.0.0/24 10.150.0.2 0 64500 65002 i
*> 10.165.0.0/24 10.150.0.2 0 64500 65001 i
CE1-A#
CE1-A#show ip route bgp
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
a - application route
+ - replicated route, % - next hop override, p - overrides from PfR
Gateway of last resort is not set
10.0.0.0/8 is variably subnetted, 8 subnets, 3 masks
B 10.150.0.4/30 [20/0] via 10.150.0.2, 00:19:13
B 10.150.0.8/30 [20/0] via 10.150.0.2, 00:23:06
B 10.160.0.0/24 [20/0] via 10.150.0.2, 00:15:59
B 10.165.0.0/24 [20/0] via 10.150.0.2, 00:23:06
CE1-A#ping 10.160.0.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.160.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 7/7/7 ms
CE1-A#ping 10.165.0.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.165.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 5/5/6 ms
CE1-A#
Summary:
Using BGP for both CE-PE routing and at the core network of MPLS infrastructure eliminates the need for redistribution between multiple routing protocols. The simple design provides less complex configuration implementation, and it much easier to troubleshoot missing prefixes because the only customer's routers inject the prefixes into the MPLS data structure.
VIRL: IOSv 15.7
EVE-NG: Cisco vIOS Router vios-15.6
GNS3: vios-adventerprisek9-m.vmdk.SPA.156-2.T
Description:
BGP will be routing protocol of choice for a new service with another customer, this contract will be including the installation of L3 MPLS VPN services at the three remote locations, client expecting completion of the work as soon as possible, bring your excellent skills, obtained from the previous experience to this project, implement the configuration of VRF, CE-PE routing using eBGP, and MP-BGP protocol.
Topology:
Download Lab: EVE-NG | GNS3
Scenario:
Another contract has been signed, this client needs to use eBGP as the mechanism to exchange routes between the ISP and its private networks, there are three locations needed to be interconnected over the MPLS cloud, the same standard procedure has to be implemented, configuring the VRF, exchange routes with the client, redistribute into BGP VPNv4 tables and finally verify the proper operation of the service.
Lab tasks:
1. Configure VRF CE1 on all PE routers connected to the customer's locations.
2. Assign VRF CE1 to the G0/3 interfaces on the PE routers.
3. Exchange prefixes between PE and CE routers using the eBGP routing protocol.
4. Redistribute routes between the BGP VPNv4 and eBGP routing structures.
5. Verify that customers' sites able to communicate with each other.
Lab procedure:
Task1: Implement VRFs named CE1 at PE2, PE3, PE4.
Configuration:
PE2(config)#vrf definition CE1
PE2(config-vrf)#rd 2000:2000
PE2(config-vrf)#address-family ipv4 unicast
PE2(config-vrf-af)#route-target export 2000:2000
PE2(config-vrf-af)#route-target import 2000:2000
PE2(config-vrf-af)# exit
Complete the same configuration on the remaining LSRs.
Verification:
PE2# show vrf brief
PE2# show vrf detail CE1
Task2: Assign VRF CE1 to the G0/3 interfaces on the PE routers.
Configuration:
PE2(config)#interface g0/3
PE2(config-if)#vrf forwarding CE1
PE2(config-if)#ip address 10.150.0.2 255.255.255.252
PE2(config-if)#exit
Verification:
PE2#show ip route vrf CE1
Routing Table: CE1
10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C 10.150.0.0/30 is directly connected, GigabitEthernet0/3
L 10.150.0.2/32 is directly connected, GigabitEthernet0/3
Task3: Exchange prefixes between PE and CE routers using the eBGP routing protocol.
Configuring nodes PE2 and CE1-A:
PE2(config)#router bgp 64500
PE2(config-router)#address-family ipv4 unicast vrf CE1
PE2(config-router-af)#neighbor 10.150.0.1 remote-as 65000
CE1-A(config)#router bgp 65000
CE1-A(config-router)#neighbor 10.150.0.2 remote-as 64500
CE1-A(config-router)#network 10.150.0.0 mask 255.255.255.252
CE1-A(config-router)#network 10.155.0.0 mask 255.255.255.0
CE1-A(config-router)#
Complete a similar configuration on the remaining LSRs and CE routers.
Autonomous system per customer site:
| Site | AS Number |
| CE1-A | 65000 |
| CE1-B | 65001 |
| CE1-C | 65002 |
Verification:
PE2#show bgp vrf CE1 all summary
PE2#show bgp vrf CE1
Task4: Redistribute routes between the BGP VPNv4 and eBGP routing structures.
Actually this happens automatically as soon as you enabled BGP neighborship between the CE and PE routers, routes from BGP VPNv4 table go into BGP table for routing instance CE1 and vise versa, then what prefixes go over MPLS cloud completely controlled by CE nodes unless there is some kind of routing policy implemented at the ISP site.
Verification:
PE2#show bgp vpnv4 unicast vrf CE1
PE2#show bgp vrf CE1 all summary
PE2#show bgp vrf CE1
PE2#show ip route vrf CE1
Task5: Verify that customers' sites able to communicate with each other.
CE1-A#show bgp ipv4 unicast summary
BGP router identifier 10.155.0.1, local AS number 65000
BGP table version is 11, main routing table version 11
6 network entries using 864 bytes of memory
6 path entries using 480 bytes of memory
3/3 BGP path/bestpath attribute entries using 456 bytes of memory
2 BGP AS-PATH entries using 48 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 1848 total bytes of memory
BGP activity 6/0 prefixes, 8/2 paths, scan interval 60 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
10.150.0.2 4 64500 29 28 11 0 0 00:21:50 4
CE1-A#
CE1-A#show bgp ipv4 unicast
BGP table version is 11, local router ID is 10.155.0.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter,
x best-external, a additional-path, c RIB-compressed,
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found
Network Next Hop Metric LocPrf Weight Path
*> 10.150.0.0/30 0.0.0.0 0 32768 i
*> 10.150.0.4/30 10.150.0.2 0 64500 65002 i
*> 10.150.0.8/30 10.150.0.2 0 64500 65001 i
*> 10.155.0.0/24 0.0.0.0 0 32768 i
*> 10.160.0.0/24 10.150.0.2 0 64500 65002 i
*> 10.165.0.0/24 10.150.0.2 0 64500 65001 i
CE1-A#
CE1-A#show ip route bgp
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
a - application route
+ - replicated route, % - next hop override, p - overrides from PfR
Gateway of last resort is not set
10.0.0.0/8 is variably subnetted, 8 subnets, 3 masks
B 10.150.0.4/30 [20/0] via 10.150.0.2, 00:19:13
B 10.150.0.8/30 [20/0] via 10.150.0.2, 00:23:06
B 10.160.0.0/24 [20/0] via 10.150.0.2, 00:15:59
B 10.165.0.0/24 [20/0] via 10.150.0.2, 00:23:06
CE1-A#ping 10.160.0.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.160.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 7/7/7 ms
CE1-A#ping 10.165.0.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.165.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 5/5/6 ms
CE1-A#
Summary:
Using BGP for both CE-PE routing and at the core network of MPLS infrastructure eliminates the need for redistribution between multiple routing protocols. The simple design provides less complex configuration implementation, and it much easier to troubleshoot missing prefixes because the only customer's routers inject the prefixes into the MPLS data structure.
Comments
Post a Comment