Multiple switch firmware updates

When a firmware update is kicked off for multiple devices, are they queued and then updated sequentially or do we have "N" running in parallel, and can we control "N"?

Also, is there a way to submit a batch with specific sequence to update? In other words, I want to update specific access switches before updating the distribution switch, and need to confirm the access device updates complete successfully before triggering the distribution switch update.

Find more posts tagged with

network_configuration_manager

script

firmware upgrades

Accepted answers

mesverrum

Default N is 5, and yes you can change it if needed

https://documentation.solarwinds.com/en/success_center/ncm/content/ncm-simultaneuos-firmware-upgrade-operations.htm

And no, in order to manage the sequence the way you describe you need to just set up multiple jobs. Just access in job 1, distribution in job 2.

Looks like I havent dont one of these in a long time, apparently you can set an order

All comments

mesverrum

Default N is 5, and yes you can change it if needed

https://documentation.solarwinds.com/en/success_center/ncm/content/ncm-simultaneuos-firmware-upgrade-operations.htm

And no, in order to manage the sequence the way you describe you need to just set up multiple jobs. Just access in job 1, distribution in job 2.

Looks like I havent dont one of these in a long time, apparently you can set an order

sum_giais

Adding some quick clarification on this. The default N (5 by default) is the amount of Firmware Upgrade Operations (not to be confused with NCM "Jobs") that can run in tandem, which is a global setting that can be changed in Settings -> All Settings -> NCM Settings -> Upgrade Settings, adjust the "Maximum number of simultaneous upgrade operations to run".

Firmware Upgrade Operations run their firmware upgrade template steps in serial, e.g. Download FW to Switch1 -> Upgrade Switch1 -> Reboot Switch1 -> Download FW to Switch2 -> Upgrade Switch2 -> Reboot Switch2 -> rinse/repeat.

The order in which the nodes perform the above sequence in a single firmware operation is adjustable at the end before submitting the firmware operation at the Summary page. E.g. if you have an operation set to go against SWITCH1, SWITCH2, SWITCH3 you can configure it to go SWITCH3 -> SWITCH1 -> SWITCH2, see below.