Skip to content

High Availability

Location in GUI: Devices » Device Management » High Availability

Diagram
NameTypeConstraintMandatoryDefault Value
ha_pairsList[ha_pairs]No

NameTypeConstraintMandatoryDefault Value
nameStringYes
primary_deviceStringYes
secondary_deviceStringYes
ha_link_logical_nameStringYes
ha_link_interface_nameStringYes
ha_link_primary_ipIPYes
ha_link_secondary_ipIPYes
ha_link_netmaskIPYes
state_link_use_same_as_haBooleantrue, falseYes
actionChoiceSWITCHNo
encryption_enabledBooleantrue, falseNofalse
encryption_keyStringNo
encryption_key_generation_schemeChoiceAUTO, CUSTOMNo
failed_interfaces_limitIntegermin: 1, max: 211No1
failed_interfaces_percentIntegermin: 1, max: 100No
ha_link_use_ipv6Booleantrue, falseNofalse
interface_hold_timeIntegermin: 25, max: 75No
interface_poll_timeIntegermin: 1, max: 999No
interface_poll_time_unitChoiceSEC, MSECNo
peer_hold_timeIntegermin: 3, max: 999No
peer_hold_time_unitChoiceSEC, MSECNo
peer_poll_timeIntegermin: 1, max: 999No
peer_poll_time_unitChoiceSEC, MSECNo
state_link_interface_nameStringNo
state_link_logical_nameStringNo
state_link_netmaskStringNo
state_link_primary_ipIPNo
state_link_secondary_ipIPNo
state_link_use_ipv6Booleantrue, falseNofalse

Prerequisites:

As any new configuration will be made to the primary device, it is important to note the deploy: true value should present on the primary and deploy: false should be present on the secondary for Terraform to manage the deployment of changes from the FMC to the firewalls. If deploy: false is set for all devices, changes will need to be manually deployed after they have been sent to the FMC.

Interface configuration is done on the primary device under interface configuration section. Please note that:

  • it is mandatory to configure monitor_interface and ipv4_standby_address for standby IP to be configured
  • it is mandatory to configure both ha_active_mac_address and ha_standby_mac_address for this configuration to take effect
fmc:
domains:
- name: Global
policies:
access_control_policies:
- name: MyAccessPolicyName2
default_action: BLOCK
devices:
devices:
- name: MyDeviceName1
host: 10.1.120.203
access_control_policy: MyAccessPolicyName2
registration_key: cisco123
deploy: true
licenses:
- ESSENTIALS
- IPS
performance_tier: FTDv5
vrfs:
- name: Global
physical_interfaces:
- name: "GigabitEthernet0/1"
- name: "GigabitEthernet0/2"
ipv4_static_address: 10.62.159.201
ipv4_static_netmask: 24
logical_name: INSIDE
- name: MyDeviceName2
host: 10.62.158.216
registration_key: cisco123
access_control_policy: MyAccessPolicyName2
deploy: false
licenses:
- ESSENTIALS
- IPS
performance_tier: FTDv5

High Availability:

fmc:
domains:
- name: Global
devices:
ha_pairs:
- name: MyHAName1
primary_device: MyDeviceName1
secondary_device: MyDeviceName2
ha_link_logical_name: failover
ha_link_interface_name: GigabitEthernet0/1
ha_link_primary_ip: 10.10.4.1
ha_link_secondary_ip: 10.10.4.2
ha_link_netmask: 255.255.255.248
state_link_use_same_as_ha: true
# Merge High Availability interface configuration with regular interface configuration
devices:
- name: MyDeviceName1
vrfs:
- name: Global
physical_interfaces:
- name: "GigabitEthernet0/2"
ipv4_standby_address: 10.62.159.202
monitor_interface: true
ha_active_mac_address: c460.15e4.0edd
ha_standby_mac_address: c460.15e4.0ed0