Lab - Troubleshoot IPv4 and IPv6 Static Routing

Topology

Addressing Table
IPv6 Link
Device Interface IPv4 Address/Mask IPv6 Address/Prefix Default Gateway
Local

R1 G0/0/0 10.10.12.1/24 2001:db8:0:12::1/64 f e80::1:1 N/A

R1
G0/0/1 10.10.1.1/24 2001:db8:0:1::1/64 f e80::1:2 N/A

R1
S0/1/0 N/A 2001:db8:0:13::1/64 f e80::1:3 N/A

R2 G0/0/0 10.10.12.2/24 2001:db8:0:12::2/64 f e80::2:1 N/A

R2
G0/0/1 10.10.23.1/24 2001:db8:0:23::1/64 f e80::2:2 N/A

R3 G0/0/0 10.10.23.2/24 2001:db8:0:23::2/64 f e80::3:1 N/A

R3
G0/0/1 10.10.3.1/24 2001:db8:0:3::1/64 f e80::3:2 N/A

R3
S0/1/0 2001:db8:0:13::2/64 f e80::3:3 N/A

D1 VLAN 10 10.10.1.2/24 N/A N/A 10.10.1.1

D2 VLAN 10 10.10.3.2/24 N/A N/A 10.10.3.1

© 2020 - 2020 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 1 of 4 www.netacad.com
Lab - Troubleshoot IPv4 and IPv6 Static Routing

IPv6 Link
Device Interface IPv4 Address/Mask IPv6 Address/Prefix Default Gateway
Local

10.10.1.1
PC1 NIC 10.10.1.10/24 2001:db8:0:1::10/64 EUI-64/CGA
2001:db8:0:1::1
10.10.1.1
PC2 NIC 10.10.1.20/24 2001:db8:0:1::20/64 EUI-64/CGA
2001:db8:0:1::1
10.10.3.1
Web Server NIC 10.10.3.5/24 2001:db8:0:3::5/64 EUI-64/CGA
2001:db8:0:3::1
10.10.3.1
FTP Server NIC 10.10.3.20/24 2001:db8:0:3::20/64 EUI-64/CGA
2001:db8:0:3::1

Objectives
Troubleshoot network issues related to IPv4 and IPv6 static routing.

Background / Scenario
In this topology, routers R1, R2, and R3 are conf igured f or static routing. Switches D1 and D2 provide LAN
connectivity f or VLAN 10 f or the respective locations. You will be loading conf igurations with intentional errors
onto the network. Your tasks are to FIND the error(s), document your f indings and the command(s) or
method(s) used to f ix them, FIX the issue(s) presented here and then test the network to ensure both of the
f ollowing conditions are met:
1) the complaint received in the ticket is resolved
2) f ull reachability is restored
Note: The routers used with CCNA hands-on labs are Cisco 4221 with Cisco IOS XE Release 16.9.4
(universalk9 image). The switches used in the labs are Cisco Catalyst 3560 with Cisco IOS XE Release
16.9.4 (universalk9 image). Other routers, switches, and Cisco IOS versions can be used. Depending on the
model and Cisco IOS version, the commands available and the output produced might vary f rom what is
shown in the labs. Ref er to the Router Interf ace Summary Table at the end of the lab f or the correct interf ace
identif iers.
Note: Make sure that the switches have been erased and have no startup conf igurations. If you are unsure,
contact your instructor.

Required Resources
• 3 Routers (Cisco 4221 with Cisco IOS XE Release 16.9.4 universal image or comparable)
• 2 Switches (Cisco 3650 with Cisco IOS XE Release 16.9.4 universalk9 image or comparable)
• 4 PCs (Choice of operating system with terminal emulation program installed)
• Console cables to conf igure the Cisco IOS devices via the console ports
• Ethernet cables as shown in the topology

© 2020 - 2020 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 2 of 4 www.netacad.com
Lab - Troubleshoot IPv4 and IPv6 Static Routing

Instructions

Part 1: Trouble Ticket 1.1.3.1

Scenario:
An FTP Server was recently added to the HQ network. The FTP Server is accessible f rom all devices in the
HQ network. Branch network hosts PC1 and PC2 are able to connect to the Web Server but are unable to
connect to the FTP Server using IPv4.
Note: Web or FTP services are not required on the PCs.
Use the commands listed below to load the conf iguration f iles f or both trouble ti ckets:

Device Command

R1 copy flash:/enarsi/1.1.3.1-r1-config.txt run

R2 copy flash:/enarsi/1.1.3.1-r2-config.txt run

R3 copy flash:/enarsi/1.1.3.1-r3-config.txt run

D1 copy flash:/enarsi/1.1.3.1-d1-config.txt run

D2 copy flash:/enarsi/1.1.3.1-d2-config.txt run

• PC 1, PC 2, FTP Server, and Web Server should be conf igured with the addressing listed in the
Addressing Table.
• Passwords on all devices are cisco12345. If a username is required, use admin.
• Af ter you have f ixed the ticket, change the MOTD on EACH DEVICE using the f ollowing command:
banner motd # This is $(hostname) FIXED from ticket <ticket number> #
• Then save the conf iguration by issuing the wri command (on each device).
• Inf orm your instructor that you are ready f or the next ticket.
• Af ter the instructor approves your solution f or this ticket, issue the reset.now privileged exec
command. This script will clear your conf igurations and reload the devices.

Part 2: Trouble Ticket 1.1.3.2

Scenario:
A WAN connection through R2 was recently added to increase the bandwidth that is available between the
branch and HQ. It was decided to keep the dedicated T1 connection f rom R1 to R3 as a backup link f or IPv6
traf f ic. Users at the branch have been complaining that data transf er speeds to PCs at HQ seem to be slow;
however, downloads seem to be f ine.
Use the commands listed below to load the conf iguration f iles f or both trouble tickets:

Device Command

R1 copy flash:/enarsi/1.1.3.2-r1-config.txt run

R2 copy flash:/enarsi/1.1.3.2-r2-config.txt run

R3 copy flash:/enarsi/1.1.3.2-r3-config.txt run

D1 copy flash:/enarsi/1.1.3.2-d1-config.txt run

© 2020 - 2020 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 3 of 4 www.netacad.com
Lab - Troubleshoot IPv4 and IPv6 Static Routing

Device Command

D2 copy flash:/enarsi/1.1.3.2-d2-config.txt run

• PC 1, PC 2, FTPServer, and WebServer should be conf igured with the IPv6 addressing listed in the
Addressing Table. It is not necessary to conf igure the IPv4 addresses.
• Passwords on all devices are cisco12345. If a username is required, use admin.
• Af ter you have f ixed the ticket, change the MOTD on EACH DEVICE using the f ollowing command:
banner motd # This is $(hostname) FIXED from ticket <ticket number> #
• Then save the conf iguration by issuing the wri command (on each device).
• Inf orm your instructor that you are ready f or the next ticket.
• Af ter the instructor approves your so lution f or this ticket, issue the reset.now privileged EXEC
command. This script will clear your conf igurations and reload the devices.

Router Interface Summary Table

Router Model Ethernet Interface #1 Ethernet Interface #2 Serial Interface #1 Serial Interface #2

Fast Ethernet 0/0 Fast Ethernet 0/1

1800 (F0/0) (F0/1) Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1)
Gigabit Ethernet 0/0 Gigabit Ethernet 0/1
1900 (G0/0) (G0/1) Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1)
Fast Ethernet 0/0 Fast Ethernet 0/1
2801 (F0/0) (F0/1) Serial 0/1/0 (S0/1/0) Serial 0/1/1 (S0/1/1)
Fast Ethernet 0/0 Fast Ethernet 0/1
2811 (F0/0) (F0/1) Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1)
Gigabit Ethernet 0/0 Gigabit Ethernet 0/1
2900 (G0/0) (G0/1) Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1)
Gigabit Ethernet 0/0/0 Gigabit Ethernet 0/0/1
4221 (G0/0/0) (G0/0/1) Serial 0/1/0 (S0/1/0) Serial 0/1/1 (S0/1/1)
Gigabit Ethernet 0/0/0 Gigabit Ethernet 0/0/1
4300 (G0/0/0) (G0/0/1) Serial 0/1/0 (S0/1/0) Serial 0/1/1 (S0/1/1)

Note: To f ind out how the router is conf igured, look at the interf aces to identif y the type of router and how many
interf aces the router has. There is no way to ef f ectively list all the combinations of conf igurations f or each router
class. This table includes identif iers f or the possible combinations of Ethernet and Serial interf aces in the device.
The table does not include any other type of interf ace, even though a specif ic router may contain one. An
example of this might be an ISDN BRI interf ace. The string in parenthesis is the legal abbreviation that can b e
used in Cisco IOS commands to represent the interf ace.
End of document

© 2020 - 2020 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 4 of 4 www.netacad.com