06-30-2014 12:16 AM - edited 03-07-2019 07:51 PM
When I have the master C3850-48T and the slave C3850-48T are ready(version: 03.03.03SE), the priority of master C3850-48T is 15 and slave C3850-48T is 14. We plug in the stack cable from slave C3850-48T to master C3850-48T, the two C3850-48T have no response at this time, and the front of panel is always green light(STAT and SYST) on two C3850-48T. It’s also no response to press the “MODE” button on the front of panel. We pull the stack cable and plug in it, the two C3850-48T reload immediately and made stack completely. In normal, only the low priority will reboot, the master will not. So what problem between this procedure or what is wrong on these step?
Solved! Go to Solution.
06-30-2014 03:44 PM
You say that when slave is POWERED UP and then you CONNECT the stacking cable, the entire stack will reboot so it can go into a stack election
Presume the following scenario:
Ok, you've got above setup. The very minute you attach the stacking cable from the existing stack to an already-power-up new switch, the entire stack will reboot. This is to be expected.
This is why it's stated in the recommendation to POWER DOWN the new stack member before attaching/connecting the stacking cable. Once you've attached, a minimum of, ONE stacking cable to the new member, you can power up the new member switch. This will cause the new member to join the stack un-interrupted.
It doesn't matter if you are talking about 2960S/X/XR, 3750-series family of switches, 3650 or 3850, the behaviour is the same to all the platform involved.
06-30-2014 03:22 AM
We pull the stack cable and plug in it, the two C3850-48T reload immediately and made stack completely. In normal, only the low priority will reboot, the master will not.
If your slave is POWERED UP and then you CONNECT the stacking cable, the entire stack will reboot so it can go into a stack election. This behaviour is to be expected.
IF you need to connect the slave, make sure the slave is POWERED OFF and then connect the stacking cable.
06-30-2014 05:50 AM
Thanks for your reply. You say that when slave is POWERED UP and then you CONNECT the stacking cable, the entire stack will reboot so it can go into a stack election, But we try to test by
another platform "3750X" by the same situation. Only the low priority will reboot, and they don't go into a stack election. So the different platform have different result? Thanks....
06-30-2014 03:44 PM
You say that when slave is POWERED UP and then you CONNECT the stacking cable, the entire stack will reboot so it can go into a stack election
Presume the following scenario:
Ok, you've got above setup. The very minute you attach the stacking cable from the existing stack to an already-power-up new switch, the entire stack will reboot. This is to be expected.
This is why it's stated in the recommendation to POWER DOWN the new stack member before attaching/connecting the stacking cable. Once you've attached, a minimum of, ONE stacking cable to the new member, you can power up the new member switch. This will cause the new member to join the stack un-interrupted.
It doesn't matter if you are talking about 2960S/X/XR, 3750-series family of switches, 3650 or 3850, the behaviour is the same to all the platform involved.
06-30-2014 07:51 PM
Thanks~ I got it. Thanks for your suggestion and answer...
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide