Alcatel Carrier Internetworking Solutions 6800 User Manual

Troubleshooting Spanning Tree

Writing a PR for Spanning Tree

OmniSwitch Troubleshooting Guide

page 4-27

If the show spanning tree CLI command still displays the same information while a port state has changed 
then the problem could be due to a broken communication path between the CMM and NI. In this case do 
the following (for both the CMM and NI):

• Time-out trace of the socket handler (stpNISock_totraceprint or stpCMMSock_totraceprint).

• Warning trace of the socket handler (stpNISock_warningprint or stpCMMSock_warningprint).

• Event trace (stpni_traceprint and stpCMM_traceprint).

• Board-up trace (stpNISock_boardupprint or stpCMMSock_boardupprint).

For analysis of Spanning Tree on an NI do the following:

• Event trace (stpni_traceprint).

• Dump the port trace (stpni_debugport).

• Time-out trace of the socket handler (stpNISock_totraceprint or stpCMMSock_totraceprint).

• Warning trace of the socket handler (stpNISock_warningprint or stpCMMSock_warningprint).

• Inter-NI trace: (stpNISock_intraceprint).

• Boards seen alive by the Socket Handler (stpNISock_boardupprint or 

stpCMMSock_boardupprint).

For analysis of Spanning Tree on a CMM do the following:

• Event trace (stpCMM_traceprint).

• Time-out trace of the socket handler (stpNISock_totraceprint or stpCMMSock_totraceprint).

• Warning trace of the socket handler (stpNISock_warningprint or stpCMMSock_warningprint).

• Boards seen alive by the Socket Handler (stpNISock_boardupprint or 

stpCMMSock_boardupprint).