From: Chuck Larrieu (chuck@xxxxxxxxxxxxx)
Date: Sun May 27 2001 - 12:09:10 GMT-3
Best? For you or for me? For me it is getting there :->
There are only so many ways to break things. You have to be organized in how
you approach. I have come up with five categories of trouble:
1) router issues
console baud rates, router config register settings, bad IOS images, etc
2) physical layer
bad cables, cables inserted upside down, cables connected to the wrong port,
etc
I would put "interfaces in shutdown state" into this category. Others might
differ.
3) data link layer
serial line protocols, clock rates, NMBA issues for frame and ATM, VLAN
issues such as names, ports set into proper VLAN, etc
4) network layer
numbering, routing protocol configuration, etc.
5) higher layers
problems caused by access lists, route maps, distribute lists,
authentication, filtering,
Thing is, my list may be different from yours, or any one else's. but I have
a list. This list should serve you in constructing your lab and it should
serve you in troubleshooting it.
Knock 'em dead!
Chuck
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
mascot net
Sent: Saturday, May 26, 2001 5:36 PM
To: ccielab@groupstudy.com
Subject: Troubleshooting
Please recommend the best strategy I should follow for
the troubleshooting section. 4 more day to go...
Mascot
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:54 GMT-3