cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5003
Views
5
Helpful
6
Replies

Failed to configure bootvar system for sup-1: imghdr library error in Nexus 7k

avinash2092
Beginner
Beginner

Hi All,

 

I am getting below error message when i am trying to configure the boot variable in nexus 7k.

 

N7k(config)# boot system bootflash:/n7000-s1-kickstart.5.2.9.bin sup-1
Failed to configure bootvar system for sup-1: imghdr library error (0x4045001C)

 

 

Need your help on how to resolve this as we have to upgrade the device .

 

Current version : 5.0.2a

 

 

Regards,
Avinash

 

 

 

6 Replies 6

Mark Malone
VIP Alumni
VIP Alumni

Is it the same if you don't specify the Sup-1 as in Nexus the sup2 will auto upgrade anyway ?active will copy to standby

can you post the current show boot

another option is try issu upgrade

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/6_x/nx-os/upgrade/guide/b_Cisco_Nexus_7000_Series_NX-OS_Software_Upgrade_and_Downgrade_Guide_Release_6-x.html#con_317522

Hi Mark,

 

I have even tried to set the bootvar without sup-1 but still i am getting the same error.

 

N7k(config)# boot system bootflash:/n7000-s1-dk9.5.2.9.bin
Failed to configure bootvar system for sup-1: imghdr library error (0x4045001C)
Failed to configure bootvar system for sup-2: imghdr library error (0x4045001C)

 

We have only single supervisor.

 

Please find the show boot . Boot variables are showing not set. I have tried for other system and kickstart images. for everything its showing the same error. Am not sure , what would happen if it gets reloaded. 

N7k(config)# sh boot
Current Boot Variables:

sup-1
kickstart variable not set
system variable not set
sup-2
kickstart variable not set
system variable not set
No module boot variable set

Boot Variables on next reload:

sup-1
kickstart variable not set
system variable not set
sup-2
kickstart variable not set
system variable not set
No module boot variable set

 

Also confirm if using install command would help to complete the upgrade.

 

Regards,

Avinash

Hi

have you uploaded the images to the flash yet can you you post the dir bootflash: output ?

If you use the install its an inline upgrade ISSU , you should not have to reboot the Nexus its cleaner but first you need to have the files in dir as below

7kdist-1# dir
          0    Nov 22 13:49:52 2012  20121122_134952_poap_4961_init.log
          0    Nov 22 14:20:32 2012  20121122_142032_poap_4966_init.log
        524    Aug 17 00:41:04 2012  JAF1626BNNJ_183875131.lic
       4096    Aug 14 14:27:51 2013  lost+found/
  208481976    Aug 17 00:39:57 2012  n7000-s1-dk9-npe.6.1.1.bin
  207224893    Nov 15 15:51:33 2012  n7000-s1-dk9-npe.6.1.2.bin
  207916248    Aug 14 13:16:23 2013  n7000-s1-dk9-npe.6.1.4.bin
  392037489    Jul 25 13:37:45 2015  n7000-s1-dk9-npe.6.2.12.bin
   41848116    Aug 14 13:18:25 2013  n7000-s1-epld.6.1.4.img
   30035968    Aug 17 00:38:39 2012  n7000-s1-kickstart-npe.6.1.1.bin
   29471232    Nov 15 15:45:07 2012  n7000-s1-kickstart-npe.6.1.2.bin
   29729792    Aug 14 13:19:24 2013  n7000-s1-kickstart-npe.6.1.4.bin
   31170048    Jul 25 13:33:57 2015  n7000-s1-kickstart-npe.6.2.12.bin
      17567    Nov 22 13:42:58 2012  oldconfig.cfg
    3729926    Nov 15 17:54:10 2012  preISSU_binary_show_tech_all_11_15_2012_17_53_38HRS.tar.gz
       4096    Nov 22 13:22:51 2012  scripts/
       4096    Aug 17 00:48:03 2012  vdc_2/
       4096    Aug 17 00:48:03 2012  vdc_3/
       4096    Aug 17 00:48:03 2012  vdc_4/
       4096    Jul 25 14:05:50 2015  vdc_5/

 

Then when there confirmed in flash you set the boot statements and the bootvar will show like this

7kdist-1# show boot
Current Boot Variables:

sup-1
kickstart variable = bootflash:/n7000-s1-kickstart-npe.6.2.12.bin
system variable = bootflash:/n7000-s1-dk9-npe.6.2.12.bin
sup-2
kickstart variable = bootflash:/n7000-s1-kickstart-npe.6.2.12.bin
system variable = bootflash:/n7000-s1-dk9-npe.6.2.12.bin
No module boot variable set

Boot Variables on next reload:

sup-1
kickstart variable = bootflash:/n7000-s1-kickstart-npe.6.2.12.bin
system variable = bootflash:/n7000-s1-dk9-npe.6.2.12.bin
sup-2
kickstart variable = bootflash:/n7000-s1-kickstart-npe.6.2.12.bin
system variable = bootflash:/n7000-s1-dk9-npe.6.2.12.bin
No module boot variable set


 

 

 

Please find the dir output below:

 

N7k# dir
       1347    Jun 03 17:08:46 2010  aaa_cnv.log
      49152    Jun 03 16:49:59 2010  lost+found/
   99698682    Jan 08 09:33:38 2008  n7000-s1-dk9.4.2.2a.bin
  107369112    Jun 03 16:45:25 2010  n7000-s1-dk9.5.0.2a.bin
  164479117    Aug 17 23:44:08 2015  n7000-s1-dk9.5.2.9.bin
   23875072    Jan 08 09:33:46 2008  n7000-s1-kickstart.4.2.2a.bin
   23613440    Jun 03 16:47:29 2010  n7000-s1-kickstart.5.0.2a.bin
   29777920    Aug 18 00:00:10 2015  n7000-s1-kickstart.5.2.9.bin
       4096    Jan 08 09:57:32 2008  vdc_2/
       4096    Jan 08 09:57:32 2008  vdc_3/
       4096    Jan 08 09:57:32 2008  vdc_4/

Usage for bootflash://
  574902272 bytes used
 1234997248 bytes free
 1809899520 bytes total

I have tried to set bootvar after uploading the images.

 

Regards,

Avinash

Ok have you tried to use the issu method instead does it return the same results ?

Run in this order with your images

show install all impact kickstart n7000-s1-kickstart.6.0.1.bin system n7000-s1-dk9.6.0.1.bin

install all kickstart n7000-s1-kickstart.6.0.1.bin system n7000-s1-dk9.6.0.1.bin

Hi Mark,

We will try to do that in next maintenance window.

We did a upgrade yesterday in another N7k from 5.1.3 to 6.2.12 and faced some issue.

Whether upgrading directly is recommended also could someone share the prerequisites for the upgrade.

The issue we faced was , the modules got upgraded to 6.2.12 but the physical interfaces were not available for all the modules.

Module and supervisor status was fine.

When we consoled into the switch , we were able to see that the interface configurations were missing.

 

When we try to configure the interfaces we were getting error messages as below:

N7k# sh run int eth1/1

                         ^
Invalid range at '^' marker.


N7k(config)# int ethernet 1/29

Error: Invalid range: Ethernet1/29.

Kindly suggest why this happened. If we have to enable some features.

 

Regards,

Avinash

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: