IPS Recovery procedure - Error

Answered Question
Mar 9th, 2009

Hello guys...

I forgot the password for AIP-SSM-10 module and am trying to break it by recover. It runs 5.x and hence have to do a recovery. upon recovery procedure the image copies to the system from tftp server and throws the below error message...

Slot-1 772> Bad magic number (0x-47cd60cf)

Slot-1 773> Rebooting due to Autoboot error ...

Slot-1 774> Rebooting....

any suggestion on wht could be the reason and how to go about this?

Thanks,

AJ

Correct Answer by marcabal about 7 years 11 months ago

the file being attempted for install is not what the ROMMON of the SSM is expecting.

Either the System Image file being used has been corrupted during download.

OR the System Image procedure is being attempted with a file Other than a System Image.

There are several different types of files for IPS and their usage is often confused.

For example:

For version 6.1(2)E3 there were 3 different files for the AIP-SSM-10:

System Image:

IPS-SSM_10-K9-sys-1.1-a-6.1-2-E3.img

- For installing through ROMMON, or mroe technically through the "hw-module module 1 recover ..." command of the ASA. It install a complete System Image on the SSM and erases all previous data from the SSM.

NOTE: This is the file type that should be used in the method you are following.

Upgrade:

IPS-K9-6.1-2-E3.pkg

- For upgrading from earlier version of the sensor to this new version. It converts previous configuration to work with the newer version.

Recovery Partition:

IPS-K9-r-1.1-a-6.1-2-E3.pkg

- For upgrading JUST the recovery partition of the SSM. The recovery partition can then be used for recovery with the "recovery application-partition" command in the sensor's CLI.

There can be some confusion here because this file is the "Recovery" image, BUT is NOT used with the ASA's "hw-module module 1 recover" command.

Instead the "System Image" is what is used with the "hw-module module 1 recover" command.

If you find that you are not using the correct file type (unkowingly used an Upgrade file or Recovery file), then download the System Image file and try again.

If you ARE using the System Image file, then do a verification of the size and md5 checksum of the file and compare it to what is on cisco.com. It may have been corrupted during download from cisco.com, and you may need to do a fresh download of the file.

If the file size and md5 checksum match the file on cisco.com, then check your TFTP server. Using a 3rd machine attempt to tftp the file from the tftp server. Once tftp'd check the size and md5 checksum again to ensure that your TFTP server is able to serve out the entire file. You want to ensure that your TFTP server is not truncating your file on download.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
marcabal Mon, 03/09/2009 - 12:26

the file being attempted for install is not what the ROMMON of the SSM is expecting.

Either the System Image file being used has been corrupted during download.

OR the System Image procedure is being attempted with a file Other than a System Image.

There are several different types of files for IPS and their usage is often confused.

For example:

For version 6.1(2)E3 there were 3 different files for the AIP-SSM-10:

System Image:

IPS-SSM_10-K9-sys-1.1-a-6.1-2-E3.img

- For installing through ROMMON, or mroe technically through the "hw-module module 1 recover ..." command of the ASA. It install a complete System Image on the SSM and erases all previous data from the SSM.

NOTE: This is the file type that should be used in the method you are following.

Upgrade:

IPS-K9-6.1-2-E3.pkg

- For upgrading from earlier version of the sensor to this new version. It converts previous configuration to work with the newer version.

Recovery Partition:

IPS-K9-r-1.1-a-6.1-2-E3.pkg

- For upgrading JUST the recovery partition of the SSM. The recovery partition can then be used for recovery with the "recovery application-partition" command in the sensor's CLI.

There can be some confusion here because this file is the "Recovery" image, BUT is NOT used with the ASA's "hw-module module 1 recover" command.

Instead the "System Image" is what is used with the "hw-module module 1 recover" command.

If you find that you are not using the correct file type (unkowingly used an Upgrade file or Recovery file), then download the System Image file and try again.

If you ARE using the System Image file, then do a verification of the size and md5 checksum of the file and compare it to what is on cisco.com. It may have been corrupted during download from cisco.com, and you may need to do a fresh download of the file.

If the file size and md5 checksum match the file on cisco.com, then check your TFTP server. Using a 3rd machine attempt to tftp the file from the tftp server. Once tftp'd check the size and md5 checksum again to ensure that your TFTP server is able to serve out the entire file. You want to ensure that your TFTP server is not truncating your file on download.

jaravinthan Tue, 03/10/2009 - 06:07

Hello Marcoa,

That was a plum!!! i uploaded correct image and phew!!! cool!!

great explanation... Thanks...

Actions

This Discussion