
Troubleshooting Routers
6-16
5.
Enter the following command to display the IP forwarding table:
get wfIpBaseRtEntry.7.*
The Technician Interface displays the table in the following format:
wfIpBaseRtEntry.wfIpBaseRouteNextHop.
<network>
=
<next_hop>
Identify the incorrect routes. If you take a snapshot of your network
periodically, as described in Chapter 1, comparing the data can help you to
identify the incorrect routes.
Use the Packet Capture utility or a network analyzer to trace routes through
the network to see what, if any, nodes are forwarding incorrect routing
information in the form of RIP or Link State packets.
6. Determine whether the link is operational and the communication is
bi-directional. You can do this by getting the MIB object wfOspfIfEntry.
The display shows the state of OSPF on the interface, the identity of the
DR and BDR on the segment, how many hello packets the interface
received and transmitted, and how many link state updates it received,
and received and transmitted.
Troubleshooting IPX
This section assumes that you have isolated a problem to IPX. If not, refer to
Chapter 2 to determine whether these instructions apply to your problem.
This section assumes that you have loaded the scripts. Refer to Using Technician
Interface Scripts for instructions.
Troubleshoot IPX as follows:
1. Use the Events Manager or the Technician Interface to filter the log to
display messages of all severity levels for IPX running on the slots in
question.
The Technician Interface command is
log -fftwid -eIPX -s
<slot_no.>
Example
If you are filtering events from Slots 3 and 4, you enter
log -fftwid -eIPX -s3 -s4
Comentários a estes Manuais