
Troubleshooting Routers
1-4
Responding to a Failed prom Command
If you reboot after the prom command fails, a Bay Networks representative must
reinsert new PROMs (programmable, read-only memory chips) on the board and
rewrite the PROM software to them before the router can recover.
Preparing to Troubleshoot
• “Getting Acquainted with the Troubleshooting Tools”
•“T
aking a Snapshot of Your Network”
Getting Acquainted with the Troubleshooting Tools
Troubleshooting is much more complicated when you have to solve a problem
that requires an urgent solution and at the same time learn the how to use the tools
you need to solve the problem. Read this section and familiarize yourself with the
tools before you begin troubleshooting. The instructions later in this manual
assume you can use the tools identified in this section.
This chapter includes the following sections:
•“Using the System Lo
g to Display Event Messages”
•“Displa
ying and Changing Configuration Settings and Statistics”
•“Using Ping
”
•“Using P
acket Capture”
•“Using Inbound
Telnet to Access the Technician Interface”
Using the System Log to Display Event Messages
The processor running software in each slot maintains its own log file in local
memory. Software entities (such as CSMACD and IP) report messages when
routine and noteworthy events occur. When you command Site Manager or the
Technician Interface to display the messages, the router automatically assembles
the messages from all slots into a single file and displays the file. Use the
messages in this file to diagnose a problem with a port, slot, router, or protocol.
Caution:
If the Technician Interface
prom
command fails, do not reboot.
Instead, call the Bay Networks Technical Response Center.
Comentários a estes Manuais