Step 1:
Copy the files onto the device: You can use TFTP, FTP or SCP. I like SCP because its way faster then then TFTP. Download a free copy of Solar Winds SCP.
copy scp://admin@192.168.100.1/n3000-uk9.5.0.3.U3.2.bin bootflash:
copy scp://admin@192.168.100.1/n3000-uk9-kickstart.5.0.3.U3.2.bin bootflash:
Step 2:
Confirm the files are are in the directory you specified: You also don't need to run an MD5 check because that is part of the install all option.
switch# dir
638 Jun 18 19:37:32 2012 license_FOC1536R01A_4.lic
49152 Feb 26 18:24:48 2013 lost+found/
3166 Feb 26 18:02:57 2013 mts.log
25439232 Jun 18 19:31:49 2012 n3000-uk9-kickstart.5.0.3.U2.2b.bin
25439744 Feb 26 19:00:08 2013 n3000-uk9-kickstart.5.0.3.U3.2.bin
93751392 Jun 18 19:32:32 2012 n3000-uk9.5.0.3.U2.2b.bin
126502986 Feb 26 18:59:16 2013 n3000-uk9.5.0.3.U3.2.bin
4096 Jan 29 19:35:08 2010 vdc_2/
4096 Jan 29 19:35:08 2010 vdc_3/
4096 Jan 29 19:35:08 2010 vdc_4/
Step 3:
Select which images to install and from what directory:
install all kickstart bootflash:///n3000-uk9-kickstart.5.0.3.U3.2.bin system bootflash:///n3000-uk9.5.0.3.U3.2.bin
switch# install all kickstart bootflash:///n3000-uk9-kickstart.5.0.3.U3.2.bin system bootflash:///n3000-uk9.5.0.3.U3.2.bin
Installer is forced disruptive
Verifying image bootflash:/n3000-uk9-kickstart.5.0.3.U3.2.bin for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/n3000-uk9.5.0.3.U3.2.bin for boot variable "system".
[####################] 100% -- SUCCESS
Verifying image type.
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/n3000-uk9.5.0.3.U3.2.bin.
[####################] 100% -- SUCCESS
Extracting "kickstart" version from image bootflash:/n3000-uk9-kickstart.5.0.3.U3.2.bin.
[####################] 100% -- SUCCESS
Extracting "bios" version from image bootflash:/n3000-uk9.5.0.3.U3.2.bin.
[####################] 100% -- SUCCESS
Performing module support checks.
[####################] 100% -- SUCCESS
Notifying services about system upgrade.
[####################] 100% -- SUCCESS
Compatibility check is done:
Module bootable Impact Install-type Reason
------ -------- -------------- ------------ ------
1 yes disruptive reset ISSU not supported
Images will be upgraded according to following table:
Module Image Running-Version New-Version Upg-Required
------ ---------- ---------------------- ---------------------- ------------
1 system 5.0(3)U2(2b) 5.0(3)U3(2) yes
1 kickstart 5.0(3)U2(2b) 5.0(3)U3(2) yes
1 bios v1.2.0(08/29/2011) v1.2.0(08/29/2011) no
1 power-seq v5.1 v5.1 no
Step 4: You will be prompted to reboot. Select Yes.
ISSU is not supported on this platform!!
Switch will be reloaded for disruptive upgrade.
Do you want to continue with the installation (y/n)? [n] y
ISSU is not supported on this platform!!
Switch will be reloaded for disruptive upgrade.
Do you want to continue with the installation (y/n)? [n] y
Install is in progress, please wait.
Performing runtime checks.
[####################] 100% -- SUCCESS
Setting boot variables.
[####################] 100% -- SUCCESS
Performing configuration copy.
[####################] 100% -- SUCCESS
Finishing the upgrade, switch will reboot in 10 seconds.
switch#
Step 5: Issue a show version to confirm the NX-OS version once it comes back from the reboot.
Tuesday, February 26, 2013
Sunday, February 10, 2013
Troubleshooting High CPU due to Multicast
Great Video on Troubleshooting High CPU due to Multicast. This video is geared toward IOS and not NX-OS.
https://supportforums.cisco.com/community/netpro/network-infrastructure/switching/blog/2012/12/12/troubleshooting-high-cpu-due-to-multicast
Subscribe to:
Posts (Atom)