Alcatel OmniSwitch 6624 Troubleshooting Manual page 52

Troubleshooting IPC on OS-6/7/8XXX Series of Switches
LocalPool: Full size is 0, remaining: 1024
In socket queues: 0 Not queued: 0:
In DMA queues: 0
value = 6 = 0x6
The above display of the command does not show the Full size of any of the pools. This indicates that
CMM is unable to view the IPC pools of the NI. In this scenario, one needs to load the NI Debugger and
go to the NI and look at the IPC Pools. One of the NI would be generating many IPC messages that would
result in IPC sockets to be eaten up by that NI resulting in flooding of enormous amount of IPC messages
and in turn loosing communication with the CMM.
The following is an example of using the NiDebug command to display the IPC pools of all NIs.
Certified:[Kernel]->NiDebug
nidbg> ipc_pools
ipc_pools
UrgentPool: Full size is 256, remaining: 256
In socket queues: 0 Not queued: 0:
In DMA queues: 0
ControlPool: Full size is 1024, remaining: 1024
In socket queues: 0 Not queued: 0:
In DMA queues: 0
NormalPool: Full size is 256, remaining: 131
In socket queues: 123 Not queued: 2:
In DMA queues: 0
JumboPool: Full size is 64, remaining: 64
In socket queues: 0 Not queued: 0:
In DMA queues: 0
LocalPool: Full size is 1024, remaining: 1024
In socket queues: 0 Not queued: 0:
In DMA queues: 0
value = 0 = 0x0
nidbg> ipc_normal_pools_detail 10
NormalPool: Full size is 256, remaining: 135
Socket ID = 0x19, dest slot = 2, remote addr = 0x3030002, ipc status = S
Task ID = 0x17fd170, PayLoad Len= 128,
62d108
next = 0x17ca60c, pFreeQ = 0x2fc7a8, data_offset = 0, free_list_num = 6
Socket ID = 0x19, dest slot = 2, remote addr = 0x3030002, ipc status = S
Task ID = 0x17fd170, PayLoad Len= 128,
630108
next = 0x17c8bec, pFreeQ = 0x2fc7a8, data_offset = 0, free_list_num = 6
Socket ID = 0x19, dest slot = 2, remote addr = 0x3030002, ipc status = S
Task ID = 0x17fd170, PayLoad Len= 128,
page 1-32
ipc_normal_pools_details
ipc priority = 0x1, data ptr = 0x1
ipc priority = 0x1, data ptr = 0x1
ipc priority = 0x1, data ptr = 0x1
OmniSwitch Troubleshooting Guide
Troubleshooting the Switch System
September 2005