Ok so after some further digging, the below post seems to clarify. There are two upgrade modes for performing the upgrade, install mode and bundle mode.
If I go to install mode, it seems like I will need to manually force the reboot by issuing the command "install activate".
This doesnt really work for me as it I say, its manual. So in that case, I will need to use bundle mode, by adding the code version to the switch and then setting the boot variable.
Can anyone confirm my assumptions above please?
-------- Previous Post ------------------------------------
There are two "modes" for upgrading:
Bundle mode:
- delete unnecessary flash files (if apllicable) - delete bootflash: xxxx
- copy the new .bin file to every switch in the stack and set the boot variable to point to the new bin file, save and reload whole stack
-no boot system
-boot system bootflash:xxxx.bin
-write
Install mode:
You can perform this in s single command if you wish as already stated (install add file bootflash:xxx.bin activate commit) or you can do this step by step so then you have more control pver the upgrade as such if you have any issues with the remote upgrade and you are unable to reconnect to the switch stack the upgrade will rollback if you dont manually commit after upgrade.
Perform a cleanup of any old install files before you upgrade
- install remove inactive
Make sure boot variable is pointing to packages.conf
-no boot system
-boot system bootflash:packages.conf
-write
Copy the new .bin file onto the switch
- copy tftp://x.x.x.//xxxxxxxxx.bin bootflash:
expand the .bin file to extract the .pkg files (used to boot new software)
- install add file bootflash:xxx.bin
- show install summary
- show install inactive
- more packages.conf
activate new software < stack will reload)
- install activate
one reloaded and your happy with the upgrade commit the changes
- show install uncommitted
- install commit
--------------------------------------------------------
