OmniSwitch OS6860/OS6900/OS10K Troubleshooting Guide Part No.032996-00 Rev.A
AOS Release 7.X and 8.X January 2015
Alcatel-Lucent Page 45 of 148
swlog appid portMgrCmm subapp all level info
swlog appid intfCmm subapp all level info
swlog appid VlanMgrCmm subapp all level info
swlog appid portMgrNi subapp all level info
swlog appid VlanMgrNi subapp all level info
show log swlog
Troubleshooting by Debug Commands
BPDU statistics collection:
OS6860-> debug stp bpdu-stats 1 start
BPDU Statistics collection started For inst 1
OS6860-> debug stp bpdu-stats show 1
Port rxCfg rxRstp rxMstp rxTcn | txCfg txRstp txMstp txTcn
-------+-----+------+------+------+------+------+------+-----
1/1/1 0 0 0 0 0 0 0 0
1/1/2 0 0 0 0 0 0 0 0
1/1/3 0 11 0 0 0 1146 0 0
1/1/4 0 0 0 0 0 0 0 0
1/1/5 0 0 0 0 0 0 0 0
1/1/6 0 0 0 0 0 0 0 0
1/1/7 0 12 0 0 0 1133 0 0
1/1/8 0 0 0 0 0 0 0 0
1/1/9 0 5 0 0 0 1156 0 0
1/1/10 0 0 0 0 0 0 0 0
OS6860-> debug stp bpdu-stats 1 stop
BPDU Statistics collection Stopped
Troubleshooting in Maintenance Shell Commands
Maintenance Shell commands should only be used by Alcatel-Lucent personnel or under the direction of
Alcatel-Lucent. Misuse or failure to follow procedures that use Maintenance Shell commands in this guide
correctly can cause lengthy network down time and/or permanent damage to hardware.
To dispay the number of flush events:
SHASTA #-> pidof stpNi
2100
SHASTA #-> debug 2100 "p stpniFlushCount"
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
0xb6a8ecbc in epoll_wait () from /lib/libc.so.6
$1 = 42
Command stpni_printStats :
The usual command (show spantree [VlanId]) only shows the real topology changes in the network. The aim
of the commands introduced below is to view the topology changes frames (TCN) received by the switch that
are not causing a change in the Spanning Tree (STP) Topology Counter displayed with show spantree
[VlanId].
The commands can be used to find the sources of Topology Change STP frames (BPDUs) in a network. These
topology changes make the switch clear its MAC address table according to the spanning tree protocol, and
consequently its ARP table. This can increase the CPU load on the switch. The source of the Topology Change
can be a switch added by the users of the network, a Blade Centre that includes internal switches, etc. This can
also be a configuration error on switches cause make them send BPDUs with topology change notifications
when a port dedicated to users changes status. In that case each time a user powers up or disconnects his
computer, a topology change will be sent.
To Next Page
Loading...
