cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2773
Views
0
Helpful
7
Replies

stack switch C9200-24T upgrade without downtime

zamaludeen
Level 1
Level 1

Hi ,

We are having currently our stack on the C9200-24T with four member ( current mode is install ) and the below version 

Software [Gibraltar], Catalyst L3 Switch Software (CAT9K_LITE_IOSXE), Version 16.12.02. We would like to upgrade from 16.12.02 version to cat9k_lite_iosxe.17.06.03.SPA.bin. we have followed the prodcure 

Step 1. Remove Unwanted Packages
C9200K#install remove inactive
Step 2. Copy New Image to Flash
C9200K#copy usbflash1:cat9k_lite_iosxexxx.bin flash:
Step 3. Set Boot Variable
C9200K(config)#boot system flash:packages.conf
C9200K(config)#end
C9200K#wr
C9200K#show boot system
Step 4. Software Install Image to Flash
install add file flash: cat9k_lite_iosxexxx.bin

After that, we are getting the below error

%INSTALL-3-OPERATION_ERROR_MESSAGE: R0/0: install_engine: Failed to install_add package flash:cat9k_lite_iosxe.17.06.03.SPA.bin, Error: [1]: FAILED: Add failed in switch 1

we donot want to reload the our stack switch now and try to upload the new image to the stack and waiting for available time to restart 

install activate

install commit

Please let me know 

why i am getting this type error 

is it recommendate direct upgrade from 16.12.02 to 17.06.03 or need to pass some other intermediate version 

share with me upgrade procdure minimum downtime 

 

 

 

 

7 Replies 7

Reza Sharifi
Hall of Fame
Hall of Fame

Hi,

Follow this document. And yes, you can go directly from 16.12.02 to 17.06.03

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst9200/software/release/16-12/release_notes/ol-16-12-9200.html

 

HTH

Leo Laohoo
Hall of Fame
Hall of Fame

@zamaludeen wrote:
%INSTALL-3-OPERATION_ERROR_MESSAGE: R0/0: install_engine: Failed to install_add package flash:cat9k_lite_iosxe.17.06.03.SPA.bin, Error: [1]: FAILED: Add failed in switch 1

I know what this error message:  This error message is generated because the process to perform the "unpacking" of the firmware file has crashed.  This is a very common "feature" with IOS-XE and the fix is to reboot all the stack members and re-running the Install Mode command again. 

zamaludeen
Level 1
Level 1

Hi,

Thanks for your update .Please share with me the procdure to upgrade stack 4 members without reboot . I will do the reboot after non business hours.

Best Regards,

Zamaludeen 

Hi,

Please share with me the procdure to upgrade stack 4 members without reboot

In order for the new IOS to take effect, you have to reboot the stack. Rebooting is a must, and that is why you need to make the change in a maintenance window because there is downtime.

HTH


@zamaludeen wrote:
Please share with me the procdure to upgrade stack 4 members without reboot

I really have no idea who's been peddling this idea that upgrading the IOS/IOS-XE of a switch, router, AP, WLC, etc do not require a reboot.  

Upgrading the firmware will always require a reboot. 

And, in your particular case, the correct question should be:  How long does it take for a switch stack to reboot?

Is it possible to copy the new firmware and only reboot one switch at a time? I have multiple WLCs (one connected to each of a different switch in a stack). I don't my whole wireless down while the switches reboot as I have 24x7 critical services that rely on it. If rebooting one at a time is not possible is there another way to achieve upgrades without taking out my whole wireless infrastrusture?


@MorrisonJ wrote:
Is it possible to copy the new firmware and only reboot one switch at a time? I have multiple WLCs (one connected to each of a different switch in a stack). I don't my whole wireless down while the switches reboot as I have 24x7 critical services that rely on it. If rebooting one at a time is not possible is there another way to achieve upgrades without taking out my whole wireless infrastrusture?

Yes and no. 

Yes, it is possible using ISSU or FSU/eFSU/xFSU.  

No, I would not risk it because if-and-when ISSU or FSU/eFSU/xFSU goes wrong, it goes out "in style".   ISSU or FSU/eFSU/xFSU does not work for everyone.  Success rates varies and I am not shy in telling people that ISSU or FSU/eFSU/xFSU only works in corner cases, demo or in a lab.  

If you want to try ISSU or FSU/eFSU/xFSU, raise a Proactive TAC Case and the TAC agent/engineer is on the phone/WebEx before starting.  This is to make sure that when ISSU or FSU/eFSU/xFSU inevitably, invariably and eventually fails, TAC will be able to recover the runaway switch/stack quickly.

Good luck.