05-02-2012 08:46 AM
I am attempting to downgrade from 5.1.3.N1.1 to 5.0.3.N2.2b for standards compliance.
When following the ISSU steps for validation of the install all command I receive the following error on the following command:
sh install all impact kickstart bootflash:n5000-uk9-kickstart.5.0.3.N2.2b.bin system bootflash:n5000-uk9.5.0.3.N2.2b.bin
Verifying image bootflash:/n5000-uk9-kickstart.5.0.3.N2.2b.bin for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/n5000-uk9.5.0.3.N2.2b.bin for boot variable "system".
[####################] 100% -- SUCCESS
Verifying image type.
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/n5000-uk9.5.0.3.N2.2b.bin.
[# ] 0% -- FAIL. Return code 0x404F0003 (SRG file not present/cannot be opened).
I followed some recommendations from this post https://supportforums.cisco.com/thread/2108814
I found this information http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/deferral/Deferral_Advisory_Notice_N5K.html
I am unsure of how to upgrade when the steps to validate indicate a problem with the upgrade/downgrade.
I still receive the error.
Any help would be greatly appreciated.
Attached are the steps done so far and outputs.
05-02-2012 10:45 AM
Update: I am able to downgrade to 5.0.3.N1.1b with no issues.
This appears to be an issue with going from N1 to N2.
Can any elloborate on this?
05-04-2012 09:19 AM
Hello Heath
Please open a TAC case to work on this - there may be many reasons for such behavior.
Also as Krun proposed - you can set boot variables manually, then reload the switch. And after that do not forget to run "install all" command to ensure that everything has downgraded properly.
HTH,
Alex
05-02-2012 05:30 PM
You can set boot variable manually and reload switch
Sent from Cisco Technical Support iPhone App
05-04-2012 09:32 AM
can you please send us output of following
show system internal flash
show system internal dir /var/tmp
also we dont recommend to change boot variables and reload.
This might cause some other problems after you downgrade.
We would rather fix the problem first and then downgrade
using install all.
Vinayak
Cisco TAC
05-04-2012 11:50 AM
I had already created a case with our reseller. The engineer there had me reload the 5ks and attempt the show install all impact again. When I did it was successful.
I was able to then downgrade to 5.0.3.N2.2b. I am currently working to duplicate the issue by going back to 5.1.3.N1.1.
The engineer also stated that I was probably running into this bug:
Here is the contents of the sh system internal flash and show system internal dir /var/tmp:
Mount-on 1K-blocks Used Available Use% Filesystem
/ 409600 72564 337036 18 /dev/root
/proc 0 0 0 0 proc
/post 2048 4 2044 1 none
/var 409600 72564 337036 18 none
/sys 0 0 0 0 none
/isan 1536000 409628 1126372 27 none
/var/tmp 307200 72 307128 1 none
/var/sysmgr 1024000 0 1024000 0 none
/var/sysmgr/ftp 409600 68 409532 1 none
/var/sysmgr/ftp/cores 102400 0 102400 0 none
/callhome 61440 0 61440 0 none
/dev/shm 524288 126552 397736 25 none
/volatile 153600 0 153600 0 none
/debug 20480 0 20480 0 none
/dev/mqueue 0 0 0 0 none
/debugfs 0 0 0 0 nodev
/mnt/plog 49024 1300 47724 3 /dev/mtdblock2
/mnt/cfg/0 114909 4274 104702 4 /dev/sda5
/mnt/cfg/1 112920 4274 102816 4 /dev/sda6
/var/sysmgr/startup-cfg 409600 2104 407496 1 none
/dev/pts 0 0 0 0 devpts
/mnt/pss 114917 5923 103060 6 /dev/sda4
/bootflash 1609984 779460 748740 52 /dev/sda3
./ 640
../ 240
bootloader_ver 0
util_cli_history_admin 48
mysrg 1664
mcm_ascii.log 1019
m2rib_ascii.3248 68
arping 101
stp.log.1 3836
fwm1.out 0
cmp_slot_id.1 0
ntpd_1 0
ntp_client_1 0
ntp__libdapi.log 0
igmp_restart.log 0
radius_debug.log 232
cfs_mac.log 166
climib.log 1416
lcc.log 694
security_stderr 77
security_stdout 0
aaa_debug.log 519
security_debug.log 647
evmc.3005 31
idehsd.log 602
mvsh.3000 0
lockcisco 0
.flexlm/ 60
logs@ 20
first_setup.log 2981
boot_uptime.log 56
vsh/ 40
05-04-2012 12:13 PM
I am assuming this output you sent me is after the reload ? Did you collect this before the reload? Also that bug is not really a bug, it just documents the condition for which we see the problem. ie if the files in one of the directories are full then it impacts the upgrade/downgrade. The action plan would be to get with Cisco TAC, load a dplug and clean out the files for the concerned directories via dplug. Not sure if this was done. But a reboot will also clean out the files hence you did not see the issue after reload.
V.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide