EIGRP Router ID

Each EIGRP router has a unique 32-bit router ID (RID) number that is represented the same way as an IP address.

EIGRP automatically selects the highest IP address on any active loopback interface as the router ID. If there is no loopback interface then the highest IP address on any active interface is used. You can also overrule this by manually setting the router ID.

Even though each router should have a unique router ID, it doesn’t matter all that much. Two EIGRP routers with the same router ID will still form a neighbor adjacency. When we use OSPF, the router ID is important to know if you are digging in the OSPF LSDB. When we use EIGRP we don’t really care about the router ID, you don’t need to know it if you are looking at the topology table.

There is one exception to this, when an EIGRP router receives an external route (redistributed route) from a neighbor that has the same router ID then it will not accept it. This is an interesting scenario for a troubleshooting lab so let’s take a closer look at it.

Configuration

To demonstrate this, I’ll use the following two routers:

R1 R2 loopback behind R2

We only need two routers for this. R2 has a loopback interface that we will redistribute in EIGRP. Let’s look at a “normal” scenario first where we have unique router IDs.

EIGRP Unique router IDs

Let’s start with the EIGRP configuration:

R1(config)#router eigrp 12
R1(config-router)#no auto-summary 
R1(config-router)#network 192.168.12.0
R2(config)#router eigrp 12
R2(config-router)#no auto-summary              
R2(config-router)#network 192.168.12.0         
R2(config-router)#redistribute connected metric 1 1 1 1 1

Let’s check the router IDs of these routers:

R1#show ip eigrp topology | include ID
IP-EIGRP Topology Table for AS(12)/ID(192.168.12.1)
R2#show ip eigrp topology | include ID
IP-EIGRP Topology Table for AS(12)/ID(2.2.2.2)

R1 is using the IP address on its FastEthernet interface as the router ID, R2 is using the one on its loopback interface. Let’s verify that R1 has learned network 2.2.2.0 /24:

R1#show ip route eigrp 
     2.0.0.0/24 is subnetted, 1 subnets
D EX    2.2.2.0 [170/2560025856] via 192.168.12.2, 00:04:52, FastEthernet0/0

There it is as expected. This is how it should work…now let’s mess things up by using a duplicate router ID!

EIGRP Duplicate router IDs

Let’s change the router ID of R2 so that it’s the same as the one on R1:

R2(config)#router eigrp 12
R2(config-router)#eigrp router-id 192.168.12.1
R2#show ip eigrp topology 
IP-EIGRP Topology Table for AS(12)/ID(192.168.12.1)
R2#clear ip eigrp neighbors

Even though the router ID is the same, our routers will still become neighbors:

R1#show ip eigrp neighbors 
IP-EIGRP neighbors for process 12
H   Address                 Interface       Hold Uptime   SRTT   RTO  Q  Seq
                                            (sec)         (ms)       Cnt Num
0   192.168.12.2            Fa0/0             14 00:00:05   73   438  0  25

Unfortunately R1 no longer has network 2.2.2.0 /24 in its topology or routing table:

R1#show ip eigrp topology 
IP-EIGRP Topology Table for AS(12)/ID(192.168.12.1)

Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
       r - reply Status, s - sia Status 

P 192.168.12.0/24, 1 successors, FD is 281600
        via Connected, FastEthernet0/0
R1#show ip route eigrp
    

This issue might be hard to spot. You could check all the router IDs by looking at the EIGRP topology table of each router but if you don’t have access to the router that is doing the redistribution then you are out of luck. Maybe a debug will help?

R1#debug ip eigrp    
IP-EIGRP Route Events debugging is on
R1#clear ip eigrp neighbors 
IP-EIGRP(Default-IP-Routing-Table:12): Processing incoming UPDATE packet
IP-EIGRP(Default-IP-Routing-Table:12): ExtS 2.2.2.0/24 M 2560025856 - 2560000000 25856 SM 2560000256 - 2560000000 256

Our debug tells us that we receive 2.2.2.0 /24 so this doesn’t help us, everything looks ok here. There is one hidden command however that will give us the answer:

We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 662 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

519 Sign Ups in the last 30 days

satisfaction-guaranteed
100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!

Tags: ,


Forum Replies

  1. Hey Rene Thanks for getting back. Sorry I did not frame my question correctly. I will try again ^_^.

    So I was trying to make topology diagram using the OSPF LSDB. I was not able to get the subnet mask for link R1 <–> R5. Then I went through the blog again and found this

    “R1 also has two stub networks, one to represent each of the point-to-point links shown above. Without these entries, other routers would not have routing information for the 10.0.15.0/24 and 10.0.12.0/24 subnets.”

    That’s what I was missing. I misunderstood the following LSA information with ST

    ... Continue reading in our forum

  2. Hello Rene,

    I have three questions:

    1. Can you please explain what vertex means? maybe an example will help me understand the concept.

    2. When you start analyzing R2 and it LSDB, how you determine that R2 has two networks with the same subnet. I can see R1-R2 subnet is 10.0.12.0/24 and LAN R2 is 10.12.0/24, as well.

    I got confused in this part:

    Link connected to: a Stub Network
    (Link ID) Network/subnet number: 10.0.12.0
    (Link Data) Network Mask: 255.255.255.0
    Number of TOS metrics: 0
    TOS 0 Metrics: 10

    I think the above entry in 2.2.2.2 is referring to the R1-R2

    ... Continue reading in our forum

  3. Mark,
    Since LSA Type-2s are only associated with DRs, your statement is correct for networks where a DR has been elected (network type Broadcast, for example). In other network types (Point-to-Point, for example), it would be LSA Type 1.

  4. Hello Chaminda

    You are correct. The output should actually read:

    Link connected to: a Stub Network
     (Link ID) Network/subnet number: 10.0.35.0
     (Link Data) Network Mask: 255.255.255.0
      Number of TOS metrics: 0
       TOS 0 Metrics: 17
    

    where the (Link ID) Network/subnet number should be 10.0.35.0 and not 10.0.15.0.

    I will let Rene know to change t

    ... Continue reading in our forum

  5. Thank you for the explanation , Laz

18 more replies! Ask a question or join the discussion by visiting our Community Forum