Can anyone advise me if in a stack of 3750's, if the master was to fail and another switch in the stack had to take over as Master. Is the transition "totally" seemless with no break in service at all (other than anything connected to the failed switch of course) ?
The reason why I ask is we currently use stacked switches from another vendor and recently the Master switch failed and there was a disruption of service across the stack for around 30 seconds whilst the new master did some kind of soft reset to load the master config to run the stack again. This wasn't acceptable as clustered devices got upset. So I am wondering if in this case Cisco is a better option.
Many thanks in advance
Here are some numbers provided by Cisco. It depends on if you are running the stack as layer-2 or 3.
Reconvergence times tested under heavy load:
Layer 1 failure is detected in several microseconds
Layer 2 failure ~ mseconds
Layer 3 link failure—sub 200 mseconds
Layer 3 member failure—sub 300 mseconds
Layer 3 master failure—up to eight seconds
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Besides what Reza has provided, when a 3750 stack master fails, by default, gateway MAC, if hosted on the stack, will change. This might "confuse" hosts that don't process the gractious ARP. Two ways to mitigate this, there's an option to retain the original master's MAC or use HSRP.
If the stack is doing dynamic routing, its peer/neighbors might see the interruption too. If NSF is enabled, this interruption can be minimized.
Thank you both for the answers, they are both excellent and give me plenty to offer back to the business.
I guess ultimately the best option is a Chassis based solution though as there is still a potential for disruption.