request high-availability sync-to-remote

Description

On a WildFire appliance cluster, synchronize the local controller node’s candidate configuration or running configuration, or the local controller node’s clock (time and date) to the remote high-availability (HA) peer controller node.

Hierarchy Location

request high-availability

Syntax

request { 
high-availability { 
sync-to-remote { 
candidate-config; 
clock; 
running-config; 
} 
} 
} 

Options

> candidate-config—Synchronize the candidate configuration on the local peer controller node to the remote HA peer controller node.
> clock—Synchronize the clock (time and date) on the local peer controller node to the remote HA peer controller node.
> running-config—Synchronize the running configuration on the local peer controller node to the remote HA peer controller node.

Sample Output

The highlighted line in the output shows that the HA configuration state is synchronized on the HA peer controller node.
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

Related Documentation