8.3. Deleting an HA Pair

Home Prev	InCenter 2.2.5 On-Premises Administration Guide	Next

There are two ways in which an HA pair can be deleted from InCenter:

Both the HAPair object and the associated StandaloneNode objects can be deleted from InCenter. This will leave a functioning HA pair that is no longer under InCenter control.
The HAPair object can be deleted but not the StandaloneNode objects. This leaves two nodes which are no longer part of an HA pair but are still under InCenter control.

Performing these two operations is described next.

Deleting the HA Pair and Standalone Node

To delete the HA pair and nodes from InCenter control, the sequence of commands would be the following:

admin@InCenter:/> delete HAPair my-hapair
Deleted HAPair my-hapair
admin@InCenter:/> delete StandaloneNode my-node1
Deleted StandaloneNode my-node1
admin@InCenter:/> delete StandaloneNode my-node2
Deleted StandaloneNode my-node2
admin@InCenter:/> commit

This will remove the HA pair from InCenter control but still leave it fully functioning as an external HA pair. However, the AutoSyncCfg property of the HighAvailability object in both firewall configurations will still be disabled. It is recommended to enable this property.

Deleting the HA Pair and Leaving Standalone Nodes

Instead of removing the HA pair and its component nodes, the requirement may be to keep the nodes in the pair under InCenter control as standalone nodes.

This is done with the following steps:

Delete the HAPair object:

admin@InCenter:/> delete HAPair my-hapair

The nodes are now standalone in InCenter but their management interface IP address is a shared address and must be changed before activating. If the management interface is if1, this is done with the following commands.

For NetWall nodes:

admin@InCenter:/> cc StandaloneNode my-node1
admin@InCenter:/my-node1> set IP4Address if1_ip
			Address=10.6.15.87
Updated IP4Address if1_ip 
admin@InCenter:/my-node1> cc
admin@InCenter:/> cc StandaloneNode my-node2
admin@InCenter:/my-node2> set IP4Address if1_ip
			Address=10.6.15.89
Updated IP4Address if1_ip
admin@InCenter:/my-node2> cc
admin@InCenter:/> activate
admin@InCenter:/> commit

For NetShield nodes:

admin@InCenter:/> cc StandaloneNode my-node1
admin@InCenter:/my-node1> set IPAddress if1_ip
			Address=10.6.15.87
Updated IPAddress if1_ip 
admin@InCenter:/my-node1> cc
admin@InCenter:/> cc StandaloneNode my-node2
admin@InCenter:/my-node2> set IPAddress if1_ip
			Address=10.6.15.89
Updated IPAddress if1_ip 
admin@InCenter:/my-node2> cc
admin@InCenter:/> activate
admin@InCenter:/> commit

This leaves two standalone nodes still under InCenter control.

	Important: Initial management IP must not be the shared IP
Avoid using the shared management IP as the initial standalone management IP for either node in an HA pair, or as setting the shared IP as the management IP when removing them from the HAPair object to become standalone nodes. This could result in both nodes using the same management IP, which can be a valid scenario if the deletion from InCenter is reverted at this stage. If this needs to be done then first assign some temporary management IP in step 2 above. Then change this to the shared IP later, after the activate and commit.

Important: Initial management IP must not be the shared IP

Avoid using the shared management IP as the initial standalone management IP for either node in an HA pair, or as setting the shared IP as the management IP when removing them from the HAPair object to become standalone nodes. This could result in both nodes using the same management IP, which can be a valid scenario if the deletion from InCenter is reverted at this stage.

If this needs to be done then first assign some temporary management IP in step 2 above. Then change this to the shared IP later, after the activate and commit.