cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3891
Views
5
Helpful
7
Replies

Readiness Check status failure migration firepower 6.1.0 to 6.2.0

hello everybody I have issue with migration firepower 6.1.0 to 6.2.0 show the following message:

 

 

Status log:Readiness Check complete with failure log@/var/log/sf/Sourcefire_3D_Upgrade-6.2.0/upgrade_readiness ------      Failure

 

Can you help me thank you.

 

Rafael Navarrete

 

 

7 Replies 7

mikael.lahtela
Level 4
Level 4
Hi,

Don't know what you have tried, but please read the release notes about upgrade path.
There are several important jumps from 6.1.0 to 6.2.0.
https://www.cisco.com/c/en/us/td/docs/security/firepower/620/relnotes/Firepower_System_Release_Notes_Version_620/important_update_notes.html#id_38002

br, Micke

hi micke thank you,  vefified the link cisco. Installed the following file:

 

Sourcefire_3D_Defense_Center_S3_Pre-install-6.0.1.999-1252.sh,  
Sourcefire_3D_Defense_Center_S3_Upgrade-6.0.1-1222.sh
Sourcefire_3D_Defense_Center_S3_Patch-6.0.1.4-1083.sh   
Sourcefire_3D_Defense_Center_S3_Upgrade-6.1.0-330.sh,  
Sourcefire_3D_Defense_Center_S3_Hotfix_AF-6.1.0.2-1.sh
Sourcefire_3D_Defense_Center_S3_Hotfix_AI-6.1.0.2-3.sh
Sourcefire_3D_Defense_Center_S3_Hotfix_AJ-6.1.0.2-1.sh
Sourcefire_3D_Defense_Center_S3_Upgrade-6.2.0-367.sh(with this file I have issue to migration to 6.2.0)

 

path update:

Version 5.4.1.1+ > Version 6.0.0 Pre-Installation Package > Version 6.0.0 >
Version 6.0.1 Preinstall > Version 6.0.1 > Version 6.1.0 Pre-Installation Package >
Version 6.1.0 > Version 6.2.0

 

thank you

 

Mickey

attachment the log:

 

[171213 21:11:38] Readiness check for :Sourcefire_3D_Defense_Center_S3_Upgrade-6.2.0-367
[171213 21:11:38] #####################################
[171213 21:11:38] # UPGRADE READINESS CHECK STARTING
[171213 21:11:38] #####################################
[171213 21:11:40] SKIP 000_start/000_check_update.sh
[171213 21:11:41] BEGIN  000_start/100_start_messages.sh
[171213 21:11:42] SKIP 000_start/100_zz_verify_bundle.sh
[171213 21:11:42] SKIP 000_start/101_prune_SnortAttribConfig.sh
[171213 21:11:42] SKIP 000_start/101_run_pruning.pl
[171213 21:11:42] BEGIN  000_start/102_check_sru_install_running.pl
[171213 21:11:44] BEGIN  000_start/105_check_model_number.sh
[171213 21:11:45] SKIP 000_start/106_check_HA_sync.pl
[171213 21:11:45] BEGIN  000_start/106_check_HA_updates.pl
[171213 21:11:46] BEGIN  000_start/107_version_check.sh
[171213 21:11:48] BEGIN  000_start/108_check_sensors_ver.pl
[171213 21:11:49]   FAILED  000_start/108_check_sensors_ver.pl
[171213 21:11:50] continuing on next script due to readiness check.
[171213 21:11:51] BEGIN  000_start/109_check_HA_MDC_status.pl
[171213 21:11:58] BEGIN  000_start/110_DB_integrity_check.sh
[171213 21:12:24] BEGIN  000_start/111_FS_integrity_check.sh
[171213 21:12:25] BEGIN  000_start/112_CF_check.sh
[171213 21:12:26] BEGIN  000_start/113_EO_integrity_check.pl
[171213 21:13:37] SKIP 000_start/170_link_log.sh
[171213 21:13:37] BEGIN  000_start/250_check_system_files.sh
[171213 21:13:38] SKIP 000_start/320_remove_backups.sh
[171213 21:13:38] SKIP 000_start/400_run_troubleshoot.sh
[171213 21:13:38] BEGIN  000_start/410_check_disk_space.sh
[171213 21:13:44] BEGIN  200_pre/001_check_reg.pl
[171213 21:13:45] BEGIN  200_pre/002_check_mounts.sh
[171213 21:13:48] BEGIN  200_pre/003_check_health.sh
[171213 21:13:51] BEGIN  200_pre/005_check_manager.pl
[171213 21:13:52] BEGIN  200_pre/006_check_snort.sh
[171213 21:13:54] BEGIN  200_pre/007_check_sru_install.sh
[171213 21:14:02] BEGIN  200_pre/009_check_snort_preproc.sh
[171213 21:14:05] BEGIN  200_pre/011_check_self.sh
[171213 21:14:08] BEGIN  200_pre/015_verify_rpm.sh
[171213 21:14:11] BEGIN  200_pre/100_check_correlation_rules.pl
[171213 21:14:12] SKIP 200_pre/100_check_dashboards.pl
[171213 21:14:12] SKIP 200_pre/100_get_snort_from_dc.pl
[171213 21:14:12] BEGIN  200_pre/100_log_version.sh
[171213 21:14:13] SKIP 200_pre/110_setup_upgrade_ui.sh
[171213 21:14:13] SKIP 200_pre/120_generate_auth_for_upgrade_ui.pl
[171213 21:14:13] SKIP 200_pre/152_save_etc_sf.sh
[171213 21:14:13] SKIP 200_pre/199_before_maintenance_mode.sh
[171213 21:14:13] SKIP 200_pre/200_enable_maintenance_mode.pl
[171213 21:14:13] SKIP 200_pre/201_disable_faild.sh
[171213 21:14:13] SKIP 200_pre/202_disable_syncd.sh
[171213 21:14:13] SKIP 200_pre/400_restrict_rpc.sh
[171213 21:14:13] SKIP 200_pre/470_revert_prep.sh
[171213 21:14:13] SKIP 200_pre/500_stop_system.sh
[171213 21:14:14] SKIP 200_pre/501_recovery.sh
[171213 21:14:14] SKIP 200_pre/501_stop_blackbird_cards.sh
[171213 21:14:14] SKIP 200_pre/600_ftd_onbox_data_export.sh
[171213 21:14:14] SKIP 200_pre/999_enable_sync.sh
[171213 21:14:14]  Readiness check completed....
[171213 21:14:14] Attempting to remove upgrade lock
[171213 21:14:14] Success, removed upgrade lock
[171213 21:14:14]
[171213 21:14:14] #######################################################
[171213 21:14:14] # UPGRADE READINESS CHECK COMPLETE  status : FAILED! #
[171213 21:14:14] #######################################################

What version do you have on your sensors?

br, Micke

hello mickey, the version of the IPS7125 is 5.4.0.4

 

regards,

 

Rafael Navarrete

 

 

 

 

FMC 6.2 and later can only manage sensors (devices) at release 6.1 or later. The release notes mention that here:

 

https://www.cisco.com/c/en/us/td/docs/security/firepower/620/relnotes/Firepower_System_Release_Notes_Version_620/important_update_notes.html#id_38002

 

So you will have to upgrade all of your managed sensors to 6.1 first. Only then will you be able to take FMC up to 6.2+

thank you very much Marvin. I will update the sensor first to version 6.1.0.

 

 

 

Regards,

 

Rafael Navarrete

Review Cisco Networking products for a $25 gift card