If a standalone L2 VPN Client has failed or crashed, you can replace this failed appliance by deploying a new standalone L2 VPN client, and configure this newly deployed appliance from the NSX Edge console.
Consider that you have already deployed two standalone L2 VPN client appliances called L2VPN-Client-01 and L2VPN-Client-02, and enabled HA on both the appliances. The L2VPN-Client-01 node has failed or crashed. To replace this failed node, you will deploy a new standalone L2 VPN client appliance called L2VPN-Client-Replace, and specify the same VPN configuration as the active node.
Procedure
- Log in to the console of the active node (L2VPN-Client-02), and check its HA index.
- Run the ha get-localnode command on the L2VPN-Client-02 node to retrieve the vNIC MAC addresses, and copy the CLI output of this command.
- Deploy a new standalone L2 VPN client appliance and name it L2VPN-Client-Replace. During deployment, make sure that you specify the following details:
- Enable the HA feature.
- Type the correct HA IP address for both node 0 and node 1. The IP addresses must be in the /30 IP subnet.
- Select the HA index value.
- If the node with HA index 1 has failed, then select 0 for the HA index of the L2VPN-Client-Replace appliance.
- If the node with HA index 0 has failed, then select 1 for the HA index of the L2VPN-Client-Replace appliance.
- Log in to the console of the new L2VPN-Client-Replace appliance, and do these steps:
- Run the ha set-peernode command and set the MAC address of the peer node (L2VPN-Client-02).
- Run the ha get-localnode command, and copy the CLI output of this command.
- Log in to the console of the active node (L2VPN-Client-02), and run the ha set-peernode command to set the vNIC MAC addresses of the newly deployed appliance (L2VPN-Client-Replace).
- Finally, run the commit command on both L2VPN-Client-02 and L2VPN-Client-Replace appliances.