Information Technology Reference
In-Depth Information
Task 4: Troubleshoot the HQ Router
Begin troubleshooting at the host connected to the HQ router.
Step 1.
From the host PC2, is it possible to ping PC1?
no
From the host PC2, is it possible to ping the web server on the ISP LAN?
no
From the host PC2, is it possible to ping the default gateway?
yes
Examine the HQ router to find possible configuration errors.
Step 2.
Begin by viewing the summary of status information for each interface on the router.
Are there any problems with the status of the interfaces?
Yes, the interface status and the protocol on Serial 0/0/1 are both down.
If there are any problems with the status of the interfaces, record any commands that will
be necessary to correct the configuration errors.
HQ(config)#
interface Serial0/0/1
HQ(config-if)#
clock rate 64000
If you have recorded any commands above, apply them to the router configuration now.
Step 3.
View a summary of the status information.
Step 4.
If any changes were made to the configuration in the previous step, view the summary of
the status information for the router interfaces again.
Does the information in the interface status summary indicate any configuration errors?
no
If the answer is
yes
, troubleshoot the interface status of the interfaces again.
Troubleshoot the static routing configuration on the HQ router.
Step 5.
Begin by viewing the routing table.
What routes are shown in the routing table?
172.20.1.0 is directly connected, Serial0/0/0
192.168.38.252 is directly connected, Serial0/0/1
Are there any problems with the routing table?
The route for the BRANCH LAN, 172.20.1.128/25, is missing from the routing table.
If there are any problems with the routing table, record any commands that will be neces-
sary to correct the configuration errors.
HQ(config)#
ip route 172.20.1.128 255.255.255.128 172.20.1.1
If you have recorded any commands above, apply them to the router configuration now.
Step 6.
View the routing information.
Step 7.
If any changes were made to the configuration in the previous step, view the routing table
again.
Does the information in the routing table indicate any configuration errors?
no
If the answer is
yes
, troubleshoot the routing table again.
