08-16-2013 08:42 AM - edited 03-07-2019 02:58 PM
Hi Team
Due to some bugs i am planning to upgrade current VSS release from 15.1.1.sy to 15.1.1.sy1 ..We are planning to follow the procedure mentioned below...Please suggest your thoughs on the same..
redundancy reload peer
Regards
Sameer
Solved! Go to Solution.
08-16-2013 10:28 AM
Hi Sameer,
As I said before, I would not do that way, but ultimately it is up to you. I can only make suggestion based on my experience.
Reza
08-16-2013 09:09 AM
Hi Sameer,
When using ISSU, you would need to reboot one switch at a time. If you have an outage window, the other option would be to load the new IOS in both primary and stand-by switches, set your boot variable, save the config and reboot both devices at the same time. Just an option, if you envirenment can tolerate a 15 minute down time.
HTH
08-16-2013 09:33 AM
Hi Reza
We can have downtime of 15-20 minute in the network sooption 2 suggested by you can be posisble.Little fear in mind is both the switches should come properly after relaod or else we will be totally in trouble.
What will be the VSS redundnacy in case of 2 switches running differnt ios version for sometime (Is it RPR instaed of SSo)..thinking of plan below but not sure how feasible this is
Please suggest..
08-16-2013 09:44 AM
Hi Sameer,
I would not go that far and do any of these you suggest below. I think, this will actually cause more trouble than anything else.
That said, I have done a few IOS upgrades with VSS and have booted both chassis at the same time with no issues. The key is to make sure IOS is loaded on both devices, change you boot variable, SAVE the config and than reboot. If anything goes wrong, you can always change the boot variable to point to the old IOS and reboot again.
There is no guarante in life, but I think you will be fine.
HTH
08-16-2013 09:59 AM
Hi reza
To avoid mismatch with diffrent releses we can make some changes as below
1-As mentioned in step 1 isolate core2 from the network .upgrade it with new image.before enabling all ports on the line cards,switch of core1 (before switching of core1,disable all ports on line card).During this time we will have netwrok downtime.Once we switched of core1,we can enable all ports for line cards on core2.all trafifc will flow from core 2.In this case total downtime will be the time required for enabling ports on core2.
2-Switch on core 1 which is already out of network(During this time VSL links will be physically removed)..upgrade the core 1 switch with new image.Connect the VSL link.let the VSS come up.Once VSS come up,enable all ports on line cards for core1..by this time our both core switches will be up and running with new image..
Note--Downtime in this case is leass than 10 min.disabling all ports on core 1 and switching it off.enabling all ports on core 2 switch to make it operational.
Note--Switching of both cores at the same time is littel bit risky if we have some issue with the hardware especailly the sup engines..
08-16-2013 10:28 AM
Hi Sameer,
As I said before, I would not do that way, but ultimately it is up to you. I can only make suggestion based on my experience.
Reza
08-17-2013 04:26 AM
Hi reza
Yes looks like changing the boot variable with new inamge and reloading the entire vss after saving the latest config will be the best option.Its reduces the complication..
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