03-18-2007 01:37 AM - edited 02-21-2020 01:27 AM
Hello:
Does anyone have a step by step upgrade procedure for upgrading the PIX from v7.0 to v7.22 ?
I have tried the normal upgrade procedure similar to the one available for 6.3 to 7.0, but i get an error saying "Not Enough Space on Device"..even if i try to replace the files. Im upgrading with 64MB RAM and 16MB Flash installation on a 515E.
Thanks,
VINEET BHATIA
03-18-2007 12:34 PM
Hey Vineet,
Here are the steps involved and also illustration of how to upgrade PIX with
7.0(1) to OS 7.2(2).
I have included my comments in with "//" in below illustration-
LAB-PIX-7(config)# sh flash
Directory of flash:/
7 -rw- 5124096 20:53:57 Nov 24 2005 pix701.bin
11 -rw- 5919340 20:59:06 Nov 24 2005 asdm-501.bin
13 -rw- 7017 14:00:58 Jul 22 2005 admin.cfg
15998976 bytes total (4930560 bytes free)
// We need to free up the flash as there is not enough memory available to store
// other OS image.
// Deleting the image from flash would not cause any network down issues as PIX
// is running from the image loaded in the RAM during the boot time.
LAB-PIX-7(config)# del pix701.bin
Delete filename [pix701.bin]?
Delete flash:/pix701.bin? [confirm]
LAB-PIX-7(config)# copy tftp flash
Address or name of remote host []? 10.x.x.x
Source filename []? pix722.bin
Destination filename [pix722.bin]?
Accessing tftp://10.x.x.x/pix722.bin...!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Writing file flash:/pix722.bin...
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
5437440 bytes copied in 148.150 secs (36739 bytes/sec)
LAB-PIX-7(config)#
LAB-PIX-7(config)# sh flash
Directory of flash:/
7 -rw- 5437440 21:12:42 Nov 24 2005 pix722.bin
11 -rw- 5919340 20:59:06 Nov 24 2005 asdm-501.bin
13 -rw- 7017 14:00:58 Jul 22 2005 admin.cfg
15998976 bytes total (4617216 bytes free)
// Above indicates that PIX OS image 7.2(2) has been copied successfully to flash.
// Now we need to set PIX to use the newly installed image during the boot time.
LAB-PIX-7(config)# no boot system flash:/pix701.bin
LAB-PIX-7(config)# boot system flash:/pix722.bin
LAB-PIX-7(config)# sh run | in boot
boot system flash:/pix722.bin
LAB-PIX-7(config)#
If this is the procedure you are using, let me know what error/issue you are facing when trying to upgrade.
Hope that helps.
Regards,
Vibhor.
03-19-2007 06:49 AM
Hi Vibhor:
I have used a similar proceudre before and even if i try to first delete and then copy it still gives me an error. See the excerpt below:
pix(config)# sh flash
Directory of flash:/
7 -rw- 5437440 04:05:32 Jan 01 1993 image
11 -rw- 5958324 04:04:27 Jan 01 1993 asdm
16128000 bytes total (4719104 bytes free)
pix(config)# del image.bin
Delete filename [image.bin]?
Delete flash:/image.bin? [confirm]
%Error deleting flash:/image.bin (No such file or directory)
Now its strange for the device to tell me that no such file or directory exists because i can see the file in the sh flash command.
Thanks for your help.
VINEET BHATIA
03-19-2007 07:55 AM
OK I know its a stupid mistake. But the issue is resolved. I was typing out image.bin whereas the file on the flash was just image without an extension. Duhh!
Anyways Thanks to everyone who helped. Vibhor, how do i reload the new 5.2.2 asdm now ?
Thanks
VINEET BHATIA
03-19-2007 01:59 AM
Apart from what the TAC engineer has posted. Adding more to it i would say that when you converted from 6.3 to 7.0 the image in the flash would have stored as image.bin . Now when upgrading from the 7.0 to 7.2 approx there might be only 5-6 mb left in your flash which is less. So delete your image.bin file and if you have also copied the asdm file. Delete that too. Now do the upgradation procedure as the TAC engineer has suggested. Remember to get the proper asdm for the 7.2 also. Working with asdm has also become easier. The problem your facing is like the earlier upgrades that you do in which the process automatically deletes your earlier pix image here you have to delete the image on your own using delete flash:image.bin
HTH
Hoogen
03-22-2007 07:54 AM
ASDM UPGRADE PROCEDURE :
AB-ASA-7(config)# copy tftp flash
Address or name of remote host [10.130.102.153]?
Source filename [ASA704.bin]? asdm-522.bin
Destination filename [asdm-522.bin]?
Accessing tftp://10.130.102.153/asdm-522.bin...!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Writing file flash:/asdm-522.bin...
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
5958324 bytes copied in 165.460 secs (36111 bytes/sec)
LAB-ASA-7(config)#
LAB-ASA-7(config)# sh flash
Directory of flash:/
7 -rw- 5437440 21:12:42 Nov 24 2005 ASA704.bin
11 -rw- 5919340 20:59:06 Nov 24 2005 asdm-522.bin
13 -rw- 7017 14:00:58 Jul 22 2005 admin.cfg
// asdm-522.bin is now copied in the flash. Now we need to set ASA to use
// this image for loading ASDM.
LAB-ASA-7(config)# asdm image flash:/asdm-522.bin
// Last steps involve saving the running configuration to memory as we have
// made changes to boot files and reloading the ASA.
LAB-ASA-7(config)# write memory
Building configuration...
Cryptochecksum: d4f498de e877e418 2f9effa7 62ca0d6b
4807 bytes copied in 3.20 secs (1602 bytes/sec)
[OK]
LAB-ASA-7(config)# reload
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