01-17-2017 11:01 AM - edited 03-08-2019 08:56 AM
Hello everyone,
I can't seem to find solid documenation on replacing a bad 3850 in stack.
I have a stack of 4 3850's and I need to replace the active member which has been having switchport problems. I need to keep all the configurations the same. does anyone know the quickest way of doing this? i'm doing it during down-time.
thanks
Solved! Go to Solution.
01-17-2017 11:58 AM
Hello
1) Power down old switch and remove from stack
2) On new switch load same ios and feature set as exiting stack members
3) On new new switch change switch member number and priority to the old switch member number and priority ( you can find this on the live stack by sh switch command as the provision from old switch should still exist
4)save the config and power down new switch
5) reattached new switch to stack via stackwise cabling and power new switch up
should be good to go.
res
paul
01-17-2017 11:40 AM
Hi,
Try this document:
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3850/software/release/3se/ha_stack_manager/configuration_guide/b_hastck_3se_3850_cg/b_hastck_3se_3850_cg_chapter_010.html#task_1177470
HTH
01-17-2017 11:58 AM
Hello
1) Power down old switch and remove from stack
2) On new switch load same ios and feature set as exiting stack members
3) On new new switch change switch member number and priority to the old switch member number and priority ( you can find this on the live stack by sh switch command as the provision from old switch should still exist
4)save the config and power down new switch
5) reattached new switch to stack via stackwise cabling and power new switch up
should be good to go.
res
paul
01-17-2017 12:00 PM
Thank you. So, I don't have to upload the configs into the new switch? It will do this automatically?
01-17-2017 12:10 PM
Hello
Nope - the provision should still be there ,So only what would be necessary would to do the above
Note: Install ios and renumber and prioritize the new switch when the new switch is NOT attached to the stack only when you have completed the steps above attach the switch powered down first, not when its powered up
Only when its physically connected again power up new switch, it should then join the stack as the same member as the last switch with the same priority also
res
Paul
01-17-2017 12:49 PM
The whole stack will reboot anyways at the end though, right? What if I powered everything down, swapped the 2 switches, then powered everything back on?
01-17-2017 01:15 PM
Hello
Replacing a failed switch wont make the whole stack to reload - but replacing 2 switches at the same time would depend on what role they were running and where they were located within the stack .
What if I powered everything down, swapped the 2 switches, then powered everything back on?
You may need to power up a good switch first and then add the second ( good or new), third etc. if you were to keep the same ordering and priorities ( but DONT power then up all at the same time.
Personally -I would check the cco documentation for multiple failed switch scenarios
res
Paul
05-25-2018 03:36 AM
I tried this it doesn't take on the new 3850.
3) On new new switch change switch member number and priority to the old switch member number and priority ( you can find this on the live stack by sh switch command as the provision from old switch should still exist
12-09-2020 07:38 PM
Hello Experts!
Please I need to know if the procedure describe by Paul and the link provided by Reza above applies to all the
switches in the 3000 series family?
Thank you.
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