[c-nsp] Nexus 7K NX-OS Upgrade

Neil Barnett interarchetype at gmail.com
Mon Nov 19 12:41:54 EST 2012 

I Was upgrading to 6.1(1) from a Software Standpoint, which required a
requisite 6.1(1) EPLD Image Upgrade. 
EPLD Image upgrade took a significant amount of time to upgrade, which is
standard. 

Neil 

-----Original Message-----
From: Antonio Soares [mailto:amsoares at netcabo.pt] 
Sent: Monday, November 19, 2012 10:50 AM
To: 'Neil Barnett'; 'Tim Stevenson'; 'Dirk Woellhaf'
Cc: 'Charles Spurgeon'; 'cisco-nsp'
Subject: RE: [c-nsp] Nexus 7K NX-OS Upgrade

What upgrade did you make ? In my case it was from 5.2.3a to 5.2.7. The
5.2.3 EPLD was already installed.


Regards,

Antonio Soares, CCIE #18473 (R&S/SP)
amsoares at netcabo.pt
http://www.ccie18473.net



-----Original Message-----
From: Neil Barnett [mailto:interarchetype at gmail.com]
Sent: segunda-feira, 19 de Novembro de 2012 14:22
To: 'Antonio Soares'; 'Tim Stevenson'; 'Dirk Woellhaf'
Cc: 'Charles Spurgeon'; 'cisco-nsp'
Subject: RE: [c-nsp] Nexus 7K NX-OS Upgrade

I had an odd situation where I did a software upgrade on one box
successfully. On the 2nd box the VLAN Configurations were arbitrarily
missing, which was frustrating As we thought immediately that the vpc was
down for other reasons. Not sure if this had anything to do with the m1, (I
did do an EPLD Upgrade as well) 

Psion

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Antonio Soares
Sent: Saturday, November 17, 2012 12:29 PM
To: 'Tim Stevenson'; 'Dirk Woellhaf'
Cc: 'Charles Spurgeon'; 'cisco-nsp'
Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade

Another long night... The upgrade of one Nexus was completely clean, the
second one was a nightmare. One M1-32XP card remained in the state
"powered-up" forever... The reload didn't make it work, neither the re-seat
or even the NX-OS downgrade... Had to open a P1 TAC case and then the
engineer said it was a faulty card. Got the replacement but had to delay the
installation 48 hours.

Anyone has have bad experiences with this M1 type of cards card lately ?
It's the second one that gets faulty in less than a year. It seems the MTBF
is inversely proportional to the price :(


Thanks.

Regards,

Antonio Soares, CCIE #18473 (R&S/SP)
amsoares at netcabo.pt
http://www.ccie18473.net


-----Original Message-----
From: Tim Stevenson [mailto:tstevens at cisco.com]
Sent: quinta-feira, 8 de Novembro de 2012 18:21
To: Antonio Soares; 'Dirk Woellhaf'
Cc: 'cisco-nsp'; 'Charles Spurgeon'
Subject: RE: [c-nsp] Nexus 7K NX-OS Upgrade

At 09:36 AM 11/8/2012, Antonio Soares mused:
>Thanks Tim, I will follow that procedure, it's the one that makes 
>perfect sense.
>
>The documentation should be more clear about this kind of situations, 
>don't you think ?
>
>There are important things that are omitted between steps 10 and 11:


You mean specific to also upgrading the DRAM? 
This particular procedure is not intended to cover also upgrading DRAM at
the same time, that's not really something we assume you're doing every time
you upgrade.

BTW, Sukumar does make a good point about the install script - it will
potentially make some changes to the config based on updated features, CoPP
being a prominent example.

An alternative in your case would be to just power off, upgrade DRAM,
reboot, and then install all. Clearly that involves 2 reboots with a single
sup.

Tim


>http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/upgrad
>e/gui
>de/b_Cisco_Nexus_7000_Series_NX-OS_Software_Upgrade_and_Downgrade_Guide
>__Rel
>ease_5.x_chapter_00.html#task_304731
>
>
>
>Regards,
>
>Antonio Soares, CCIE #18473 (R&S/SP)
>amsoares at netcabo.pt
>http://www.ccie18473.net
>
>
>
>-----Original Message-----
>From: Tim Stevenson [mailto:tstevens at cisco.com]
>Sent: quinta-feira, 8 de Novembro de 2012 15:51
>To: Antonio Soares; 'Dirk Woellhaf'
>Cc: 'cisco-nsp'; 'Charles Spurgeon'
>Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade
>
>At 07:18 AM 11/8/2012, Antonio Soares mused:
> >I just have one SUP... You are talking about dual supervisors setup, 
> >right
>?
>
>
>Ah. In that case, clearly, the box is going to go offline when you upgrade.
>You might want to consider buying another sup.
>
>IMO, there is no huge benefit in using the install all script in a 
>single sup system - in the end, all it will do for you is a little 
>sanity checking and maybe save you from fat fingering a bootstring.
>
>In your situation, I would copy over the new images you want; manually 
>change the bootstrings & save to startup; power off the box, yank the 
>sup & add the DRAM; and then power it all back on.
>
>Tim
>
>
>
> >Regards,
> >
> >Antonio Soares, CCIE #18473 (R&S/SP)
> >amsoares at netcabo.pt
> >http://www.ccie18473.net
> >
> >
> >
> >-----Original Message-----
> >From: Dirk Woellhaf [mailto:dirk.woellhaf at gmail.com]
> >Sent: quinta-feira, 8 de Novembro de 2012 14:10
> >To: Antonio Soares
> >Cc: Charles Spurgeon; cisco-nsp
> >Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade
> >
> >Hi Antonio,
> >
> >You should be able to do the memory-upgrade without rebooting the box.
> >I've never done it on my I own but I know a few which did without any 
> >problem. I believe they first upgraded the memory and then did the
update!
> >
> >Dirk
> >
> >Sent from my iPhone
> >
> >On 08.11.2012, at 13:42, Antonio Soares <amsoares at netcabo.pt> wrote:
> >
> > > Thanks, I don't know if you noticed but somewhere in the thread 
> > > the bug was mentioned and it is resolved in 5.1.5 and later.
> > >
> > > Bug CSCtn61286 - Boot variables are not set up correctly on Sup-2 
> > > after ISSU
> > >
> > > So in my case, it should not give me problems (5.2.3a to 5.2.7).
> > >
> > > But since I also need to upgrade the SUP1 RAM from 4G to 8G, I 
> > > have no other option than doing the traditional upgrade. It's the 
> > > only way to just send the box down 1 time:
> > >
> > > - update the boot variables
> > > - power off and upgrade the RAM
> > > - power on
> > >
> > > The install all script has another limitation: it won't let us to 
> > > reboot when we chose to do it. This is what happened to me last time:
> > >
> > > +++++++++++++++++
> > > Switch will be reloaded for disruptive upgrade.
> > > Do you want to continue with the installation (y/n)?  y
> > >
> > > Install is in progress, please wait.
> > >
> > > (..)
> > >
> > > A few minutes later:
> > >
> > > Finishing the upgrade, switch will reboot in 10 seconds.
> > > +++++++++++++++++
> > >
> > > I don't see how to upgrade the RAM and upgrade the NX-OS with the 
> > > install script in just one shot...
> > >
> > >
> > > Regards,
> > >
> > > Antonio Soares, CCIE #18473 (R&S/SP) amsoares at netcabo.pt 
> > > http://www.ccie18473.net
> > >
> > >
> > > -----Original Message-----
> > > From: Charles Spurgeon [mailto:c.spurgeon at austin.utexas.edu]
> > > Sent: quinta-feira, 8 de Novembro de 2012 00:50
> > > To: Antonio Soares
> > > Cc: 'Tóth András'; 'cisco-nsp'
> > > Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade
> > >
> > > While doing some more testing this aft I also removed the sup from 
> > > slot 5 and did a "disruptive" single sup ISSU upgrade from 5.1(5) 
> > > to
> > > 5.2(7) on the slot 6 sup without issues.
> > >
> > > -Charles
> > >
> > > On Tue, Nov 06, 2012 at 11:48:35PM +0000, Antonio Soares wrote:
> > >> Great, I must confess that I searched a lot and I didn't find 
> > >> this bug. So I suppose the install all script will work well this
time.
> > >> I will come back to the list next week with the good news. I hope
> > >> :)
> > >>
> > >>
> > >> Thanks.
> > >>
> > >> Regards,
> > >>
> > >> Antonio Soares, CCIE #18473 (R&S/SP) amsoares at netcabo.pt 
> > >> http://www.ccie18473.net
> > >>
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: Tóth András [mailto:diosbejgli at gmail.com]
> > >> Sent: terça-feira, 6 de Novembro de 2012 23:35
> > >> To: Antonio Soares
> > >> Cc: cisco-nsp
> > >> Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade
> > >>
> > >> Hi Antonio,
> > >>
> > >> In general, doing a traditional upgrade (changing boot variables) 
> > >> will not update the BIOS for example, while an ISSU does and it's 
> > >> non-disruptive with dual-supervisors.
> > >>
> > >> There's a defect which caused the behavior you were seeing,
> > >> CSCtn61286 which affects 5.1(3). Since you were upgrading from 
> > >> that version, it was still impacting the upgrade process. It has 
> > >> been fixed in 5.1(4) and 5.2(1) already, so upgrading from
> > >> 5.2(3a) to
> > >> 5.2(7) will not have the
> > > same issue.
> > >>
> > >> http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do
> > >> ?m
> > >> et
> > >> h
> > >> od=fet
> > >> chBugDetails&bugId=CSCtn61286
> > >>
> > >>
> > >> If the boot variables are incorrect, you can edit them as you'd 
> > >> do on an IOS device, make sure you update the kickstart and 
> > >> system as
>well.
> > >>
> > >> Upgrading from 5.2(3a) to 5.2(7) can be done using the install 
> > >> all
> > >> (ISSU) method.
> > >>
> > >> Best regards
> > >>
> > >> On Tue, Nov 6, 2012 at 11:38 AM, Antonio Soares 
> > >> <amsoares at netcabo.pt>
> > > wrote:
> > >>> Hello group,
> > >>>
> > >>>
> > >>>
> > >>> Anyone knows the difference between using the install all script 
> > >>> or just update the boot system flash command when upgrading 
> > >>> NX-OS on a Nexus
> > >> 7K ?
> > >>>
> > >>>
> > >>>
> > >>> The question applies to a single supervisor setup.
> > >>>
> > >>>
> > >>>
> > >>> The official documentation mentions the two ways of doing it:
> > >>>
> > >>>
> > >>>
> > >>> - using the install all script:
> > >>>
> > >>>
> > >>>
> > >>> http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os
> > >>> /u
> > >>> pg
> > >>> ra
> > >>> de/gui
> > >>> de/b_Cisco_Nexus_7000_Series_NX-OS_Software_Upgrade_and_Downgrad
> > >>> e_
> > >>> Gu
> > >>> id
> > >>> e__Rel
> > >>> ease_5.x_chapter_00.html#con_314241
> > >>>
> > >>>
> > >>>
> > >>> - using the traditional procedure:
> > >>>
> > >>>
> > >>>
> > >>> http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os
> > >>> /u
> > >>> pg
> > >>> ra
> > >>> de/gui
> > >>> de/b_Cisco_Nexus_7000_Series_NX-OS_Software_Upgrade_and_Downgrad
> > >>> e_
> > >>> Gu
> > >>> id
> > >>> e__Rel
> > >>> ease_5.x_chapter_00.html#task_39E26688E1204F8CAAE876450A575E73
> > >>>
> > >>>
> > >>>
> > >>> I had a bad experience in the past with the install all script. 
> > >>> I was doing an upgrade to a 7010 with only 1 supervisor that was 
> > >>> installed in
> > >> slot 6.
> > >>> The install all script has a problem, may a bug, it only 
> > >>> correctly updates the boot variables for slot 5:
> > >>>
> > >>>
> > >>>
> > >>> boot kickstart bootflash:/n7000-s1-kickstart.5.2.3a.bin sup-1
> > >>>
> > >>> boot system bootflash:/n7000-s1-dk9.5.2.3a.bin sup-1
> > >>>
> > >>> boot kickstart bootflash:/n7000-s1-kickstart.5.1.3.bin sup-2
> > >>>
> > >>>
> > >>>
> > >>> The install all script assumes that if there is only one 
> > >>> supervisor, it should be on slot 5. Above we can see that the 
> > >>> boot system is missing for sup-2.
> > >>>
> > >>>
> > >>>
> > >>> In summary, is there any problem if I simply update the boot 
> > >>> variables and reload ? May I end up with the supervisor running 
> > >>> the new NX-OS release and the modules the old NX-OS release ?
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> Regards,
> > >>>
> > >>>
> > >>>
> > >>> Antonio Soares, CCIE #18473 (R&S/SP) amsoares at netcabo.pt
> > >>>
> > >>> http://www.ccie18473.net <http://www.ccie18473.net/>
> > >>>
> > >>> _______________________________________________
> > >>> cisco-nsp mailing list  cisco-nsp at puck.nether.net 
> > >>> https://puck.nether.net/mailman/listinfo/cisco-nsp
> > >>> archive at http://puck.nether.net/pipermail/cisco-nsp/
> > >>
> > >>
> > >> _______________________________________________
> > >> cisco-nsp mailing list  cisco-nsp at puck.nether.net 
> > >> https://puck.nether.net/mailman/listinfo/cisco-nsp
> > >> archive at http://puck.nether.net/pipermail/cisco-nsp/
> > >
> > >
> > > _______________________________________________
> > > cisco-nsp mailing list  cisco-nsp at puck.nether.net 
> > > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
> >
> >_______________________________________________
> >cisco-nsp mailing list  cisco-nsp at puck.nether.net 
> >https://puck.nether.net/mailman/listinfo/cisco-nsp
> >archive at http://puck.nether.net/pipermail/cisco-nsp/
>
>
>
>
>Tim Stevenson, tstevens at cisco.com
>Routing & Switching CCIE #5561
>Distinguished Technical Marketing Engineer, Cisco Nexus 7000 Cisco - 
>http://www.cisco.com IP Phone: 408-526-6759
>********************************************************
>The contents of this message may be *Cisco Confidential* and are 
>intended for the specified recipients only.




Tim Stevenson, tstevens at cisco.com
Routing & Switching CCIE #5561
Distinguished Technical Marketing Engineer, Cisco Nexus 7000 Cisco -
http://www.cisco.com IP Phone: 408-526-6759
********************************************************
The contents of this message may be *Cisco Confidential* and are intended
for the specified recipients only.



_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

More information about the cisco-nsp mailing list