Hi guys. I need your help. We have 2 asa, fmc, asdm. Tried to install last software updates (6.2.3), everything went good except one asa. FMC, first ASA updated successfully. But on second asa it doesnt pass readiness check.
Currently it's version is 6.1.0.6 and 6.2.3 says we can update straightly from it. I checked console, no log folder created in /var/log/sf/updates/Cisco_Network_Sensor_Upgrade-6.2.3-83, but were for others (e.g. Sourcefire_3D_Def...)
Then i tried to run readiness-check manually to see some logs as there werent any in gui. So, running
perl /var/sf/bin/install_update.pl --readiness-check /var/sf/updates/Cisco_Network_Sensor_Upgrade-6.2.3-83 show me this error: Update is not a signed or content update at /var/sf/bin/install_update.pl line 509.
line 509:
if (defined($$update_info{is_sig_valid}))
{
# signed package. validated_filename is the extracted makeself file
$filepath = $$update_info{'validated_filename'};
$is_bundle = 1;
if ($$update_info{is_sig_valid} == 0)
{
warn "Update has invalid signature";
exit_update(1, "cleanup");
}
}
else
{
# unsigned package. filename is the file argument passed to this script
$filepath = $$update_info{'filename'};
$is_bundle = 0;
# Allow unsigned updates only for GeoDB, VDB, SRU
if (($$update_info{'update_type'} !~ /GeoLocation.+Database/) &&
($$update_info{'update_type'} !~ /Vulnerability.+Database/) &&
($$update_info{'update_type'} !~ /Rule.+Update/))
{
warn "Update is not a signed or content update";
exit_update(1, "cleanup");
}
}
As wee see is_sig_valid is not defined. From SF::Util::Update module we can see, if I understand right, it is defined when checksum (md5sum,sha512sum) executed correctly. But there is no problem with checksums, i check it manually and it is competing with original md5 and sha512 hashes.
Also, i thought about straight update incompability and because of that i checked Cisco_Network_Sensor_Upgrade-6.2.0-362, Cisco_Network_Sensor_Upgrade-6.2.2-81 and failed with same error. Please, help me to udnerstand and solve the problem
