Alcatel Carrier Internetworking Solutions 6800 User Manual

Page of 614
Troubleshooting the Switch System
Dshell Troubleshooting
OmniSwitch Troubleshooting Guide
September 2005
page 1-21
tCS_CVM
Chassis Version Manager
SesMon_12
Session Monitor
tTelnetOut0e4208c
Telnet Outgoing
tTelnetIn0
Telnet Incoming
CliShell0
CLI session 0 shell Task
tPolMonSvr
Policy Manager Monitor LDAP Servers
tDcacheUpd
FPGA Support
To further qualify the source of the problem we need to look at each and every NI.
Troubleshooting NIs on OmniSwitch 7700/7800/8800
Looking at the health statistics of each NI would give an idea about which one is causing the problem. 
Following CLI command can be used to diagnose:
Show health <slot number> 
Example:
-> show health 5
* - current value exceeds threshold
Slot  05
1 Min 1 Hr 1 Hr
Resources
Limit Curr
Avg
Avg
Max
----------------+-------+-----+------+-----+-----+-------
Receive
80
01
01
01
01
Transmit/Receive
80
01
01
01
01
Memory
80
39
39
39
39
Cpu
80
21
22
21
24
The NI Debugger software can be launched in Dshell using the following command:
Working: [dshell]-> <nidebug
This will launch the NI Debugger. To change to a specific slot and slice (Coronado) the following 
command can be used:
changeSlot slot,slice
Now the processor on that slot can be accessed just like CMM to see all tasks (running or suspended), 
tasks consuming the CPU the most, and other commands like task trace (tt) or task info (ti).
Working: [Kernel]->NiDebug
1:0 nidbg>
1:0 nidbg> nisup_cpuShow
1:0
1:0 Task                 Cpu
1:0 Id       Name        Abs  Rel
1:0 -------- ----------- ---- ----
1:0 017fd170 tsHw_qdisp   13%  13%
1:0 015ea1c0 taIpni        2%   9%
1:0 015fae50 taVmnCtrl     0%   2%