VMware vRealize Operations Manager 6.0.1

VMware vRealize Operations Manager 6.0.1 Release Notes

vRealize Operations Manager 6.0.1 | 26 FEB 2015 | Build 2523166

vRealize Operations Manager Appliance 6.0.1 | 26 FEB 2015 | Build 2523163

vRealize Operations Manager 6.0.1 PAK Upgrade | 26 FEB 2015 | Build 2523167

Last Document Update: 14 OCT 2015

Check frequently for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

vRealize Operations Manager 6.0.1 is the first update to the vRealize Operations Manager 6.0 release. Updates cover all major areas of the product including installation, migration, configuration, licensing, alerting, dashboards, reports, and policies. To take advantage of the following significant enhancements, upgrade to version 6.0.1.

  • Hot fix 2
    A hot fix for vRealize Operations Manager 6.0.1 addresses the following issues:
    • Combined metric graphs do not show a resource name.
    • If an Object List widget is a providing widget and is collapsed and configured for Auto Select First Row, it does not interact with receiving widgets.
    • Datastore clusters that exist in a folder are not visible in the vRealize Operations Manager inventory.
    • A Health Chart widget that is configured to automatically refresh Health status charts in ascending or descending order, does not consistently reorder charts correctly.
    Hot fix 2 also covers the issues addressed by hot fix 1. To install hot fix 2, see KB 2116366
  • Hot fix 1
    A hot fix issued April 9, 2015, addresses the following issues:
    • VIN adapters do not collect data properly. Data appears as question marks in the UI.
    • Cluster and Slice Administration service times out quickly on nodes with long latency such as remote collectors. This typically occurs during a cluster upgrade, when there are long delays in communication between cluster nodes.
    • Cluster Management page displays no adapter instances.
    • HTTP Post adapter fails to implement token based authentication.
    • Health chart widget display is different in vRealize Operations Manager 6.0 than in vCenter Operations Manager 5.8. Self and child objects are transposed.
    • In a vRealize Operations Manager deployment with more than 50 dashboards, dashboards beyond the first 50 cannot be shared.
    To install the hot fix, see KB 2110330
  • Improved scaling numbers
    The number of objects that a single large node supports has been increased to 12,000. Also, in multi-node configurations, a four large-node configuration can manage up to 40,000 objects and an eight large-node configuration can manage up to 75,000 objects. For details on scaling numbers and a link to a Sizing Guideline Worksheet, see KB 2093783.
  • vSphere v6.0 interoperability support
    With this release, vSphere v6.0 can function both as a platform for vRealize Operations Manager installation, and as an environment to which vRealize Operations Manager can connect for operational assurance.
  • User interface improvements
    • Corrections in the Views and Reports content for vSphere Hosts and Clusters.
    • Addition of Hierarchical View in the Topology widget.
    • Enhancement to the Geo widget displays objects on a world map.
  • Licensing improvements
    New functionality provides a way to use the REST API to add a license key.
  • Metrics switched to Collection OFF to improve performance
    Extraneous metrics are switched to Collection OFF in the default Policy. An option to enable Collection is available. However, maintaining metrics in the OFF state saves disk space, improves CPU performance, and has no negative impact on the vRealize Operations Manager functionality to collect and analyze data. For a list of metrics with Collection switched to OFF, see KB 2109869.
  • Alert Definition Updates
    • Improved alert definitions for vSphere clusters, hosts, and virtual machines, to better detect CPU and memory problems.
    • Improved alert definitions for hosts and virtual machines in the vSphere 5.5 Hardening Guide, to identify and report more non-compliance issues.
    • Additional alert definitions to detect duplicate object names in vCenter and vSphere Storage Management Service errors. Note: To identify duplicate object names in the vCenter Server system, the name-based identification feature must be enabled for the vSphere adapter.

Top of Page

Before You Begin

Review this section before you begin installing and configuring vRealize Operations Manager.


This vRealize Operations Manager release is compatible with the following VMware products:

  • VMware vCenter Server 4.0 Update 2 and later, managing hosts running ESX/ESXi 4.0 and later
  • vCenter Infrastructure Navigator 2.0
  • vRealize Configuration Manager 5.6 and 5.7.x
  • vRealize Operations Manager for View 1.5
  • vCenter Hyperic 5.8.2 or later

Browser Support

This vRealize Operations Manager release supports the following Web browsers:

  • Google Chrome: Current and most earlier versions
  • Mozilla Firefox: Current and most earlier versions
  • Safari: Current version
  • Internet Explorer for Windows 10 and 11
  • Note: Slower performance is observed on Internet Explorer 10 or 11.

The minimum supported resolution is 1024 x 768.

Deployment Requirements

You can deploy vRealize Operations Manager using the following installation formats:

  • VMware virtual appliance
  • RHEL and Windows installation packages

Virtual Appliance Deployment

Use a VMware vSphere Client to connect to a VMware vCenter Server, and deploy the vRealize Operations Manager virtual appliance through the vCenter Server. The vRealize Operations Manager virtual appliance must be deployed on an ESX/ESXi host version 4.0 or later that is managed by VMware vCenter Server 4.0 Update 2 or later.

Linux and Windows Requirements

You can install and upgrade the standalone version of vRealize Operations Manager on the following operating systems:

Licensing Keys

vRealize Operations Manager version 6.0 allows customers to install multiple Advanced and Enterprise editions in the same vRealize Operations Manager deployment. This enhancement lets customers deploy single choice and suite licenses together.

License counting for individual license keys is handled through licensing groups. You can mix editions or licensing models in one of the following ways:

  • Deploy vCloud Suite Standard, vSphere with Operations Management, and vRealize Operations Standard together in one deployment.
  • Deploy vCloud Suite Advanced or Enterprise, vSphere with Operations Management Advanced, vRealize Operations Insight, and vRealize Operations Advanced or Enterprise in one deployment.

Note: You cannot deploy a Standard edition license with either an Advanced or Enterprise license in the same deployment.

Sizing and Scaling

The CPU, memory, and disk requirements that will meet the needs of a particular environment depend on the number and type of objects in your environment and data collected, which includes the number and type of adapters installed, the presence of HA, the duration of data retention, and the quantity of specific data points of interest. VMware updates the following Knowledge Base article with the most current information about sizing and scaling.

KB 2093783

The Knowledge Base article includes overall maximums and spreadsheet calculators that provide a recommendation based on the number of objects and metrics you expect to monitor.

Top of Page

Upgrade From the Previous Version

Note: If you have customized the content that vRealize Operations Manager provides such as alerts, symptoms, recommendations, and policies, and you want to install content updates, a best practice is to clone the content before performing the upgrade. In this way, you can select the option to reset out-of-the-box content when you install the software update, and the update will provide new content without overwriting customized content.

To upgrade from vRealize Operations Manager version 6.0 to version 6.0.1 follow these steps.

  1. Download the PAK file.
    • For an OS upgrade, the file is: vRealize_Operations_Manager-VA-OS-xxx.pak
    • For vApp clusters, the file is: vRealize_Operations_Manager-VA-xxx.pak
    • For Linux clusters, the file is: vRealize_Operations_Manager-RHEL-xxx.pak
    • For Windows clusters, the file is: vRealize_Operations_Manager-WIN-xxx.pak
    • For heterogeneous clusters that have VA nodes with Windows Remote Collectors, the file is: vRealize_Operations_Manager-VA-WIN-xxx.pak
    • For heterogeneous clusters that have RHEL nodes with Windows Remote Collectors, the file is: vRealize_Operations_Manager-RHEL-WIN-xxx.pak
  2. Before starting the upgrade, take a snapshot of your entire vRealize Operations cluster as a precaution.
  3. On your existing vRealize Operations Manager cluster, log in to the master node administrator interface.
  4. On the left, click Software Update.
  5. Click Install a Software Update.
  6. Follow the wizard to locate and install your downloaded PAK files.
    1. Perform the OS upgrade. This updates the OS on the virtual appliance and restarts each virtual machine.
    2. Install the other PAK files. Installation might take several minutes or even a couple hours depending on the size of your cluster and node type, vApp or non-vApp.
    Do not refresh the screen during the installation. When the installation is completed, the administrator interface logs you out.
  7. Log back in to the master node administrator interface.
    The main Status and Troubleshooting page of the administrator interface appears, and the cluster goes online automatically. The status page also displays the Bring Online button, but do not click the button.
  8. If the browser page does not refresh automatically, refresh the page.
    The cluster status changes to Going Online. When the cluster status changes to Online, the upgrade is complete.
  9. On the left, click Software Update.
  10. Verify that vRealize_Operations_Manager_Enterprise (Upgrade vRealize Operations Manager Enterprise) appears on the right.
    If the update does not appear, wait a few minutes, and refresh the page in your browser.
  11. After upgrading, apply the 6.0.1 hot fix patch. For installation instructions, see KB 2116366

After you upgrade, if the vSphere Web Client for the machine that is being monitored by vRealize Operations Manager 6.0.1 does not display the Health, Risk, and Efficiency badges, see the Known Issues section of these release notes.

Top of Page

Installation Notes for This Release

For guidance about installing and configuring vRealize Operations Manager, see the following guides.

Adapter Support

In addition to the VMware adapters (MPSD, Log Insight, VCM, VIN, and Hyperic) in the deployment guides, the following adapters are supported for this release.

AdaptervApp Single NodevApp Multiple NodeRHEL Single NodeRHEL Multiple NodeWindows Single NodeWindows Multiple NodeUpgrade Migration
AWS 1.0YesYesYesYesNoNoNo
SCOM 3.1YesYesYesYesNoNoYes
EMC Smarts 2.4YesYesYesYesYesYesYes
EMC Smarts 3.0YesYesYesYesNoNoYes
Text File 2.0YesYesYesYesYesYesYes
Relationships 2.5YesYesYesYesYesYesYes
vCloud Director 2.5YesYesYesYesYesYesYes
GSSQL 2.18YesYesYesYesYesYesYes
HP-SiteScope 2.4YesYesYesYesYesYesYes
KeyNote 2.1YesYesYesYesYesYesNo
TeamQuest 2.0YesYesYesYesYesYesYes
SNMP 2.1YesYesYesYesYesYesYes
HP-BAC 2.7YesYesYesYesYesYesYes
Port 1.1YesYesYesYesYesYesYes

Management Pack for Storage Devices 6.0 is compatible with vSphere 5.1 Update 2 or later.

Top of Page

Resolved Issues

This section contains issues that have been resolved in this release.

  • No data is reported for Device on the Workload Breakdown page
    On the Analytics tab, under Workload, a Device category displays two sub-categories: Reads per second and Writes per second. In this release, these sub-categories report data.

  • Delta values for some metrics are not correctly calculated
    Some delta metrics for cluster and analytic resources are not calculated correctly. The value is always 0. In this release, the vRealize Operations Manager adapter calculates delta metrics correctly.

  • The alert notification that vRealize Operations services are down is not generated
    If the collector on which you are running the vRealize Operations Manager adapter stops running and no data is received for two times the monitoring interval, an alert is not triggered. This issue is resolved in this release.

  • Disabled compliance alert appears on the All Standards tab
    If you disable a compliance alert in a policy, then inspect an object of the same kind with the assigned policy, the disabled alert appears on the All Standards tab on the Compliance analysis page. In this release, only enabled alerts appear in the list of All Standards.

  • Blank metrics and resource counts in multiple-node cluster
    When one node fails to retrieve metrics and resource counts for any reason, other nodes of a multiple-node cluster might also show blank metrics and resource counts. This behavior appears on the Cluster Management page of the administration interface. In this release, a node cannot cause metrics and resource counts related to another node to disappear from the UI. Any blanks indicate a direct issue with that node.

  • The analytics services fail to start after upgrading
    If the cluster fails to start after about 30 minutes, you search the analytics-{node-GUID}.log files for errors in the ActivityDataService. In this release, analytics services correctly start and run after an upgrade.

  • Option to bring cluster online enabled with an unresponsive node present
    If a node in a cluster becomes unresponsive while the cluster is offline, you must not bring the cluster online. However, the button to bring the cluster online is enabled. In this release, the button to bring the cluster online is disabled.

  • A user who has permission to create other user accounts can assign permission to a new or existing user account to access all objects in the environment
    When a user has permission to create user accounts, that user can create a new user account with permission to access to all objects in the environment, even if the user who is creating the new user account only has limited access to objects in the environment. In this release, the new user account has the same permissions as the user who created the account.

  • When the applied policy changes for an object group, updates to the capacity badges and metrics are delayed
    After you apply a policy other than Default Policy to an object group, if you view the Analysis tabs for an object in the group, updates to the computed badges and metrics do not appear immediately. This issue is resolved in this release.

  • Disabled capacity metrics in vCenter Operations Manager 5.8.x are enabled after migration to vRealize Operations Manager 6.0
    Migrated capacity metrics that are disabled for vCenter Server, host systems, virtual machines, and other objects in vCenter Operations Manager 5.8.x, are enabled in vRealize Operations Manager 6.0. In this release, disabled capacity metrics migrated from vCenter Operations Manager 5.8.x remain disabled in vRealize Operations Manager 6.0.

  • Maximum Observed Transmitted Throughput metric is reset to a lower value after the collector service is restarted
    If the collector service is restarted, the Max Observed Transmitted Throughput metric is reset to the lower default value rather than returning to the previous maximum observed value. This issue is resolved in this release.

  • Anomaly Breakdown widget is empty
    If you select the Multiple Mode option when you configure the Anomaly Breakdown widget, no data appears in the widget. This issue is resolved in this release.

  • Only one email alert notification is sent by the Standard Email Plug-In, even though notifications must be sent for multiple alerts
    If you create an outbound alert where you configure the Standard Email Plug-In to use TLS, only one email alert notification is sent for an alert. Other notifications are not delivered. In this release, email is delivered for every generated alert.

  • Cannot search for notification or hard threshold alert event information messages
    When a notification or hard threshold event is generated, the event message is appended to the alert name. In the Alerts lists, you can search for notification or hard threshold, but a search for the appended event message yields no results. In this release, alert names appended with the event message appear in the Alerts list.

  • Support bundle for multiple nodes in a cluster creates file for only one node
    When creating a support bundle, in Administration > Support > Support Bundles, if you select two nodes to include in the support bundle, only one node is included in the bundle. This issue is resolved in this release.

  • Alert list count for generated alerts after High Availability failover is incorrect
    In a multinode environment where HA is configured, if the master node goes offline unexpectedly, the alert list count in the lower right does not match the number of alerts displayed in the list. In this release, the alert list count correctly matches the number of alerts listed.

  • Taking a node offline sometimes results in a timeout message
    When you take a cluster node offline, a timeout message sometimes appears: Communication Error: Timeout reached while trying to communicate with the server. Try refreshing the UI manually. This issue is resolved in this release.

  • Migrated users can gain additional permissions
    After migrating a 5.x deployment to vRealize Operations Manager 6.0, migrated users are able to perform tasks, such as creating dashboards, that they did not have permissions to perform in version 5.x. In this release, migrated users can perform the same tasks in a 6.0 deployment for which they had permissions in 5.x deployment.

  • Database becomes unresponsive when temporary log files fill the disk partition
    When you monitor many active resources that have long data retention times, the vRealize Operations Manager database might stop responding because temporary database log files fill the disk partition that holds the /storage/log directory. This issue is resolved in this release.

  • License key could be added to Unlicensed group
    vRealize Operations Manager 6.0 allows you to associate a license key with the Unlicensed group. This issue is resolved in this release.

  • When the Scoreboard widget is in interaction mode, the user does not see the expected information after the refresh interval
    The problem occurs when you follow these steps:
    1. Set Self Provider to ON.
    2. Select a valid configuration.
    3. Save the widget.
    4. Set Self Provider to OFF.
    5. Set Refresh Content to ON and define a small value for Refresh Interval (for example, 5 seconds).
    6. Save the widget.
    7. Configure another widget as a provider for the Scoreboard widget.
    8. Select an object from the source widget.
    The Scoreboard widget shows information about the selected object, as expected. The Scoreboard widget shows information according to the first configuration after the Refresh interval, not as expected. In this release, the data on the scoreboard widget changes after the Refresh interval.

  • Top of Page

Known Issues

This section contains known issues for this release.

Installation and Upgrade Issues
  • Upgrades require Java on vRealize Operations Manager for Linux
    Before you upgrade vRealize Operations Manager for Red Hat Enterprise Linux (RHEL), you must have Java installed, in addition to the Java version that vRealize Operations Manager installed at $VMWARE_JAVA_HOME.
    If the other version of Java is not present, the upgrade appears to work but does not actually upgrade all vRealize Operations Manager components.
    Workaround: Avoid uninstalling Java from your RHEL system, or reinstall it if it has been uninstalled.
    The Java version that you install is not important. By default, RHEL 6.5 comes with the open JDK 1.7, but you can install JRE 1.7 or 1.8, for example.

  • After applying the hot fix for vRealize Operations Manager 6.0.1, the VIN adapter still does not collect data properly
    After applying the hot fix documented in KB 2110330, the VIN adapter still does not collect data properly. Data appears as question marks in the UI.
    Workaround: Delete the VIN adapter instance and add a new VIN adapter instance with the same vCenter credentials.

  • Attempting to re-upload a PAK file following a UI timeout results in an error message
    When performing a software update, if you leave the console unattended and you do not select install after the PAK file uploads, the UI will timeout. If you restart the software update and attempt to upload the PAK file again, the UI displays an error message indicating that the update is already installed.
    Workaround: When you perform the software update again, check the option to Install the PAK file even if it is already installed, then click Upload.

  • Verisign certificates are not migrated during an upgrade
    After updating the trustore file with Verisign certificates for vRealize Operations Manager 6.0 and upgrading to 6.0.1, the certificates are not available. Updating the trustore file is a customization step required to support the AWS adapter.
    Workaround: Verisign certificates are removed during an upgrade. Other certificates are not removed. To re-install the Verisign certificates, repeat the customization step in vRealize Operations Manager 6.0.1.

  • After upgrading to vRealize Operations Manager 6.0.1, badge values do not appear in the vSphere Web Client
    After you upgrade vRealize Operations Manager from 6.0 to 6.0.1, the vSphere Web Client for the machine that is being monitored by vRealize Operations Manager 6.0.1 does not display the Health, Risk, and Efficiency badges.
    Workaround: Register the vRealize Operations Manager 6.0.1 plug-in with your vCenter Server instance.
    1. In vRealize Operations Manager, click Administration and click Solutions.
    2. In the top pane, click the VMware VSphere solution, and click Configure.
    3. To re-register vRealize Operations Manager with your vCenter Server instance, in the top pane, click your vCenter Adapter. The instance name appears highlighted in the lower pane, and displays the adapter settings.
    4. Click Manage Registrations, enter your user name and password, and click Register.
    Your vRealize Operations Manager 6.0.1 instance appears in the lower Solutions pane, and the collection status indicates Data receiving.

  • Before a migration, pre-requisite upgrade might become unresponsive
    A migration to this version requires that the source be vCenter Operations Manager 5.8.1 or later. When you attempt to update a source that uses DHCP, the source deployment might become unresponsive.
    Workaround: Follow the steps in KB 1037601.

Cluster Management Issues
  • Cannot replace the current master replica node
    After nominating a new master replica node, the cluster status shows that the slice is not removed.
    Workaround: Remove all remote collector nodes from the cluster before replacing the master replica node.

  • Failed to finish adding nodes when one or more remote collectors are added to a running cluster
    When attempting to expand an online cluster, you add a new remote collector node and click Finish Adding New Nodes in the administration interface. The cluster state updates to Online, but text beneath the state indicates Failed to add new node.
    Workaround: After failure, wait approximately 30 seconds and click Finish Adding New Nodes. If the operations fails again, wait and click the button again. Once the vRealize Operations Suite API is online, communication can be established and the cluster is able to add new nodes.

  • Cannot remove a previous master node
    In the administration interface, after an HA replica node takes over and becomes the new master node, you cannot remove the previous, offline master node from the cluster. In addition, the previous node continues to be listed as a master node.
    Workaround: To refresh the display and enable removal of the node, refresh the browser.

  • Error message when configuring a master node in a multiple node environment
    After you configure a node as the master node, the Preparing the node message appears. When you click Start to start the cluster, the Communication Error: Timeout reached while trying to communicate with the server. Try refreshing the UI manually message appears.
    Workaround: Refresh the browser to refresh the user interface.

  • PAK installation does not prevent cluster modification as expected
    When installing a solution, you can perform cluster modification tasks in the product administration interface, such as enabling HA or taking nodes online or offline. When you modify the cluster during PAK installation, however, the product might behave unpredictably or become unresponsive.
    Workaround: Avoid any cluster modification activities while solutions are being installed.

  • Cluster can not start when node name contains forward slash
    A cluster that includes a node with a forward slash (/) in its name can not start.
    Workaround: None. Avoid the forward slash (/) character in cluster node names.

  • External shutdown affects cluster nodes
    When you shut down a data node from outside vRealize Operations Manager, such as by using vSphere, all nodes report an inaccessible status for a few moments and then change to waiting for analytics. For vRealize Operations Manager, an external shutdown equates to pulling the power plug on a running node, and depending on the complexity of your deployment and the amount of data that was on the node, you might need to wait for many minutes or even hours before the remaining nodes return to normal.
    Workaround: Do not shut down online cluster nodes externally or by using any means other than the vRealize Operations Manager interface. Shut down a node externally only after taking it offline in the vRealize Operations Manager interface.

  • Windows cluster behaves unpredictably after NetBackup restore
    After using NetBackup to perform a successful restore of a vRealize Operations Manager Windows-based cluster node, the application behaves unpredictably.
    Workaround: After successfully restoring a vRealize Operations Manager Windows-based node, restart the Windows operating system.

  • Replica node cannot take over after master and replica go offline
    If the master node and replica node go offline, and the master remains offline for any reason while the replica goes online, the replica node does not take over the master role.
    Workaround: Manually configure the replica node as the master node.
    1. Take the entire cluster offline, including data nodes.
    2. Log in to the replica node command line console as root.
    3. Open $ALIVE_BASE/persistence/persistence.properties in a text editor.
    4. Locate and set the following properties:


    5. Save and close persistence.properties.
    6. In the administration interface, bring the replica node online, and verify that it becomes the master node.
    7. Bring the remaining cluster nodes online.

  • Removed nodes can reconnect to the cluster
    If a node goes offline for any reason, and you remove the node from the vRealize Operations Manager cluster, the node reconnects to the cluster when you bring the node back online.
    Workaround: None. Do not bring removed nodes back online.

  • Master and replica nodes cannot be simultaneously brought online
    If the master node and replica node go offline at the same time for any reason, and they are brought online together, they do not properly take over management of the vRealize Operations Manager cluster.
    Workaround: If the master node and replica node go offline together, bring them back online separately. Bring the master node completely online first, and then bring the replica node online.

  • Top of Page

General Issues
  • New Edit Monitoring Policy ineffective for canceling alerts
    Unable to cancel alerts using policies, even with a policy that is properly associated to an object that has a maintenance schedule.
    Workaround: None. The maintenance schedule feature is not correctly implemented for policies.

  • vRealize Operations Manager extension is registered using the IP address instead of DNS name
    By default, vRealize Operations Manager registers its extension with vCenter using the vRealize Operations Manager IP address and not the DNS name. Users who click to open vRealize Operations Manager from the Monitor tab in vCenter open a URL based on the vRealize Operations Manager IP address and not the DNS name.
    Workaround: To allow registration of the vRealize Operations Manager extention with the DNS name, follow these steps:
    1. On every node in the vRealize Operations Manager cluster, follow these steps:
      1. From the console, open the following file in a text editor.
      2. Add the following line to the properties.
        Note: You can return to using the IP address by changing the property to false.
      3. Save and close configuration.properties.
    2. Log in to the vRealize Operations Manager administration interface, and restart the cluster.

  • Self-Metric count is sigificantly different in version 6.0.1
    Following an upgrade to version 6.0.1, the vRealize Operations Manager Generated self-metric count value appears significantly lower than in version 6.0.
    Workaround: None. In version 6.0.1, a correction to the dynamic threshold computations excludes capacity generated metrics. The product works as designed.

  • Health badge color differs in the vSphere Web Client depending on the plug-in version installed
    In the vSphere Web Client, with the vRealize Operations Manager 6.0 or 6.0.1 plug-in installed, the Health badge, which is calculated based on alerts, appears in green for a powered off virtual machine. With the vCenter Operations Manager 5.x plug-in installed, the Health badge, which is calculated based on metrics, appears in gray for a powered off virtual machine.
    The vSphere 5.5 and 6.0 documentation indicates that the color of the Health badge is gray for a powered off object, which is true when the vCenter Operations Manager 5.x plug-in is installed, but is not true when the vRealize Operations Manager 6.x plug-in is installed.
    Workaround: None

  • Only one LDAP host configuration with identical IP, PORT, and BASE DN values can be migrated
    Migration of LDAP host configurations from vCenter Operations Manager 5.x to vRealize Operations Manager might complete with a success with warnings status. The warning occurs whenever version 5.x has more than one LDAP host configuration in its database with identical IP, PORT, and BASE DN values, even when other values such as USERNAME are unique.
    Workaround: None. In such cases, only one of the LDAP host configurations with identical IP, PORT, and BASE DN values is successfully migrated.

  • Slow performance in large-scale deployments due to logs set to the debug level
    When vRealize Operations Manager log files are set to the debug level by default, slow performance might occur in large-scale deployments.
    Workaround: Change the log file setting to the error level.
    1. In the vRealize Operations Manager UI, select Admininstration > Support > Logs.
    2. Click to open the folder for the master node.
      • Select the ANALYTICS folder and click Edit Properties. For the Log Names: LockTraceLogger and QueryProfiler, click the Logging Level to change the setting from debug to error.
      • Select the SUITEAPI folder and click Edit Properties. For the Log Names: com.vmware.ops.api.server.utils.HttpRequestLogger, com.vmware.ops.api.server.utils.Profiler, and org.apache.http, click the Logging Level to change the setting from debug to error.

  • Time Remaining badge on the Analysis tab shows "?"
    After policies are edited multiple times, the breakdown on the Time Remaining badge displays "?".
    Workaround: None. Time remaining is a capacity metric. Frequent policy changes affect capacity computations. Correct Time Remaining values appear after the next scheduled nightly capacity computation.

  • Display shows No data for Last month or Last 6 months or Last Year
    Charts with date controls that limit the data displayed to a selected time frame, report no data if selection is Last month, Last 6 months, or Last Year.
    Workaround: None.

  • Alerts remain on after resource is powered off
    When a resource is powered off, metric collection stops and eventually cancels alarms and alerts. However, if the adapter continues to send metric data, the alerts remain on.
    Workaround: None.

  • Compliance failure reported for missing property
    When checking the compliance status of an object in the UI, the check fails if the property is missing.
    Workaround: To bring the object into compliance, add the isolation.tools.autoinstall.disable property to the configuration parameters on the vSphere Client and set the value to True. To make the correction on the vSphere Client, go to Edit settings > Options > General > Configuration Parameters.

  • Unable to log in to vSphere Web Client after updating the vRealize Operations Manager plug-in for vSphere
    When the vRealize Operations Manager plug-in for vSphere is undeployed due to an action such as an update, parts of the core vSphere Web Client might redeploy. This can result in instability in the vSphere Web Client and loss of service. Visible symptoms include not being able to log in to the vSphere Web Client or an empty inventory display on the vSphere Web Client.
    Workaround: Restart the vSphere Web Client to restore service.

  • Some vSphere 6 diskspace metrics do not appear
    When you register vRealize Operations Manager with vSphere 6, not all diskspace metrics appear. Only the following diskspace metrics are published to vRealize Operations Manager from vSphere 6.
    Virtual machine: diskspace|used, diskspace|diskused, diskspace|snapshot
    Host: diskspace|used, diskspace|diskused, diskspace|snapshot
    Cluster: diskspace|used, diskspace|diskused, diskspace|snapshot
    Datastore: diskspace|used, diskspace|diskused, diskspace|snapshot, diskspace|swap, diskspace|capacity, diskspace|disktotal, diskspace|provisioned
    Workaround: None.

  • vSphere 6 displays older text and images related to vRealize Operations Manager
    When you register vRealize Operations Manager with vSphere 6, the vSphere 6 user interface displays the older product name of vCenter Operations Manager in the Monitoring tab of the vSphere Web client. In addition, the illustration of the product interface shows the older vCenter Operations Manager interface instead of the vRealize Operations Manager interface.
    Workaround: None. You can safely ignore the older name and image, however, because monitoring uses vRealize Operations Manager as expected.

  • Discrepancy in Memory|Host Demand value for VMs
    On the Analysis Workload tab, two charts display the memory demand. One chart displays the host demand, and the other displays the demand of the VMs on the host. The host demand aggregates the VM demand with the VM reservation and limit. So the host demand and the total VM demand might appear mismatched. For example, when VMs on the host have a large reservation, the host demand is greater than the total VM demand.
    Workaround: None.

  • VVOL datastores are masked
    If a VM, host, cluster, data center, or vCenter Server object with VVOL datastores is selected from the list of all object, an incorrect datastore count appears on the Environment Objects Map tab or the Troubleshooting All Metrics tab. Additionally, if a VM is deployed on a VVOL datastore, raw or derived metrics may be missing.
    Workaround: None. The VVOL datastores are masked because vRealize Operations Manager does not implement the VVOL datastore metrics. However, the VVOL datastores are included in the count.

  • Long wait for Time Remaining metric values to appear in the UI
    Values for the Time Remaining metric do not appear in the UI for several days.
    Workaround: None. Capacity computations are based on data collected over a period of time with one capacity data point generated in a 24 hour period. vRealize Operations Manager uses the trend of historical capacity data points to forecast Time Remaining values. Because at least two days are required to determine a trend, several days is a normal amount of time to wait for Time Remaining values to appear.

  • When trying to manually add an SNMP device, the imported SNMP MIB file is not listed
    After you copy an SNMP MIB file to the /usr/lib/vmware-vcops/user/plugins/inbound/snmp_adapter3/conf/mibs folder, and perform steps to import the script and re-describe the SNMP adapter, the file is not listed as an Object type on the Add Object workspace in the UI.
    Workaround: To list the MIB file, sync the MIBs on the collector nodes.
    1. Copy the new MIB file to $ALIVE_BASE/user/plugins/inboud/snmp_adapter3/conf/mibs on the master node.
    2. Re-describe the SNMP adapter.
    3. Restart the vmware-vcops service on each of the slices or collectors where the MIB file does not exist so that all the MIBs are synced as part of the Sync operation.

  • Communication error when creating a support bundle
    Support bundles are created when you select Administration > Support > Support Bundles or in the Administration user interface. When you create a support bundle to review or to send to support services, the ERROR com.vmware.vcops.adminui.action.UtilityAction:25 - JavaScript Error - Msg:Communication error, Url: supportBundle.action message appears. This error occurs when the file size is approximately 10 GB or larger. Although the error is generated, the support bundle is created and is usable.
    Workaround: None.

  • After a migration to vRealize Operations Manager 6.0, some badge metrics do not appear in the Override Attributes and Override Alert / Symptom Definitions areas of the policy workspace

    Migrated badge metrics for vCenter Server, host systems, virtual machines, and other objects in vCenter Operations Manager 5.8.x, do not appear in the vRealize Operations Manager 6.0 policy workspace.

    When you view the policy Override Attributes workspace, and select Metric for the Attribute Type, the following badge metrics do not appear:
    badge|health, badge|health_state, badge|health_classic, badge|risk, badge|risk_state, badge|risk_classic, badge|efficiency, badge|efficiency_state, badge|efficiency_classic

    When you view the policy Override Alert / Symptom Definitions workspace, and attempt to view the badge metrics for the Symptom Definitions, the following badge metrics do not appear:
    badge|workload, badge|anomaly, badge|fault, badge|time_remaining, badge|time_remaining_whatif, badge|capacity_remaining, badge|stress, badge|waste, badge|density, badge|compliance

    Workaround: None

  • Some symptom definitions are in English even when the browser in which vRealize Operations Manager is running is set to another language
    If you install vRealize Operations Manager as a vApp or on a localized RHEL operating system, some of the Metric and Supermetric symptom definitions appear in English.
    Workaround: Install vRealize Operations Manager on a localized Windows operating system.

  • Migrated key names might not be localized
    At migration, if a source metric has no counterpart in the target version of vRealize Operations Manager, the migrated metric is treated as a new metric on the target. Its metric attributes (metadata) are added dynamically during the metric ID request, and its key names are considered to be localized names even though they might not be correctly localized.
    Workaround: None

  • Relationships between resources managed by the MPSD adapter and resources managed by the VMware vSphere Adapter are broken
    When the MPSD adapter is installed, it creates relationships between newly discovered resources that it manages and resources that the VMware vSphere adapter manages. These relationships might break during the second collection cycle after resource discovery.
    Workaround: Restart the collector on the vRealize node where the MPSD instance is installed. To restart the collector, run: ~$ $ALIVE_BASE/common/bin/vmware-vcops.sh restart collector

  • vCenter Adapter stops collecting from vCenter Server 5.5
    When vCenter Server collections fail on a vCenter Server 5.5 instance and the logs show RuntimeException WstxEOFException exception, vFlash is enabled on hosts in your vSphere Server environment.
    Workaround: Apply the workaround provided in KB 2072392.

  • An installed solution does not appear in the Add License Key drop-down menu
    If you are licensing an instance of a solution adapter by selecting Administration › Solution › ‹adapter name› license › Configure › Add, and the adapter does not appear in the Add License Key drop-down menu, then the license process failed to refresh the license keys.
    Workaround: To force a license refresh, make a cURL request on the master node.
    1. Use SSH to log in to the master node.
    2. Run the command: curl -k -X POST -i -H "Content-type: application/json" -H "X-vRealizeOps-API-use-unsupported: true" -u admin -X POST https://localhost/suite-api/internal/adapterkinds/describe
    3. Provide the password for the administrator user.
    The license process refreshes the list.

  • Metrics for Distributed Virtual Switch object types are not collected
    Metrics for Distributed Virtual Switch object types are not collected due to permission problems or a session timeout. Errors such as The session is not authenticated or Cannot complete the operation due to an incorrect request to the server are reported in the collector.log file.
    Workaround: None.

  • Symptoms and alerts generated due to notification events ignore the criticality of the event and always default to Info
    Most events include a criticality. When symptoms that are based on event notifications are triggered and an alert generated, the criticality of the event is ignored and the criticality of the generated alert is displayed as Info.
    Workaround: None

  • Metric value that depends on property and other metrics are not null when dependent metric values are missing
    For metric calculations that are based on property and other metrics, if the dependent metrics are missing, the metric is incorrectly calculated based on property only. The metric value should be null because the dependent information is insufficient.

  • Metric for 'Outstanding IO requests' might be inaccurate on some vSphere object types
    The datastore|demand_oio metric that appears as Datastore|Outstanding IO Requests in the UI, might be inaccurate for the vCenter Server, Datacenter, Cluster, and Datastore object types. Due to the method used to calculate a weighted average of transactions and the latency of transactions across hosts, the value of this metric might be artificially high.

  • After migrating from an earlier version of vRealize Operations Manager, some migrated dashboard widgets do not contain any data
    If you migrate two or more instances of vCenter Operations Manager 5.x to vRealize Operations Manager 6.0, and each of the 5.x instances is collecting and monitoring from the same vCenter Server instance, the migrated dashboards might not contain any data.
    Workaround: Reconfigure the dashboard widgets after migration.

  • Cannot open an object in vSphere Web client
    When the vSphere Web client is installed on a port other than the default port 9443, the vRealize Operations Manager options to open an object in vSphere, such as Open Virtual Machine in vSphere Client, do not open the object in the vSphere Web Client as expected.
    Workaround: None. Install the vSphere Web Client on default port 9443.

  • Some features are missing after you transition to vRealize Operations Manager Standard edition
    After you run vRealize Operations Manager 6.0 Evaluation, Advanced, or Enterprise edition, either as part of the beta program or because you initially installed one of these editions, when you transition to the Standard edition, you no longer have the following Advanced and Enterprise features:
    • Ability to create or modify dashboards
    • Ability to create or modify supermetrics
    • Ability to create custom reports
    • Ability to commit projects
    • Ability to install solutions other than the provided VMware vSphere Solution
    After you transition to the Standard edition, you should delete any content that you created in the other versions to ensure that you comply with the EULA.
    Workaround: You must have the correct license key to support these features.

  • Adapter test is unsuccessful if Virtual Infrastructure Navigator adapter instance name includes non-ASCII characters
    When you create a Virtual Infrastructure Navigator adapter instance, the credentials that you specify for the vCenter Server must use only ASCII characters.
    Workaround: None

  • Project scenarios with the same effective date can conflict and be overwritten
    When the following two types of project scenarios occur on the same date, the second type of scenario takes effect and overwrites the first type of scenario.
    1. A scenario to add, remove, or modify provider capacity. For example, add hosts, add datastores, or modify host capacity.
    2. A scenario that modifies the capacity of a container of providers directly, for example modify cluster capacity by 20 percent, where the modified cluster is an ascendant of providers in scenario type 1.
    These scenarios only conflict if the providers in type 1 are descendants of containers in type 2.
    Workaround: Create these two types of scenarios at slightly different dates.

  • Migrating custom rules results in incorrect unit conversions
    When you migrate custom groups to vRealize Operations Manager 6.0 or later, the resulting unit conversion of properties in rules is incorrect for cluster and virtual machine objects. For example:
    • For a cluster, a conversion of CPU total capacity from 2000 GHz results in an incorrect value of 2048000 MHz. The correct value would be 2000000 MHz.
    • For a virtual machine, a CPU conversion from 15000 MHz results in an incorrect value of 15000 Hz.
    Workaround: None

  • Cannot disable outbound alert instances
    Outbound Alert Settings include the option to disable an outbound alert instance. When you select the option and click Disable, the outbound alert instance is not disabled.
    Workaround: Delete the outbound alert instance.
    1. In the left pane, click the Administration icon.
    2. Click Outbound Alert Settings.
    3. Select the instance and click Delete.

  • Capacity badges take time to compute after migration
    When migrating from vCenter Operations Manager 5.x to this release, it might take time for the capacity computation to reach the current time. The amount of time required to reach the current time depends on the amount of data and the inventory size. During this migration time, the sub-badges grid in the badge details displays partial data.
    Workaround: None

  • The out-of-the-box Classic Summary dashboard does not display content in widgets
    The Classic Summary dashboard displays no content in the widgets. This issue occurs because of an incorrect Self Provider setting in the widget configuration.
    Workaround: To correct the issue, edit each widget in the dashboard. Click the edit icon in the top right corner of a widget, set Self Provider to ON, and click OK to save the change.

  • Dashboards cannot export and import related data
    When you export a dashboard, the related data such as resource kinds, metrics, super metrics, views and so on, is not included. Therefore, when you import a dashboard, the related data is missing.
    Workaround: Separately export and import the dashboard related data. For example, if you use a view in your dashboard, export the view separately and import it to the vRealize Operations Manager instance where you imported the dashboard.

  • LDAP test results in success regardless of which common name you select
    When you add an LDAP import source by selecting Administration > LDAP Import Sources, either Common Name option in the Add Source dialog box is selectable, and the LDAP test result is successful. Based on the version of Active Directory used in your environment, only one option should be selectable .

  • Default metric collection behavior for the legacy adapter
    vRealize Operations Manager collects metrics for defaultmonitored="true" and defaultmonitored is missing. This is the default behavior. vRealize Operations Manager does not collect metrics with defaultmonitored="false".
    In contrast, vCenter Operations Manager 5.x uses the default package attribute and all attribute package to collect metrics. The all attribute package is assigned to the attribute package by default. In vCenter Operations Manager 5.x, all metrics are collected by default regardless of the setting defaultmonitored="true", defaultmonitored="false", or defaultmonitored is missing. If defaultmonitored is missing for a metric, and the resource kind is assigned the default attribute package, vCenter Operations Manager 5.x does not collect that metric.

  • The Text Display widget cannot display some Web sites in HTML mode
    If a Text Display widget is configured with the View Mode set to HTML, then the URL should use HTTPS protocol. The functionality of the Text Display widget with Web sites that use HTTP depends on the individual settings of the Web sites.
    Workaround: None

  • Deselecting Read permissions for Resources and Dashboards has no effect
    When you create a user role with no Read permission for Resources and Dashboards, the user can still see the dashboards and all resources on the home page. Object Relationships page is always visible to the user with or without any permission.
    Workaround: None

  • The Topology Graph widget does not correctly display the relationship between VMs and hosts when using path exploration mode
    The Topology Graph widget shows a Runs-on relationship with a single line and a Connected-to relationship with a double line. Since the VMs have a Runs-on relationship with hosts, the paths between VMs and hosts should appear as a single line. The Topology Graph widget incorrectly shows the relationship between a VM and host with a double line.
    Workaround: None

  • Sorting the columns in List and Summary views applies only for data in the current page
    When you sort columns in List and Summary view, data is sorted only in the currently selected page of the data grid.
    Workaround: None

  • vCenter Operations Manager 5.8.x custom dashboards migrated to vRealize Operation Manager 6.0 show no data or display incorrectly
    When you migrate vCenter Operations Manager 5.8.x custom dashboards to vRealize Operation Manager 6.0, the dashboards do not show any data or might not show resource names as expected.
    Workaround: Reconfigure the custom dashboard.

    Top of Page

User Interface Issues
  • Applications for HTTP Post adapter are not listed in Open in External Application drop-down menu
    When you want to use an external application to obtain information about an object through an adapter link, you select the application for that adapter in the Open in External Application drop-down menu. However, if a vCenter user that authenticates does not have permission for the HTTP Post adapter, no applications are listed.
    Workaround: The user must be local or imported from an LDAP source. You cannot edit permissions so that the vCenter user can open the application.

  • New object fails to appear on Topology widget
    When you add a new object to the Topology Graph widget provisioned object, the graphical presentation does not update automatically.
    Workaround: Manually refresh the page.

  • Multiple Open in External Application selections are not listed in UI
    If an adapter is defined with multiple Launch in Context configurations, only one external application selection is listed in the UI. The user cannot control the selection, and any of the Launch in Context configurations might be listed.
    Workaround: None.

  • Some of the options in the report template tab toolbar options do not work when you log in to vRealize Operations Manager using Internet Explorer 11
    When you log in to vRealize Operations Manager using Internet Explorer 11, you cannot create, edit, or clone a report template.
    Workaround: Use Internet Explorer 10, Firefox, or Chrome browser.

  • Network link failure related alerts might not auto clear when the problem is fixed
    The following network link failure related alerts might not be cleared if the vSphere Client does not report that the events are cleared to vRealize Operations Manager, even if the underlying problem is fixed:
    • ESXi host has detected a link status down on a physical NIC
    • The host has lost connectivity to a dvPort
    • The host has lost redundant connectivity to a dvPort
    • The host has lost connectivity to physical network
    • The host has lost redundant uplinks to the network
    Workaround: When the physical NIC or vSwitch or DV Port is functional, confirm that the network issue no longer exists, and manually cancel the alert.

  • Some operating system and browser combinations do not support Flash 11.5 for the Open in External Application option
    If you are running vRealize Operations Manager on a Red Hat operating system and using Firefox as the browser to access vSphere Web Client 5.5, the Open in External Application option fails with the error To view this page, ensure that Adobe Flash Player version 11.5 or greater is installed. This error occurs because vSphere Web Client 5.5 requires Flash 11.5. Flash 11.5 is not support on Red Hat.
    Workaround: To use the option with vSphere Web Client 5.5, use a browser and operating system that supports Flash 11.5. If you are using a vSphere Web Client earlier than 5.5, the error does not occur because the earlier versions of vSphere Web Client use earlier versions of Flash.

  • In the analysis views, the data transmit rate and receive rate values for virtual machines display the host system value
    If you are monitoring ESXi 5.5 hosts, the display that should show the data transmit and receive rates collected from the host for the virtual machines, shows the transmit and receive rate values for the hosts. This problem only occurs if you are monitoring a host running ESXi 5.5.
    Workaround: None

  • Duplicate dashboards appear after migration
    If you migrate an earlier vCenter Operations Manager deployment to version 6.0 or later, and configure management packs for SCOM and EMC Smarts, duplicate default dashboards appear in the new version.
    Workaround: Delete the duplicate dashboards.

Documentation Issues

The following information did not make it into the product Help or documentation in time for publication.

  • Deployments must be within the same data center
    In addition to the networking requirements for nodes listed in the documentation, vRealize Operations Manager analytics cluster nodes must be deployed and installed within the same data center. Connect the analytics cluster to the same local area network (LAN). With the exception of remote collectors, do not distribute nodes over a wide area network (WAN).

  • Additional global setting for Deletion Scheduling Interval
    In this release, a new Deletion Scheduling Interval setting determines how often vRealize Operations Manager runs its purging algorithm. The setting works together with the existing Deleted Objects setting to remove objects that no longer exist in the environment. vRealize Operations Manager transparently marks objects for removal that have not existed for the length of time specified under Deleted Objects. vRealize Operations Manager then removes the marked objects at the frequency specified under Deletion Scheduling Interval.

Top of Page