Summit Stack hitless upgrade
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎10-06-2014 11:14 AM
Hi guys,
I have a stack with two x480 running XOS 15.3.1.4
Is it possible to upgrade the two switches in the stack one after another so that one of the switches is allways forwarding traffic?
Thanks,
Thomas
I have a stack with two x480 running XOS 15.3.1.4
Is it possible to upgrade the two switches in the stack one after another so that one of the switches is allways forwarding traffic?
Thanks,
Thomas
14 REPLIES 14
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-04-2016 04:08 PM
I'm on version 15.3.1.4 patch1-36 and moving to 16.1.2.14 patch1-1. I want to upgrade a stack one at a time but I'm not clear on this process. Please let me know if I understand correctly. I can install the new image to the non active partitions but reboot to the new install, one stack at a time? Meaning the switches will be running at the same time on two different images ( I just have a 2 stack with both stack ports connected). Or will I need to un-stack them to keep them connected. This situation I'm not using MLAG on the upstream, but I have others that are using sharing to a MLAG connection on my cores. I'll need to work that scenario out too.
Thank you very much.
Thank you very much.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-04-2016 04:08 PM
I appreciate all the info. I'll schedule the downtime.
Thank you,
Ted
Thank you,
Ted
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-04-2016 04:08 PM
Further, the hitless/rolling upgrade described above would not be supported with the large jump in software version that you're planning.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-04-2016 04:08 PM
Technically, you can reboot one node at a time, but as each ones comes back up, it won't be able to communicate with the master node and you'd end up with a mess.
"Breaking" the stack would cause you to lose your configuration. Your safest bet is to schedule a reboot of the stack.
"Breaking" the stack would cause you to lose your configuration. Your safest bet is to schedule a reboot of the stack.
