Nexus 93180YC-EX SW Upgrade from 7.0(3)I7(3) to 10.2.5

[MATTHIAS SCHAERER]

I have 4 Nexus (2 and 2 pairs) in a productive network that have not been upgraded for quite some time. The upgrade path between the above versions would be 7.0(3)I7(3) - 7.0(3)I7(10) - 9.3.11 - 10.2.5.

How would you suggest to do the upgrade? One switch from 7.0(3)I7(3) to 10.2.5, then the next one and so on?
Or rather all switches to 7.0(3)I7(10), then all switches to 9.3.11 and then to 10.2.5?

I use the following features:

feature bash-shell
feature scp-server
feature tacacs+
cfs eth distribute
feature bgp
feature pim
feature msdp
feature interface-vlan
feature hsrp
feature lacp
feature vpc
feature lldp
feature bfd

[Christopher Hart · Accepted solution]

Hi Matthias!

In multi-hop software upgrades on Nexus series switches in a vPC domain such as yours, you should generally perform intermediate upgrades on both vPC peers in sequence. To use a practical example, you should typically do the following:

• Upgrade N9K-1 from NX-OS 7.0(3)I7(3) to NX-OS 7.0(3)I7(10)

• Upgrade N9K-2 from NX-OS 7.0(3)I7(3) to NX-OS 7.0(3)I7(10)

• Upgrade N9K-1 from NX-OS 7.0(3)I7(10) to NX-OS 9.3(11)

• Upgrade N9K-2 from NX-OS 7.0(3)I7(10) to NX-OS 9.3(11)

• Upgrade N9K-1 from NX-OS 9.3(11) to NX-OS 10.2(5)

• Upgrade N9K-2 from NX-OS 9.3(11) to NX-OS 10.2(5)

The above process will generally yield the best, most stable results during your upgrade maintenance window.

With that being said, you can perform all intermediate upgrades on a single vPC peer before upgrading the other vPC peer (e.g. upgrade N9K-1 from 7.0(3)I7(3) to 7.0(3)I7(10), then to 9.3(11), then to 10.2(5), then perform the same on N9K-2) but that is more risky for a variety of reasons (significant differences in vPC consistency checks and compatibility parameters between the two vPC peers, differences in forwarding behavior/efficiencies between the two vPC peers since one peer is running software that is several years newer and may be more optimized, etc.) I would generally advise against this upgrade strategy - stick with keeping both vPC peers in "lockstep" when performing multi-hop software upgrades.

I hope this helps - thank you!

-Christopher

[MATTHIAS SCHAERER]

Hi Christopher

Although I hoped you would tell me that doing all switch after switch would work easily I am very happy with your clear and concise answer. It completely makes sense to me and we include your ideas into our planning.

Thanks a lot for taking the time to answer my question.

Mat