Allied Telesis AT-8900 Series - Manual
Allied Telesis AT-8900 Series – Manual, read for free online in PDF format. We hope this helps you resolve any issues you may have. If you have further questions, please contact us through the contact form.
Table of Contents:
- Page 2 – Starting off; Concrete piece of advice #1: Capture everything
- Page 3 – Following up theories
- Page 4 – What counters are changing?
- Page 5 – Providing a convincing case; Annotating afterwards
C613-16028-00 REV B
www.alliedtelesis.com
Best Practice |
Introduction
This How To Note describes techniques for on-site debugging. It is in no way intended to be
a comprehensive guide to debugging Allied Telesis equipment. Instead, it is aimed at passing
on some techniques that have been found to be useful. Particularly, this document describes
techniques which:
z
make it less likely that you will miss important pieces of information
z
make it simpler for someone else to analyse the debug information that you capture
z
enable you to be more accurate in after-the-event discussions of what you saw.
Which products does it apply to?
This document applies to the following Allied Telesis routers and managed layer 3 switches:
z
AR300, AR400, and AR700 series routers
z
AT-8600, AT-8700XL, AT-8800, Rapier, and Rapier i series switches
z
AT-9800 series switches
z
AT-8900, AT-9900, and AT-9900s series switches
z
x900 series switches
z
SwitchBlade series switches
Related How To Notes
You also may find the following How To Notes useful, because they specifically discuss how to
debug connections:
z
How To Troubleshoot ISDN Connections
z
How To Troubleshoot VPNs
Note that many other How To Notes include troubleshooting information as well as
configuration examples.
How To Notes are available from
www.alliedtelesis.com/resources/literature/howto.aspx
On-Site Debugging
"Loading the manual" means you need to wait until the file loads and becomes available for online reading. Some manuals are very large, and the time they take to appear depends on your internet speed.
Summary
2 Starting off When going on-site to investigate a network problem, your guiding aim is to understand the root cause of the problem, which might be: z a cable plugged into the wrong socket z a misconfiguration of some piece of equipment z an interoperability problem between two pieces of equipment z...
3 show ip count show pim route show pim count show pim neighbour and other commands relevant to the hardware forwarding of multicast in the particular models of switch you are working with. Once this initial survey is complete, you can start following up your theories about what is going on. Followi...
4 All the way through the capture, type (just at the CLI prompt) what you are thinking, and what you are doing. Just write it as stream-of-consciousness, things like: “Hmmm.. that counter value looks strange, lets look at this a bit more” “I have just pulled out blade 5, lets look the internal ports...
