Avaya Troubleshooting Routers Guide de dépannage télécharger pdf (Page 67)

Troubleshooting an Operational Problem

3-15

wfKernelEntry.wfKernelBufOwnerTask3.2 = "31619B04"

wfKernelEntry.wfKernelMemOwnerTask1.2 = "3002923E"

. . .

wfKernelEntry.wfKernelMemOwnerTask3.2 = "30081CF6"

. . .

3. To determine which protocols are running, enter the following Technician

Interface command:

loadmap

<slot_no.>

Example

$ loadmap 2

----------------------

Loadmap from SLOT 2:

----------------------

--> arp.exe 0x31685720 0009784

--> vines.exe 0x315f47e0 0121448

--> ftp.exe 0x3164d6e0 0042868

--> tcp.exe 0x31657e70 0057776

--> tftp.exe 0x31666030 0020488

--> snmp.exe 0x3166b050 0030328

--> tn.exe 0x316726e0 0038424

--> ip.exe 0x31687d70 0182004

--> tms380.exe 0x3158ef80 0094428

--> hdlc.exe 0x31612260 0058496

--> dst.exe 0x315f3730 0004244

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.

The column on the right of the loadmap display shows the number of bytes

assigned to the module. (If you convert the number of bytes to hexadecimal

format and add it to the PC code to the left, the number equals the PC code of the

next module in memory.)

Note: Issue the loadmap command on the same slot on which you entered the

get wfKernelEntry.*.

<slot_no.>

command. The order of the tasks change each

time you boot a slot.

1 2 ... 62 63 64 65 66 67 68 69 70 71 72 ... 253 254

Pas de commentaire

Avaya Troubleshooting Routers Guide de dépannage Page 67