NSX provides two approaches to disable HA on standalone L2 VPN Edge appliances.

Consider that you have deployed two standalone L2 VPN Edge appliances called L2VPN-Client-1 and L2VPN-Client-2, and you have established HA between both these appliances. L2VPN-Client-1 is the active appliance, and L2VPN-Client-2 is the standby appliance.

In the first approach, you can do the following steps to disable HA:
  1. Delete or power off the standby appliance (L2-VPN-Client-2) directly.
  2. Log in to the console of the active appliance (L2-VPN-Client-1), and run the ha disable command.
The advantage of this approach is that the HA failover time is minimum. However, the limitations of this approach are as follows:
  • You have to power off the standby L2 VPN appliance manually.
  • This approach might lead to a dual active state situation. For example, you might forget to power off the standby appliance and start up the standby appliance. This might cause both L2 VPN appliances to become active.
In the second approach, you can do the following steps to disable HA:
  1. Delete or power off any one of the L2 VPN appliances, either active or standby appliance.
  2. Log in to the console of the other appliance, and run the ha disable command to disable the HA feature on this appliance.
In the second approach too, the HA failover time is minimum. However, the limitations of the second approach are as follows:
  • You have to power off the L2 VPN appliance manually.
  • This approach might also lead to a dual active state situation. For example, you might forget to power off the appliance and start up the same appliance. This might cause both L2 VPN appliances to become active.
  • Service is disrupted when you delete the active appliance because the HA failover might not happen immediately to make the standby appliance active.