Filter
Top Products
Troubleshooting the Switch System Troubleshooting IPC on OS-6/7/8XXX Series of Switches
OmniSwitch Troubleshooting Guide September 2005 page 1-31
Now doing a task trace on this task can be helpful to see if the task is moving:
Working: [Kernel]->tt 0x67f3c10
108e9c vxTaskEntry +c : Letext (&dataInfo, 67f3920, 67f3a20, 34000000, 66ff8
00, 6a69800)
66b69b4 Letext +2d4: zcSelect (5, 67f3a20, 0, 0, 6a6c800, 247)
6ff56f8 zcSelect +458: semTake (67eedc0, ffffffff, a, 28, a, 0)
158b4c semTake +2c : semBTake (67eedc0, ffffffff, &semTakeTbl, 0, &semBTa
ke, 264c00)
value = 0 = 0x0
Working: [Kernel]->
Using this command multiple times will give an idea if the task is stuck in some routine.
Gathering this data and attaching in the Problem Report will help Engineering to identify the source of the
problem.
The CMM also keeps a prospective of NI for their IPC Pools. These can be displayed using the following
commands:
• IpcSlotPools slot,slice
• IpcSlotUrgentPoolsDetail slot,slice
• IpcSlotControlPoolsDetail slot,slice
• IpcSlotNormalPoolsDetail slot,slice
• IpcSlotJumboPoolsDetail slot,slice
• IpcSlotLocalPoolsDetail slot,slice
Rest of the information about the sockets and the tasks can be found using the same commands as
discussed above.
If a NI generating many IPC messages then CMM might not be able to see the IPC pools of that and as
well as any other NI. E.g.
Certified: [Kernel]->ipcSlotPools 6,0
ipcSlotPools slot 6, slice 0
UrgentPool: Full size is 0, remaining: 256
In socket queues: 0 Not queued: 0:
In DMA queues: 0
ControlPool: Full size is 0, remaining: 1024
In socket queues: 0 Not queued: 0:
In DMA queues: 0
NormalPool: Full size is 0, remaining: 255
In socket queues: 0 Not queued: 0:
In DMA queues: 0
JumboPool: Full size is 0, remaining: 64
In socket queues: 0 Not queued: 0:
In DMA queues: 0