- Bronze, 100 points or more
I'm working on a site with 3750 switch stacks built using a mix of E 48 port and G 24/48 port units, all running 12.2.53 IPBase.
The E series are set with the highest priority.
Following a complete stack reload or power failure the 24 port G becomes active first, and as the other switches in the stack havent yet reloaded, it becomes stack master. I think is simply due to the fact it is the quickest unit (least electronics or diagnostics) to reload.
So I loose the additional features of the E series in the stack, in this case its the enviromental information relating to chassis tempreatures. If the master is reloaded once the stack is back online, the E switch with the highest priority becomes master, according to the configured priority value.
Reading through all the posts on this subject I dont think there is a way around this, we may just have to accept this is the way the stack works. But before signing off on this I am asking if my understanding of this is correct, or is there any way to guarantee the E becomes master following a stack reload without the second reboot?