CE-PE: Static Routes: First, let's configure the customer's remote sites (CEs): R15 interface Loopback15 ip address 15.15.15.1 255.255.255.0 ! interface FastEthernet0/0 ip address 172.16.158.2 255.255.255.0 ! ip route 0.0.0.0 0.0.0.0 172.16.158.1 ! R16 interface Loopback16 ip address 16.16.16.1 255.255.255.0 ! interface FastEthernet0/0 ip address 172.16.36.2 255.255.255.0 ! ip route 0.0.0.0 0.0.0.0 172.16.36.1 ! As you can see from the above config, The CEs are pushing all traffic to the next hop IP addresses which are the PEs. Next, we should configure the provider edges (PEs facing the remote sites) for both sites: R8 router bgp 100 address-family ipv4 vrf CUSTA100 redistribute static no synchronization network 172.16.158.0 mask 255.255.255.0 exit-address-family ! ip route vrf CUSTA100 15.15.15.0 255.255.255.0 172.16.158.2 ! R13 router bgp 100 address-family ipv4 vrf CUSTA111 redistribute static no synchronization network 172.16.36.0 mask 255.255.255.0 exit-address-family
Tag: L3VPN
L3VPN Part 1 of 5
L3VPN was one of the recent challenges for me in routing and switching world as it introduces many new concepts that change conventional routing as we know it, but with a lot of reading, lab scenarios I became quite comfortable with L3VPN now. To be honest, even though it is really a complex topic, I think most of the books were not doing a good job explaining this. I had to read CCIE cert guide, BGP implementation and then MPLS fundamentals to finally be able to work some lab scenarios. Only then, I started to get the big picture of how L3VPN works. Now I am glad to share what I learnt so far in this post. I will try to