Alcatel Carrier Internetworking Solutions 6800 User Manual
Troubleshooting Spanning Tree
Dshell
OmniSwitch Troubleshooting Guide
September 2005
page 4-7
0 0
660885c : 0 0 0 0 0 0
0 0
value = 1 = 0x1
Binary: 0000 0000 0011
For VLAN 1 the bits set are 203 which are equivalent to binary 0000 0000 0011. Bits 1 and 2 are set indi-
cating that ports 1 and 2 have the spanning tree vector set for VLAN 1. The next register value is for
VLAN 2, hex value is 8000000.
cating that ports 1 and 2 have the spanning tree vector set for VLAN 1. The next register value is for
VLAN 2, hex value is 8000000.
Binary: 1000 0000 0000 0000 0000 0000 0000
Binary value indicates that bit 28 is set which means that port 24 is set for VLAN 2. The next register
value will indicate the value for VLAN 3. Hex value is c00.
value will indicate the value for VLAN 3. Hex value is c00.
Binary: 1100 0000 0000
Bits 11 and 12 are set indicating that spanning tree has been set for ports 11 and 12. These ports are
forwarding.
forwarding.
Each NI when boots up sends a message to every other NI indicating that it is up and running. This
message is critical for setting up the port Queues to transfer data as well as for Spanning tree. If an IPC
message is lost by a particular NI then other NI will not see that NI as being a part of spanning tree
domain. This may result in split spanning tree leading to a layer 2 loop. This kind of scenario might
happen in the case of hot swaps.
message is critical for setting up the port Queues to transfer data as well as for Spanning tree. If an IPC
message is lost by a particular NI then other NI will not see that NI as being a part of spanning tree
domain. This may result in split spanning tree leading to a layer 2 loop. This kind of scenario might
happen in the case of hot swaps.
To verify that each NI known about every other NI the following command should be used in NI Debug-
ger, This should be run on all NIs that are used in STP.
ger, This should be run on all NIs that are used in STP.
Working: [Kernel]->NiDebug
1:0 nidbg> stpNISock_boardupprint
1:0
1:0 STP boards up :
1:0 board in slot : 2 slice : 0 is up
1:0 board in slot : 4 slice : 0 is up
1:0 board in slot : 5 slice : 0 is up
1:0 board in slot : 6 slice : 0 is up
1:0 board in slot : 7 slice : 0 is up
1:0 board in slot : 8 slice : 0 is up
1:0 board in slot : 9 slice : 0 is up
1:0 board in slot : 10 slice : 0 is up
1:0 board in slot : 11 slice : 0 is up
1:0 board in slot : 12 slice : 0 is up
1:0 board in slot : 13 slice : 0 is up
1:0 board in slot : 14 slice : 0 is up
1:0 board in slot : 16 slice : 0 is up
1:0 value = 0 = 0x0
1:0 nidbg> stpNISock_boardupprint
1:0
1:0 STP boards up :
1:0 board in slot : 2 slice : 0 is up
1:0 board in slot : 4 slice : 0 is up
1:0 board in slot : 5 slice : 0 is up
1:0 board in slot : 6 slice : 0 is up
1:0 board in slot : 7 slice : 0 is up
1:0 board in slot : 8 slice : 0 is up
1:0 board in slot : 9 slice : 0 is up
1:0 board in slot : 10 slice : 0 is up
1:0 board in slot : 11 slice : 0 is up
1:0 board in slot : 12 slice : 0 is up
1:0 board in slot : 13 slice : 0 is up
1:0 board in slot : 14 slice : 0 is up
1:0 board in slot : 16 slice : 0 is up
1:0 value = 0 = 0x0
This command will show all the other slots except for itself.
To look at all the BPDUs being received and transmitted on a particular slot and slice the following
command can be used in NiDebug command. This will display, BPDUs as well as notifications when
there is a topology change in real time.
command can be used in NiDebug command. This will display, BPDUs as well as notifications when
there is a topology change in real time.
1:0 nidbg> stp_printf_flag=1
1:0 *** stpkern_bpduIn stp_id=511 portid=c type=2
1:0 PIM port c state 4 1024 0
1:0 PIM port c state 4 1024 0