Steps to migrate LoadMasters to a new VMware environment
Information
Summary: |
This article will outline how to properly migrate the LoadMaster as it currently is |
Environment: |
Product: LoadMaster Version: Any Platform: VMware Application: Any |
Question/Problem Description: |
We have LoadMasters deployed on VMware and I want to know what would be the proper way of migrating them to a new VMware environment. |
Steps to Reproduce: | |
Error Message: | |
Defect Number: | |
Enhancement Number: | |
Cause: | |
Resolution: |
A backup of the configuration and certificates should first be taken to ensure the configuration is preserved. Instructions on backing up these items can be found here: https://support.kemptechnologies.com/hc/en-us/articles/360003231971-How-to-create-and-restore-a-LoadMaster-Configuration-or-Certificate-Backup Once the backup is taken, take care to ensure the MAC address of each interface is set to Static. The reason for this is that the license is tied to the Serial Number, which depends on the MAC address. If the MAC address changes during the migration, the Serial Number will change and the license of the unit will revert to a Trial license. While this is possible to remedy by reaching out to Support, this measure can prevent the need for the migration in the first place. If applicable, the new environment should be confirmed as having the proper HA criteria in place as outlined here: https://support.kemptechnologies.com/hc/en-us/articles/360039126271-HA-Requirements-and-Recommendations. HA is noted by two boxes in the upper-right corner of the screen. Ideally, these will both be green, but they could also be Red with a yellow "X", Gray, or Blue. For full information on these boxes, please click here: https://support.kemptechnologies.com/hc/en-us/articles/203125199-High-Availability-HA-#MadCap_TOC_17_3. Once the environment has been confirmed, the units can be migrated at any time. We recommend the migration takes place during a period of downtime or maintenance to ensure impact is minimized. |
Workaround: | |
Notes: |