Re: [c-nsp] Nexus 7K NX-OS Upgrade
Just for future reference if someone runs into the same issues: The hw revision of the M132XP that had no problems: 1.7 The hw revision of the M132XP that failed: 1.5 The hw revision of the spare card that had no problems: 2.3 Regards, Antonio Soares, CCIE #18473 (RS/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Antonio Soares Sent: sábado, 17 de Novembro de 2012 21:24 To: 'Colin Whittaker'; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade Unbelievable, this is a 70k card, isn't it ? Regards, Antonio Soares, CCIE #18473 (RS/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Colin Whittaker Sent: sábado, 17 de Novembro de 2012 18:22 To: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade On Sat, Nov 17, 2012 at 05:28:48PM -, Antonio Soares wrote: 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 :( Upgrade cycles tend to flush out latent faults in the linecards. When doing upgrades it is best to have spare cards on hand to handle those that fail. The failure rate on the M1 cards has gotten a lot better over the last two years. Gone are the days of 20% of the cards being DOA. Colin -- Colin Whittaker +353 (0)86 8211 965 http://colin.netech.ie co...@netech.ie ___ 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/
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-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 (RS/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 (RS/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 (RS/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 amsoa...@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
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 (RS/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: Neil Barnett [mailto:interarchet...@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-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 (RS/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 (RS/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 (RS/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 amsoa...@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
Re: [c-nsp] Nexus 7K NX-OS Upgrade
Hello, We had a similar sitatuation. We have two n7k in a vpc domain with vdc feature as well. The upgrade of the first switch was without any issue, but we upgraded the second one too, and the M1 card failed to boot, this caused that VDC couldn't start... After removing the failed card the vdc was able to boot up. And we received a new line card from Cisco within four hours (it depends on support contract). -A. On Sat, 17 Nov 2012, Antonio Soares wrote: 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 (RS/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 (RS/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 (RS/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 amsoa...@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
Re: [c-nsp] Nexus 7K NX-OS Upgrade
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:amsoa...@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 (RS/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: Neil Barnett [mailto:interarchet...@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-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 (RS/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 (RS/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 (RS/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
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 (RS/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 (RS/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 (RS/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 amsoa...@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 (RS/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: Charles Spurgeon [mailto:c.spurg...@austin.utexas.edu] Sent: quinta-feira, 8 de Novembro de 2012 00:50
Re: [c-nsp] Nexus 7K NX-OS Upgrade
On Sat, Nov 17, 2012 at 05:28:48PM -, Antonio Soares wrote: 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 :( Upgrade cycles tend to flush out latent faults in the linecards. When doing upgrades it is best to have spare cards on hand to handle those that fail. The failure rate on the M1 cards has gotten a lot better over the last two years. Gone are the days of 20% of the cards being DOA. Colin -- Colin Whittaker +353 (0)86 8211 965 http://colin.netech.ie co...@netech.ie ___ 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/
Re: [c-nsp] Nexus 7K NX-OS Upgrade
Hi, had about 6-7 faulty M1-32XP Linecards in the last 1.5 years. I already asked Cisco about some known build-errors for that card but they never came back with a answer. As far as I know, they expect about 6% of the cards to be faulty. It is what is,... :( regards Am 17.11.2012 um 18:28 schrieb Antonio Soares amsoa...@netcabo.pt: 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 (RS/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 (RS/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 (RS/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 amsoa...@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
Re: [c-nsp] Nexus 7K NX-OS Upgrade
Unbelievable, this is a 70k card, isn't it ? Regards, Antonio Soares, CCIE #18473 (RS/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Colin Whittaker Sent: sábado, 17 de Novembro de 2012 18:22 To: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade On Sat, Nov 17, 2012 at 05:28:48PM -, Antonio Soares wrote: 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 :( Upgrade cycles tend to flush out latent faults in the linecards. When doing upgrades it is best to have spare cards on hand to handle those that fail. The failure rate on the M1 cards has gotten a lot better over the last two years. Gone are the days of 20% of the cards being DOA. Colin -- Colin Whittaker +353 (0)86 8211 965 http://colin.netech.ie co...@netech.ie ___ 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/
Re: [c-nsp] Nexus 7K NX-OS Upgrade
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 (RS/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: Charles Spurgeon [mailto:c.spurg...@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 +, 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 (RS/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?meth od=fet chBugDetailsbugId=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 (RS/SP) amsoa...@netcabo.pt http://www.ccie18473.net http://www.ccie18473.net/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https
Re: [c-nsp] Nexus 7K NX-OS Upgrade
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 (RS/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 +, 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 (RS/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 chBugDetailsbugId=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 (RS/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/
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 amsoa...@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 (RS/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: Charles Spurgeon [mailto:c.spurg...@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 +, 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 (RS/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?meth od=fet chBugDetailsbugId=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
Re: [c-nsp] Nexus 7K NX-OS Upgrade
I just have one SUP... You are talking about dual supervisors setup, right ? Regards, Antonio Soares, CCIE #18473 (RS/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 amsoa...@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 (RS/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: Charles Spurgeon [mailto:c.spurg...@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 +, 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 (RS/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 h od=fet chBugDetailsbugId=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
Re: [c-nsp] Nexus 7K NX-OS Upgrade
At 04:37 AM 11/8/2012, Antonio Soares mused: 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: You should not need to take the box down to do a DRAM upgrade if you have 2 sups. Provided you're on 5.1 or later you don't need to upgrade the software/do an ISSU either. You will perform a stateful switchover from the active to the standby sup at one point in the process in order to upgrade the memory on the second sup. The procedure is described in the user docs: http://www.cisco.com/en/US/docs/switches/datacenter/hw/nexus7000/installation/guide/n7k_replacing.html#wp1272213 This procedure is completely unrelated to upgrading the software (provided you're already on/past the minimum release to support 8GB which is 5.1(1)). I would point out that at Step 21, you need to make sure to wait for the newly inserted 8GB sup come fully online and enter hot standby mode before attempting to switchover/yank the other sup. Tim - 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 (RS/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: Charles Spurgeon [mailto:c.spurg...@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 +, 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 (RS/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?meth od=fet chBugDetailsbugId=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
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 (RS/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 amsoa...@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 (RS/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: Charles Spurgeon [mailto:c.spurg...@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 +, 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 (RS/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 h od=fet chBugDetailsbugId=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
Re: [c-nsp] Nexus 7K NX-OS Upgrade
Any new CoPP best Practice configs update available in the new code is applied only when using install script. sukumar Thumb typed on my Smartphone. Excuse Typos. On Nov 8, 2012, at 7:54 AM, Tim Stevenson (tstevens) tstev...@cisco.com wrote: 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 (RS/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 amsoa...@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 (RS/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: Charles Spurgeon [mailto:c.spurg...@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 +, 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 (RS/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 h od=fet chBugDetailsbugId=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
Re: [c-nsp] Nexus 7K NX-OS Upgrade
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: http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/upgrade/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 (RS/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 (RS/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 amsoa...@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 (RS/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: Charles Spurgeon [mailto:c.spurg...@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 +, 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 (RS/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?m et h od=fet chBugDetailsbugId=CSCtn61286 If the boot variables are incorrect, you can edit them
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/upgrade/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 (RS/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 (RS/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 amsoa...@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 (RS/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: Charles Spurgeon [mailto:c.spurg...@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 +, 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 (RS/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
Re: [c-nsp] Nexus 7K NX-OS Upgrade
Hi Pete, Do you know what caused the 3 secs blip? How can Cisco claims that it is non-disruptive then? Thanks for sharing. Regards, Alexander Lim On 7 Nov, 2012, at 12:12 PM, Pete Templin peteli...@templin.org wrote: On 11/6/12 3:35 PM, Tóth András wrote: 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. Just to add a data point, it's almost non-disruptive. There's a noticeable blink on a per-linecard basis, probably 3 seconds, but I've had to deal with explaining the blip during a non-disruptive upgrade. pt ___ 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/
Re: [c-nsp] Nexus 7K NX-OS Upgrade
On 11/7/12 6:02 AM, Alexander Lim wrote: Do you know what caused the 3 secs blip? How can Cisco claims that it is non-disruptive then? Thanks for sharing. From what I've learned from others, the 'install all' unpacks the new files which run the processes, and then the processes are stopped/started. The blip aligns with the card that's actively being upgraded, as shown by the 'install all' or 'show install all status' if run on another login session/console. pt ___ 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/
Re: [c-nsp] Nexus 7K NX-OS Upgrade
At 06:05 AM 11/7/2012, Pete Templin mused: On 11/7/12 6:02 AM, Alexander Lim wrote: Do you know what caused the 3 secs blip? How can Cisco claims that it is non-disruptive then? Thanks for sharing. From what I've learned from others, the 'install all' unpacks the new files which run the processes, and then the processes are stopped/started. The blip aligns with the card that's actively being upgraded, as shown by the 'install all' or 'show install all status' if run on another login session/console. There are no software processes that affect hardware/data plane forwarding, any process can be statefully restarted without impacting data flow (in theory, ignoring bugs). We do claim it is non-disruptive and we can easily demonstrate that and have many times. It is unexpected and not per design to lose data traffic during an ISSU, provided you are ISSU'ing to/from supported releases (as per the ISSU matrix in the user documentation), all your data traffic is being hardware switched, and assuming no software defects (such as the specific one cited earlier in the thread). 2 cents, Tim pt ___ 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/ Tim Stevenson, tstev...@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Nexus 7K NX-OS Upgrade
Hi, I've seen ISSU disrupting data-forwarding during a CPoC in 2011 but this was all related to a bug. I have recently updated 4 N7k's from 5.2(3) to 5.2(5) without any problem! Regards dirk On Wed, Nov 7, 2012 at 4:20 PM, Tim Stevenson tstev...@cisco.com wrote: At 06:05 AM 11/7/2012, Pete Templin mused: On 11/7/12 6:02 AM, Alexander Lim wrote: Do you know what caused the 3 secs blip? How can Cisco claims that it is non-disruptive then? Thanks for sharing. From what I've learned from others, the 'install all' unpacks the new files which run the processes, and then the processes are stopped/started. The blip aligns with the card that's actively being upgraded, as shown by the 'install all' or 'show install all status' if run on another login session/console. There are no software processes that affect hardware/data plane forwarding, any process can be statefully restarted without impacting data flow (in theory, ignoring bugs). We do claim it is non-disruptive and we can easily demonstrate that and have many times. It is unexpected and not per design to lose data traffic during an ISSU, provided you are ISSU'ing to/from supported releases (as per the ISSU matrix in the user documentation), all your data traffic is being hardware switched, and assuming no software defects (such as the specific one cited earlier in the thread). 2 cents, Tim pt __**_ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/**mailman/listinfo/cisco-nsphttps://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/**pipermail/cisco-nsp/http://puck.nether.net/pipermail/cisco-nsp/ Tim Stevenson, tstev...@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@puck.nether.net https://puck.nether.net/**mailman/listinfo/cisco-nsphttps://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/**pipermail/cisco-nsp/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/
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 +, 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 (RS/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?method=fet chBugDetailsbugId=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/upgra de/gui de/b_Cisco_Nexus_7000_Series_NX-OS_Software_Upgrade_and_Downgrade_Guid 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/upgra de/gui de/b_Cisco_Nexus_7000_Series_NX-OS_Software_Upgrade_and_Downgrade_Guid 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 (RS/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/
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 +, 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 (RS/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?method=fet chBugDetailsbugId=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/upgra de/gui de/b_Cisco_Nexus_7000_Series_NX-OS_Software_Upgrade_and_Downgrade_Guid 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/upgra de/gui de/b_Cisco_Nexus_7000_Series_NX-OS_Software_Upgrade_and_Downgrade_Guid 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 (RS/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/
[c-nsp] Nexus 7K NX-OS Upgrade
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/upgrade/gui de/b_Cisco_Nexus_7000_Series_NX-OS_Software_Upgrade_and_Downgrade_Guide__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/upgrade/gui de/b_Cisco_Nexus_7000_Series_NX-OS_Software_Upgrade_and_Downgrade_Guide__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 (RS/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/
Re: [c-nsp] Nexus 7K NX-OS Upgrade
Thanks, I appreciate your feedback. Since it is a lab environment, may I ask you to see what happens when you upgrade with the install all script and with the sup in slot 6 ? I had the problem when upgrading from 5.1.3 to 5.2.3a. Now I need to upgrade to 5.2.7 and I want to avoid the issue. Regards, Antonio Soares, CCIE #18473 (RS/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: Charles Spurgeon [mailto:c.spurg...@austin.utexas.edu] Sent: terça-feira, 6 de Novembro de 2012 22:39 To: Antonio Soares Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade On Tue, Nov 06, 2012 at 10:38:46AM +, Antonio Soares 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 ? 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 ? I was just testing that this aft and it works fine in my lab tests, with the caveat that I have a dual-sup 7010. Manually configuring the boot strings and then typing reload resulted in sups and mods all coming up on the new code. -Charles Charles E. Spurgeon / UTnet UT Austin ITS / Networking c.spurg...@its.utexas.edu / 512.475.9265 ___ 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/
Re: [c-nsp] Nexus 7K NX-OS Upgrade
Hi Antonio, The difference between the two procedures is that install all will perform an in-service software upgrade, ie, this should be non disruptive to the data plane while the sups and all the modules will upgrade to the new version. Versus just changing the boot strings and rebooting, which is clearly disruptive to the entire system. In the end, both should result in all sups modules running the new release. Not sure what issues you ran into with ISSU, would at a minimum suggest you check the release notes to make sure the starting and target releases are compatible etc. Hope that helps, Tim At 03:04 PM 11/6/2012, Antonio Soares mused: Thanks, I appreciate your feedback. Since it is a lab environment, may I ask you to see what happens when you upgrade with the install all script and with the sup in slot 6 ? I had the problem when upgrading from 5.1.3 to 5.2.3a. Now I need to upgrade to 5.2.7 and I want to avoid the issue. Regards, Antonio Soares, CCIE #18473 (RS/SP) amsoa...@netcabo.pt http://www.ccie18473.net -Original Message- From: Charles Spurgeon [mailto:c.spurg...@austin.utexas.edu] Sent: terça-feira, 6 de Novembro de 2012 22:39 To: Antonio Soares Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Nexus 7K NX-OS Upgrade On Tue, Nov 06, 2012 at 10:38:46AM +, Antonio Soares 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 ? 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 ? I was just testing that this aft and it works fine in my lab tests, with the caveat that I have a dual-sup 7010. Manually configuring the boot strings and then typing reload resulted in sups and mods all coming up on the new code. -Charles Charles E. Spurgeon / UTnet UT Austin ITS / Networking c.spurg...@its.utexas.edu / 512.475.9265 ___ 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/ Tim Stevenson, tstev...@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
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?method=fetchBugDetailsbugId=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/upgrade/gui de/b_Cisco_Nexus_7000_Series_NX-OS_Software_Upgrade_and_Downgrade_Guide__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/upgrade/gui de/b_Cisco_Nexus_7000_Series_NX-OS_Software_Upgrade_and_Downgrade_Guide__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 (RS/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/
