You can migrate the existing load balancer node using the VMware Pulse IoT Center private CA certificate or where the CA has changed.
- Install the new load balancers as mentioned in High Availability for Load Balancer Node and set the virtual IP from the VMware Pulse IoT Center Administration Console.
- Generate a new SSL certificate that includes the FQDN of the old load balancer with the FQDN of the two new load balancers.
- Push the root CA certificate of the newly generated SSLcertificates using campaigns to all the VMware Pulse IoT Center gateways. Add a root CA certificate to the VMware Pulse IoTC Agent certificate trust store through campaigns. See Creating a Campaign Package to Replace the New SSL Certificate.
- Verify that the campaign has succeeded in all the gateways.
Note: This is a mandatory step. If you do not perform this step, you might have to re-enroll the device again.
- Load the newly generated certificate to both the newly deployed load balancers.
- Add the upgraded Pulse nodes from one of the VMware Pulse IoT Center Administration consoles of the new load balancer.
- Using the virtual IP, test from the browser if the VMware Pulse IoT Center Administration console can be accessed.
- Change the DNS record for the FQDN of the old load balancer to point to the floating IP of the new load balancer.
Note: If there are local DNS caches, the changes might take time to propagate across the network.
- Test from the browser if the VMware Pulse IoT Center Administration Console can be accessed through the FQDN.
From the dashboard, ensure that the current VMware Pulse IoT Center UI is of the latest load balancer by doing a IP version check. The test can also be done from a gateway if the FQDN resolves to the virtual IP.