Lab ID: [Link].

Troubleshooting EIGRP Routing

Objective
Analyze, locate, and fix Enhanced Interior Gateway Routing Protocol (EIGRP) operation problems in the
network.

Lab Topology
The topology diagram below represents the NetMap in the Simulator.

Command Summary
Command Description
configure terminal enters global configuration mode from privileged EXEC mode
[no] debug eigrp packets [terse | displays debugging information about EIGRP packets; the hello
hello] option limits the output to display only information about hello
packets, and the terse option displays information about all EIGRP
packets except hello packets; the no form turns off debugging
enable enters privileged EXEC mode
end ends and exits configuration mode
exit exits one level in the menu structure
key chain key-chain-name creates or modifies a key chain
key key-id creates or modifies a key chain key

1 Boson NetSim Lab Manual

 Command Description
key-string key-string-text specifies the authentication string for the key
[no] metric weights tos k1 k2 k3 tunes EIGRP metric calculations; the no form resets the metric
k4 k5 calculations to their defaults
ping ip-address sends an Internet Control Message Protocol (ICMP) echo request
to the specified address
router eigrp autonomous-system- enters router configuration mode for EIGRP
number
show ip eigrp interfaces [type displays information about interfaces configured for EIGRP
number] [as-number] detail
show ip eigrp neighbors displays information about EIGRP neighbors
show ip interface brief displays a brief summary of interface status and configuration
show key chain displays authentication key information
show running-config displays the active configuration file

The IP addresses and subnet masks used in this lab are shown in the table below:

IP Addresses
Device Interface IP Address Subnet Mask
BBRouter1 Serial 0/0 [Link] [Link]
BBRouter2 Serial 0/0 [Link] [Link]
Router1 Serial 0/0 [Link] [Link]
Serial 0/1 [Link] [Link]
Serial 0/3 [Link] [Link]
Router2 Serial 0/1 [Link] [Link]
FastEthernet 1/0 [Link] [Link]
Router3 Serial 0/1 [Link] [Link]
FastEthernet 1/0 [Link] [Link]
Router4 Serial 0/1 [Link] [Link]
FastEthernet 1/0 [Link] [Link]

2 Boson NetSim Lab Manual

 Lab Tasks
Complex network troubleshooting requires a structured approach. Network documentation that includes
thorough troubleshooting procedures can decrease the amount of time required to resolve network
problems. Troubleshooting procedures should contain a process to diagnose problems and the steps
necessary to verify that a proposed solution resolved the problem. In this lab, this will be referred to as a
troubleshooting and verification plan.

Trouble Ticket 1: EIGRP Connectivity Issue

A new IT associate was asked to optimize EIGRP operations for the [Link] network. After the
assistant applied changes to improve metric calculations, connectivity became limited and local network
performance deteriorated. Create a troubleshooting and verification plan, and then correct the problem.

Trouble Ticket 2: EIGRP Adjacency Issue

The new IT associate was also asked to improve routing security on the network. After the assistant
configured the network routers, the adjacencies between Router1 and BBRouter1 were lost. The associate
was given the following values to use when configuring the routers:

• Key chain: WANKey

• Key: 1
• Key-string: Boson
• Accept-lifetime: infinite beginning 1 AM January 1, 2010
• Send-lifetime: infinite beginning 1 AM January 1, 2010

You must diagnose and correct the cause of the adjacency problem. Create a troubleshooting and
verification plan, and then correct the problem.

You can do so by clicking the Grade Lab icon ( ) in the toolbar or by pressing Ctrl+G.

3 Boson NetSim Lab Manual

 Lab Solutions
Trouble Ticket 1: EIGRP Connectivity Issue
You should create a troubleshooting and verification plan before attempting to correct the problem. There
are several possible answers to this task. You will be working on Router1, Router2, Router3, and Router4
in this task. The following are steps that you can take to resolve the issue:
1. One of the first steps you should perform when troubleshooting is to determine the line and protocol
state of the affected interfaces. Therefore, you should issue the show ip interface brief command
on each router to verify that the line and protocol states of Serial 0/3 on Router1, Serial 0/1 on
Router2, Serial 0/1 on Router3, and Serial 0/1 on Router4 are all up. Sample output from each of the
four routers is shown below:

Router1#show ip interface brief

Interface IP-Address OK? Method Status Protocol
Serial0/0 [Link] YES unset up up
Serial0/1 [Link] YES unset up up
Serial0/2 unassigned YES unset up down
Serial0/3 [Link] YES unset up up
FastEthernet1/0 unassigned YES unset up up

Router2#show ip interface brief

Interface IP-Address OK? Method Status Protocol
Serial0/0 unassigned YES unset up down
Serial0/1 [Link] YES unset up up
Serial0/2 unassigned YES unset down down
Serial0/3 unassigned YES unset down down
FastEthernet1/0 [Link] YES unset up up

Router3#show ip interface brief

Interface IP-Address OK? Method Status Protocol
Serial0/0 unassigned YES unset up down
Serial0/1 [Link] YES unset up up
Serial0/2 unassigned YES unset down down
Serial0/3 unassigned YES unset down down
FastEthernet1/0 [Link] YES unset up up

Router4#show ip interface brief

Interface IP-Address OK? Method Status Protocol
Serial0/0 unassigned YES unset up down
Serial0/1 [Link] YES unset up up
Serial0/2 unassigned YES unset down down
Serial0/3 unassigned YES unset down down
FastEthernet1/0 [Link] YES unset up up

2. You should then verify IP connectivity between neighboring routers. On Router1, ping Router2’s
Serial 0/1 interface ([Link]), ping Router3’s Serial 0/1 interface ([Link]), and ping Router4’s
Serial 0/1 interface ([Link]). All pings should be successful.

Router1#ping [Link]
Router1#ping [Link]
Router1#ping [Link]

4 Boson NetSim Lab Manual

 3. A router logs EIGRP neighbor changes by default. You should review the neighbor changes on each
device. When you accessed the consoles of Router1, Router2, Router3, and Router4, you should
have noticed that neighbor relationship messages were being displayed on each router. On Router1,
you should have observed that the output reported a K-value mismatch with the neighbor [Link]
(Router4). You should also have observed that Router4 reported a K-value mismatch with the
neighbor [Link] (Router1). On Router2 and Router3, you should have noted that the neighbor
[Link] (Router1) relationship was unstable. Sample output from the EIGRP neighbor messages
on each router is below:

Router1
[Link] %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor [Link] (Serial0/3)
is down: K-value mismatch

Router2
[Link] %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor [Link] (Serial0/1)
is up: new adjacency
[Link] %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor [Link] (Serial0/1)
is down: Interface Goodbye received

Router3
[Link] %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor [Link] (Serial0/1)
is up: new adjacency
[Link] %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor [Link] (Serial0/1)
is down: Interface Goodbye received

Router4
[Link] %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor [Link] (Serial0/1)
is down: K-value mismatch

5 Boson NetSim Lab Manual

 4. The next logical step would be to verify EIGRP adjacencies; however, the neighbor messages in
the previous step indicate that there are obvious neighbor reliability issues over the nonbroadcast
multiaccess (NBMA) portion of the topology. You should issue the show running-config command
on Router4 and Router1 to compare EIGRP configurations. Sample output from Router1 and
Router4 is shown below:

Router1#show running-config
Building configuration...
Current configuration : 1379 bytes
!
<output omitted>
!
interface Serial0/0
ip address [Link] [Link]
ip authentication mode eigrp 100 md5
ip authentication key-chain eigrp 100 WANKey
no ip directed-broadcast
!
interface Serial0/1
ip address [Link] [Link]
ip authentication mode eigrp 100 md5
ip authentication key-chain eigrp 100 WANKey
no ip directed-broadcast
!
<output omitted>
!
router eigrp 100
network [Link]
network [Link] [Link]
!
<output omitted>

Router4#show running-config
Building configuration...
Current configuration : 1387 bytes
!
<output omitted>
!
interface Serial0/1
ip address [Link] [Link]
ip authentication mode eigrp 100 md5
ip authentication key-chain eigrp 100 WANKey
delay 1000
encapsulation frame-relay
frame-relay interface-dlci 401
!
<output omitted>
!
router eigrp 100
network [Link]
network [Link] [Link]
metric weights 0 1 1 1 0 0
!
<output omitted>

6 Boson NetSim Lab Manual

 5. Metric weights have been assigned to Router4 and have not been assigned to Router1. Because the
metric weights on Router1 and Router4 are different, adjacencies are prevented from forming, which
leads to poor network performance.

A consequence of adjusting EIGRP K-values is the loss of adjacencies between neighboring routers.
Two devices configured to run EIGRP will not form an adjacency if both are not configured with
equal K-values.

A second consequence of configuring EIGRP K-values is incorrect path selection. K-values affect
the metric calculated by EIGRP and affect the cost associated with each path.

Another consequence of configuring EIGRP K-values is reduced network bandwidth. If K-values

on neighboring devices configured to run EIGRP are not equal, the router will send out “Graceful
Shutdown” messages to all of its peers until the mismatch is no longer present. Peers receiving the
messages will remove the neighbor and may send QUERY and UPDATE packets for routes lost by
down neighbors.

The spike in bandwidth consumed by unnecessary EIGRP traffic caused by incorrectly configured K-
values can be detrimental to a network. Configuring K-values to adjust path selection is not generally
advised and should be performed by only the most highly skilled network administrators.

In this task, you should note that the new associate also configured a delay of 1000 on the Serial
0/1 interface of Router4; this configuration should improve network performance for the [Link]
network.

To correct the configuration mismatch, you should issue the following commands to remove the
metric weights configured on Router4:

Router4(config)#router eigrp 100

Router4(config-router)#no metric weights 0 1 1 1 0 0

6. You should observe that Router4 has formed an adjacency with Router1 after the configuration
change in the previous step. Since the neighbor log messages have ended, you should now verify
all adjacencies by using the show ip eigrp neighbors command on Router1, Router2, Router3, and
Router4. Below is sample output:

Router1#show ip eigrp neighbors

IP-EIGRP neighbors for process 100
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 [Link] Se0/1 14 [Link] 828 4968 0 4
1 [Link] Se0/3 10 [Link] 416 2496 0 188
2 [Link] Se0/3 10 [Link] 603 3618 0 188
3 [Link] Se0/3 10 [Link] 371 2226 0 2

(continued on next page)

7 Boson NetSim Lab Manual

 (continued from previous page)

Router2#show ip eigrp neighbors

IP-EIGRP neighbors for process 100
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 [Link] Se0/1 12 [Link] 420 2520 0 0
1 [Link] Fa1/0 12 [Link] 609 3654 0 0

Router3#show ip eigrp neighbors

IP-EIGRP neighbors for process 100
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 [Link] Se0/1 11 [Link] 248 1488 0 0

Router4#show ip eigrp neighbors

IP-EIGRP neighbors for process 100
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 [Link] Se0/1 14 [Link] 337 2022 0 7
1 [Link] Fa1/0 12 [Link] 389 2334 0 0

Trouble Ticket 2: EIGRP Adjacency Issue

You should need to access only the consoles of Router1 and BBRouter1 in this task to resolve this
problem. The troubleshooting and verification plan you create before attempting to correct the problem
should include steps to determine the cause of the adjacency problem, steps to correct the problem,
and steps to verify that the problem has been resolved. Additionally, you should document the steps you
take during this process. There are several possible solutions to the adjacency problem in this task. The
following are steps that you can take to resolve the issue:
1. One of the first steps you should perform when troubleshooting is to determine the line and protocol
state of the affected interfaces. Therefore, you should issue the show ip interface brief command
on both routers to verify that the line and protocol state of each Serial 0/0 interface is up. Sample
output is shown below:

BBRouter1#show ip interface brief

Interface IP-Address OK? Method Status Protocol
Serial0/0 [Link] YES unset up up
Serial0/1 unassigned YES unset down down
Serial0/2 unassigned YES unset down down
Serial0/3 unassigned YES unset down down

Router1#show ip interface brief

Interface IP-Address OK? Method Status Protocol
Serial0/0 [Link] YES unset up up
Serial0/1 [Link] YES unset up up
Serial0/2 unassigned YES unset up down
Serial0/3 [Link] YES unset up up
FastEthernet1/0 unassigned YES unset up up

8 Boson NetSim Lab Manual

 2. You should then verify IP connectivity between both routers. On BBRouter1, ping Router1’s Serial
0/0 interface ([Link]). The ping should be successful.

BBRouter1#ping [Link]

3. Now that you have verified Layer 1 and Layer 2 connectivity between the routers, you should
determine whether there is a problem with Layer 3. Because you know that the IT associate was
asked to improve routing security on the network, the next logical steps are to issue the debug
eigrp packets command on BBRouter1 to enable EIGRP packet debugging and to observe
messages that could indicate potential problems with EIGRP.

BBRouter1#debug eigrp packets

EIGRP Packets debugging is on

4. You should be able to determine from the output of the debug eigrp packets command on
BBRouter1 that packets received on its Serial 0/0 interface from Router1 ([Link]) are being
ignored because of an authentication issue. Sample output is shown below:

[Link] EIGRP: Sending HELLO on Serial0/0

[Link] AS 100, Flags 0x0, Seq 0/0
[Link] EIGRP: Serial0/0: ignored packet from [Link], opcode = 5 (missing
authentication)

5. To determine the reason why BBRouter1 is ignoring EIGRP packets from Router1, you should
issue the show ip eigrp interface detail command on both routers to verify that each interface is
configured to perform EIGRP authentication. Sample output is shown below:

BBRouter1#show ip eigrp interfaces detail

IP-EIGRP interfaces for process 100

Xmit Queue Mean Pacing Time Multicast Pending

Interface Peers Un/Reliable SRTT Un/Reliable Flow Timer Routes
Se0/0 0 0/0 0 0/0 36 0
Hello interval is 5sec
Next xmit serial <none>
Un/reliable mcasts: 0/0 Un/reliable ucasts: 0/0
Mcast exceptions: 0 CR packets: 0 ACKs suppressed: 0
Retransmissions sent: 0 Out-of-sequence rcvd: 0
Authentication mode is md5, key-chain is “WANKey”
Use unicast

Router1#show ip eigrp interfaces detail

IP-EIGRP interfaces for process 100

Xmit Queue Mean Pacing Time Multicast Pending

Interface Peers Un/Reliable SRTT Un/Reliable Flow Timer Routes
Se0/0 0 0/0 0 0/0 162 0
Hello interval is 5sec
Next xmit serial <none>
Un/reliable mcasts: 0/0 Un/reliable ucasts: 0/0
Mcast exceptions: 0 CR packets: 0 ACKs suppressed: 0
Retransmissions sent: 0 Out-of-sequence rcvd: 0
Authentication mode is md5, key-chain is “WANKey”
<output omitted>

9 Boson NetSim Lab Manual

 6. Because both routers are configured to perform EIGRP authentication, you should verify key chain
configurations for EIGRP on Router1 and BBRouter1. Sample output is shown below:

BBRouter1#show key chain

Key-chain WANKey:
key 1 -- text “boson”
accept lifetime ([Link] Jan 01 2010) - (infinite) [valid now]
send lifetime ([Link] Jan 01 2010) - (infinite) [valid now]

Router1#show key chain

Key-chain WANKey:
key 1 -- text “Boson”
accept lifetime ([Link] Jan 01 2010) - (infinite) [valid now]
send lifetime ([Link] Jan 01 2010) - (infinite) [valid now]

7. You should observe that the key string for Router1’s WANKey is different from BBRouter1’s
WANKey. Key strings are case-sensitive.

8. Because the correct key string is Boson, you should issue the following commands on BBRouter1
to correct the configuration error. A new EIGRP adjacency should be created, and you should
observe the first exchange of UPDATE and ACK packets after the key string is corrected. Sample
output is shown below:

BBRouter1(config)#key chain WANKey

BBRouter1(config-keychain)#key 1
BBRouter1(config-keychain-key)#key-string Boson
[Link] EIGRP: Sending HELLO on Serial0/0
[Link] AS 100, Flags 0x0, Seq 0/0
[Link] EIGRP: received packet with MD5 authentication, key id = 1
[Link] EIGRP: received packet with MD5 authentication, key id = 1
[Link] EIGRP: Received HELLO on Serial0/0 nbr [Link]
[Link] AS 100, Flags 0x0, Seq 0/0
[Link] %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor [Link] (Serial0/0)
is up: new adjacency
[Link] EIGRP: Sending UPDATE on Serial0/0 nbr [Link]
[Link] AS 100, Flags 0x1, Seq 1/0
[Link] EIGRP: received packet with MD5 authentication, key id = 1
[Link] EIGRP: Received UPDATE on Serial0/0 nbr [Link]
[Link] AS 100, Flags 0x1, Seq 406/1
[Link] EIGRP: Sending ACK on Serial0/0 nbr [Link]
[Link] AS 100, Flags 0x0, Seq 0/406
[Link] EIGRP: Sending UPDATE on Serial0/0
[Link] AS 100, Flags 0x0, Seq 2/0
[Link] EIGRP: received packet with MD5 authentication, key id = 1
[Link] EIGRP: Received ACK on Serial0/0 nbr [Link]
[Link] AS 100, Flags 0x0, Seq 0/2

10 Boson NetSim Lab Manual

 9. To verify that you have resolved the adjacency problem for the trouble ticket, you should issue
the show ip eigrp neighbors command on both routers to verify that the Serial 0/0 interfaces on
BBRouter1 and Router1 formed an adjacency. Sample output is shown below:

BBRouter1#show ip eigrp neighbors

IP-EIGRP neighbors for process 100
H Address Interface Hold Uptime SRTT RTOQ Seq
(sec) (ms) Cnt Num
0 [Link] Se0/0 13 [Link] 604 3624 0 406

Router1#show ip eigrp neighbors

IP-EIGRP neighbors for process 100
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 [Link] Se0/3 13 [Link] 283 1698 0 817
1 [Link] Se0/3 12 [Link] 256 1536 0 817
2 [Link] Se0/1 11 [Link] 835 5010 0 2
3 [Link] Se0/3 12 [Link] 825 4950 0 2
4 [Link] Se0/0 7 [Link] 812 4872 0 2

10. Finally, you should issue the no debug eigrp packets command on BBRouter1 to disable EIGRP
packet debugging.

BBRouter1#no debug eigrp packets

EIGRP Packets debugging is off

11 Boson NetSim Lab Manual

 Sample Configuration Scripts
BBRouter1 BBRouter1 (continued)
BBRouter1#show running-config interface Serial0/1
Building configuration... no ip address
Current configuration : 946 bytes no ip directed-broadcast
! !
Version 15.b interface Serial0/2
service timestamps debug uptime no ip address
service timestamps log uptime no ip directed-broadcast
no service password-encryption !
! interface Serial0/3
hostname BBRouter1 no ip address
! no ip directed-broadcast
key chain WANKey !
key 1 router eigrp 100
key-string Boson network [Link]
accept-lifetime [Link] Jan 01 2010 infinite !
send-lifetime [Link] Jan 01 2010 infinite ip classless
! no ip http server
ip subnet-zero !
! line con 0
ip cef line aux 0
no ip domain-lookup line vty 0 4
! login
interface Serial0/0 !
ip address [Link] [Link] no scheduler allocate
ip authentication mode eigrp 100 md5 end
ip authentication key-chain eigrp 100 WANKey
no ip directed-broadcast
clock rate 64000
!

12 Boson NetSim Lab Manual

 Router4 Router4 (continued)
Router4#show running-config interface Serial0/2
Building configuration... no ip address
Current configuration : 1358 bytes no ip directed-broadcast
! !
Version 15.b interface Serial0/3
service timestamps debug uptime no ip address
service timestamps log uptime no ip directed-broadcast
no service password-encryption !
! interface FastEthernet1/0
hostname Router4 ip address [Link] [Link]
! ip authentication mode eigrp 100 md5
key chain WANKey ip authentication key-chain eigrp 100 LANKey
key 1 no ip directed-broadcast
key-string Boson !
accept-lifetime [Link] Jan 01 2010 infinite router eigrp 100
send-lifetime [Link] Jan 01 2010 infinite network [Link]
key chain LANKey network [Link] [Link]
key 1 !
key-string Boson ip classless
accept-lifetime [Link] Jan 01 2010 infinite no ip http server
send-lifetime [Link] Jan 01 2010 infinite !
! line con 0
ip subnet-zero line aux 0
! line vty 0 4
ip cef login
no ip domain-lookup !
! no scheduler allocate
interface Serial0/0 end
no ip address
no ip directed-broadcast
!
interface Serial0/1
ip address [Link] [Link]
ip authentication mode eigrp 100 md5
ip authentication key-chain eigrp 100 WANKey
delay 1000
encapsulation frame-relay
frame-relay interface-dlci 401
no frame-relay inverse-arp
!

Copyright © 1996–2017 Boson Software, LLC. All rights reserved. NetSim software and documentation are protected by copyright law.

13 Boson NetSim Lab Manual