2.3.2.

4 Lab – Troubleshooting IPv4 and IPv6 Static Routes

Topology

Addressing Table
Device Interface IP Address Default Gateway

192.168.0.1/25
HQ G0/1 2001:DB8:ACAD::1/64 N/A
FE80::1 link-local

10.1.1.2/30
S0/0/0 (DCE) N/A
2001:DB8:ACAD:20::2/64

192.168.0.253/30
S0/0/1 N/A
2001:DB8:ACAD:2::1/64

172.16.3.1/24
ISP G0/0 2001:DB8:ACAD:30::1/64 N/A
FE80::1 link-local

10.1.1.1/30
S0/0/0 N/A
2001:DB8:ACAD:20::1/64

192.168.1.1/24
BRANCH G0/1 2001:DB8:ACAD:1::1/64 N/A
FE80::1 link-local

192.168.0.254/30
S0/0/0 (DCE) N/A
2001:DB8:ACAD:2::2/64

S1 VLAN 1 N/A N/A

S3 VLAN 1 N/A N/A

192.168.0.3/25 192.168.0.1
PC-A NIC
2001:DB8:ACAD::3/64 FE80::1

172.16.3.3/24 172.16.3.1
Web Server NIC
2001:DB8:ACAD:30::3/64 FE80::1

192.168.1.3/24 192.168.1.1
PC-C NIC
2001:DB8:ACAD:1::3/64 FE80::1
Objectives
Part 1: Build the Network and Configure Basic Device Settings
Part 2: Troubleshoot Static Routes in an IPv4 Network
Part 3: Troubleshoot Static Routes in an IPv6 Network
Background / Scenario
As a network administrator, you must be able to configure routing of traffic using static routes. Understanding
how to configure and troubleshoot static routing is a requirement. Static routes are commonly used for stub
networks and default routes. Your company’s ISP has hired you to troubleshoot connectivity issues on the
network. You will have access to the HQ, BRANCH, and the ISP routers.
In this lab, you will begin by loading configuration scripts on each of the routers. These scripts contain errors
that will prevent end-to-end communication across the network. You will need to troubleshoot each router to
determine the configuration errors, and then use the appropriate commands to correct the configurations. When
you have corrected all of the configuration errors, the hosts on the network should be able to communicate with
each other.
Note: The routers used with CCNA hands-on labs are Cisco 1941 Integrated Services Routers (ISRs) with
Cisco IOS Release 15.2(4)M3 (universalk9 image). The switches used are Cisco Catalyst 2960s with Cisco IOS
Release 15.0(2) (lanbasek9 image). Other routers, switches, and Cisco IOS versions can be used. Depending on
the model and Cisco IOS version, the commands available and output produced might vary from what is shown
in the labs. Refer to the Router Interface Summary Table at the end of this lab for the correct interface
identifiers.
Note: Make sure that the routers and switches have been erased and have no startup configurations. If you are
unsure, contact your instructor.
Required Resources
3 Routers (Cisco 1941 with Cisco IOS Release 15.2(4)M3 universal image or comparable)
2 Switches (Cisco 2960 with Cisco IOS Release 15.0(2) lanbasek9 image or comparable)
3 PCs (Windows 7, Vista, or XP with terminal emulation program, such as Tera Term)
Console cables to configure the Cisco IOS devices via the console ports
Ethernet and serial cables as shown in the topology
Part 1: Build the Network and Configure Basic Device Settings
In Part 1, you will set up the network topology and configure the routers and switches with some basic settings,
such as passwords and IP addresses. Preset configurations are also provided for you for the initial router
configurations. You will also configure the IP settings for the PCs in the topology.
Step 1: Cable the network as shown in the topology.
Attach the devices as shown in the topology diagram and cable, as necessary.
Step 2: Initialize and reload the routers and switches.
Step 3: Configure basic settings for each router.
a. Disable DNS lookup.
b. Configure device name as shown in the topology.
c. Assign class as the privileged EXEC mode password.
d. Assign cisco as the console and vty passwords.
e. Configure logging synchronous to prevent console messages from interrupting command entry.
Step 4: Configure hosts and Web Server.
a. Configure IP addresses for IPv4 and IPv6.
b. Configure IPv4 default gateway.
Step 5: Load router configurations.
Router HQ
hostname HQ
ipv6 unicast-routing
interface GigabitEthernet0/1
ipv6 address 2001:DB8:ACAD::1/64
ip address 192.168.0.1 255.255.255.128
ipv6 address FE80::1 link-local
!no shutdown
interface Serial0/0/0
ipv6 address 2001:DB8:ACAD:20::2/64
ip address 10.1.1.2 255.255.255.252
clock rate 800000
no shutdown
interface Serial0/0/1
ipv6 address 2001:DB8:ACAD:2::3/64
!ipv6 address 2001:DB8:ACAD:2::1/64
ip address 192.168.0.253 255.255.255.252
no shutdown
ip route 172.16.3.0 255.255.255.0 10.1.1.1
ip route 192.168.1.0 255.255.255.0 192.16.0.254
!ip route 192.168.1.0 255.255.255.0 192.168.0.254
ipv6 route 2001:DB8:ACAD:1::/64 2001:DB8:ACAD:2::2
ipv6 route 2001:DB8:ACAD:30::/64 2001:DB8:ACAD::20:1
!ipv6 route 2001:DB8:ACAD:30::/64 2001:DB8:ACAD:20::1
Router ISP
hostname ISP
ipv6 unicast-routing
interface GigabitEthernet0/0
ipv6 address 2001:DB8:ACAD:30::1/64
ip address 172.16.3.11 255.255.255.0
!ip address 172.16.3.1 255.255.255.0
ipv6 address FE80::1 link-local
no shutdown
interface Serial0/0/0
ipv6 address 2001:DB8::ACAD:20:1/64
!ipv6 address 2001:DB8:ACAD:20::1/64
ip address 10.1.1.1 255.255.255.252
no shutdown
ip route 192.168.1.0 255.255.255.0 10.1.1.2
!ip route 192.168.0.0 255.255.254.0 10.1.1.2
ipv6 route 2001:DB8:ACAD::/62 2001:DB8:ACAD:20::2
Router BRANCH
hostname BRANCH
ipv6 unicast-routing
interface GigabitEthernet0/1
ipv6 address 2001:DB8:ACAD:1::1/64
ip address 192.168.1.1 255.255.255.0
ipv6 address FE80::1 link-local
no shutdown
interface Serial0/0/0
ipv6 address 2001:DB8:ACAD:2::2/64
clock rate 128000
ip address 192.168.0.249 255.255.255.252
!ip address 192.168.0.254 255.255.255.252
clock rate 128000
no shutdown
ip route 0.0.0.0 0.0.0.0 10.1.1.2
!ip route 0.0.0.0 0.0.0.0 192.168.0.253
!ipv6 unicast-routing
ipv6 route ::/0 2001:DB8:ACAD::1
!ipv6 route ::/0 2001:DB8:ACAD:2::1
Part 2: Troubleshoot Static Routes in an IPv4 Network
IPv4 Addressing Table
Device Interface IP Address Subnet Mask Default Gateway

G0/1 192.168.0.1 255.255.255.0 N/A

S0/0/0 (DCE) 10.1.1.2 255.255.255.252 N/A

HQ S0/0/1 192.168.0.253 255.255.255.252 N/A

G0/0 172.16.3.1 255.255.255.0 N/A

ISP S0/0/0 10.1.1.1 255.255.255.252 N/A

G0/1 192.168.1.1 255.255.255.0 N/A

BRANCH S0/0/0 (DCE) 192.168.0.254 255.255.255.252 N/A

S1 VLAN 1 192.168.0.11 255.255.255.128 192.168.0.1

S3 VLAN 1 192.168.1.11 255.255.255.0 192.168.1.1

PC-A NIC 192.168.0.3 255.255.255.128 192.168.0.1

Web Server NIC 172.16.3.3 255.255.255.0 172.16.3.1

 Device Interface IP Address Subnet Mask Default Gateway

PC-C NIC 192.168.1.3 255.255.255.0 192.168.1.1

Step 1: Troubleshoot the HQ router.
The HQ router is the link between the ISP router and the BRANCH router. The ISP router represents the outside
network while the BRANCH router represents the corporate network. The HQ router is configured with static
routes to ISP and BRANCH networks.
a. Display the status of the interfaces on HQ. Enter show ip interface brief. Record and resolve any issues as
necessary.
_________________________________________________
b. Ping from HQ router to BRANCH router (192.168.0.254). Were the pings successful? ______
c. Ping from HQ router to ISP router (10.1.1.1). Were the pings successful? _____
d. Ping from PC-A to the default gateway. Were the pings successful? _____
e. Ping from PC-A to PC-C. Were the pings successful? _____
f. Ping from PC-A to Web Server. Were the pings successful? ______
g. Display the routing table on HQ. What non-directly connected routes are shown in the routing table?
________________________________________________
h. Based on the results of the pings, routing table output, and static routes in the running configuration, what can
you conclude about network connectivity?
___________________________________________________
i. What commands (if any) need to be entered to resolve routing issues? Record the command(s).
__________________________________________________
j. Repeat any of the steps from b to f to verify whether the problems have been resolved. Record your
observations and possible next steps in troubleshooting connectivity.
__________________________________________________
Step 2: Troubleshoot the ISP router.
For the ISP router, there should be a route to HQ and BRANCH routers. One static route is configured on ISP
router to reach the 192.168.1.0/24, 192.168.0.0/25, and 192.168.0.252/30 networks.
a. Display the status of interfaces on ISP. Enter show ip interface brief. Record and resolve any issues as
necessary.
____________________________________________________
b. Ping from the ISP router to the HQ router (10.1.1.2). Were the pings successful? ______
c. Ping from Web Server to the default gateway. Were the pings successful? _______
d. Ping from Web Server to PC-A. Were the pings successful? _______
e. Ping from Web Server to PC-C. Were the pings successful? ______
f. Display the routing table on ISP. What non-directly connected routes are shown in the routing table?
__________________________________________________
g. Based on the results of the pings, routing table output, and static routes in the running configuration, what can
you conclude about network connectivity?__________________________________________________
h. What commands (if any) need to be entered to resolve routing issues? Record the command(s).
(Hint: ISP only requires one summarized route to the company’s networks 192.168.1.0/24, 192.168.0.0/25, and
192.168.0.252/32.)
____________________________________________________
i. Repeat any of the steps from b to e to verify whether the problems have been resolved. Record your
observations and possible next steps in troubleshooting connectivity.
_____________________________________________________
Step 3: Troubleshoot the BRANCH router.
For the BRANCH router, a default route is set to reach the rest of the network and ISP.
a. Display the status of the interfaces on BRANCH. Enter show ip interface brief. Record and resolve any
issues, as necessary.
______________________________________________________
b. Ping from the BRANCH router to the HQ router (192.168.0.253). Were the pings successful? ______
c. Ping from PC-C to the default gateway. Were the pings successful? _____
d. Ping from PC-C to PC-A. Were the pings successful? _____
e. Ping from PC-C to Web Server. Were the pings successful? ______
f. Display the routing table on BRANCH. What non-directly connected routes are shown in the routing
table?__________________________________________________
g. Based on the results of the pings, routing table output, and static routes in the running configuration, what can
you conclude about network connectivity?
_____________________________________________________
h. What commands (if any) need to be entered to resolve routing issues? Record the command(s).
_____________________________________________________
i. Repeat any of the steps from b to e to verify whether the problems have been resolved. Record your
observations and possible next steps in troubleshooting connectivity.
_____________________________________________________
/1
Part 3: Troubleshoot Static Routes in an IPv6 Network
Device Interface IPv6 Address Prefix Length Default Gateway

G0/1 2001:DB8:ACAD::1 64 N/A

S0/0/0 (DCE) 2001:DB8:ACAD:20::2 64 N/A

HQ S0/0/1 2001:DB8:ACAD:2::1 64 N/A

G0/0 2001:DB8:ACAD:30::1 64 N/A

ISP S0/0/0 2001:DB8:ACAD:20::1 64 N/A

G0/1 2001:DB8:ACAD:1::1 64 N/A

BRANCH S0/0/0 (DCE) 2001:DB8:ACAD:2::2 64 N/A

PC-A NIC 2001:DB8:ACAD::3 64 FE80::1

Web Server NIC 2001:DB8:ACAD:30::3 64 FE80::1

PC-C NIC 2001:DB8:ACAD:1::3 64 FE80::1

Step 1: Troubleshoot the HQ router.
The HQ router is the link between the ISP router and the BRANCH router. The ISP router represents the outside
network while the BRANCH router represents the corporate network. The HQ router is configured with static
routes to both the ISP and the BRANCH networks.
a. Display the status of the interfaces on HQ. Enter show ipv6 interface brief. Record and resolve any issues, as
necessary.
_____________________________________________________
b. Ping from the HQ router to the BRANCH router (2001:DB8:ACAD:2::2). Were the pings successful?
c. Ping from the HQ router to the ISP router (2001:DB8:ACAD:20::1). Were the pings successful? _______
d. Ping from PC-A to the default gateway. Were the pings successful? _______
e. Ping from PC-A to Web Server. Were the pings successful? _______
f. Ping from PC-A to PC-C. Were the pings successful? _______
g. Display the routing table by issuing a show ipv6 route command. What non-directly connected routes are
shown in the routing table?
____________________________________________________
h. Based on the results of the pings, routing table output, and static routes in the running configuration, what can
you conclude about network connectivity?
_____________________________________________________
i. What commands (if any) need to be entered to resolve routing issues? Record the command(s).
_____________________________________________________
j. Repeat any of the steps from b to f to verify whether the problems have been resolved. Record your
observations and possible next steps in troubleshooting connectivity.
_____________________________________________________
Step 2: Troubleshoot the ISP router.
On the ISP router, one static route is configured to reach all the networks on HQ and BRANCH routers.
a. Display the status of the interfaces on ISP. Enter show ipv6 interface brief. Record and resolve any issues, as
necessary.
____________________________________________________
b. Ping from the ISP router to the HQ router (2001:DB8:ACAD:20::2). Were the pings successful? _______
c. Ping from Web Server to the default gateway. Were the pings successful? _______
d. Ping from Web Server to PC-A. Were the pings successful? _______
e. Ping from Web Server to PC-C. Were the pings successful? ________
f. Display the routing table. What non-directly connected routes are shown in the routing table?
____________________________________________________
g. Based on the results of the pings, routing table output, and static routes in the running configuration, what can
you conclude about network connectivity?
____________________________________________________
h. What commands (if any) need to be entered to resolve routing issues? Record the command(s).
____________________________________________________
i. Repeat any of the steps from b to e to verify whether the problems have been resolved. Record your
observations and possible next steps in troubleshooting connectivity.
____________________________________________________
Step 3: Troubleshoot the BRANCH router.
For the BRANCH routers, there is a default route to the HQ router. This default route allows the BRANCH
network to the ISP router and Web Server.
a. Display the status of the interfaces on BRANCH. Enter show ipv6 interface brief. Record and resolve any
issues, as necessary.
_____________________________________________________
b. Ping from the BRANCH router to the HQ router (2001:DB8:ACAD:2::1). Were the pings successful?
______
c. Ping from the BRANCH router to the ISP router (2001:DB8:ACAD:20::1). Were the pings successful?
______
d. Ping from PC-C to the default gateway. Were the pings successful? ______
e. Ping from PC-C to PC-A. Were the pings successful? ______
f. Ping from PC-C to Web Server. Were the pings successful? ______
g. Display the routing table. What non-directly connected routes are shown in the routing table?
____________________________________________________
h. Based on the results of the pings, routing table output, and static routes in the running configuration, what can
you conclude about network connectivity?____________________________________________________
i. What commands (if any) need to be entered to resolve routing issues? Record the command(s).
____________________________________________________
j. Repeat any of the steps from b to f to verify whether the problems have been resolved. Record your
observations and possible next steps in troubleshooting connectivity.
____________________________________________________
Router Interface Summary Table
Router Interface Summary

Router Ethernet Interface Ethernet Interface Serial Interface Serial Interface

Model #1 #2 #1 #2

Fast Ethernet 0/0 Fast Ethernet 0/1 Serial 0/0/0 Serial 0/0/1
1800 (F0/0) (F0/1) (S0/0/0) (S0/0/1)

Gigabit Ethernet 0/0 Gigabit Ethernet 0/1 Serial 0/0/0 Serial 0/0/1
1900 (G0/0) (G0/1) (S0/0/0) (S0/0/1)

Fast Ethernet 0/0 Fast Ethernet 0/1 Serial 0/1/0 Serial 0/1/1
2801 (F0/0) (F0/1) (S0/1/0) (S0/1/1)

Fast Ethernet 0/0 Fast Ethernet 0/1 Serial 0/0/0 Serial 0/0/1
2811 (F0/0) (F0/1) (S0/0/0) (S0/0/1)

Gigabit Ethernet 0/0 Gigabit Ethernet 0/1 Serial 0/0/0 Serial 0/0/1
2900 (G0/0) (G0/1) (S0/0/0) (S0/0/1)

Note: To find out how the router is configured, look at the interfaces to identify the type of router and how
many interfaces the router has. There is no way to effectively list all the combinations of configurations for
each router class. This table includes identifiers for the possible combinations of Ethernet and Serial
interfaces in the device. The table does not include any other type of interface, even though a specific router
may contain one. An example of this might be an ISDN BRI interface. The string in parenthesis is the legal
abbreviation that can be used in Cisco IOS commands to represent the interface.

Device Configs
Router HQ (Corrected)
HQ# show run
Building configuration...
Current configuration : 1652 bytes
!
version 15.2
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname HQ
!
boot-start-marker
boot-end-marker
!
enable secret 4 06YFDUHH61wAE/kLkDq9BGho1QM5EnRtoyr8cHAUg.2
!
no aaa new-model
memory-size iomem 15
!
ip cef
ipv6 unicast-routing
ipv6 cef
multilink bundle-name authenticated
!
interface Embedded-Service-Engine0/0
no ip address
shutdown
!
interface GigabitEthernet0/0
no ip address
shutdown
duplex auto
speed auto
!
interface GigabitEthernet0/1
ip address 192.168.0.1 255.255.255.128
duplex auto
speed auto
ipv6 address FE80::1 link-local
ipv6 address 2001:DB8:ACAD::1/64
!
interface Serial0/0/0
ip address 10.1.1.2 255.255.255.252
ipv6 address 2001:DB8:ACAD:20::2/64
clock rate 2000000
!
interface Serial0/0/1
ip address 192.168.0.253 255.255.255.252
ipv6 address 2001:DB8:ACAD:2::1/64
!
ip forward-protocol nd
!
no ip http server
no ip http secure-server
!
ip route 172.16.3.0 255.255.255.0 10.1.1.1
ip route 192.168.1.0 255.255.255.0 192.168.0.254
!
ipv6 route 2001:DB8:ACAD:1::/64 2001:DB8:ACAD:2::2
ipv6 route 2001:DB8:ACAD:30::/64 2001:DB8:ACAD:20::1
!
control-plane
!
line con 0
password cisco
logging synchronous
line aux 0
line 2
no activation-character
no exec
transport preferred none
transport input all
transport output pad telnet rlogin lapb-ta mop udptn v120 ssh
stopbits 1
line vty 0 4
password cisco
login
transport input all
!
scheduler allocate 20000 1000
!
end
Router ISP (Corrected)
ISP# show run
Building configuration...
Current configuration : 1493 bytes
!
version 15.2
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname ISP
!
boot-start-marker
boot-end-marker
!
enable secret 4 06YFDUHH61wAE/kLkDq9BGho1QM5EnRtoyr8cHAUg.2
!
no aaa new-model
memory-size iomem 15
!
ip cef
ipv6 unicast-routing
ipv6 cef
multilink bundle-name authenticated
!
interface Embedded-Service-Engine0/0
no ip address
shutdown
!
interface GigabitEthernet0/0
ip address 172.16.3.1 255.255.255.0
duplex auto
speed auto
ipv6 address Fe80::1 link-local
ipv6 address 2001:DB8:ACAD:30::1/64
!
interface GigabitEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/0/0
ip address 10.1.1.1 255.255.255.252
ipv6 address 2001:DB8:ACAD:20::1/64
!
interface Serial0/0/1
no ip address
shutdown
clock rate 2000000
!
ip forward-protocol nd
!
no ip http server
no ip http secure-server
!
ip route 192.168.0.0 255.255.254.0 10.1.1.2
!
ipv6 route 2001:DB8:ACAD::/62 2001:DB8:ACAD:20::2
!
control-plane
!
line con 0
password cisco
logging synchronous
login
line aux 0
line 2
no activation-character
no exec
transport preferred none
transport input all
transport output pad telnet rlogin lapb-ta mop udptn v120 ssh
stopbits 1
line vty 0 4
password cisco
login
transport input all
!
scheduler allocate 20000 1000
!
end
Router BRANCH (Corrected)
BRANCH# show run
Building configuration...
Current configuration : 1522 bytes
!
version 15.2
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname BRANCH
!
boot-start-marker
boot-end-marker
!
enable secret 4 06YFDUHH61wAE/kLkDq9BGho1QM5EnRtoyr8cHAUg.2
!
no aaa new-model
memory-size iomem 10
!
ip cef
ipv6 unicast-routing
ipv6 cef
multilink bundle-name authenticated
!
interface Embedded-Service-Engine0/0
no ip address
shutdown
!
interface GigabitEthernet0/0
no ip address
shutdown
duplex auto
speed auto
!
interface GigabitEthernet0/1
ip address 192.168.1.1 255.255.255.0
duplex auto
speed auto
ipv6 address FE80::1 link-local
ipv6 address 2001:DB8:ACAD:1::1/64
!
interface Serial0/0/0
ip address 192.168.0.254 255.255.255.252
ipv6 address 2001:DB8:ACAD:2::2/64
clock rate 128000
!
interface Serial0/0/1
no ip address
shutdown
!
ip forward-protocol nd
!
no ip http server
no ip http secure-server
!
ip route 0.0.0.0 0.0.0.0 192.168.0.253
!
ipv6 route ::/0 2001:DB8:ACAD:2::1
!
control-plane
!
line con 0
password cisco
logging synchronous
login
line aux 0
line 2
no activation-character
no exec
transport preferred none
transport input all
transport output pad telnet rlogin lapb-ta mop udptn v120 ssh
stopbits 1
line vty 0 4
password cisco
login
transport input all
!
scheduler allocate 20000 1000
!
end