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

Thu Nov 8 10:51:08 EST 2012

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?met
> >> 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/upg
> >>> ra
> >>> de/gui
> >>> de/b_Cisco_Nexus_7000_Series_NX-OS_Software_Upgrade_and_Downgrade_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/upg
> >>> ra
> >>> de/gui
> >>> de/b_Cisco_Nexus_7000_Series_NX-OS_Software_Upgrade_and_Downgrade_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.