Avaya Troubleshooting Routers Anleitung zur Fehlerbehebung PDF herunterladen (Seite 67)

Troubleshooting an Operational Problem

308656-14.00 Rev 00

3-15

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

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 column to the right of the display shows the number of bytes assigned to the

module. If you convert the number of bytes to hexadecimal format and add it to

PC code, the number equals the PC code of the next module in memory.

Determining which protocol owns a task can help you determine which protocols

are using the most memory. To do this, compare the PC code of the wfKernelEntry

attribute with the starting PC codes in the

loadmap display. Determine which PC

code in the display is the next higher number, compared with the number in the

wfKernelEntry display, and which PC code is the next lower number. The protocol

associated with the higher number owns the task.

Example

The following example shows another portion of the response to the get

wfKernelEntry.*.2

command:

$ get wfKernelEntry.*.2

. . .

wfKernelEntry.wfKernelMemOwnerTask6.2 = "315F7F08"

To make comparisons easier, the following illustration of the loadmap display

reorganizes the entries by PC code. You can determine that the PC code 315F7F08

is a higher number than the PC code associated with the vines.exe software

module, and that it is lower than the next highest PC code in the display, hdlc.exe.

Therefore, the task is a VINES task.

$ loadmap 2

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

Loadmap from SLOT 2:

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

--> tms380.exe 0x3158ef80 0094428

--> dst.exe 0x315f3730 0004244

--> vines.exe 0x315f47e0 0121448

--> hdlc.exe 0x31612260 0058496

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

Kommentare zu diesen Handbüchern

Keine Kommentare

Avaya Troubleshooting Routers Anleitung zur Fehlerbehebung Seite 67

Kommentare zu diesen Handbüchern

Verwandte Produkte und Handbücher für Vernetzung Avaya Troubleshooting Routers