Avaya Troubleshooting Routers Guia de Resolução de Problemas descarregar pdf (Página 127)

Troubleshooting a Network Connection Problem

6-21

Troubleshooting OSI

This section assumes that you have isolated a problem to OSI. If not, refer to

Chapter 2 to determine whether these instructions apply to your problem.

Troubleshoot OSI as follows:

1. Use the Events Manager or the Technician Interface to ﬁlter the log to

display messages of all severity levels for OSI running on the slots in

question.

The Technician Interface command is

log -fftwid -eOSI -s

<slot_no.>

Example

If you are ﬁltering events from Slots 3 and 4, you enter

log -fftwid -eOSI -s3 -s4

Enter the following command and parameters to request data from the

OSI interface:

osidata -s

-t

<type>

-i

<ID>

<slot no.> is the number of a slot on which the OSI service is running on the

router. Valid values are 1 to 13, inclusive.

<type> is the database information you want displayed. Valid values are

• lsp_L1 — link state packet for Level 1

• lsp_L2 — link state packet for Level 2

• path_L1 — internal path control block for Level 1 path

• path_L2 — internal path control block for Level 2 path

• adj_L1 — adjacency control block for Level 1

• adj_L2 — adjacency control block for Level 2

• adj_ES — adjacency control block for end system

<ID> is the identifier for the database information. The ID varies in length,

depending on the type. For example, the LSP ID is 8 bytes, the adj ID is 6

bytes, and the path ID (also referred to as the router ID) is 6 bytes. All

identiﬁers are in hexadecimal notation.

1 2 ... 122 123 124 125 126 127 128 129 130 131 132 ... 253 254

Sem comentários

Avaya Troubleshooting Routers Guia de Resolução de Problemas Página 127