Home > Blogs > VMware TAM Blog > Tag Archives: vROps

Tag Archives: vROps

vRealize Operations Manager—Avoiding an Out-of-Space Situation

Petr_McAllisterby Petr McAllister

There is no doubt that vRealize Operations Manager (vROps) is a very powerful tool that helps you with monitoring, troubleshooting, and planning your datacenter workloads and components. You can find a lot of blog posts, webcasts, presentations, and recordings on how the product can be used because it benefits both worlds—both technical folks and the management layers of the organization. vROps provides high-level dashboards, details on specific objects, the history, and trends.

In my experience, the customers who get the most out of a product are the ones who have vROps dashboards displayed on big TV screens inside their IT staff areas where they can view the current health status of their environment. Then as soon as the dashboard turns yellow or red, they can jump in to start a troubleshooting analysis and investigate the reasons for the “not-so-green” dashboard on their workstations.

Continue reading

vRealize Operations Manager – Architecture

Carl OlafsonBy Carl Olafson

vRealize Operations Manager v6.x is a completely redesigned operations management tool. From an architectural standpoint, vRealize Operations Manager is vastly superior to vCenter Operations Manager, which was a two-VM vApp, and could only scale up. As a starting point, vRealize Operations Manager v6.x uses Gemfire cluster technology, and as such can also scale-out for additional capacity. In addition, the Advanced and Enterprise editions allow vRealize Operations Manager High Availability to be enabled (not to be confused with vSphere HA) for fault tolerance. The remainder of this article will be broken down into some key concepts and architecture terminologies.

Cluster Technology and Scale-Up/Scale-Out Capacity

As mentioned, Gemfire is a cluster technology and for vRealize Operations Manager v6.0/v6.1, there is a node cluster limit of 8 in v6.0.x, and 16 in v6.1.x. This gives vRealize Operations Manager scale-out capacity of 8–16 nodes. In addition, each node/VM has scale-up capacity of 4 vCPUs/16 GB vRAM (small) and 16 vCPUs/48 GB vRAM (large). From a best practices standpoint this brings up a couple of items that must be adhered to:

  1. For a multi-node cluster, all nodes must be the same scale-up size (small, medium or large). Gemfire assumes all nodes are equal and distributes load across the cluster equally. Performance problems will occur if you have different sized nodes in your vRealize Operations Manager cluster. And you can adjust node size after the initial implementation as your environment grows.
  2. For a multi-node cluster, all nodes must have Layer 2 (L2) adjacency. Gemfire cluster technology is latency sensitive. From a VMware supportability standpoint, placing nodes in a cluster across a WAN or Metro Cluster is not supported.
  3. Proper sizing of the cluster and utilization of Remote Collectors is key to a successful implementation. The next article will cover this in detail.

Node Types

For vRealize Operations Manager there are two primary types of nodes: cluster nodes and remote collectors.

Cluster Nodes

The cluster nodes participate in the vRealize Operations Manager cluster. There are three distinct sub-types.

  • Master node, which is the first node assigned to the cluster. The master node is also responsible for managing all the other nodes in the cluster.
  • Data nodes, which would make up the remaining nodes of a non-HA cluster.
  • Replica node, which is a backup to the master node should the master node fail. This assumes vRealize Operations Manager HA is enabled.

Examples of vRealize Operations Manager cluster architectures.

COlafson Cluster 1

Remote Collectors

Remote collectors do not participate in the vRealize Operations Manager cluster analytic process. However, the remote collector is an important node when you have a multi-site implementation or are using specific management packs that cannot be assigned to a cluster node. The remote collector only contains the Admin UI and the REST API component that allows it to talk to the vRealize Operations Manager cluster.

Although your cluster is limited to 8–16 nodes (based on version) and determines your overall object collection capacity, you can have an additional 30–50 remote collectors: 30 in version 6.0, and 50 in version 6.1. The remote collector’s object count applies against the cluster, but does not diminish the size or number of cluster nodes. With the release of vRealize Operations Manager v6.1, remote collectors can also be clustered, and an emerging best practice is to move all management packs/adapters to clustered remote collectors. This helps reduce the load on the analytics cluster, and combined with remote collector clustering provides a higher level of fault tolerance and efficiency.

The remote collector is an important design consideration if you are using management packs (like MPSD) or have vCenters across a WAN/Metro Cluster. If your vRealize Operations Manager cluster is going to collect from multiple vCenters over a WAN or utilize management packs, consult a qualified SME on your design for cluster nodes, remote collectors and level of fault tolerance. VMware Professional Services (PSO) provides vRealize Operations services ranging from Architecture to Operational Transformation.

COlafson Multinode Cluster

Load Balancer

A load balancer is another important design consideration for a multi-node cluster. vRealize Operations Manager v6.x does not currently come with a load balancer, but can utilize any third-party stateful load balancer. Utilizing a load balancer ensures the cluster is properly balanced for performance of UI traffic. It also simplifies access for users. Instead of accessing each node individually the user only needs one URL to access the entire cluster and not be concerned with what node is available.

COlafson Multinode Cluster Load Balancer

 


Carl Olafson is a VMware Technical Account Manager based out of California.

vROPS 6.1 and the New End Point Operations Monitoring Feature

Vegard-bw2By Vegard Sagbakken

In the 6.1 release of vRealize Operations, VMware merged the Hyperic Monitoring solutions into vROPS. This makes it a lot easier to get a full holistic view through the vROPS management interface all the way down to services, processes and the application layer.

To use the OS Monitoring feature described here you need vRealize Operations Advanced licensing.

Currently we support the following OSs with this End Point Operations agent:

Operating System

Processor Architecture

JVM

Scaling Considerations

Red Hat Enterprise Linux (RHEL) 5.x, 6.x, 7.x x86_64, x86_32 Oracle Java SE7
CentOS 5.x, 6.x, 7.x x86_64, x86_32 Oracle Java SE7
SUSE Enterprise Linux (SLES) 11.x, 12.x x86_64 Oracle Java SE7
Windows 2003 Server R2 x86_64, x64_32 Oracle Java SE7
Windows 2008 Server, 2008 Server R2 x86_64, x64_32 Oracle Java SE7
Windows 2012 Server, 2012 Server R2 x86_64, x64_32 Oracle Java SE7
Solaris 10, or higher x86_64, x86_32 Oracle Java SE7
HP-UX 11.11 or higher PA-RISC Oracle Java SE7
AIX 6.1, 7.1 Power PC IBM Java SE7
Ubuntu 10.11 x86_64, x86_32 Oracle Java SE7 For development environments only.

Here is an excellent example of what you can do with this dashboard; it shows the status of a Windows vCenter Server and the status of all services running. This gives your operations team a great way of making sure all vCenter services are up and running so they can take action on any anomalies early before they escalate into bigger issues. This example was created by Peter Tymbel, Sr.Consultant, PSO, VMware.

Some of my colleagues at VMware have already documented the installation and use of this new functionality within vROPS. Please see the following blogs to get started with this new functionality, and don´t forget to use the official documentation as well.

vROPS 6.1 – EPO Agents Installation Guide

http://www.vmignite.com/2015/10/vrops-6-1-epo-agents-installation-guide/

vRealize Operations 6.1 End Point with existing JRE

http://virtual-red-dot.info/vrealize-operations-6-1-end-point-with-existing-jre/

vROPS 6.1 – How to Monitor any Windows Service

http://www.vmignite.com/2015/10/vrops-6-1-how-to-monitor-any-windows-service/

vRealize Operations 6.1 End Point: how to add metrics

http://virtual-red-dot.info/vrealize-operations-6-1-end-point-how-to-add-metrics/

If you would like to dig further into this I suggest you head over to the VMworld Hands-On Labs and launch, “HOL-SDC-1601 Cloud Management with vRealize Operations Insight.” Here you can play around in a pre-installed environment and look at how the End Point Operations agents are working.


Vegard Sagbakken is a Senior Technical Account Manager working out of Oslo, Norway. He currently holds multiple VMware certifications, VCP 2-6 and VCAP-DCD 4-5