Aruba & ProVision-based

Re: Spanning Tree and SonicWall SonicPoints

 
Antonio Milanese
Trusted Contributor

Re: Spanning Tree and SonicWall SonicPoints

Umm..i've reread yours logs and may be I was tricked at first glance looking/searching on the wrong direction i.e. for BPDU coming from/to WAP/Sonicwalls

show span ist:

B15   100/1000T 20000     128      Designated Forwarding c09134-41a900
B16   100/1000T 20000     128      Designated Forwarding c09134-41a900
B17   100/1000T 200000    128      Root       Forwarding 001372-485db1
B18   100/1000T Auto      128      Disabled   Disabled

and now from a show span of both msti

B17   100/1000T 200000    128      Master     Forwarding c09134-41a900
B18   100/1000T Auto      128      Disabled   Disabled
B19   100/1000T Auto      128      Disabled   Disabled

notice that port b17 is flagged as master port to and outside MST region (legacy RSTP/STP !?) in both instances and as RP on ist,

now the general stats froms ist

Topology Change Count   : 585
Time Since Last Change  : 5 days

i was foolished by the fact that the topology was stable in the last 5 days and the changes were caused by power outage/tests

 

on the first post you say:

 

"Port B1 connects to the WAP, B15-B16 connect to the Sonicwalls, B21 & B23 connect to the E2510 edge switches"

 

what is attached to b17 ?

could you please post those commands outputs

sh span root-history ist
sh span root-history cst

sh span instance ist
sh span debug-counters ports B17 instance 0
sh span debug-counters ports B17 instance 1
sh span debug-counters ports B17 instance 2

Regards,

Antonio

Re: Spanning Tree and SonicWall SonicPoints

B17 is an uplink to a telco managed switch that provides a layer 2 metro-ethernet connection to another site. It is set untagged for VLAN 10. 

 

Attached is the output you requested.  Please keep in mind that yesterday I updated the switch software to the latest version (K.15.06) at the recommendation of HP Networking support, but we've already seen one of the WAPs go non-responsive this morning.

Antonio Milanese
Trusted Contributor

Re: Spanning Tree and SonicWall SonicPoints


>ITCATXCORE1# sh span root-history cst
> Status and Counters - CST Root Changes History
>  MST Instance ID        : 0        
>  Root Changes Counter   : 2          
>  Current Root Bridge ID : 0:000d56-2f6e00   
>
>  Root Bridge ID      Date     Time   
>  ------------------- -------- --------
>      0:000d56-2f6e00 10/09/11 15:35:54
>  32768:c09134-41a900 10/09/11 15:35:22

pay attention to what's in the above output:
the switch with MAC 000d56-2f6e00 with priority 0 (a rapid lookup to oid suggests a Dell Powerconnect gear) has been elected as YOUR CST root..

>sh span debug-counters ports B17 instance0
>  Topology Changes Detected   1          10/09/11 15:35:54
>  Topology Changes Tx         0                          
>  Topology Changes Rx         75         10/09/11 15:38:14
>  Topology Change ACKs Tx     0                          
>  Topology Change ACKs Rx     5          10/09/11 15:36:01
>  TCN BPDUs Tx                5          10/09/11 15:36:01

and its TC/TCN are exchanged/coming from port B17 (it's elected as a boundary port to a legacy (non MSTP) region...well can you guess what this means?
yes ofcourse...a topology change to CST will affect all MSTIs and the CIST =)

If you have only one uplink to the other site I suggest to filter BPDU filter B17 since I think we found who is our possible culprit

Regards,

Antonio

Re: Spanning Tree and SonicWall SonicPoints

I enabled BPDU filtering on port B17 last night, but we are still having the issue.   As shown below it looks like the device is still fighting to be root.  Any ideas?  If I was to assign the two wireless networks to their own MSTP instance would that exclude the network from the flapping?

 

ITCATXCORE1# sh spanning-tree root-history cst

 Status and Counters - CST Root Changes History

  MST Instance ID        : 0
  Root Changes Counter   : 98
  Current Root Bridge ID : 32768:0024a8-fd4c00

  Root Bridge ID      Date     Time
  ------------------- -------- --------
  32768:0024a8-fd4c00 10/11/11 03:23:19
  32768:0024a8-fde900 10/11/11 03:23:18
  32768:c09134-41a900 10/11/11 03:23:18
      0:000d56-2f6e00 10/11/11 03:23:18
  32768:c09134-41a900 10/11/11 03:23:18
      0:000d56-2f6e00 10/11/11 03:23:18
  32768:c09134-41a900 10/11/11 03:23:17
      0:000d56-2f6e00 10/11/11 03:23:17
  32768:c09134-41a900 10/11/11 03:23:17
      0:000d56-2f6e00 10/11/11 03:23:17

 

Re: Spanning Tree and SonicWall SonicPoints

Actually, I just looked at the current time and it looks like the switch isn't factoring in the time zone. So, the above root-history changes were all around the time I implemented bpdu-filtering last night.
Still, we had to reboot one of the WAPs this morning.
Antonio Milanese
Trusted Contributor

Re: Spanning Tree and SonicWall SonicPoints

OK, so things are not so obvious after all =)

may be you can post the following commands:

- on the 5412zl

sh span instance ist
sh span instance 1
sh span instance 2

sh span debug-counters ports A1,A4,C1,D23 instance 0
sh span debug-counters ports A1,A4,C1,D23 instance 1
sh span debug-counters ports A1,A4,C1,D23 instance 2

- on ToR E6600 #1 & #2

sh span instance ist
sh span instance 1
sh span instance 2

both before and after a WAP reboot, plus on ALL 3 switches clear log and than

show log -a

solely after WAP reboot indicating the time when happened

If you can would be nice to have the configurations (purified) of core and ToR switches.

 

Regards,

 

Antonio

Re: Spanning Tree and SonicWall SonicPoints

Last night we moved all the SonicPoint traffic to a separate switch that has no spanning tree enabled.  By mid morning once of the WAPs went unresponsive again. I believe at this point the problem is SonicWalls and the STP troubleshooting should have been concluded once bpdu-filtering was enabled.  Thanks for your help though.