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

Troubleshooting Routers

3-16

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 loadmap display is the next higher number,

compared with the number in the wfKernelEntry display, and which is the next

lower number. The protocol associated with the higher number owns the task.

Example

The following illustration 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 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

--> ftp.exe 0x3164d6e0 0042868

--> tcp.exe 0x31657e70 0057776

--> tftp.exe 0x31666030 0020488

--> snmp.exe 0x3166b050 0030328

--> tn.exe 0x316726e0 0038424

--> arp.exe 0x31685720 0009784

--> ip.exe 0x31687d70 0182004

If a signiﬁcant number of lack-of-resource errors are occurring, such as more than

50/min, report the problem to the Bay Networks Technical Response Center.

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

Sem comentários

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