Avaya Troubleshooting Routers Instrukcja Naprawy Pobierz pdf (Strona 131)

Troubleshooting a Network Layer Problem

308656-14.00 Rev 00

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 an OSI connection as follows:

Use the Events Manager or the Technician Interface to filter the log to

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

question.

The Technician Interface command is as follows:

log -fftwid -eOSI -s

<slot_no.>

Example

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

log -fftwid -eOSI -s3 -s4

Enter the following command 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 to display. Valid values are as

follows:

•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

identifiers are in hexadecimal notation.

1 2 ... 126 127 128 129 130 131 132 133 134 135 136 ... 267 268

Brak uwag

Avaya Troubleshooting Routers Instrukcja Naprawy Strona 131