When you activate the VMware Aria Operations for Logs integrated load balancer (ILB) on a VMware Aria Operations for Logs cluster, you must configure one or more virtual IP addresses.
The Integrated Load Balancer supports one or more virtual IP addresses (vIPs). Each vIP balances incoming ingestion and query traffic among available VMware Aria Operations for Logs nodes. It is a best practice to connect all VMware Aria Operations for Logs clients through a vIP and not directly to a node.
To simplify future changes and upgrades, you can have clients point to an FQDN that resolves to the ILB IP address, instead of pointing directly to the ILB IP address. VMware vSphere, VMware Aria Operations integrations, and alert messages use the FQDN if provided. Otherwise, they use the ILB IP address. VMware Aria Operations for Logs can resolve the FQDN to the given IP address, which means that the FQDN value you provide should match what is defined in DNS.
Prerequisites
- Verify that all VMware Aria Operations for Logs nodes and the specified Integrated Load Balancer IP address are on the same network.
- If you are using VMware Aria Operations for Logs with NSX, verify that the Enable IP Discovery option is deactivated on the NSX logical switch.
- The VMware Aria Operations for Logs primary and worker nodes must have the same certificates. Otherwise, the VMware Aria Operations for Logs Agents configured to connect through SSL reject the connection. When uploading a CA-signed certificate to VMware Aria Operations for Logs primary and worker nodes, set the Common Name to the ILB FQDN (or IP address) during the certificate generation request. See Generate a Certificate Signing Request.
- You must synchronize the time on the VMware Aria Operations for Logs virtual appliance with an NTP server. See Synchronize the Time on the Log Insight Virtual Appliance.