On the ASA CLI you can execute "debug module-boot" which will help you see what settings are being used for the TFTP download, and what TFTP errors may be happening.
If you need to change a setting (like the IP Address), then you can execute "hw-module module 1 recover stop".
Then execute "hw-module module 1 recover configure" to correct the configuration.
Then execute "hw-module module 1 recover boot" again to try the recovery again.
(NOTE: You might have to wait till the module is Up or has timed out and Unresponsive before executing the "recover boot".)
--------
As a side note.
If you run "hw-module module 1 recover stop", and the module actually makes it to an Up state, then you have another alternative.
The recover method you are using above really only needs to be used when the SSM has experiences a problem and needs to be recovered.
The recovery method should generally not be used for upgrading to higher versions.
The recovery method will erase all configuration from the SSM.
If your SSM is running properly, then you can do an "upgrade" instead of a "recover".
For upgrade instructions refer to:
http://www.cisco.com/en/US/partner/docs/security/ips/6.1/configuration/guide/cli/cli_system_images.html#wp1142504
An SSM sensor running 5.0(2) IS able to upgrade to 6.1(2)E3 directly.
You will want to use the IPS-K9-6.1-2-E3.pkg upgrade file:
http://www.cisco.com/cgi-bin/tablebuild.pl/ips6
The easiest method is to actually push the upgrade to the sensor using IDM:
http://www.cisco.com/en/US/partner/docs/security/ips/5.0/configuration/guide/idm/dmadmin.html#wp1030863
Place the IPS-K9-6.1-2-E3.pkg file on your own desktop, then in IDM use the "Update is located on this client" option (Step 3 in the directions) to push that update to the sensor.
