NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Configuration of RSTP to stop my network frequently Dying.
We have severe problems, I believe with someone in the office crossing network ports, and causing a loop somewhere. This has happened a few times now, and on most occasions, after a few hours Ive man...
Hello,
This afternoon we suffered another outage, and I watched the secondary GSM switch reset itself again (from my syslogs, I think the ROOT did the same, but I wasnt in that room). At the time of the problem, I had only configured the 2 GSM switches as per your recommendation, and had yet to get round to setting all the others to MSTP (They were all on RSTP with priority at 32768). The problem did not seem to last as long this time, after about 30 mins, everything settled down, and I couldnt see anything in the syslogs suggesting a cause of the outage. Slightly irritated by this, I have now connected to all of the LAN switches (not the FS728TP just yet), and set them to MSTP, 32768 priority, enabled broadcast storm, and set it to disable any of the ports at 1% threshold, EXCEPT for the uplink ports, which Ive left the storm control disabled. As of right now, nothing has happened, so Ill put the same settings on the 728TP switches. If Ive understood any of your suggestions, this should then disable any port that starts flooding topolgy updates, except for the uplink ports.
Your thoughts are of course very welcome.
Broadcast storm won't really cause an outage as you described especially if you network recovered short while later. I suggest pulling the tech support file from both the managed switches and sending it to me so I can take a look.
Also as per my PM reply, The port won't shutdown unless the switch offers such option. On the switches where you have this option and you have selected to shutdown when threshold is met, then yes it will shutdown. Otherwise it will just rate limit it.
Most switches typically do rate limit (not shutdown) when it comes to smart switches. Managed switches will always allow both option types. For smart switches, it varies based on capability of the switch.
Hello Jedi_Exile. I have now completed the suggestions you made. My network now has the following settings...
All switches (GSM7328S, GS724/48, FS728TP) are set to MSTP, edge switches bridge priority set to 32768, except for ...
Core Switch (building A) which has its BP set to 0, and Building B which is 16384.
All Non Core switches have Storm control set. the GS724/48 switches are set to disable the port if the 3500 threshold is reached, and the FS728TP are set to Rate Limit at 1% since they dont have a port disable option. These options have been set on ALL BUT the last port, which is used to Uplink to the Building Core switch. These have the storm control disabled.
on the FS728TPs, I have the POE ports (1-24) set to FastLink. Ive not YET set this option on all of the LAN switches since I need to check how this might affect users with VMWare/VirtualBox etc on their machines?
I noticed on the CST Port Configs, that there is a "STP Status" option that can be enabled / disabled. How should I have this set?
STP setting should be on by default if STP is turned on. You can turn it off on per port basis if you want but not sure why you would need to do that.
Have you had the chance to collect tech support log so I can take a look into the reboot situation you mentioned in your previous post.
The battle moves ahead... Last weeks catastrophe appears to be caused by the Meraki wireless equipment somehow. At one stage, we only had the two core switches and our 6 APs connected, and the STP problem still occurred, Since then, we removed the Aps, and the problem stopped.
Ive reconnected all but one of these because I believe the problem is caused by one of them losing its LAN connection, so it bridges itself from one of the other APs - that happens to be connected to the other Core switch in the other building. The net result of this is that all of those clients suddenly appear to be in the other half of the building. Not sure if thats the cause, but without that AP, we havent (yet) had a repeat of the problem... One other thing to note, the port on the GSM7328s for one of the remaining APs seems to drop from time to time, come back up 3 seconds later, forcing a topology change. This doesnt appear to have any adverse effects, but the symptoms appear to be very much the same as when there is a problem. Syslogs for this event are :
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
