6.3

n
If you deploy analytics cluster nodes in a highly consolidated vSphere cluster, you might need resource
reservations for optimal performance.
Determine whether the virtual to physical CPU ratio is aecting performance by reviewing CPU ready
time and co-stop.
n
Deploy analytics cluster nodes on the same type of storage tier.
n
To continue to meet analytics cluster node size and performance requirements, apply storage DRS anti-
anity rules so that nodes are on separate datastores.
n
To prevent unintentional migration of nodes, set storage DRS to manual.
n
To ensure balanced performance from analytics cluster nodes, use ESXi hosts with the same processor
frequencies. Mixed frequencies and physical core counts might aect analytics cluster performance.
n
To avoid a performance decrease, vRealize Operations Manager analytics cluster nodes need
guaranteed resources when running at scale. The vRealize Operations Manager Knowledge Base
includes sizing spreadsheets that calculate resources based on the number of objects and metrics that
you expect to monitor, use of HA, and so on. When sizing, it is beer to over-allocate than under-
allocate resources.
See Knowledge Base article 2093783.
n
Because nodes might change roles, avoid machine names such as Master, Data, Replica, and so on.
Examples of changed roles might include making a data node into a replica for HA, or having a replica
take over the master node role.
n
The NUMA placement is removed in the vRealize Operations Manager 6.3 and later. Procedures related
to NUMA seings from the OVA le follow:
Table 1‑2. NUMA Setting
Action Description
Set the vRealize Operations Manager cluster status to
oine
1 Shut down the vRealize Operations Manager cluster.
2 Right-click the cluster and click Edit  >
Options > Advanced General.
3 Click  Parameters. In the vSphere
Client, repeat these steps for each VM.
Remove the NUMA seing 1 From the Conguration Parameters, remove the
seing numa.vcpu.preferHT and click OK.
2 Click OK.
3 Repeat these steps for all the VMs in the vRealize
Operations cluster.
4 Power on the cluster.
N To ensure the availability of adequate resources and continued product performance, monitor
vRealize Operations performance by checking its CPU usage, CPU ready and CPU contention time.
Using IPv6 with vRealize Operations Manager
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
n
All vRealize Operations Manager cluster nodes, including remote collectors, must have IPv6 addresses.
Do not mix IPv6 and IPv4.
vRealize Operations Manager vApp Deployment and Configuration Guide
14 VMware, Inc.