Suspend a Device in an HA Pair

Introduction

Suspending a device in an HA pair keeps the HA configuration in place but the device does not perform any failover checking. This is useful for preventing failovers while troubleshooting a device, when upgrading the software on a device, or when both devices go into active/active state due to a misconfiguration. The suspended device will appear disabled to the other device in the HA pair. A suspended device can be managed and will operate like any standalone device. When you suspend the active device, then both devices in the HA pair are suspended. When you resume the active, then both devices are resumed. When you suspend the standby device, only it is suspended. When you resume the standby, only the standby is resumed.

To Suspend a Device in an HA Pair:

Step 1

Send an HA suspend POST request to the device.

curl -X POST -H "Accept: application/json" -H "Authorization: Bearer ACCESS_TOKEN" https://ftd.example/api/fdm/latest/devices/default/action/ha/suspend

{
  "nodeRole" : "HA_SECONDARY",
  "nodeState" : "HA_SUSPENDED_NODE",
  "peerNodeState" : "HA_UNKNOWN_NODE",
  "configStatus" : "UNKNOWN",
  "haHealthStatus" : "CRITICAL",
  "id" : "default",
  "type" : "hastatus",
  "links" : {
    "self" : "https://ftd.example/api/fdm/latest/devices/default/action/ha/suspend/default"
  }
}

Step 2

Send periodic HA status GET requests to the device until it becomes suspended.

curl -H 'Accept: application/json'  -H "Authorization: Bearer ACCESS_TOKEN"  https://ftd.example/api/fdm/latest/devices/default/operational/ha/status/default

{
  "nodeRole" : "HA_SECONDARY",
  "nodeState" : "HA_SUSPENDED_NODE",
  "peerNodeState" : "HA_UNKNOWN_NODE",
  "configStatus" : "UNKNOWN",
  "haHealthStatus" : "CRITICAL",
  "id" : "default",
  "type" : "hastatus",
  "links" : {
    "self" : "https://ftd.example/api/fdm/latest/devices/default/action/ha/status/default"
  }
}