cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
468
Views
5
Helpful
6
Replies
Highlighted
Beginner

Nexus 5548UP Upgrade

Hi All,

 

I was hoping to get some feedback about the approach I was going to take for a Nexus upgrade.

 

The current code is 5.2(1)N1(7) and I intend on migrating to 7.3(3)N1(1). There are two switches in a VPC configuration with no FEXs involved and no FC. The switches are pure L2 and serve as the access layer to a UCS blade center.

 

The upgrade will be done under a maintennace window and I intend to take one of the following paths:

 

ISSU

5.2(1)N1(7) > 7.0(8)N1(1) > 7.1(4)N1(1) > 7.3(3)N1(1)

 

Or to save some time due to limited window

 

Part ISSU then Disruptive

5.2(1)N1(7) > 7.0(8)N1(1) then disruptive to 7.3(3)N1(1)

 

The question was whether a disruptive upgrade from 7.0(8)N1(1) to 7.3(3)N1(1) may trigger bug CSCul22703 which can cause config loss with a disruptive upgrade. Looking over the bugid it looks to affect only 5.2(1)N1 and some 6.x code. Could anyone confirm if this bug also affects other code versions?

6 REPLIES 6
Beginner

Re: Nexus 5548UP Upgrade

Hello,

I would not recommend jumping directly from 7.0(8)N1(1)  to   7.3(3)N1(1) .

Go the long way 5.2(1)N1(7) > 7.0(8)N1(1) > 7.1(4)N1(1) > 7.3(3)N1(1) .

If I remember correctly, there is a bios upgrade between 7.0(8)N1(1)  and  7.1(4)N1(1) .

Read the messages you might be requested to power off the switch after it comes up.

There might also be configuration changes, make sure to have full backup and status. 

Beginner

Re: Nexus 5548UP Upgrade

Beginner

Re: Nexus 5548UP Upgrade

Short report:
disruptive upgrades series

5.1(3)N1(1a)>5.1(3)N2(1)>5.2(1)N1(1)>7.0(4)N1(1)>7.1(4)N1(1)>7.3(3)N1(1)

on 2 vPC pairs with 8 dualhomed FEXs each went smoothly. But a lot of gemorrous with FEX reload leads to dramatical upgrade window extension (one pair took 8 hours).

Beginner

Re: Nexus 5548UP Upgrade

I followed the below path as suggested by Cisco TAC

The Upgrade path is: 5.0(3)N2(1) --> 5.2(1)N1(9b) --> 7.0(8)N1(1) --> 7.1(5)N1(1) --> 7.3(3)N1(1)

I ran into a hurdle upgrading from 7.0.8 to 7.1.5, not a resume generating event but I did lose the IP configuration for my management interface. We don't have a KVM/terminal server for console access so it caused panic.

Make sure you keep frequent backup copies of your config.

 

Beginner

Re: Nexus 5548UP Upgrade

Check ISSU impact prior to upgrade

Recently I upgrade from 5 to 7.3.3 considering the following upgrade path

5 >6.0.2>7.0.8>7.1.5 >7.3.3

 

Good luck

Network Consultant DC

Beginner

Re: Nexus 5548UP Upgrade

Check ISSU impact prior to upgrade

Recently I upgrade from 5 to 7.3.3 considering the following upgrade path

5 >6.0.2>7.0.8>7.1.5 >7.3.3

 

Good luck

Network Consultant DC

Everyone's tags (1)
CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards