Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

Error while upgrading Firmware

Hi,

Am upgrading my cisco MDS9513 firmware from 3.0.2(b) to 3.2.3(a)..I get following errors when i start the installation,have done installation successfully on other switches,but this switch in particular throws the error.

Appreciate your help..Thanks

Setting boot variables.

[# ] 0% -- FAIL. Return code -1.

Install has failed. Return code 0x4093000C (Setting boot variables failed).

Please identify the cause of the failure, and try 'install all' again.

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: Error while upgrading Firmware

Most of the time this is caused by a syntax issue with the 'install all' command.

Please ensure that the kickstart and main SAN-OS image are on the active supervisor bootflash and then issue this command from the command line.

install all system bootflash:m9500-sf2ek9-mz.3.2.3a.bin kickstart

bootflash:m9500-sf2ek9-kickstart-mz.3.2.3a.bin

Follow the prompts and at some point you will need to enter Y to continue.

I have seen where the module number, or sup-local was used in the install command and it caused problems.

Hope this helps,

Mike

2 REPLIES
Cisco Employee

Re: Error while upgrading Firmware

Most of the time this is caused by a syntax issue with the 'install all' command.

Please ensure that the kickstart and main SAN-OS image are on the active supervisor bootflash and then issue this command from the command line.

install all system bootflash:m9500-sf2ek9-mz.3.2.3a.bin kickstart

bootflash:m9500-sf2ek9-kickstart-mz.3.2.3a.bin

Follow the prompts and at some point you will need to enter Y to continue.

I have seen where the module number, or sup-local was used in the install command and it caused problems.

Hope this helps,

Mike

Community Member

Re: Error while upgrading Firmware

Thanks Mike,the solution turned out to be almost the same what you suggested..I opened up a case with Cisco and here is what he suggested.

CSCsr12337

install all Return code 0x4093000C when //sup-local files used

Symptom:

the upgrade process will fail if the "install all" command

is given a module location as part of the image uri. eg:

install all kickstart bootflash://sup-local/image_filename

Workaround:

do not use module locations when specifying image uri's.

-----------------------------------------------------------------

The command "install all..." may eventually also fail thereafter

with the same error code, even if not using the prefixes //sup-local/ etc.

This may happen if the boot variables on the standby already contain

these prefixes - this can be checked with "show boot" and to see

which is the standby use "show mod".

Here is the procedure how to recover from that scenario:

1. Remove the incorrect boot statements:

conf t

no boot kickstart

no boot system

if that is accepted, go directly to step 4.

Otherwise if the switch returns:

failed to clear bootvar kickstart ( or system )

then go to step 2:

2. In that case you first need to perform system switchover:

- make sure that "show system redundancy status" shows the system

is in "operational: HA" state

- issue "system switchover"

- wait until the system returns to HA state as above

3. Remove the incorrect boot statements:

conf t

no boot kickstart

no boot system

4. Restore the correct boot commands

conf t

boot kickstart bootflash:old_kickstart_filename system bootflash:old_system_filename

exit

5. issue "copy run start"

After the above - the upgrade should go through this time.

As per the defect CSCsr12337 mentioned above - this issue

should not happen even when using the absolute paths

- in the software versions that have the fix ( 4.1(2) and later ).

In earlier software versions, when hitting this issue

316
Views
0
Helpful
2
Replies
CreatePlease to create content