Unsolved
This post is more than 5 years old
1 Rookie
•
63 Posts
0
118454
March 3rd, 2016 06:00
Replacement of an M8024-K stack member....
I have 3rd party support on my M1000e chassis, and I have a pair of M8024-K switches that are stacked. One has failed (DMA errors, and reboots, looping...) I'm being shipped a new switch blade. Question: What is involved in a replacement? The master "Mgmt Switch" is still up and healthy, and holds a good config. I'm guessing such as:
1.) Switch is inserted, and an automatic firmware upgrade is done, to match the Master. What if a downgrade is necessary to bring the OS of the new switch down to the level of the current Master? This will automatically reboot the switch (or the whole stack) when complete?
2.)the config will then be sync'ed after the OS is at the proper level, I'm thinking. --this will require a second reboot (of the new switch, or the whole stack)?
We're just wondering how much downtime may be needed in order to get the new switch inserted, get the OS sync'ed and the config sync'ed....
BatsonA
1 Rookie
•
63 Posts
0
March 4th, 2016 08:00
We would like to minimize downtime, so we'd like to keep the current Master up and running for as long as possible during this process. We'd like to follow the route where the Master causes an automatic upgrade/downgrade of the firmware on the new card being introduced.
BatsonA
1 Rookie
•
63 Posts
0
March 4th, 2016 16:00
Great, thanks.... So, when the switch is inserted, it will have the firmware upgraded/downgraded. (then just the new switch will reboot)? after the firmware is equal, then the configuration will sync, and the new switch will be brought into the stack. At this point, does the entire STACK reboot, or just the new member?
BatsonA
1 Rookie
•
63 Posts
0
March 7th, 2016 08:00
Daniel, thanks for the guidance! ---Let me re-state my facts in one spot, and let me know if I have it straight....----Here's what I think will happen....
We will need the two commands in place to allow for config-sync, and for downgrade of firmware:
# boot auto-copy-sw
# boot auto-copy-sw allow-downgrade
FACT: The existing master already has all the stacking-commands in place from before the 2nd member failed
We insert the switch, and:
1.) The switch boots, and the Master Switch will initiate an updgrade or downgrade of the firmware on the replacement switch
2.) the new replacement switch reboots after the firmware upgrade/downgrade.
3.) when the new switch comes up, it will receive the config from the Master
4.) At this point, the new replacement switch should a.)have the proper firmware and b.)have a sync'ed config from the master.
5.) If we issue, "show switch", we should see both switches present, with one indicating, "Mgmt Sw" and one indicting "Stack Mbr"
--do I have it straight? ---just so we know what to expect.....
BatsonA
1 Rookie
•
63 Posts
0
March 7th, 2016 13:00
so its necessary to change one single config item on the New Replacement Switch: setting two interfaces into stack-mode, and nothing else. When the new Replacement Switch boots the second time, the Master's config will overwrite what's on the new switch?
BatsonA
1 Rookie
•
63 Posts
0
March 8th, 2016 13:00
On the New Replacement Switch, after I put those two interfaces into Stack mode, wouldn't I need to do [tag:copy] running-config startup-config? Otherwise, when the new Replacement Switch boots, those interfaces won't be in Stack Mode anymore....
tib_nmorris
6 Posts
0
March 23rd, 2016 07:00
Daniel, what about the switch operating mode? new/replacement kit ships in simple mode, if in place stack is in normal mode, would you have to update the configuration to normal mode for the new/replacement to join the stack?
tib_nmorris
6 Posts
0
March 23rd, 2016 07:00
Daniel, what about the switch operating mode? new/replacement kit ships in simple mode, if in place stack is in normal mode, would you not have to change this on the config of the new/replacement?
tib_nmorris
6 Posts
0
March 23rd, 2016 17:00
Thanks Daniel. Found the reference on page 7.