End-of-Life (EoL)

request high-availability state

Description

On a WildFire appliance cluster, make the high-availability (HA) state of the local controller node or of the peer controller node functional.

Hierarchy Location

request high-availability

Syntax

request { high-availability { state { functional; } peer {   functional; } } }

Options

> functional
—Make the HA state of the local controller node functional.
> peer
—Make the HA state of the peer controller node functional.

Sample Output

The highlighted lines in the output show that the HA state of the local controller node is functional in the active (primary) controller role and that the HA state of the peer controller node is functional in the passive (backup) controller role.
admin@wf-500(active-controller)>
show high-availability state
High-Availability: Local Information: Version: 1
State: active-controller (last 1 days)
Device Information: Management IPv4 Address: 10.10.10.14/24 Management IPv6 Address: HA1 Control Links Joint Configuration: Encryption Enabled: no Election Option Information: Priority: primary Preemptive: no Version Compatibility: Software Version: Match Application Content Compatibility: Match Anti-Virus Compatibility: Match Peer Information: Connection status: up Version: 1
State: passive-controller (last 1 days)
Device Information: Management IPv4 Address: 10.10.20.112/24 Management IPv6 Address: Connection up; Primary HA1 link Election Option Information: Priority: secondary Preemptive: no Configuration Synchronization: Enabled: yes Running Configuration: synchronized

Required Privilege Level

superuser, deviceadmin

Recommended For You