|
Home > Archive > CCNP > October 2004 > What is the best, brief troubleshooting book?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
What is the best, brief troubleshooting book?
|
|
| c3533586 2004-09-18, 2:37 am |
| I am looking for a book that covers troubleshooting live issues on cisco routers and switches. I know there is the CIT book, but I want something small, brief and straight to the point that will cover things like, troubleshooting slowness, an outage, flapping interfaces, etc...the most common things that are seen. AKA....if you have this problem then use these commands to diagnose, etc, etc. Because in the real world it is all about how quicly you can get the network back up. Any feedback welcome. | |
| Just Visiting 2004-09-28, 4:04 pm |
| There is no book like you describe to my kmowledge and with good reason. No one could possibly describe all the situations that a tech can cause on a network. If you understand a technology well you will understand what to look for to solve your issue. Unfortunately it usually means understanding several technologies and how they interact to find and correct the problem.
Want the best hint on how to fix what seems to be a difficult problem on your network? Go find the last change made to the config!
-JV | |
| peterd 2004-09-30, 7:09 am |
| Hello,
yes, that sums it up nicely.
It's down to experience unfortunately. You could get by with a good faulting technique...
keep a record of everything that you (or other) do and undo the last change.
Or keep a backup copy every time you change something and you can go backwards progressively to get a working system again (similar to the 'Last Known Good' when booting a dodgy PC).
If it's not something that you did recently, then you're down to removing suspect bits of hardware/config until it works and then move forward from there.
In a worst case you go for 'minumum config', again either on hardware, software or configuration and re-build bit by bit testing at every stage.
I don't recall seeing a simple 'if this then do that' guide as there's an infinate number of possibilites.
There could be money in writing one!
The CIT book gives some hints on how to chase faults.
Regards
Peter | |
| nethead 2004-09-30, 8:20 am |
| If there are any short books on this then I don't see how they can comprehensively cover this area.
Troubleshooting is a vast area and often the first time you come across an issue will be in a live environment as it is impossible to cover every problem in a book.
Make sure you know the relevent show and debug commands for each topic and understand the output that this gives you. This will take you a long way in the troubleshooting world. | |
| SureshHomepage 2004-10-16, 6:12 pm |
| Laura Chapel’s book on CIT covers most of the issues related to reasons behind interface resetting, runts, interface queues, collision aspects, dial-up/ISDN troubleshooting, fragmentation/error packets, RST/CST counters etc. If you want more on the chassy related hardware issues visit cisco.com You would get more than handful of pdf files listed for each chassy.
Other than that I found good use of the website run by her. I really love the way she explains the SMTP, Telnet, FTP, DNS protocol conversations with peers/daemons, troubleshooting ICMP, analysis on TCP stack protocols, with the help of block diagrams and screen shots from a sniffer perspective.
Its really worth visiting her website and she really deserves a huge patronage for her priceless contributions to the network community.
http://www.packet-level.com | |
|
|
| Just Visiting 2004-10-21, 9:48 pm |
| Darthee,
I still like and respect ya 
-JVee | |
| yanqui 2004-10-22, 4:57 pm |
|  | |
| darthfeces 2004-10-26, 11:36 pm |
| maybe one could swing on over to the ccie forum it's utterly useless .... |
|
|
|
|