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-local
 ipv6 address FC00:1:13::3/64
!
interface FastEthernet0/1
 ipv6 address FE80::3 link-local
 ipv6 address FC00:1:23::3/64

We will start off by enabling IPv6 on the three routers, the only way to enable eigrp IPv6 is under the interface level since network command under the process level is not supported

so on R1, R2 and R3

interf f0/0
ipv6 eigrp 1
!
interf f0/1
ipv6 eigrp 1
!
interf lo0
ipv6 eigrp 1

and on R3

interf lo1
ipv6 eigrp 1
!
interf lo2
ipv6 eigrp 1

we will check the IPv6 eigrp neighbors to make sure that we have adjacency on the three routers

R1#show ipv6 eigrp neighbors
IPv6-EIGRP neighbors for process 1
% EIGRP 1 is in SHUTDOWN

This is the output of R1, SHUTDOWN means that the eigrp process it self is shutdown, this option is only available in eigrp and all new eigrp processes are shutdown by default, we need to un-shut the eigrp process

on R1, R2 and R3

ipv6 router eirgp 1

no shutdown

now let’s check if the the eigrp neighbors would come up now

R3#show ipv6 eigrp neighbors
IPv6-EIGRP neighbors for process 1
% No router ID for EIGRP 1

if we check R1 and R2 we would see the same, no Router-ID and the reason is that EIGRP IPv6 and OSPV v3 is using the IPv4 32 bits router-id and because we don’t have any IPv4 interfaces configured and we haven’t configured router-ID manually the process couldn’t be started

we need to fix this on the three routers

R1(config)#ipv6 router eigrp 1
R1(config-rtr))#router-id 1.1.1.1

R2(config)#ipv6 router eigrp 1
R2(config-rtr)#router-id 2.2.2.2

R3(config)#ipv6 router eigrp 1
R3(config-rtr)#router-id 3.3.3.3

once we started configuring the router-id we should started seeing the eigrp neighbors coming up

on R1

R1(config-rtr)#do sh ipv6 eig ne
IPv6-EIGRP neighbors for process 1
H   Address                 Interface       Hold Uptime   SRTT   RTO  Q  Seq
                                            (sec)         (ms)       Cnt Num
1   Link-local address:     Fa0/1             14 00:12:40   30   200  0  8
    FE80::3
0   Link-local address:     Fa0/0             13 00:12:55   41   246  0  10
    FE80::2

and R2

R2(config)#do sh ipv6 eig nei
IPv6-EIGRP neighbors for process 1
H   Address                 Interface       Hold Uptime   SRTT   RTO  Q  Seq
                                            (sec)         (ms)       Cnt Num
1   Link-local address:     Fa0/1             10 00:00:13   39   234  0  9
    FE80::3
0   Link-local address:     Fa0/0             13 00:08:13   41   246  0  11
    FE80::1

All other EIGRP parameters remain the same from IPv4 EIGRP, variance, the K values used for the metric, one thing that we need to note is with the summary address we don’t have the leak-map option like in IPv4 EIGRP

Comments

Post a Comment

Popular posts from this blog

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 test our configuration BPDU
Read more

BGP Weight Attribute

Image
Before we start the lab let's see the BGP path selection process If the path specifies a next hop that is inaccessible, drop the update. •Prefer the path with the highest weight. •If the weights are the same, prefer the path with the largest local preference. •If the local preferences are the same, prefer the path that was originated by BGP running on this router. •If no route was originated, prefer the route that has the shortest AS_path. •If all paths have the same AS_path length, prefer the path with the lowest origin code (where IGP is lower than EGP, and EGP is lower than incomplete). •If the origin codes are the same, prefer the path with the lowest MED attribute. •If the paths have the same MED, prefer the external path over the internal path. •If the paths are still the same, prefer the path through the closest IGP neighbor. •Prefer the path with the lowest IP address, as specified by the BGP router ID. I read this on CCIE Pursuit blog We Love Oranges As O
Read more

OSPF–Point To Multipoint Non-Broadcast

Image
Using same setup that we have been using in the last 3 posts, we will change the network type to point-to-multipoint Non-Broadcast we will also add a Ethernet link between R2 and R3 and enable OSPF on it Our final configuration should be something like this R1 interface Serial0/0   no ip address   encapsulation frame-relay   no frame-relay inverse-arp ! interface Serial0/0.123 multipoint   ip address 10.1.123.1 255.255.255.0   ip ospf network point-to-multipoint non-broadcast   ip ospf 1 area 0   frame-relay map ip 10.1.123.2 102   frame-relay map ip 10.1.123.3 103 !          router ospf 1   router-id 1.1.1.1   log-adjacency-changes   neighbor 10.1.123.2   neighbor 10.1.123.3 R2 interface Serial0/0   no ip address   encapsulation frame-relay   no frame-relay inverse-arp ! interface Serial0/0.123 multipoint   ip address 10.1.123.2 255.255.255.0   ip ospf network point-to-multipoint non-broadcast   ip ospf 1 area 0   frame-relay map ip 10.1.123.1 201 R3 interface
Read more