How to Break a High Availability Pair in Active-Active State
Both units in a remote deployment are in an active-active state because the failover interface became non-operational and they stopped receiving a response on their data interfaces. In this case, both units use the active IP address on their data management interface, which results in an unstable network between the units and Security Cloud Control.
You can determine if the units are both in active mode by logging into the device CLI and using the “show failover state” command on both units. The device status of both units shows ‘active’, and the same active IP address is assigned to both units.
Note | You can try rectifying the failover interface to restore the communication between the two peers and then perform the Force Break operation. If you cannot repair the connectivity issues of the failover interface, then perform the following steps: |
Procedure
Step 1 | Identify a device you want to remove from the network among the two units. | ||
Step 2 | Connect to the CLI of the identified device, either from the console port or using SSH. | ||
Step 3 | Log in with the Admin username and password. | ||
Step 4 | Enter the pmtool disablebyid sftunnel command.
| ||
Step 5 | Disconnect all the interfaces from the device you want to remove from the network. | ||
Step 6 | Enter configure network management-data-interface ipv4 manual ip_address ipv4_netmask gateway_ip_address interface interface_id command. In ip_addressspecify the IP address of the standby device. Example:
| ||
Step 7 | Enter configure high-availability suspend to suspend HA.
| ||
Step 8 | In the Security Cloud Control navigation bar, click Inventory. | ||
Step 9 | Click the Devices tab to locate your device. | ||
Step 10 | Click the FTD tab and select the primary device. | ||
Step 11 | In the Management pane on the left, click High Availability. | ||
Step 12 | Choose Device > Device Management. | ||
Step 13 | Next to the high availability pair where you want to separate the high availability pair, click Force Break. A message is displayed that the high-availability pair is separated successfully. | ||
Step 14 | Connect all the interfaces to the device. | ||
Step 15 | At the FTD CLI, enter pmtool enablebyId sftunnel. The threat defense device establishes its connection with Security Cloud Control in sometime.
| ||
Step 16 | Enter the sftunnel-status-brief command to view the management connection status.
| ||
Step 17 | Choose Deploy > Deployment to deploy the changes. Before the Security Cloud Control deploys the changes, it will detect the configuration differences and stop the deployment. Security Cloud Control detects the IP address change made to the device outside of the Cisco Security Cloud Control. | ||
Step 18 | Synchronize interface changes with Security Cloud Control. See Sync Interface Changes with the Management Center. | ||
Step 19 | You can now deploy the pending changes to the device. See Deploy configuration changes.. |
The device now becomes a standalone device with a new the IP address of the standby device.
What to do next
(optional) Deploy any pending changes to the other device having the IP address of the active device.