VMware vRealize Operations V6



The VMware vRealize Operations (vROps) Management Suite provides comprehensive visibility and insights into the performance, capacity and health of your infrastructure. vRealize Operations Manager collects performance data from each object at every level of your virtual environment, from individual virtual machines and disk drives to entire clusters and data centres. It stores and analyses the data, and uses that analysis to provide real-time information about problems, or potential problems, anywhere in your virtual environment.

Figure 1‑1: vROps example

The KEMP Virtual LoadMaster (VLM) operates within the vROps architecture. vROps can instantiate a LoadMaster, monitor it and provide detailed statistics and information regarding its health within the vROps architecture.

With vROps, information can be gathered from the LoadMaster to form aggregated dashboard views combining the resource consumption data that is already natively available, along with statistics relevant to how each VM is performing in the context of the applications that they serve. The LoadMaster’s proximity to virtual application server instances, and its role as an intermediary connection point between clients and VMs, puts it in an ideal location to provide this data to vROps for dashboard and other information rendering.

1.1Document Purpose

The purpose of this document is to describe the various features and functionality that can be used within the vROps Manager relating to the KEMP LoadMaster. For further information on vROps in general, refer to the VMware documentation.

This document relates to vROps version 6 and above. Refer to the VMware vCenter Operations Version 5, Installation and Feature Description for steps relating to vROps version 5.

1.2Intended Audience

This document is intended to be read by anyone who is interested in finding out how to utilize the vROps Version 6 suite with the KEMP LoadMaster.

2Using vROps with the LoadMaster


To make the LoadMaster work with vROps, follow the steps below:

  1. Download the LoadMaster vROps installation (.pak) file from the KEMP website: www.kemptechnologies.com.
  2. Log in to the vRealize Operations Manager.

Figure 2‑1: Solutions

  1. Click the Administration icon (cog) in the top left section.
  2. Select Solutions.

Figure 2‑2: Add

  1. Click Add (plus icon).

Figure 2‑3: Browse

  1. Click Browse a solution.
  2. Browse to and select the LoadMaster vROps installation .pak file.

Figure 2‑4: Upload

  1. Click Upload.
  2. When the upload is finished, click Next.

  1. To continue with the installation, select the I accept the terms of this agreement check box.
  2. Click Next.
  1. Wait for the update to complete. The progress bar will disappear when the update is complete.

The update can take several minutes to complete.

  1. Click Finish.

2.2Add a LoadMaster Adapter Instance

After installing the LoadMaster vROps .pak file, an instance of the adapter needs to be created for every Virtual LoadMaster (VLM) to be monitored. To add an instance, follow the steps below in the vRealize Operations Manager:


  1. In the top left section, click Administration (cog icon).
  1. Select Solutions on the left.

Figure 2‑6: Add New Adapter Instance

  1. Select LoadMaster Adapter and click Configure (cogs icon).

Figure 2‑7: Add

  1. Click Add (green plus icon).

Figure 2‑8: Adapter Instance details

  1. Enter a recognizable Display name.
  2. Enter a Description.
  3. Expand the Advanced Settings section.
  4. Ensure the Collector drop-down list is set to Automatically select collector.
  5. In the Advanced Settings section there are two fields; Auto API Enable and Auto Discovery. These are both enabled by default.

In order for vROps to communicate with the LoadMaster, the RESTful API interface must be enabled on the LoadMaster. When the Auto API Enable option is set to true, the API interface will be enabled on the LoadMaster automatically when the instance is created.

If Auto Discovery is set to true, the Virtual Services and Real Servers are automatically added. If this is set to false, they will need to be manually added by following the steps in Section 2.5.

  1. Click Add New (green plus icon) in the Basic Settings sectionto input the LoadMaster credentials.

Figure 2‑9: Credential details

  1. Enter a name for the credentials.

The credentials can be reused.

  1. Enter the IP Address of the LoadMaster that you want to collect statistics for.
  2. Enter the Port used to communicate with the LoadMaster.
  3. Enter the Username and Password of a LoadMaster user.

The default LoadMaster username is bal. However, any valid LoadMaster user details can be entered here.

  1. Click OK.

Figure 2‑10: Adapter Instance Name

  1. Click Test Connection.
  2. Click OK.
  3. Click Save Settings.
  4. Click OK.
  5. Click Close.

2.3LoadMaster Dashboards

Three LoadMaster dashboard are automatically created when a LoadMaster instance is added:

  • LoadMaster Health Snapshot: This provides an overview of the health of the LoadMaster, Virtual Services and Real Servers
  • LoadMaster Resource View: This provides details about each of the LoadMaster resources
  • LoadMaster Resource Metric Graphs: This provides metrics on each of the LoadMaster resources, such as the number of connections per second.

Figure 2‑11: LoadMaster dashboards

These are available in the Dashboard List on the Home page of vROps Manager.

2.4Collection Interval

By default, the statistics get collected by vROps every five minutes.

The collection interval can be changed by following the steps below in the vROps Manager:

Figure 2‑12: Environment Overview

  1. Select the Administration (cog) icon in the top left section.
  1. Select Environment Overview on the left.

Figure 2‑13: Select the instance

  1. Expand Adapter Instances.
  2. Expand LoadMaster Adapter Instance.
  3. Select the relevant LoadMaster adapter instance.

Figure 2‑14: Edit Resource

  1. Select the relevant adapter instance on the right panel.
  2. Click the Edit Resource (pencil) icon.

Figure 2‑15: Collection Interval

  1. Change the value of the Collection Interval.

Statistics in the LoadMaster are gathered in real time. The details shown in vROps are a snapshot of the statistics at the moment it polls the LoadMaster.

  1. Click OK.

2.5Discovering Virtual Services and Real Servers

When adding a LoadMaster adapter instance, there is a setting called Auto Discovery which is set to true by default.

If Auto Discovery was set to true when the instance was added, there is no need to follow the steps in this section because the Virtual Services and Real Servers will be added automatically.

If Auto Discovery was set to false when the instance was added, follow the steps below to manually add the Virtual Services and Real Servers:

Figure 2‑16: Environment Overview

  1. Select Administration (cog icon) in the top left section.
  1. Select Environment Overview on the left section.

Figure 2‑17: Discover resources

  1. Click the Discover Objects (binoculars) icon.

Figure 2‑18: Resource Discovery details

  1. Select vRealize Operations Manager Collector-VROPS6 as the Collector.
  2. Select LoadMaster Adapter in the Adapter Kind drop-down list.
  3. Select the Adapter Instance name, for example the one added in Section 2.2.
  4. Select Discover in the Discovery Info drop-down list.
  5. Disable the Only New Resources option.

Selecting the Only New Resources check box means that it only checks for new Virtual Services and Real Servers. For example, if the resources were already discovered/added initially, and then a new Virtual Service or Real Server is added - you can run a discovery again to detect the new resource. If the Virtual Services and Real Servers have been discovered before, there is no need to detect all resources again. So, selecting the Only New Resources check box speeds up the discovery.

  1. Click OK.

Figure 2‑19: Discovery Results

  1. The discovery results will be displayed.

VIPs are Virtual Services. RSs are Real Servers.

To get more information, double-click the VIP or RS line. Further information will be displayed in the Resources section underneath.

  1. Select the Collect check box for whatever resources to collect statistics for.

When you select Collect, the Import check box also gets automatically ticked. Ensure that both of these check boxes are ticked.

  1. Click OK.

Figure 2‑20: Select the instance name

  1. Select the LoadMaster instance name on the left to display the Virtual Services and Real Servers for that instance.

2.6Health Status

In the LoadMaster Resource Relationships screen, different colours can be displayed in the Container Overview section. A percentage health rating is also shown. The health rating score is dynamic (either 25, 50, 75 or 100%). For example, if there is a constant connection rate and the rate deviates to an unusual level, an alert will be generated and the health score will be affected.

The different coloured icons are described below.

Figure 2‑21: Up

A green icon means that the resource is up and the health is good.

Figure 2‑22: Lower scores

Yellow and orange icons are also displayed for lower health scores.

Figure 2‑23: Discovering

A grey icon with a question mark means that the resource has not been detected yet. Wait for the collection interval to elapse and then refresh the page to see the new health status.

Figure 2‑24: Down

Red icons are displayed when a resource is down.

2.7View the Health Tree

Statistics can be displayed at the VLM, Virtual Service and Real Server level. To view the health tree, follow the steps below:

Figure 2‑25: Home

  1. Click the Home (house) icon in the top left.

Figure 2‑26: LoadMaster Health Snapshot

  1. Click Dashboard List and select LoadMaster Health Snapshot.

Figure 2‑27: Double-click the resource

  1. Double-click the relevant item.

Figure 2‑28: Environment > Map

  1. Select the Troubleshooting tab.
  2. Click All Metrics.

Figure 2‑29: Tree

The health tree will be displayed. The above screenshot shows four Virtual Services sitting underneath the VLM.

Figure 2‑30: Real Server

Double-click a Virtual Service to view its health tree.

2.8View Resource Metrics

LoadMaster-specific resource metrics exist for the LoadMaster, Virtual Services and Real Servers. There are no LoadMaster-specific resource metrics for SubVSs.

To view metrics on any of the resources, follow the steps below:

Figure 2‑31: Home

  1. Select Home (house icon), in the top left.

Figure 2‑32: LoadMaster Resource View

  1. Click Dashboard List and select LoadMaster Resource View.

Figure 2‑33: Resource Detail

  1. Select the relevant resource.
  2. Click Object Detail (graph icon).

Figure 2‑34: Troubleshooting

  1. Select the Troubleshooting tab.
  2. Select All Metrics.

Figure 2‑35: Metrics

  1. Expand LoadMaster metrics.
  2. Expand the resource metrics.

If the LoadMaster is running firmware version 7.1-16 or below, some metrics will not be available.

  1. Double-click any of the metrics to display the related graph.

You can zoom in on a specific part of the graph by dragging a box around the section to be magnified.

By default, the graphs show metrics for the last six hours.

2.9View Alerts

To view alerts, follow the steps below:

Figure 2‑36: Environment

  1. Click the Home (house icon) in the top-left section.
  1. Select Environment.
  2. Selectone of the LoadMaster filters, depending on what alerts you want to view.

Figure 2‑37: Select the relevant resource

The format of the resource names are as follows:

Virtual Service: <index>-<IPAddress>:<port>

Real Server:<index>-<IPAddress>:<port>


  1. Expand the list as needed and select the relevant resource.

Figure 2‑38: Alerts

  1. Select the Alerts tab. Double-click the alert to view more information.

Figure 2‑39: Alert Summary


Unless otherwise specified, the following documents can be found at http://www.kemptechnologies.com/documentation.

VMware vCenter Operations Version 5, Installation and Feature Description

Document History



Reason for Change



Nov 2014

Initial draft

First draft of document



Nov 2014

Updates made

New functionality added



Sep 2015

Updates to header and footer

LoadMaster reskin



Nov 2015

Minor changes

Enhancements made



Jan 2016

Minor changes




Jan 2017

Minor changes

Enhancements made



Was this article helpful?

0 out of 0 found this helpful