Problem with ISSU process on VSS 1440

Unanswered Question
Feb 25th, 2009
User Badges:
  • Bronze, 100 points or more

We are following the ISSU process for upgading a VSS 1440, using the documentation here:

After copying image onto both supervisors, when the command:

issu loadversion sup-bootdisk:s72033-adventerprisek9_wan-mz.122-33.SXI.bin is run we get the following error:

% CV [ bootdisk:s72033-advipservicesk9_wan-mz.122-33.SXI.bin ] must be named first in BOOT [ bootdisk:s72033-adventerprisek9_wan-mz.122-33.SXI.bin ]

The advipservice image is the one running, and the adventerprise is the one we are trying to upgrade to.

It would appear that the issue is to do with the boot variable, but cannot find a way around the problem.

Anyone run into this and resolved it?


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (3 ratings)
p.lockwood Tue, 04/21/2009 - 20:26
User Badges:

I have the same issue, want to run a test upgrade before going in to production, running SXI and just want to upgrade to SXI1 have loaded SXI1 to sup-bootflash: and slavesup-bootflash: and when entering the command issu loadversion sup-bootdisk:s72033-ipservicesk9_wan-mz.122-33.SXI1 it comes up with following error.

% CV [ bootdisk:s72033-ipservicesk9_wan-mz.122-33.SXI.bin ] must be named first

in BOOT [ bootdisk: ]

Anyone know how to get around this?


p.lockwood Wed, 04/22/2009 - 22:21
User Badges:

Got this working, just needed to start with a boot statement for the existing image which ties in with the issu runversion part of the ugrade.

aacole Wed, 04/22/2009 - 23:34
User Badges:
  • Bronze, 100 points or more

Can you post up the boot statement you used?

cpembleton Wed, 08/05/2009 - 12:30
User Badges:
  • Silver, 250 points or more


Did you ever get a resolution to this? Having same issue.



Daniel ElHani Fri, 08/28/2009 - 01:37
User Badges:

Hi Guys,

Had the same issue.. worked it out:

boot system flash sup-bootdisk:s72033-ipbasek9-vz.122-33.SXI1.bin

or any other image you're currently running

make sure your boot section in the running config looks as below with no extra lines:


boot system flash sup-bootdisk:s72033-ipbasek9-vz.122-33.SXI1.bin



pmchandler Wed, 11/17/2010 - 09:21
User Badges:

IMPORTANT: You must copy your running config to the startup config in order to be able to execute the issu loadversion command successfully after having corrected your boot config lines.

gwes Fri, 09/14/2012 - 03:17
User Badges:


I had the same issue, but got it fixed. Here is what I did.

(config)#no boot system flash bootflash:s2t54-advipservicesk9-mz.SPA.150-1.SY1.bin



#conf t

(config)#boot system flash bootdisk:s2t54-advipservicesk9-mz.SPA.150-1.SY1.bin



#issu loadversion 1/5 disk0:s2t54-advipservicesk9-mz.SPA.150-1.SY2.bin 2/1 slavedisk0:s2t54-advipservicesk9-mz.SPA.150-1.SY2.bin

obacati21 Wed, 09/05/2012 - 03:30
User Badges:

Hi ,

I've got same issue with 6506 and SUP-2T.

Sh run :



boot system flash bootdisk:s2t54-ipbasek9-mz.SPA.150-1.SY2.bin



I did :

copy running-config startup-config

and when I try :

#issu loadversion bootdisk:s2t54-ipbasek9-mz.SPA.150-1.SY2.bin

I have :

% CV [ bootdisk:s2t54-ipbasek9-mz.SPA.150-1.SY1.bin ] must be named first in BOOT [ bootdisk:s2t54-ipbasek9-mz.SPA.150-1.SY2.bin ]

I think I meet all requirements for eFSU. Does anybody get an idea ?


ma4d Mon, 04/01/2013 - 03:55
User Badges:

I had this issue as well on a new system.  I noticed that this was part of the default config:

boot system flash bootdisk:

and it was showing up first in the bootvar

stacey-vss-6506#sho bootvar

BOOT variable = bootdisk:,1;bootdisk:s2t54-ipservicesk9-mz.SPA.150-1.SY1.bin,12;

so I removed it:

(config)# no boot system flash bootdisk:

and was then able to complete the eFSU.

I had this issue with a 6880, and it was a really dumb mistake.


boot system bootdisk:c6880x-adventerprisek9-mz.SPA.151-2.SY2.bin

CORE-6880-VSS#issu loadversion bootdisk:c6880x-adventerprisek9-mz.SPA.151-2.SY3.bin

% CV [ bootdisk:/c6880x-adventerprisek9-mz.SPA.151-2.SY2.bin ] must be named first in BOOT [ bootdisk:c6880x-adventerprisek9-mz.SPA.151-2.SY3.bin ]


In my boot statement, I did not use the '/' in the file url.


CORE-6880-VSS(config)#no boot system bootdisk:c6880x-adventerprisek9-mz.SPA.151-2.SY2.bin
CORE-6880-VSS(config)#boot sys bootdisk:/c6880x-adventerprisek9-mz.SPA.151-2.SY2.bin
Building configuration...
CORE-6880-VSS#issu loadversion bootdisk:c6880x-adventerprisek9-mz.SPA.151-2.SY3.bin                                                                  
%issu loadversion executed successfully, Standby is being reloaded





This Discussion