vRealize Operations (Formerly vCOPS)




NOTE: Operations is an add-on to existing installations of vSphere and vCenter and does not include vSphere or vCenter.






vRealize Operations for Horizon

vRealize Operations for Horizon is sold as an add-on component for Horizon. Using the same concurrent-connection license model as Horizon, packages are available in increments of 10 and 100.

To deploy vRealize Operations Manager in a vCenter Server environment with an Essentials Plus or Standard cluster of three ESX hosts:

  1. Remove one of the ESX hosts from the cluster so that it resides directly under the parent datacenter.
  2. On that ESX host, deploy the vRealize Operations Manager vApp, specifying static IP addresses.
  3. Power on the vApp before moving the host back into the cluser to ensure IP settings are picked up.
  4. License the solution in vCenter.
  5. Move the ESX host with vRealize Operations back into the cluster.

Reference:  http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2013695


Technical FAQ: 

Question: I’m running 5.0. Do I need to upgrade to 5.8 in order to get to 6.0?

Answer: No in-place migration or upgrade. Upgrade = Side-by-Side. An in place upgrade is not supported from 5.x to 6.x. A data migration is supported from 5.8.1 or higher. If you are running, 5.8 or below, please perform an in place upgrade to 5.8.1 or higher environment first, then perform the data migration to the 6.0 environment.


Question: How should I size my vROps appliance?

Answer: See the sizing guide and calculator here.

Question: Is there a limit to the number of nodes you can add?

Answer: The current version supports up to 8 nodes in a cluster. This number does not include the number of remote collectors that can be connected.

Question: Can you differentiate the functions of master, replica, date and collector nodes ?

Answer: MASTER NODE – As the name suggests is the MASTER of the cluster. This is essentially the first node of the cluster i.e. if you plan to build one. I will talk about various deployment models as we move forward in this series. This node has the Global xDB (Postgres), the xDB as well as the FSDB. In essence, this node is where all the customization of your entire vROps solution lies. Things such as user preferences, policies and the entire brain of the solution.

REPLICA NODE – Doing justice to it’s name, the Replica Node also called ‘Master Replica’ is the exact copy of the master node. This is to give resiliency to the solution. In vROps GUI this is identified as enabling High Availability. This node is not doing any work, but just watching the master node at all times and syncing with the node to ensure that it can take its place once the Master Fails.

DATA NODE – Every node which collects data in the vROps cluster is a Data Node. The function of this node is to ensure that it collects the data from you environment based on the adapters which are assigned to this node. This node basically allows you to keep scaling your cluster by adding new nodes.

REMOTE COLLECTOR – The remote collector is not a new concept in vROps, but this is now the only solution to get data from an environment which is not within a LAN. In other words, you have to install a REMOTE COLLECTOR if you need to fetch the data from a remote location into a centralized vROps cluster/node. Good news is that it is the same appliance which you have to install, and just chose collector during the install which makes it a simple install. Collector does not have the CONTROLLER, ANALYTICS or the PERSISTENCE layer since it is not required. It sends the data out to the centralized controller and then the data is treated using the Analytics engine.

Question:  Is the maximum number of objects per node or cluster?

Answer: Check the sizing spread sheet in the VMware Ops 6.0 sizing KB, it depends on The number of Objects and Metrics and size of the nodes.

Question: Do cluster nodes need to be at the same physical datacenter?

Answer: In the current 6.0 release, all master, replica, and data nodes are required to be in the same physical datacenter. Remote Collectors can be installed in remote data centers.

Question: What ports do the remote collector communicate on to the master node?

Answer:  The remote collector communicates to the cluster nodes using tcp/10000, tcp/6061, and tcp/443, and the cluster nodes communicate to the remote collector using tcp/443. All the cluster nodes and remote collectors need access to the same ntp server over udp/123. Proper DNS forward and reverse names are required, so you’ll need udp/53 and tcp/53. More.

Question: Can vSAN data be collected and monitored

Answer: Details performance metrics for vSAN are not currently being collected. vSAN support is addressed in vROPs 6.1.


FAQ Reference:  Public presentation and recording of this webcast.