You can migrate the existing load balancer node by using an SSL certificate signed by a known Certificate Authority.
- Install the new VMware Pulse IoT Center load balancers as mentioned in the High Availability for Load Balancer Node and set the virtual IP from the Pulse IoT Administration Console.
- Generate a new SSL certificate signed by the same CA as in the old balancer that includes FQDN of the old load balancer with the FQDN of the two new load balancers. If the same CA authority is no longer available to sign the SSL certificates, move to the next step.
- 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.
- Test from the browser using the virtual IP if the VMware Pulse IoT Center Administration console can be accessed. If successful, proceed to the next step.
- 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 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 an IP version check. The test can also be done from a gateway if the FQDN resolves to the virtual IP.You have successfully migrated the existing load balancer node to a new one. The old load balancer can be decommissioned when all the devices have migrated and there are no more active connections through that load balancer.