Yes it is. But you can still use the ISSU method of doing things (install all) with just one SUP. It doesn't make too much sense, right ?
Regards, Antonio Soares, CCIE #18473 (R&S/SP) amsoa...@netcabo.pt http://www.ccie18473.net -----Original Message----- From: Alexander Lim [mailto:nsp.alexander....@gmail.com] Sent: quinta-feira, 8 de Novembro de 2012 04:56 To: Charles Spurgeon Cc: Antonio Soares; cisco-nsp Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade Hi Charles, I thought redundant sup is required for ISSU? Regards, Alexander Lim On 8 Nov, 2012, at 8:50 AM, Charles Spurgeon <c.spurg...@austin.utexas.edu> wrote: > 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) >> amsoa...@netcabo.pt >> http://www.ccie18473.net >> >> >> >> -----Original Message----- >> From: Tóth András [mailto:diosbej...@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 >> hod=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 <amsoa...@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) amsoa...@netcabo.pt >>> >>> http://www.ccie18473.net <http://www.ccie18473.net/> >>> >>> _______________________________________________ >>> cisco-nsp mailing list cisco-nsp@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@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@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
