In order to verify the failover status, use the domain UUID and the DeviceHAPair UUID from Step 4 in this query: 6. In order to verify theFTD cluster configuration and status, run the show running-config cluster and show cluster info commands on the CLI. Newly installed FMC virtual is not accessible through GUI. Also I came across a command that restart FMC console services. " uuid_gw => , admin@FTDv:~$ sudo su 04:36 AM. REQUESTED FROM REMOTE for Malware Lookup Service service, TOTAL TRANSMITTED MESSAGES <6> for service 7000 So lets execute manage_procs.pl, monitor a secondary SSH window with pigtail and filter the output by IP of the FMC. In this case, high availability is not configured and FMC operates in a standalone configuration: If high availability is configured, local and remote roles are shown: Follow these steps to verify the FMC high availability configuration and status on the FMC CLI: 1. MSGS: 04-09 07:48:58 FTDv SF-IMS[14541]: [14552] sftunneld:sf_ssl[INFO] Connect to 192.168.0.200 failed on port 8305 socket 11 (Connection refused)MSGS: 04-09 07:48:58 FTDv SF-IMS[14541]: [14552] sftunneld:sf_ssl[INFO] No IPv4 connection to 192.168.0.200 Starting Cisco Firepower Management Center 2500, please waitstarted. If the cluster is configured, but not enabled, this output is shown: If the cluster is configured, enabled and operationally up, this output is shown: For more information about the OID descriptions refer to the CISCO-UNIFIED-FIREWALL-MIB. 2. If neither exists, then the FTD runs in a standalone configuration: 3. Related Community Discussions In order to verify the FTD failover status, use the token and the slot ID in this query: 4. mojo_server is down. 2. mine is reporting killing DCCSM with /var/sf/bin/dccsmstop.pl but that is just an info error. Unfortunately, I didn't see any backups created to restore from. HALT REQUEST SEND COUNTER <0> for IDS Events service - edited Metalowa 5, 60-118 Pozna, Poland REQUESTED FOR REMOTE for RPC service pmtool status | grep -E "Waiting|Down|Disable", pmtool status | grep -E "Waiting|Down|Disable|Running". once the two partner servers re-established communication. HALT REQUEST SEND COUNTER <0> for service 7000