01-17-2018 01:44 PM - edited 03-08-2019 01:27 PM
We are planning to upgrade Cisco Nexus 5596UP switches which has FEX and in vpc. I haven't upgraded such an old version switch. Can someone please help with the upgrade paths and its steps.
Currently running version n5000-uk9.5.2.1.N1.1.bin
Target version n5000-uk9.7.1.4.N1.1.bin
Below is fex details:
FEX FEX FEX FEX
Number Description State Model Serial
--------------------------------------------------------------------
101 FEX_101 Online N2K-C2248TP-E-1GE SSI16390DYV
Nexus-5k1# sh fex 101 ver
Software
Bootloader version: 0.2
System boot mode: primary
System image version: 5.2(1)N1(1) [build 5.2(1)N1(1)]
vPC Peer-link status
---------------------------------------------------------------------
id Port Status Active vlans
-- ---- ------ --------------------------------------------------
1 Po1 up 1,10,17,30,50
vPC status
----------------------------------------------------------------------------
id Port Status Consistency Reason Active vlans
------ ----------- ------ ----------- -------------------------- -----------
99 Po99 up success success 1,10,17,30,
50
Solved! Go to Solution.
01-18-2018 01:08 AM
Hi Raghav,
If I am understanding correctly, my upgrade path will be 5.2(1)N1(1) >> 5.2(1)N1(6) >> 7.0(8)N1(1) >> 7.1(4)N1(1)
Yes, that is correct.
I also have another pair of 5K (5548UP) switches running n5000-uk9.6.0.2.N2.3.bin. Can it be upgraded directly to 7.1(4)N1(1) follow an upgrade path?
For this upgrade, I would recommend the following sequence:
6.0(2)N2(3) >> 6.0(2)N2(4) >> 7.0(8)N1(1) >> 7.1(4)N1(1)
All this information is based on the Release Notes documents mentioned earlier, and the supported ISSU upgrade paths. For N5K switches, the upgrade always has to follow ISSU paths, even if the particular switch configuration is not eligible for an ISSU.
Best regards,
Peter
01-17-2018 02:19 PM
Hi Raghavendra,
Your upgrade will need to go through several intermediary steps and multiple reloads - unfortunately, it won't be possible to perform a direct upgrade.
The sequence of upgrades would be:
The upgrade should always be performed using the install all command; never change the boot variables directly.
There might be several caveats which might be applicable to your particular configuration. It is highly recommended to consult the following Release Notes documents - they are admittedly long and complex, but it is always better to be safe than sorry.
At every upgrade stage, it is necessary to perform a backup of the show running-config and keep it saved externally. If the upgrade results in a corrupted configuration, it will be necessary to restore the correct configuration from the offline copy.
Best regards,
Peter
01-17-2018 04:29 PM
Hi Peter,
Thank you for your quick turn around.
If I am understanding correctly, my upgrade path will be 5.2(1)N1(1) >> 5.2(1)N1(6) >> 7.0(8)N1(1) >> 7.1(4)N1(1)
On other hand, I also have another pair of 5K (5548UP) switches running n5000-uk9.6.0.2.N2.3.bin.
Can it be upgraded directly to 7.1(4)N1(1) follow an upgrade path?
Regards,
Raghav
01-18-2018 01:08 AM
Hi Raghav,
If I am understanding correctly, my upgrade path will be 5.2(1)N1(1) >> 5.2(1)N1(6) >> 7.0(8)N1(1) >> 7.1(4)N1(1)
Yes, that is correct.
I also have another pair of 5K (5548UP) switches running n5000-uk9.6.0.2.N2.3.bin. Can it be upgraded directly to 7.1(4)N1(1) follow an upgrade path?
For this upgrade, I would recommend the following sequence:
6.0(2)N2(3) >> 6.0(2)N2(4) >> 7.0(8)N1(1) >> 7.1(4)N1(1)
All this information is based on the Release Notes documents mentioned earlier, and the supported ISSU upgrade paths. For N5K switches, the upgrade always has to follow ISSU paths, even if the particular switch configuration is not eligible for an ISSU.
Best regards,
Peter
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: