Comware Based
cancel
Showing results for 
Search instead for 
Did you mean: 

problem updating a 7500 switch

Nazzareno Taborgna
Occasional Contributor

problem updating a 7500 switch

Hello,

             I am trying to update my 7500, but it seems that there is not enought space left on the flash:

<switch-core1>dir
Directory of flash:/

0 -rw- 33340966 May 13 2014 13:59:31 7500-cmw520-r6708p03.app
1 drw- - May 13 2014 14:26:34 seclog
2 -rw- 5565 Apr 07 2015 22:10:31 config.cfg
3 -rw- 4160 Apr 07 2015 22:10:23 system.xml

64389 KB total (31811 KB free)

 

infact:

<switch-core1>tftp 172.16.2.52 get a7500/7500-CMW520-R6708P10.app
...
File will be transferred in binary mode
Downloading file from remote TFTP server, please wait.........

...........
Failed to write data into storage device, maybe no enough space on device

 

 

it seems that I should delete the current software file, but if something goes wrong how can I boot my 7500? I would like to follow a safe procedure.

 

My 7500 fabric card has a compact flash slot, but now I haven't a suitable card for it.

Supposing that I can install one, could I to use a file on the compact flash instead of the flash: in order to boot the 7500? in this case, how can I set the file on the compact flash as primary boot file?

 

1 REPLY
sdide
Respected Contributor

Re: problem updating a 7500 switch

Hi Nazzareno,

 

Its a known "problem". There is only room for one image on the standard 7500 flash.

 

You need to delete the old image!

 

> delete /unreserved 7500-cmw520-r6708p03.app

This takes a long time (and DO remember the /unreserved switch, otherwise no room is freed on the disk).

Get the new image (as you write)

> tftp 172.16.2.52 get a7500/7500-CMW520-R6708P10.app

and install it

> boot-loader file flash:/7500-cmw520-r6708p10.app slot 5 main

 

of course if you loose power after deleting and before finishing upload - its a mess.

 

You can put in a CF-card I have that in a few of my units.

 

>dir /all-filesystems
Directory of flash:/

0 drw- - Jan 01 2007 02:00:26 seclog
1 -rw- 33364255 Oct 02 2014 13:35:22 7500-cmw520-r6708p08.app
2 -rw- 146360 Mar 30 2015 12:56:10 config.cfg
3 -rw- 29851 Mar 30 2015 12:55:54 system.xml
4 -rw- 129083 Oct 23 2014 11:21:07 hp-ags-current.bat

64389 KB total (31473 KB free)

Directory of cfa0:/

0 drw- - Sep 18 2014 18:25:20 logfile
1 -rw- 33364255 Sep 23 2014 21:48:40 7500-cmw520-r6708p08.app
2 -rw- 33339502 Oct 02 2014 12:50:12 7500-cmw520-r6708.app

505984 KB total (440832 KB free)

File system type of cfa0: FAT32

If you have a CF-card, plug it in, and upload the image to that. That way you're safe.

You can reach the image from the boot-loader menu if somthing fails. (console access needed)

I've done all my upgrades using the "risky" delete-and-upload method.

 

So to boot from the cfa: as a backup if the primary image is gone or fails - do (case taken from the above unit of mine):

 

> boot-loader file cfa0:/7500-cmw520-r6708p08.app slot 5 backup

This command will set the boot file of the specified board. Continue? [Y/N]:Y
The specified file will be used as the backup boot file at the next reboot on slot 5!

> display boot-loader
The primary app to boot of board 5 at this time is: flash:/7500-cmw520-r6708p08.app
The primary app to boot of board 5 at next time is: flash:/7500-cmw520-r6708p08.app
The slave app to boot of board 5 at next time is: cfa0:/7500-cmw520-r6708p08.app

 

So as you can see the it tries the image at cfa0: as a "slave app" (dunno why they call it that?).

 

Regards

Søren Dideriksen, Network Administrator
Region Midtjylland