The following are the prerequisites for a functional GTM configuration managing a vRealize Operations Manager CA enabled cluster

  • GTM appliances have to be more than 1 and hosted in more than 1 independent datacenter

  • GTM appliances can be deployed in any datacenter globally as long as they are in the same cluster

  • LTM appliances have to be in the same datacenter as the respective Fault Domain which they serve

  • GTM and LTM appliances have to be paired and trust must be established between them. This is required so the GTM appliances can retrieve the health-check status from the LTM appliances by utilizing the big3d agent.

  • GTM and LTM solutions can be either virtual machines or physical systems

  • GTM and LTM solutions can be on the same systems or deployed separately

  • This document assumes that the LTM and GTM devices are already deployed in the environment and network connectivity is configured. Generic configuration of LTM and GTM devices is not covered in this document, please review the F5’s official documentation on how to configure Prober Pools, DNS Listeners and Zones, and how to pair the devices and group them into Datacenters

  • vRealize Operations must be deployed and the Continuous Availability feature needs to be enabled

  • Configure static DNS records for all vRealize Operations nodes and Fault Domains

Example:

Name

Type

ADDRESS

vrops-node1.dc1.example.com

A

IP

vrops-node2.dc1.example.com

A

IP

vrops-node3.dc1.example.com

A

IP

vrops-node4.dc1.example.com

A

IP

vrops-node5.dc2.example.com

A

IP

vrops-node6.dc2.example.com

A

IP

vrops-node7.dc2.example.com

A

IP

vrops-node8.dc2.example.com

A

IP

vrops-fd1.dc1.example.com

A

LTM VIP

vrops-fd2.dc2.example.com

A

LTM VIP

vrops.example.com

Wide-IP/A

To be configured later in this chapter

  • Issue and sign an SSL certificate containing all related DNS records