- #Master reboot tvtrope full#
- #Master reboot tvtrope professional#
- #Master reboot tvtrope series#
- #Master reboot tvtrope mac#
#Master reboot tvtrope mac#
(Of course, if there's a routing topology change, "no one is home" on the stack to process that until the stack master is fully functional.)Īs noted in my original post, if the stack's MAC changes (the default) that can cause some issues too.
However, if NSF is enabled, between stack and neighbors, remaining stack members will forward traffic, and routing neighbors will "route" to/from stack, while 元 is off-line. If stack is running 元, routing protocol neighbors may drop the node until stack master recovery resumes routing protocols.
#Master reboot tvtrope full#
You could have an issue if there are L2 topology changes until full stack master recovery. If stack is running just L2, I understand remaining switches will continue to forward while new stack master takes over. crashes for example then a new master is elected with little or no impact on traffic forwarding." " Whereas if the master simply stops working ie. Sorry for the basic questions but it's been a while :-) crashes or a failed power supply for example then a new master is elected with little or no impact on traffic forwarding. Whereas if the master simply stops working ie. a reboot command on the master will result in a complete reload of all the switches in which time there is obviously no forwarding of data. Whereas if the stack master become unavailable it does not require any of the other switches in the stack to reboot and one of the other member simply becomes the stack master and during the election traffic is forwarded normally. The guides suggest if you reset the master switch then the whole stack is reset which obviously means no forwarding of anything until the switches have reloaded. if the master goes down and the secondary reboots it doesn't matter about arp tables or anything else, there are no physical switches up so you have to wait for the secondary to reboot. So Leo when you say it is correct that the secondary would reboot itself but the downtime depends on how the clients are connected I don't follow that ie. Sorry to resurrect such an old thread but I am refreshing my 3750 knowledge and the information given here seems slightly contradictory.
The new 3850s use a new Stack that will not work with any 3750.
#Master reboot tvtrope series#
Original series 3750 used StackWise and E/X series use StackWisePlus, which is better in several way although it will work with original StackWise (yielding some of its improvements). There a command to continue to use the original master's ARP or you can use HSRP which uses a virtual MAC. It will send a gratuitous ARP, but if a host doesn't recognize it, it will send its traffic to the MAC in its local ARP table. Normally a new master uses its own mac for any gateways. Some gotchas: If your backup doesn't have the same feature set as the original master, you may lose active features. 元 too, if you enable NSF in your routing protocol. On the surviving switches - normally L2 forwarding should be almost hitless. Another switch takes over as master without needing to reboot. 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.Īs also noted by Leo, losing the stack master doesn't create much downtime (if any). Usage of this posting's information is solely at reader's own risk.
#Master reboot tvtrope professional#
Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. 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.
0 kommentar(er)
