How to a Break High Availability Pair when the Secondary Device is in a Failed or Disabled State
Problem: The secondary device is in a failed or disabled state and has lost connectivity with Security Cloud Control. In addition, the failover link may or may not be operational.
|
Primary Device State |
Secondary Device Stat |
Primary Device Connectivity with Security Cloud Control? |
Secondary Device Connectivity with Security Cloud Control? |
Failover link Operational? (Connectivity between Primary and Secondary devices) |
|---|---|---|---|---|
|
Active |
Failed |
Yes |
No |
Yes or No |
|
Active |
Disabled |
Yes |
No |
Yes or No |
Solution:
Perform a high availability force break to separate the units and then use the device CLI to remove the configuration from the standby unit and make the device a standalone device.
Procedure
| 1 |
In the Security Cloud Control navigation bar, click Security Devices. |
| 2 |
Click the Devices tab to locate your device. |
| 3 |
Click the FTD tab and select the primary device. |
| 4 |
In the Management pane on the left, click High Availability. |
| 5 |
Choose Devices > Device Management. |
| 6 |
Next to the high-availability pair you want to break, click the Break HA . |
| 7 |
Check the check box to force break as one of the peers does not respond. |
| 8 |
Click Yes. |
| 9 |
Delete the standby device from Security Cloud Control. |
| 10 |
Connect to the standby device’s CLI, either from the console port or using SSH. |
| 11 |
Log in with the Admin username and password. |
| 12 |
Enter configure high-availability disable to remove the failover configuration and disable the data management interface on the device. |
| 13 |
Enter configure network management-data-interface.
The new newtwork settings are assigned to the data device. |
What to do next
You can onboard the device as a standalone device to Security Cloud Control if required.