Vinay -
Thanks so much.
Many thanks.
I am definitely having MSTP issues. Whether the Aruba gear is the victim or the perpetrator is what I’m trying to deduce, and the Aruba is something I am only slightly up to speed on.
- Setup:
HP Core switch
5 HP Edge switches connected
1 Aruba S1500 connected as edge (it is both for AP control as well as my Internet Layer 3 connection)
1 Aruba 7210 connected
All of the edge switches recognize the Core as CST root
The problem:
It’s a weird one! Every morning (literally every morning 7 days a week) between 9 and 9:40 in the morning, I have a broadcast storm on the switch stack and HP errors indicating CST election conversations going on. I keep on trying to find a single culprit. We are a zoo, open 7 days a week, and systems do come on at this time. But to date, we have not been able to find a smoking gun here.
The temporary fix:
if I reboot one or two of the edge switches, the storm goes away. Also, if I temporarily disconnect the Aruba controller, the storm clears. I don’t have STP on the controller and I did have TAC look at that pretty extensively, so I don’t think it’s the culprit. Plus, the problem is once a day at the same time, and the controller doesn’t do anything on that kind of schedule.
So, to answer your questions:
> What is the IP connectivity interface
Hmm, I’m not sure. I’m attaching the config file.
> Can you run a continous ping to switch connectivity IP address & see if any drops
Continuous ping no problem
> If you have console access to switch, run the below commands
> show clock
hmm, I am off by an hour
> show spanning-tree | include Last (repeat this command multiple times after few seconds)
Last TC received on intf GE0/0/23, on 2015-04-21 20:35:45 (EST)
and that doesn't change
> show log all 50 | include Flushing (repeat this command multiple times after few seconds)
Apr 22 13:36:58 :340004: <WARN> |l2m| Flushing mac-addresses on GE0/0/23 vlan-id 1 due to STP topology change
Apr 22 13:36:58 :340004: <WARN> |l2m| Flushing mac-addresses on GE0/0/23 vlan-id 99 due to STP topology change
Apr 22 13:36:58 :340004: <WARN> |l2m| Flushing mac-addresses on GE0/0/23 vlan-id 110 due to STP topology change
Apr 22 13:36:58 :340004: <WARN> |l2m| Flushing mac-addresses on GE0/0/23 vlan-id 114 due to STP topology change
Apr 22 13:36:58 :340004: <WARN> |l2m| Flushing mac-addresses on GE0/0/23 vlan-id 999 due to STP topology change
Apr 22 13:36:58 :340004: <WARN> |l2m| Flushing mac-addresses on GE0/0/8 vlan-id 114 due to STP topology change
Apr 22 13:36:58 :340004: <WARN> |l2m| Flushing mac-addresses on GE0/0/9 vlan-id 114 due to STP topology change
Apr 22 13:36:58 :340004: <WARN> |l2m| Flushing mac-addresses on GE0/0/18 vlan-id 99 due to STP topology change
Apr 22 13:36:58 :340004: <WARN> |l2m| Flushing mac-addresses on GE0/0/20 vlan-id 999 due to STP topology change
Apr 22 13:47:35 :340004: <WARN> |l2m| Flushing mac-addresses on GE0/0/22 vlan-id 114 due to STP topology change
and nothing today.
#7210