The F5 BIG-IP Local Traffic Manager load balancer configuration is similar to the HAProxy configuration.

The LTM uses SSL pass-through in the same manner as with the HAProxy configuration. The LTM configuration has been tested in both one-arm and multi-arm topologies.

Prerequisites

The following are the prerequisites for a functional LTM configuration in front of a vRealize Operations Manager cluster:

  • This document assumes that an LTM device is already deployed in the environment and is configured with network connectivity to the deployed environment where the load balancer instance would be used and run from.

  • The LTM can be either physical or virtual and can be deployed in one-arm or multi-arm topologies

  • The Local Traffic Module (LTM) must be configured and licensed as Nominal, Minimum, or Dedicated. You can configure LTM on System > Resource Provisioning page.

  • A vRealize Operations Manager cluster has been deployed in the environment and is fully functional and all nodes in the cluster are accepting UI traffic. This cluster might have high availability enabled but it is not a requirement.

  • An additional VIP/Virtual Server IP address for vRealize Operations Manager analytics.

  • An additional VIP/Virtual Server IP address for EPOps in case you are configuring separate load balancers for analytics and EPOps.