...
The following shows an example for three EC2 instances with a Linux OS.
The For the private IP to public IP mapping:
...
The configuration to add to LM-X would be:
HAL_SERVER1 = 6200@172.31.5.33
HAL_SERVER2 = 6200@172.31.6.253
HAL_SERVER3 = 6200@172.31.10.194
The setting in the /etc/hosts file would be:
172.31.5.33 34.253.25.122
172.31.6.253 34.245.22.38
172.31.10.194 46.137.69.84
Please note: It's better to use an Elastic IP address to reserve your public IP address.
More information is here https://repost.aws/knowledge-center/intro-elastic-ip-addresses
After doing these steps, start or restart the LMX server. When setting up HAL from the LM-X License Server Client, the Server State might show "Down". This is because the private IP isn't reachable from outside the network.
Always check the logs after setting things up. This will help you see if HAL is set up right and if a connection was made.
Common mistakes in the setup:
- The LMX server port can't be reached.
- Public IP was changed (and didn't use Elastic) but host map was not updated.
- Using the public IP instead of the private one in the HAL configuration.
For more information about AWS addressing, see the official AWS website at at https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html. For more information about LM-X's HAL feature, see High Availability Licensing.