Nexus 7000 w/ SUP-2 upgrade 6.2(16) -> 8.1(2)

[hhaeupler]

Hello, the upgrade/downgrade guide isn't clear about using the install all command when upgrading from 6.2 to 8.1. Only 'cold boot' with this non-issu path described. What happens with BIOS or linecard microcode with cold boot method? Is it really not supported to use install all?

Should i do multihop issu instead (->7.2 -> 7.3 -> 8.1)?

Any suggestions or experience are welcome ...

Regards

Herbert

[Reza Sharifi]

Hi,

Before upgrading run the show command to see the impact of each version upgrade. 

show install all impact kickstart bootflash:<name of the image>

So, do this for 7.2, 7.3 and 8.1 and then use the install all command to upgrade each version.

HTH

[Reza Sharifi · Accepted solution]

If this is in production, I would open a ticket for each upgrade and have Cisco on the phone while you are doing it.

HTH

[hhaeupler]

Hello Reza,

finally, last saturday i was able to run a show install all impact. Result gives me confidence to run a direct update from 6.2 to 8.1 during maintenance window

Compatibility check is done:
Module bootable Impact Install-type Reason
------ -------- -------------- ------------ ------
1 yes disruptive reset Incompatible image
2 yes disruptive reset Incompatible image
3 yes disruptive reset Incompatible image
4 yes disruptive reset Incompatible image

Images will be upgraded according to following table:
Module Image Running-Version(pri:alt) New-Version Upg-Required
------ ---------- ---------------------------------------- -------------------- ------------
1 system 6.2(16) 8.1(2) yes
1 kickstart 6.2(16) 8.1(2) yes
1 bios v2.12.0(05/29/2013):v2.12.0(05/29/2013) v2.12.0(05/29/2013) no
2 system 6.2(16) 8.1(2) yes
2 kickstart 6.2(16) 8.1(2) yes
2 bios v2.12.0(05/29/2013):v2.12.0(05/29/2013) v2.12.0(05/29/2013) no
3 lc1n7k 6.2(16) 8.1(2) yes
3 bios v2.0.32(12/16/13):v2.0.32(12/16/13) v2.0.32(12/16/13) no
4 lc1n7k 6.2(16) 8.1(2) yes
4 bios v2.0.32(12/16/13):v2.0.32(12/16/13) v2.0.32(12/16/13) no

[hhaeupler]

Hello Reza,

customer agreed to have this work done during maintenance window.
So "install all" from 6.2(16) to 8.1(2) with disruption doesn't matter.
I'll run a installl all impact next week.