Static Routing - Routing Protocols and Concepts - page 107

Use the ping command to test connectivity between directly connected routers.

Step 2.

From router R2, is it possible to ping R1 at 172.16.2.1? yes

From router R2, is it possible to ping R3 at 192.168.1.1? yes

If the answer is no for any of these questions, troubleshoot the configurations to find the
error using the following systematic process:

Check the cabling. 1.

Are the routers physically connected? yes

Are link lights blinking on all relevant ports? yes

Check the router configurations. 2.

Do they match the topology diagram in Figure 2-10? yes

Did you configure the clock rate command on the DCE side of the link? yes

Has the interface been activated or enabled? yes

3.

Check the router interfaces using the show ip interface brief command. Are the
interfaces up and up? yes

4.

If your answer to all three steps is yes , you should be able to successfully ping from
R2 to R1 and from R2 to R3.

Use the ping command to check connectivity between devices that are not directly con-
nected.

Step 3.

From the host PC3, is it possible to ping the host PC1? no

From the host PC3, is it possible to ping the host PC2? no

From the host PC2, is it possible to ping the host PC1? no

From the router R1, is it possible to ping router R3? no

These pings should all fail. Why?

At this point, routers only know about directly connected networks.

Task 7: Gather Information

Check the status of interfaces. Step 1.

Check the status of the interfaces on each router with the show ip interface brief com-
mand. The following output is for R2:

R2# show ip interface brief
Interface IP-Address OK? Method Status Protocol

FastEthernet0/0 172.16.1.1 YES manual up up

FastEthernet0/1 unassigned YES unset administratively down down

Serial0/0/0 172.16.2.2 YES manual up up

Serial0/0/1 192.168.1.2 YES manual up up

Vlan1 unassigned YES manual administratively down down