So we had another crack at this. Had a stack of (3) x460-48p (G1s), 2 of the 3 which needed replacing, slots 1 and 2. So in preparation upgraded the stack to the 16.2.3.5 code and rebooted the stack, it was running the new code. Before we began the replacements the setup was like this.
Slot 1 - master
Slot 2 - backup
Slot 3 - standby
Steps Taken: replaced slot 2. Slot 3 became the backup (slot 1 still master). Added slot 2 to the stack using the standard commands enable stacking, configure stacking and give slot and synchronize stacking, then rebooted the new slot 2. It joined the stack just dandy. So now we have slot 1 master, 2 standby and 3 backup. Then replaced slot 1, it too was a champ and joined the stack as expected. It became a standby after it was rebooted. Then issued command configure stacking mac-address from the master node (slot 3 which we never had replaced but was the master at the time). Once the stack rebooted, all 3 nodes were stacked together, it booted all the way up (thanks for the tip on the newer code) but there was no config. And my .xsf file that I had saved (which would have been on all slots including slot 3) was of no use, was on a slot that I couldn't copy things from (standby).
Slot 1 - master, Slot 2 - backup, Slot 3 - standby.
It was as if it was a new switch. Had to copy an xsf file to the stack and load it to get things talking. Why didn't the config keep? Am I missing something still?
Any tips on what can I do to improve having to restore a config each time b/c the switch defaults?
Thanks,
Sarah
