MPLS - EIGRP L3 VPN

 

image

We will build this post on the previous lab MPLS - RIP L3 VPN 

Instead of using RIP for CUST_A VRF we will be using EIGRP

we will enable EIGRP on both R1 and R5

R1

router eigrp 100
 network 0.0.0.0
 no auto-summary

R5

router eigrp 100
 network 0.0.0.0
 no auto-summary

now let’s enable the EIGRP on the PEs for VRF CUST_A

R2

router eigrp 100
 auto-summary
 !
 address-family ipv4 vrf CUST_A
    network 0.0.0.0
  no auto-summary
  autonomous-system 100

R4

router eigrp 50
 no auto-summary
 !
 address-family ipv4 vrf CUST_A
  network 0.0.0.0
  no auto-summary
  autonomous-system 50

As we can see that autonomous system has to be configured under the address family in EIGRP, the autonomous system number has to match the client’s AS for EIGRP neighbor to be up

now let’s mutual redistribute between the BGP-MP and EIGRP on both R2 and R4

R2

router eigrp 100
 no auto-summary
 !
 address-family ipv4 vrf CUST_A
  redistribute bgp 100 metric 1500 10 255 1 1500
router bgp 100
address-family ipv4 vrf CUST_A
redistribute eigrp 100

R4

router eigrp 50
 no auto-summary
 !
 address-family ipv4 vrf CUST_A
  redistribute bgp 100 metric 1500 10 255 1 1500
router bgp 100
address-family ipv4 vrf CUST_A
redis eigrp 50

We can see that that MPLS is working as expected from the output of R1 and R5

R1(config-router)#do sh ip route eigr
     5.0.0.0/24 is subnetted, 1 subnets
D EX    5.5.5.0 [170/1734656] via 10.1.12.2, 00:27:01, FastEthernet0/0
     10.0.0.0/24 is subnetted, 2 subnets
D EX    10.1.45.0 [170/1734656] via 10.1.12.2, 00:27:01, FastEthernet0/0

and R5

R5(config-router)#do sh ip route eig
     1.0.0.0/24 is subnetted, 1 subnets
D EX    1.1.1.0 [170/1734656] via 10.1.45.4, 00:36:47, FastEthernet0/0
     10.0.0.0/24 is subnetted, 2 subnets
D EX    10.1.12.0 [170/1734656] via 10.1.45.4, 00:36:47, FastEthernet0/0

 

R5(config-router)#do trace 1.1.1.1

Type escape sequence to abort.
Tracing the route to 1.1.1.1

  1 10.1.45.4 36 msec 48 msec 24 msec
  2 10.1.34.3 [MPLS: Labels 18/18 Exp 0] 48 msec 84 msec 76 msec
  3 10.1.12.2 [MPLS: Label 18 Exp 0] 72 msec 52 msec 48 msec
  4 10.1.12.1 64 msec *  96 msec

Comments

Post a Comment

Popular posts from this blog

IPv6 EIGRP

Image
In this post we will try to configure IPv6 EIGRP see the different options for the protocol and how these options are almost identical to the IPv4 version of EIGRP configuration R1 ipv6 unicast-routing interface lo0 ipv6 address 2001:1:1::1/64 interface FastEthernet0/0   ipv6 address FE80::1 link-local   ipv6 address FC00:1:12::1/64 ! interface FastEthernet0/1   ipv6 address FE80::1 link-local   ipv6 address FC00:1:13::1/64 !          R2 ipv6 unicast-routing interface lo0 ipv6 address 2001:2:2::2/64 interface FastEthernet0/0   ipv6 address FE80::2 link-local   ipv6 address FC00:1:12::2/64 ! interface FastEthernet0/1   ipv6 address FE80::2 link-local   ipv6 address FC00:1:23::2/64 R3 ipv6 unicast-routing interface lo0 ipv6 address 2001:3:3::3/64 interface lo1 ipv6 address 2001:3:4::3/64 interface lo2 ipv6 address 2001:3:5::3/64 interface FastEthernet0/0   ipv6 address FE80::3 link-...
Read more

BPDU Filter vs BPDU Guard

        Today we will try to explore the difference between these 2 options, BPDU guard and BPDU filter We know that BPDU are used to communicate between switches in L2 networks  to ensure loop free topology. BPDU Guard is used to protect our access (or trunks incase of servers) ports from receiving undesired BPDU packets, this feature is helpful in enforcing your network boundary in access layer BPDU Guard can be enabled on global configuration as well as under the interface configuration BPDU Filter on the other hand is used to filter BPDU packets outbound when configured  in global configuration (after sending 11 BPDU out ) and will filter BPDU inbound/outbound when configured under the interface level To better understand these two features, let’s use this simple topology R1 is connected to SW1 through F0/0 to have R1 send and receive BPDU we will simple configure bridging group 1 on the router and we will join the bridge group when desired to...
Read more

Private VLANS and protected ports

Image
In this post we will try to learn two layer 2 technologies, private vlans and protected ports Private vlans is used to segregate the layer 2 domain within the same vlan so we don’t waste any IP addresses, think about as sub-vlans within the same vlan that share the same layer 3 address. These sub-vlans can be of two kinds                      1- Community 2- Isolated The difference between community and isolated sub-vlans that hosts within community vlan can communicate together however hosts within isolated vlans con’t communicate to each others, also note that hosts from different community vlans can’t communicate/isolated vlans can’t communicate together. The question is how these hosts in community/isolated vlans communicate to the outside world, and the answer is they communicate through the promiscuous port which is part of parent vlan but this port is allowed to communicat...
Read more