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

Troubleshooting Routers

3-14

308656-14.00 Rev 00

The Technician Interface displays the following:

-- How much memory is available

-- The starting program counter (PC, which is the address location in

memory) of the task

The Technician Interface displays each task as a PC code in the

wfKernelEntry.wfKernelBufOwnerTask lines

-- The number of buffers allocated for each task

Example

This example shows only the most important lines in the display.

$ get wfKernelEntry.*.2

wfKernelEntry.wfKernelSlot.2 = 2

wfKernelEntry.wfKernelMemorySize.2 = 23752016

wfKernelEntry.wfKernelMemoryFree.2 = 21139840

. . .

wfKernelEntry.wfKernelBufOwnerTask1.2 = "315910F4"

. . .

wfKernelEntry.wfKernelBufOwnerTask2.2 = "31619B04"

. . .

wfKernelEntry.wfKernelBufOwnerTask3.2 = "31619B04"

wfKernelEntry.wfKernelMemOwnerTask1.2 = "3002923E"

. . .

wfKernelEntry.wfKernelMemOwnerTask3.2 = "30081CF6"

. . .

To determine which protocols are running on the slot, enter the following

Technician Interface command:

loadmap

<slot_no.>

The loadmap display shows the protocols and other executable software

modules running on the slot. Their associated starting PC codes are in

hexadecimal format. The starting PC code of each wfKernelEntry attribute is

a higher number than the PC code of its associated protocol.

Example

$ loadmap 2

Note:

Issue the loadmap command on the same slot on which you issued the

get wfKernelEntry.*.

<slot_no.>

command. The order of the tasks changes

each time you boot.

1 2 ... 61 62 63 64 65 66 67 68 69 70 71 ... 267 268

Sin comentarios

Avaya Troubleshooting Routers Guía para resolver problemas Pagina 66