Information Technology Reference
In-Depth Information
Attempt to ping between the hosts again.
Step 8.
From the host PC2, is it possible to ping PC1?
yes
From the host PC2, is it possible to ping the Serial 0/0/1 interface of the ISP router?
yes
From the host PC1, is it possible to ping the web server on the ISP LAN?
no
Task 5: Troubleshoot the ISP Router
Begin troubleshooting at the host connected to the ISP router.
Step 1.
From the web server on the ISP LAN, is it possible to ping PC1?
no
From the web server on the ISP LAN, is it possible to ping PC2?
no
From the web server on the ISP LAN, is it possible to ping the default gateway?
yes
Examine the ISP 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?
The FastEthernet 0/0 interface is administratively down.
If there are any problems with the status of the interfaces, record any commands that will
be necessary to correct the configuration errors.
ISP(config)#
interface FastEthernet0/0
ISP(config-if)#
no shutdown
If you have recorded any commands, 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 ISP router.
Step 5.
Begin by viewing the routing table.
What routes are shown in the routing table?
172.20.0.0 [1/0] via 192.168.38.254
192.168.38.252 is directly connected, Serial0/0/1
192.168.39.64 is directly connected, FastEthernet0/0
Are there any problems with the routing table?
The wrong subnet mask is used in the
ip route
statement for the 172.0.0.0 network.
If there are any problems with the routing table, record any commands that will be neces-
sary to correct the configuration errors.
ISP(config)#
no ip route 172.20.0.0 255.255.255.0 192.168.38.254
ISP(config)#
ip route 172.20.0.0 255.255.254.0 192.168.38.254
