cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1939
Views
0
Helpful
5
Replies

UPGRADE READINESS CHECK - FAILED 000_start/000_check_platform_support

phil6564
Level 1
Level 1

Hi all

I am getting an error when running the readiness check to upgrade, via the FMC, a firepower sensor running version 7.0.3 to 7.0.4: 

[230510 08:45:03:652] no lsm information file available
[230510 08:45:03:682] MAIN_UPGRADE_SCRIPT_START
[230510 08:45:03:717] Readiness check for :Cisco_Network_Sensor_Upgrade-7.0.4-55
[230510 08:45:03:723] #####################################
[230510 08:45:03:726] # UPGRADE READINESS CHECK STARTING
[230510 08:45:03:729] #####################################
[230510 08:45:03:824] SKIP 000_start/000_000_repair_ftd_csp_id.sh (not applicable to this version SWVERSION=7.0.3 compare_to=COMPARE_TO=6.4.0,6.5.0 condition=CONDITION=ge,lt)
[230510 08:45:04:533] BEGIN 000_start/000_00_run_cli_kick_start.sh
[230510 08:45:07:377] END 000_start/000_00_run_cli_kick_start.sh
[230510 08:45:07:428] SKIP 000_start/000_0_check_user_agent.pl (not applicable to this version SWVERSION=7.0.3 compare_to=COMPARE_TO=6.7.0 condition=CONDITION=lt)
[230510 08:45:07:476] SKIP 000_start/000_0_minimum_28GB_RAM_NEEDED.sh
[230510 08:45:07:538] SKIP 000_start/000_0_start_upgrade_status_api_stack.sh
[230510 08:45:07:904] BEGIN 000_start/000_check_platform_support.sh
[230510 08:45:09:371] FAILED 000_start/000_check_platform_support.sh
[230510 08:45:09:660] continuing on next script due to readiness check.
[230510 08:45:09:725] SKIP 000_start/000_check_sign_type.sh
[230510 08:45:09:795] SKIP 000_start/000_check_update.sh
[230510 08:45:09:879] SKIP 000_start/000_db_schema_check.sh
[230510 08:45:09:954] SKIP 000_start/099_check_legacy_amp_port.pl (not applicable to this version SWVERSION=7.0.3 compare_to=COMPARE_TO=7.0.0 condition=CONDITION=lt)
[230510 08:45:10:332] BEGIN 000_start/100_start_messages.sh
[230510 08:45:10:845] END 000_start/100_start_messages.sh
[230510 08:45:11:321] BEGIN 000_start/101_run_pruning.pl
[230510 08:47:18:752] END 000_start/101_run_pruning.pl
[230510 08:47:18:871] SKIP 000_start/102_check_sru_install_running.pl
[230510 08:47:19:285] BEGIN 000_start/105_check_model_number.sh
[230510 08:47:19:808] END 000_start/105_check_model_number.sh
[230510 08:47:19:937] SKIP 000_start/106_check_HA_sync.pl
[230510 08:47:20:089] SKIP 000_start/106_check_HA_updates.pl
[230510 08:47:20:596] BEGIN 000_start/107_version_check.sh
[230510 08:47:23:104] END 000_start/107_version_check.sh
[230510 08:47:23:246] SKIP 000_start/108_check_sensors_ver.pl
[230510 08:47:23:385] SKIP 000_start/109_check_HA_MDC_status.pl
[230510 08:47:23:813] BEGIN 000_start/110_DB_integrity_check.sh
[230510 08:49:34:774] END 000_start/110_DB_integrity_check.sh
[230510 08:49:34:984] SKIP 000_start/112_CF_check.sh
[230510 08:49:35:521] BEGIN 000_start/113_EO_integrity_check.pl
[230510 09:18:01:122] END 000_start/113_EO_integrity_check.pl
[230510 09:18:01:338] SKIP 000_start/200_clean_csp_files.sh
[230510 09:18:01:929] BEGIN 000_start/250_check_system_files.sh
[230510 09:18:02:464] END 000_start/250_check_system_files.sh
[230510 09:18:02:681] SKIP 000_start/320_remove_backups.sh
[230510 09:18:02:862] SKIP 000_start/400_run_troubleshoot.sh
[230510 09:18:03:350] BEGIN 000_start/410_check_disk_space.sh
[230510 09:18:12:613] END 000_start/410_check_disk_space.sh
[230510 09:18:13:146] BEGIN 200_pre/001_check_reg.pl
[230510 09:18:15:411] END 200_pre/001_check_reg.pl
[230510 09:18:15:745] BEGIN 200_pre/002_check_mounts.sh
[230510 09:18:16:301] END 200_pre/002_check_mounts.sh
[230510 09:18:16:635] BEGIN 200_pre/005_check_manager.pl
[230510 09:18:17:522] END 200_pre/005_check_manager.pl
[230510 09:18:17:941] BEGIN 200_pre/006_check_snort.sh
[230510 09:18:21:542] END 200_pre/006_check_snort.sh
[230510 09:18:21:901] BEGIN 200_pre/007_check_sru_install.sh
[230510 09:18:22:418] END 200_pre/007_check_sru_install.sh
[230510 09:18:22:777] BEGIN 200_pre/009_check_snort_preproc.sh
[230510 09:18:25:018] END 200_pre/009_check_snort_preproc.sh
[230510 09:18:25:392] BEGIN 200_pre/011_check_self.sh
[230510 09:18:25:922] END 200_pre/011_check_self.sh
[230510 09:18:26:301] BEGIN 200_pre/015_verify_rpm.sh
[230510 09:18:26:979] END 200_pre/015_verify_rpm.sh
[230510 09:18:27:069] SKIP 200_pre/100_650_remove_packet_analyzers.pl (not applicable to this version SWVERSION=7.0.3 compare_to=COMPARE_TO=6.5.0 condition=CONDITION=lt)
[230510 09:18:27:158] SKIP 200_pre/100_check_dashboards.pl
[230510 09:18:27:248] SKIP 200_pre/100_get_snort_from_dc.pl
[230510 09:18:27:352] SKIP 200_pre/101_check_uncommitted_data.pl
[230510 09:18:27:451] SKIP 200_pre/110_670_web_analytics.pl (not applicable to this version SWVERSION=7.0.3 compare_to=COMPARE_TO=6.2.3,6.7.0 condition=CONDITION=ge,lt)
[230510 09:18:27:554] SKIP 200_pre/110_setup_upgrade_ui.sh
[230510 09:18:27:672] SKIP 200_pre/120_fstab_fixup.sh
[230510 09:18:27:792] SKIP 200_pre/120_generate_auth_for_upgrade_ui.pl
[230510 09:18:27:914] SKIP 200_pre/152_save_etc_sf.sh
[230510 09:18:28:042] SKIP 200_pre/199_before_maintenance_mode.sh
[230510 09:18:28:178] SKIP 200_pre/200_enable_maintenance_mode.pl
[230510 09:18:28:320] SKIP 200_pre/202_disable_syncd.sh
[230510 09:18:28:468] SKIP 200_pre/400_restrict_rpc.sh
[230510 09:18:28:616] SKIP 200_pre/500_stop_system.sh
[230510 09:18:28:774] SKIP 200_pre/501_recovery.sh
[230510 09:18:28:954] SKIP 200_pre/505_revert_prep.sh
[230510 09:18:29:125] SKIP 200_pre/506_revert_prep_eventdb.sh
[230510 09:18:29:310] SKIP 200_pre/600_ftd_onbox_data_export.sh
[230510 09:18:29:499] SKIP 200_pre/610_lamplighter_010_artifacts_export.sh
[230510 09:18:29:688] SKIP 200_pre/998_fix_broken_rules.pl
[230510 09:18:29:885] SKIP 200_pre/999_enable_sync.sh
[230510 09:18:30:070] MAIN_UPGRADE_SCRIPT_END
[230510 09:18:30:104] Readiness check completed....
[230510 09:18:31:476] Attempting to remove upgrade lock
[230510 09:18:31:479] Success, removed upgrade lock
[230510 09:18:31:485]
[230510 09:18:31:488] #######################################################
[230510 09:18:31:492] # UPGRADE READINESS CHECK COMPLETE status : FAILED! #
[230510 09:18:31:495] #######################################################

Has anyone seen this before?

Regards,

Phil.

 

1 Accepted Solution

Accepted Solutions

Shazz
Level 1
Level 1

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvy95809

Please apply the below workaround.

If no upgrade was previously attempted...
Workaround on sensor:
Rename the /ngfw to /ngfw.old
mv /ngfw /ngfw.old

Trigger the upgrade from FMC

==============

If an upgrade was previously attempted but failed...
Workaround on sensor:
Remove the upgrade lock (if present):
rm -r /tmp/upgrade.lock

Rename the /ngfw to /ngfw.old
mv /ngfw /ngfw.old

Resume the upgrade via CLI:
nohup install_update.pl --resume /var/sf/updates/<upgrade_name>

During the upgrade you may run into this error "no upgrade status package found", to resolve the error please action the same steps again and resume the upgrade.

1. remove the upgrade lock:
rm -r /tmp/upgrade.lock

2. rename the /ngfw to /ngfw.old
mv /ngfw /ngfw.old

 

View solution in original post

5 Replies 5

Marvin Rhoads
Hall of Fame
Hall of Fame

What is the sensor model and what upgrade file are you using to initiate the attempt?

phil6564
Level 1
Level 1

It's an ASA 5508, running ASA version 9.14(4) and I am attempting to upgrade the SFR module from 7.0.3 to 7.0.4. The sensor upgrade filenames are asasfr-sys-7.0.4-55.pkg and asasfr-5500x-boot-7.0.4-55.img

On reading the failed.log file in the /var/log/sf/Cisco_Network_Sensor_Upgrade-7.0.4/upgrade_readiness directory, it indicates “Platform architecture x86_64 is not supported. Supported architecture(s) are i386.” I conclude that it must be the readiness check script that is not compatible since I have upgraded other identical units to 7.0.4 using the reimage procedure, so the software itself must be compatible. If that is the case could there be a chance that the upgrade could work, even though the readiness check fails?

 

Marvin Rhoads
Hall of Fame
Hall of Fame

That's odd. 7.0.4 (and 7.0.5) are supported on the ASA 5508-X Firepower service module.

You would use Cisco_Network_Sensor_Upgrade-7.0.4-55.sh.REL.tar from FMC. The two files you mentioned are for reimage only.

For an ASA 5508-X I would recommend waiting for the forthcoming 7.0.6 since it will fix the bug that ASA Firepower service modules have with the new VDB updates (>361).

Shazz
Level 1
Level 1

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvy95809

Please apply the below workaround.

If no upgrade was previously attempted...
Workaround on sensor:
Rename the /ngfw to /ngfw.old
mv /ngfw /ngfw.old

Trigger the upgrade from FMC

==============

If an upgrade was previously attempted but failed...
Workaround on sensor:
Remove the upgrade lock (if present):
rm -r /tmp/upgrade.lock

Rename the /ngfw to /ngfw.old
mv /ngfw /ngfw.old

Resume the upgrade via CLI:
nohup install_update.pl --resume /var/sf/updates/<upgrade_name>

During the upgrade you may run into this error "no upgrade status package found", to resolve the error please action the same steps again and resume the upgrade.

1. remove the upgrade lock:
rm -r /tmp/upgrade.lock

2. rename the /ngfw to /ngfw.old
mv /ngfw /ngfw.old

 

Thanks S_Haz. That works perfectly.

 

Review Cisco Networking for a $25 gift card