Lab – Troubleshooting Basic EIGRP for IPv4 Swinburne V1.

0
Topology

LoopBack0

Serial Cables
already
connected
aa

Fa0/1 Fa0/0

PC Ethernet PC VAN

© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 1 of 9
Lab – Troubleshooting Basic EIGRP for IPv4

Addressing Table

EIGRP
Device Default Gateway
Router ID Interface IP Address

192.168.1.1/24
R1 1.1.1.1 Fa0/1 N/A

192.168.12.1/30
S0/0/0 (DCE) N/A

192.18.13.1/30
S0/0/1 N/A

R2 2.2.2.2

192.168.12.2/30
S0/0/0 N/A

192.168.23.1/30
S0/0/1 (DCE) N/A

192.168.3.1/24
R3 3.3.3.3 G0/0 N/A

192.168.13.2/30
S0/0/0 (DCE) N/A

192.168.23.2/30
S0/0/1 N/A

192.168.1.3/24 192.168.1.1
PC-A NIC

192.168.2.1/24
PC-B Loopback0 on R2

192.168.3.3/24 192.168.3.1
PC-C NIC

© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 2 of 9
Lab – Troubleshooting Basic EIGRP for IPv4

Objectives
Part 1: Build the Network and Load Device Configurations
Part 2: Troubleshoot Layer 3 Connectivity
Part 3: Troubleshoot EIGRP for IPv4

Background / Scenario
The Enhanced Interior Gateway Routing Protocol (EIGRP) is an advanced distance vector routing protocol
developed by Cisco Systems. EIGRP routers discover neighbors and establish and maintain adjacencies with
neighbor routers using Hello packets. An EIGRP router assumes that as long as it is receiving Hello packets
from a neighboring router, that neighbor is up and its routes remain viable.
EIGRP for IPv4 runs over the IPv4 network layer, communicating with other EIGRP IPv4 peers, and
advertising only IPv4 routesIn this lab, you will troubleshoot a network that runs EIGRP for IPv4. This network
is experiencing problems and you are tasked with finding the problems and correcting them.

Notes:
1. Make sure that the routers have been erased and have no startup
configurations. If you are unsure, contact your instructor.
2. Sample output is provided for the show commands. Your show output may
differ depending on your Lab Environment and the PCs, routers and switches
you are using.
3. It is important to be able to read and understand Routing Tables, in
preparation for the Network Topology Test.
4. To troubleshoot the R2 router you will need to use the Extended Ping to
specify the Loopback 0 IP address. Please ask your Instructor to show you
how to use the Extended Ping.

© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 3 of 9
Lab – Troubleshooting Basic EIGRP for IPv4

Part 1: Build the Network and Load Device Configurations

In Part 1, you will set up the network topology and configure basic settings on the PC hosts and routers.

Step 1: Cable the network as shown in the topology.

Step 2: Configure PC hosts.

Step 3: Load router configurations.

Load the following configurations into the appropriate router.
Router R1 Configuration:
conf t
hostname R1
no ip domain lookup
interface FastEthernet0/1
ip address 192.168.1.1 255.255.255.0
no shutdown
interface Serial0/0/0
bandwidth 128
ip address 192.168.21.1 255.255.255.252
no shutdown
interface Serial0/0/1
ip address 192.168.13.1 255.255.255.252
no shutdown
router eigrp 1
network 192.168.1.0
network 192.168.12.0 0.0.0.3
network 192.168.13.0 0.0.0.3
passive-interface FastEthernet0/1
eigrp router-id 1.1.1.1
no shutdown
banner motd @
Student ID! @
line con 0
logging synchronous
line vty 0 4
password cisco
login
transport input all
end

© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 4 of 9
Lab – Troubleshooting Basic EIGRP for IPv4

Router R2 Configuration:
conf t
hostname R2
no ip domain lookup
interface loopback0
ip address 192.168.2.1 255.255.255.0
interface Serial0/0/0
ip address 192.168.12.2 255.255.255.252
no shutdown
interface Serial0/0/1
bandwidth 128
ip address 192.168.23.1 255.255.255.0
no shutdown
router eigrp 1
network 192.168.12.0 0.0.0.3
network 192.168.23.0 0.0.0.3
passive-interface FastEthernet0/0
eigrp router-id 2.2.2.2
no shutdown
banner motd @
Student ID @
line con 0
logging synchronous
line vty 0 4
password cisco
login
transport input all
end

© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 5 of 9
Lab – Troubleshooting Basic EIGRP for IPv4

Router R3 Configuration:
conf t
hostname R3
no ip domain lookup
interface FastEthernet0/0
ip address 192.168.3.1 255.255.255.0
interface Serial0/0/0
ip address 192.168.13.2 255.255.255.252
no shutdown
interface Serial0/0/1
bandwidth 128
ip address 192.168.23.2 255.255.255.252
no shutdown
router eigrp 1
network 192.168.3.0
network 192.168.13.0 0.0.0.3
passive-interface FastEthernet0/0
eigrp router-id 3.3.3.3
banner motd @
Student ID @
line con 0
logging synchronous
line vty 0 4
password cisco
login
transport input all
end

© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 6 of 9
Lab – Troubleshooting Basic EIGRP for IPv4

Step 4: Save the running configuration for all routers.

Part 2: Troubleshoot Layer 3 Connectivity

In Part 2, you will verify that Layer 3 connectivity is established on all interfaces. You will need to test IPv4
connectivity for all device interfaces.
Note: All serial interfaces should be set with a bandwidth of 128 Kb/s. The clock rate on the DCE interface
should be set to 128000.

Step 1: Verify that the interfaces listed in the Addressing Table are active and configured with
correct IP address information.
a. Issue the show ip interface brief command on all routers to verify that the interfaces are in an up/up
state. Record your findings.
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
b. Issue the show run interface command to verify IP address assignments on all router interfaces.
Compare the interface IP addresses against the Addressing Table and verify the subnet mask
assignments.
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
c. Issue the show interface interface-id command to verify bandwidth setting on the serial interfaces.
Record your findings.
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
d. Issue the show controllers interface-id command to verify that clock rates have been set to 128 Kb/s on
all DCE serial interfaces. Issue the show interface interface-id command to verify bandwidth setting on
the serial interfaces. Record your findings.
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
e. Resolve all problems found. Record the commands used to correct the issues.
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________

© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 7 of 9
Lab – Troubleshooting Basic EIGRP for IPv4

____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________

Step 2: Verify Layer 3 connectivity.

Use the ping command and verify that each router has network connectivity with the serial interfaces on the
neighbor routers. Verify that the PCs can ping their default gateways. If problems still exist, continue
troubleshooting Layer 3 issues.

Part 3: Troubleshoot EIGRP for IPv4

In Part 3, you will troubleshoot EIGRP for IPv4 problems and make the necessary changes needed to
establish EIGRP for IPv4 routes and end-to-end IPv4 connectivity.
Note: LAN interfaces should not advertise EIGRP routing information, but routes to these networks should be
contained in the routing tables.

Step 1: Test IPv4 end-to-end connectivity.

From each PC host, ping the other PC hosts in the topology to verify end-to-end connectivity.
Note: It may be necessary to disable the PC firewall before testing, to ping between PCs.
a. Ping from PC-A to PC-B (loopback 0 on R2) . Were the pings successful? _____________
b. Ping from PC-A to PC-C. Were the pings successful? _____________
c. Extended Ping from PC-B (loopback 0 on R2) to PC-C. Were the pings successful? _____________

Step 2: Verify that all interfaces are assigned to EIGRP for IPv4.
a. Issue the show ip protocols command to verify that EIGRP is running and that all networks are
advertised. This command also allows you to verify that the router ID is set correctly, and that the LAN
interfaces are set as passive interfaces. Record your findings.
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
b. Make the necessary changes based on the output from the show ip protocols command. Record the
commands that were used to correct the issues.
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
c. Re-issue the show ip protocols command to verify that your changes had the desired effect.

© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 8 of 9
Lab – Troubleshooting Basic EIGRP for IPv4

Step 3: Verify EIGRP neighbor information.

a. Issue the show ip eigrp neighbor command to verify that EIGRP adjacencies have been established
between the neighboring routers.
b. Resolve any outstanding problems that were discovered.

Step 4: Verify EIGRP for IPv4 routing information.

a. Issue the show ip route eigrp command to verify that each router has EIGRP for IPv4 routes to all non-
adjoining networks.
Are all EIGRP routes available? ________
If any EIGRP for IPv4 routes are missing, what is missing?
____________________________________________________________________________________
b. If any routing information is missing, resolve these issues.

Step 5: Verify IPv4 end-to-end connectivity.

From each PC, verify that IPv4 end-to-end connectivity exists. PCs should be able to ping the other PC hosts
in the topology. If IPv4 end-to-end connectivity does not exist, then continue troubleshooting to resolve
remaining issues.
Note: It may be necessary to disable the PCs firewall.

Reflection
Why would you troubleshoot EIGRP for IPv4 and EIGRP for IPv6 separately?
_______________________________________________________________________________________
_______________________________________________________________________________________

© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 9 of 9