vRealize Operations Manager supports Internet Protocol version 6 (IPv6), the network addressing convention that will eventually replace IPv4. Use of IPv6 with vRealize Operations Manager requires that certain limitations be observed.

Using IPv6

  • All vRealize Operations Manager cluster nodes, including remote collectors, must have IPv6 addresses. Do not mix IPv6 and IPv4.

  • All vRealize Operations Manager cluster nodes, including remote collectors, must be vApp or Linux based. vRealize Operations Manager for Windows does not support IPv6.

  • 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. Master nodes and replica nodes still require fixed addresses, which is true for IPv4 as well.

  • Your DNS server must be configured to support IPv6.

  • When adding nodes to the cluster, remember to enter the IPv6 address of the master 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 that, even when vRealize Operations Manager is using IPv6, vCenter Server may still have an IPv4 address. In that case, vRealize Operations Manager does not need the square brackets.

  • You cannot register an Endpoint Operations Management agent in an environment that supports both IPv4 and IPv6. In the event that you attempt to do so, the following error appears:

    Connection failed. Server may be down (or wrong IP/port were used). Waiting for 10 seconds before retrying.