Troubleshooting Ethernet Problems
265
1, L2 - IS-IS level-2, * - candidate defaultU - per-user
static route, o - ODR
Gateway of last resort is not set
172.16.0.0/16 is variably subnetted, 3 subnets, 2 masks
C 172.16.60.0/24 is directly connected, Ethernet0/1
C 172.16.50.0/24 is directly connected, Ethernet0/0
D 172.16.30.4/30 [90/2195456] via 172.16.50.1,
00:02:59, Ethernet0/0
D 172.16.10.0/24 [90/3295676] via 172.16.50.1,
00:02:59, Ethernet0/0
Router_C>
Everything looks as if it is in place, but the ultimate test is to FTP from
Host Z to Host A. The connection was successful.
C:\WINDOWS>ftp 172.16.10.2
> ftp: connect :10061
ftp>
Let's review the steps taken. The observation was that Host Z could not
FTP to Host A. The problem was isolated by using the ping and traceroute
commands. After the problem was isolated, the correct observations were
made that enabled a problem statement to be made. The problem was that
Router B was in boot mode. This happened because the IOS image
was loaded from the ROM instead of flash. The problem was remedied by
changing the configuration register to indicate that the image should be
loaded from the system flash.
The effect of the configuration changes was validated by showing the routes
present on each router, as well as establishing an FTP session with Host A.
Troubleshooting Ethernet Problems
A
s the heading depicts, this section includes troubleshooting Ether-
net-related problems. The examples are simple, and you need to use only
Ethernet-related commands to effectively troubleshoot these problems.
Copyright ©2000 SYBEX , Inc., Alameda, CA
www.sybex.com