vRealize Operations Manager supports both, Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6). You can use IPv4 or IPv6 or both. If the environment has a dual-stack support with both IPv4 and IPv6 protocols, all nodes in the cluster must follow the same protocol. When using IPv6, the Prefer IPv6 flag must be enabled during the OVF deployment for each node. If you set the Prefer IPv6 flag, vRealize Operations Manager uses IPv6 for it internal communications. It does not affect how vRealize Operations Manager handles its external communications. The use of IPv6 with vRealize Operations Manager requires that certain limitations be observed.

Considerations While Using IPv6

  • All vRealize Operations Manager cluster nodes, including remote collectors, must have IPv6 addresses. Do not mix IPv6 and IPv4.
  • Use global IPv6 addresses only. Link-local addresses are not supported.
  • If any nodes use DHCP, your DHCP server must be configured to support IPv6.
  • DHCP is only supported on data nodes and remote collectors. Primary nodes and replica nodes still require fixed addresses, which are true for IPv4 as well.
  • Your DNS server must be configured to support IPv6.
  • When adding nodes to the cluster, enter the IPv6 address of the primary node.
  • When registering a VMware vCenter® instance within vRealize Operations Manager, place square brackets around the IPv6 address of your VMware vCenter Server® system if vCenter is also using IPv6.

    For example: [2015:0db8:85a3:0042:1000:8a2e:0360:7334]

    Note: When vRealize Operations Manager is using IPv6, vCenter Server might still have an IPv4 address. In that case, vRealize Operations Manager does not need the square brackets.