Avaya Troubleshooting Routers Guía para resolver problemas descargar pdf (Pagina 126)

Troubleshooting Routers

6-16

308656-14.00 Rev 00

The Technician Interface displays the table in the following format:

wfIpBaseRtEntry.wfIpBaseRouteNextHop.

<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 Packet Capture 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 (LSPs).

Determine whether the link is operational and the communication is

bidirectional. You can do this by displaying the MIB object

wfOspfIfEntry.

The display shows the state of OSPF on the interface, the identity of the

designated router (DR) and backup designated router (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. See Using Technician

Interface Scripts for instructions.

Troubleshoot an IPX connection as follows:

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 as follows:

log -fftwid -eIPX -s

<slot_no.>

Example

If you are filtering events from slots 3 and 4, enter the following commands:

log -fftwid -eIPX -s3 -s4

1 2 ... 121 122 123 124 125 126 127 128 129 130 131 ... 267 268

Sin comentarios

Avaya Troubleshooting Routers Guía para resolver problemas Pagina 126