Technical Tip: How to access a secondary HA unit using CLI

Prerequisites:

• Healthy HA Cluster: All units must be part of the same FortiAnalyzer HA cluster. HA status must show all devices as synchronized and online.
• Primary Unit Access: Must be logged into the primary FortiAnalyzer unit (via SSH or console). The admin account used must have super_admin privileges.
• Firmware Compatibility: All HA members should run the same FortiAnalyzer firmware version. The procedure applies to all supported versions where execute ha manage (or equivalent) is available.
• HA Communication Working:  Heartbeat and management links between HA units must be operational. No split-brain or 'out-of-sync' conditions should be present.

• CLI Access Enabled: SSH/Console access must be enabled and properly configured on the primary unit, and Access policies must allow the admin to run HA management commands.

• Cluster Information Known: Must be able to identify the target secondary unit (e.g., from 'get system ha status').

Before using the CLI command, ensure the FortiAnalyzer HA status is UP.

And then, use these CLI commands:

Viva-kvm32 # exe ssh <Secondary IP> <Username> 
Viva-kvm32 # exe ssh 10.47.3.199 admin 
The authenticity of host '10.47.3.199 (10.47.3.199)' can't be established.
ED25519 key fingerprint is SHA256:LEUYE1MPGJXbAlj/YEFfjV9obN+kK0EOb2F4GIDsaU4.
This key is not known by any other names.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
(admin@10.47.3.199) Password:
Tiara-kvm21 #

Related document: 

Setting up a FortiAnalyzer HA cluster