ICND2 200-105

ICND2 200-105

Introduction to troubleshooting EIGRP

Folks, we have seen a flowchart for troubleshooting already in this curriculum and we will see one now for Enhanced Interior Gateway Routing Protocol, or EIGRP. The flowchart is not what is truly essential, but we are going to talk about some specifics that will really improve your success chances for troubleshooting. So we are going to walk you through these questions that you see here.

Troubleshooting EIGRP - Flowchart

Are interfaces operational? First question on our plate, how do we verify that? It really takes us back to the basics of our interfaces. Are they up-up, up-down, down-down, or administratively down-down? If our interface is operational, what will we be?

Example EIGRP Infrastructure

We will be up-up. We need to be up-up and any dynamic routing protocol demands connectivity, which can only happen on an up-up interface.

Branch#show ip interface brief
Interface              IP-Address      OK? Method Status                Protocol
GigabitEthernet0/0        YES NVRAM  up                    up
Serial0/0         YES NVRAM  up                    up

What has to match for us to form neighbor adjacencies? This is important. We discussed it earlier. In this case will we successfully form a neighbor adjacency?

We're looking at the output of the show ip protocols command, invaluable for validating some of the core configuration of any dynamic routing protocol. And we see that the routing protocol has autonomous system numbers of 1 and 2 depending on what device we're on. So is that going to work?

When I'm looking at the output here, it says Routing Protocol is "eigrp 1", Routing Protocol is "eigrp 2". We're running EIGRP on both Branches in HQ. We can confirm that, but the one and the two, what did those represent?

Branch#show ip protocols
Routing Protocol is "eigrp 1"

HQ#show ip protocols
Routing Protocol is "eigrp 2"

They're the autonomous system numbers. They must match. We will not form an adjacency with a router that has a different autonomous system number. Now there are some other things that could be mismatched. We talked about the metric and what were the little flags, the little dip switches for turning on and off those metric components? They were the K values, right?

Yes, those K values have to match as well. So Branch has 1 0 1 0 0 configured for its key values, then HQ has to have those exact same values for the K values. If they don't, they don't form our neighbor adjacency either. Now something else too that we have to make sure of. Will we form a neighbor adjacency, if we are not on the same subnet?

No. And one last one, if you have authentication, then the authentication is configured differently between the devices, it's not going to work either. So there is pretty much everything. We have an up-up interface, which we just talked about. Proper IP addressing. We really are covering the gamut of things that can affect EIGRP neighborship.

What is the command we use to enable EIGRP on interfaces?

It is the network command.

So if we're looking at the output of show ip eigrp interfaces, I expect to see a certain number of lines that would be associated with the number of interfaces I expect to be enabled for EIGRP. In this case, we're only looking at Serial 0/0 on both devices.

Branch#show ip eigrp interfaces Serial 0/0
EIGRP-IPv4 Interfaces for AS(100)
                        Xmit Queue   Mean   Pacing Time   Multicast    Pending
Interface        Peers  Un/Reliable  SRTT   Un/Reliable   Flow Timer   Routes
Se0/0              1        0/0        20       0/15          95           0

HQ#show ip eigrp interfaces Serial 0/0
EIGRP-IPv4 Interfaces for AS(100)
                        Xmit Queue   Mean   Pacing Time   Multicast    Pending
Interface        Peers  Un/Reliable  SRTT   Un/Reliable   Flow Timer   Routes
Se0/0              1        0/0        24       0/15         119           0

All right. Are those the correct interfaces according to our diagram that are enabled for EIGRP?

I in fact see a problem with this. I see a problem, but wait a minute. We're seeing that they've paired it down to just looking at the serial interface. We usually don't execute command this way. We usually just show the whole command, but if I'm troubleshooting neighborships, I want to make sure that my interface is captured with the network command. And it looks like that's the case because it's not going to show up as a line here unless it was captured with a network command that says, let's include it in our autonomous system by enabling it as a local interface in the routing process for EIGRP.

Folks, will Branch form a neighbor adjacency with HQ based on the following output? Will a neighbor adjacency be formed between Branch and HQ?

Branch#sh ip protocols
Routing Protocol is "eigrp 100"
  Routing for Networks:
  Passive Interface(s):

No, not at all. If you didn't see that, let me explain it. A passive interface is one that will not send or even listen to hellos. When we do not send and receive hellos and even one of those is not done, there's no potential for neighborship out the interface. And so, if we have a passive-interface command pointing to an interface, they would go to another EIGRP-enabled router, there's no hope for us. There's no hope at all. So this in fact would be a configuration issue that we would need to solve and we solve it by just saying no passive interface Serial0/0. We would remove that and we might almost immediately get a sys log message indicating that our neighborship was up and running.