N7000 series Upgrade Non-ISSU

[pengus]

As far as I understand,

there are two possible methods to perform the upgrade:

Using the install all command

Changing the boot variable and reloading

The install all command performs pre-checks, verifies whether ISSU is possible, and then starts the upgrade process. In my case, since ISSU is not supported, the upgrade will proceed in a disruptive manner. With this method, the upgrade is carried out in a more controlled way, module by module, and finally the chassis is reloaded and brought back online.

The boot variable and reload method is relatively less controlled; no pre-checks are performed and the system simply boots directly with the new image. However, manual checks can be performed beforehand using commands such as show incompatibility system and show install all impact.

Which one is the best practice? Or are they the same thing?  Since I will be upgrading to 8.4(10) and also performing an epld upgrade, which method would be the most appropriate for the upgrade?

[Enes Simnica]

gDay @pengus The best practice is to use install all, cause it performs automatic pre-checks, validates ISSU support, handles module reboots in sequence, and provides rollback options. And dont get me wrong, changing the boot variable and reloading works, but it’s less controlled and skips the automated checks.

But since u’re upgrading to 8.4(10) and also doing an EPLD upgrade, use install all for the NX-OS image, then run the EPLD upgrade separately.

Cisco Nexus 7000 Series NX-OS Software Upgrade and Downgrade Guide, Release 8.x - Cisco

hope it helps and PEACE!

-Enes

[Enes Simnica]

and my friend @pengus, ust so u know both methods are valid, and some engineers prefer one over the other. However, when we talk about best practice for performing an upgrade, the recommended approach is to use the install all method because it provides pre-checks, impact analysis, and a more controlled process............. so in the end, its up to u.......

PEACE

[pengus]

Thanks for reply. Actually, as you mentioned, it is reasonable to consider the install all method as the recommended approach since it performs prechecks. However, for some reason, when I run install all, I get the impression that not all chassis will be restarted. Given that the switch to be upgraded has a high uptime, I would prefer the device to fully power cycle. Therefore, I am curious: after the install all prechecks, if the system determines that the upgrade will be disruptive, does it change the boot variables and perform a reload, or is a different process used?