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-boun...@puck.nether.net
[mailto:cisco-nsp-boun...@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)
amsoa...@netcabo.pt
http://www.ccie18473.net
-Original Message-
From: Tim Stevenson [mailto:tstev...@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)
>amsoa...@netcabo.pt
>http://www.ccie18473.net
>
>
>
>-Original Message-
>From: Tim Stevenson [mailto:tstev...@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)
> >amsoa...@netcabo.pt
> >http://www.ccie18473.net
> >
> >
> >
> >-Original Message-
> >From: Dirk Woellhaf [mailto:dirk.woell...@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 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 w
