N5K upgrade -

S891 · ‎06-30-2015

HI,

I am planning to do upgrade Nexus switches from 5.2.1.N1.2 to the new NX-OS code. I am wondering what are the options for direct upgrade to new code with zero down time. I have dual N5K with N2Ks with redundant PVCs. Is there possibility for absoloutely zero downtime upgrade on a major release.

Thanks,

Robert Falconer · ‎06-30-2015

Here are the guidelines:

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/upgrade/503_N1_1/n5k_upgrade_downgrade_503.html#wp640721

ISSU is supported unless you're running L3 on the 5Ks.

S891 · ‎07-05-2015

I checked for the ISSU upgrade document and the image it recommended was 7.0.3.N1. I downloaded the images on switch and did impact check. There still seems to be some issues with STP and possibly VPC due to which it says the upgrade will be disruptive. Any suggestions on how to avoid/fix this and still do the ISSU upgrade?

N5K-1# show install all impact kickstart bootflash:n5000-uk9-kickstart.7.0.3.N1.1.bin system bootflash:n5000-uk9.7.0.3.N1.1.bin

Verifying image bootflash:/n5000-uk9-kickstart.7.0.3.N1.1.bin for boot variable "kickstart".
[####################] 100% -- SUCCESS

Verifying image bootflash:/n5000-uk9.7.0.3.N1.1.bin for boot variable "system".
[####################] 100% -- SUCCESS

Verifying image type.
[####################] 100% -- SUCCESS

Extracting "system" version from image bootflash:/n5000-uk9.7.0.3.N1.1.bin.
[####################] 100% -- SUCCESS

Extracting "kickstart" version from image bootflash:/n5000-uk9-kickstart.7.0.3.N1.1.bin.
[####################] 100% -- SUCCESS

Extracting "bios" version from image bootflash:/n5000-uk9.7.0.3.N1.1.bin.
[####################] 100% -- SUCCESS

Extracting "fexth" version from image bootflash:/n5000-uk9.7.0.3.N1.1.bin.
[####################] 100% -- SUCCESS

Performing module support checks.
[####################] 100% -- SUCCESS

Notifying services about system upgrade.
[####################] 100% -- SUCCESS

Compatibility check is done:
Module bootable Impact Install-type Reason
------ -------- -------------- ------------ ------
1 yes disruptive reset STP ISSU preupgrade check failed - Upgrade needs to be disruptive!
101 yes disruptive reset STP ISSU preupgrade check failed - Upgrade needs to be disruptive!
102 yes disruptive reset STP ISSU preupgrade check failed - Upgrade needs to be disruptive!
111 yes disruptive reset STP ISSU preupgrade check failed - Upgrade needs to be disruptive!
112 yes disruptive reset STP ISSU preupgrade check failed - Upgrade needs to be disruptive!

Images will be upgraded according to following table:
Module Image Running-Version New-Version Upg-Required
------ ---------- ---------------------- ---------------------- ------------
1 system 5.2(1)N1(2) 7.0(3)N1(1) yes
1 kickstart 5.2(1)N1(2) 7.0(3)N1(1) yes
1 bios v3.6.0(05/09/2012) v3.6.0(05/09/2012) no
1 SFP-uC v1.0.0.0 v1.0.0.0 no
101 fexth 5.2(1)N1(2) 7.0(3)N1(1) yes
102 fexth 5.2(1)N1(2) 7.0(3)N1(1) yes
111 fexth 5.2(1)N1(2) 7.0(3)N1(1) yes
112 fexth 5.2(1)N1(2) 7.0(3)N1(1) yes
1 power-seq v5.0 v7.0 yes
1 uC v1.0.0.2 v1.0.0.2 no

Additional info for this installation:
--------------------------------------
Remove QoS & ACL config on L3 interfaces and SVIs if any

Service "stp" : Port: port-channel10 in VLAN0001 is Designated. Topology change could occur during ISSU.
Upgrade needs to be disruptive!!!

Service "vpc" : STP Preupgrade Check failed on VPC peer switch

Robert Falconer · ‎07-07-2015

ISSU will reset the control plane so spanning tree will be affected.

Do you have any downstream switches that are using the 5Ks as the root for those vlans?

S891 · ‎07-07-2015

Yes, it has root for vlan 1 which actually is Native vlan for FI trunk. Unfortunately we let it use the default. The other thing is it seems that we have to upgrade power-sequencer images when we go to 7.x.

Robert Falconer · ‎07-07-2015

So when the switches reset the control plane, there will be a spanning tree topology change. This may or may not disrupt traffic in your network.