vRealize Operations Manager 6.0.3 Release Notes

vRealize Operations Manager 6.0.3 | 10 SEP 2015 | Build 3041066

vRealize Operations Manager Appliance 6.0.3 | 10 SEP 2015 | Build 3041065

vRealize Operations Manager 6.0.3 PAK Upgrade | 10 SEP 2015 | Build 3041070

Last Document Update: 09 NOV 2016

Check 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.3 updates cover all major areas of the product including installation, migration, configuration, licensing, alerting, dashboards, reports, and policies. This release includes the following enhancement.

New Patch to Address Security Advisory

On October 19, 2016, a critical severity privilege escalation was disclosed. Known as "Dirty COW" the issue may allow for a local privilege escalation. The details of this vulnerability are documented in VMSA-2016-0018. To address this issue, install the public patch documented in KB 2147664.

Top of Page

Before You Begin

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

Compatibility

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 5.8 and later
  • vRealize Configuration Manager 5.6, 5.7.x, and 5.8
  • vRealize Operations Manager for Horizon 6.1.0
  • vCenter Hyperic 5.8.4

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.3 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 to the most recent version, follow these steps.

  1. Download the PAK file(s) needed based on the type of cluster.
      vApp clusters

      The vApp cluster requires the deployment of the OS upgrade and the product upgrade .pak files.

      • For an OS upgrade, the file is: vRealize_Operations_Manager-VA-OS-xxx.pak
      • For the product upgrade of vApp clusters, the file is: vRealize_Operations_Manager-VA-xxx.pak
      vApp heterogeneous clusters

      The vApp heterogeneous cluster requires the deployment of the OS upgrade and the product upgrade .pak files.

      • For an OS upgrade, the file is: vRealize_Operations_Manager-VA-OS-xxx.pak
      • For the product upgrade of a heterogeneous cluster that has VA nodes with Windows Remote Collectors, the file is: vRealize_Operations_Manager-VA-WIN-xxx.pak
      RHEL standalone clusters

      The RHEL standalone cluster requires the deployment of only the product upgrade .pak file.

      • For the product upgrade of RHEL clusters, the file is: vRealize_Operations_Manager-RHEL-xxx.pak
      RHEL heterogeneous clusters

      The RHEL heterogeneous cluster requires the deployment of only the product upgrade .pak file.

      • For the product upgrade of a heterogeneous cluster that has RHEL nodes with Windows Remote Collectors, the file is: vRealize_Operations_Manager-RHEL-WIN-xxx.pak
      Windows clusters

      The Windows cluster requires the deployment of only the product upgrade .pak file.

      • For the product upgrade of Windows clusters, the file is: vRealize_Operations_Manager-WIN-xxx.pak
  2. Before starting the upgrade, take a snapshot of your entire vRealize Operations cluster as a precaution.
  3. Note: The cluster can be online or offline when running the upgrade.
  4. On your existing vRealize Operations Manager cluster, log in to the master node administrator interface.
    https://master-node-FQDN-or-IP-address/admin
  5. On the left, click Software Update.
  6. Click Install a Software Update.
  7. Follow the wizard to locate and install your downloaded PAK files. Deploy the .pak file(s) based on the type of cluster as specified in step 1.
    1. Perform the OS upgrade. This updates the OS on the virtual appliance and restarts each virtual machine.
    2. Install the cluster upgrade file. 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.
  8. 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.
  9. 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.
  10. On the left, click Software Update.
  11. 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.

After you upgrade, if the vSphere Web Client for the machine that is being monitored by vRealize Operations Manager 6.0.3 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 2.0YesYesYesYesNoNoNo
SCOM 4.0YesYesYesYesNoNoYes
EMC Smarts 2.4YesYesYesYesYesYesYes
EMC Smarts 3.0YesYesYesYesNoNoYes
Text File 2.0YesYesYesYesYesYesYes
Relationships 2.5YesYesYesYesYesYesYes
vCloud Director 3.0YesYesYesYesYesYesYes
GSSQL 2.18YesYesYesYesYesYesYes
HP-SiteScope 2.4YesYesYesYesYesYesYes
KeyNote 2.1YesYesYesYesYesYesNo
TeamQuest 2.0YesYesYesYesYesYesYes
SNMP 2.1YesYesYesYesYesYesYes
HP-BAC 2.7YesYesYesYesYesYesYes
Port 1.1YesYesYesYesYesYesYes
OpenStack 1.5YesYesYesYesYesYesYes
NSX for vSphere 2.0YesYesYesYesYesYesYes

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.

  • 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.

    This issue is resolved in this release.

  • Cannot replace the current master replica node
    After nominating a new master replica node, the cluster status shows that the slice is not removed.

    This issue is resolved in this release.

Hot Fixes

The following issues that were resolved as hot fixes on vRealize Operations Manager 6.0.2, have been rolled up to vRealize Operations Manager 6.0.3:
  • In the Top-N widget, the Top Highest Utilization metrics analysis works incorrectly
    In the Top-N widget, the Top Highest Utilization metrics analysis displays different results based on the number of bars you select in the Edit Top-N dialog box.

  • Combined metric graphs do not display object names
    Combined metric graphs display only the metric titles and not the object names.

  • Metrics do not appear for some objects in the vCenter adapter
    Metrics are not calculated accurately or do not appear for some objects in the vCenter adapter.

  • The xDB global persistence metadata points to files that do not exist
    In a high availability (HA) environment, the xDB global persistence metadata points to files in /data/vcops/blob/ that do not exist.

  • An error occurs while retrieving alarm resources for alerts
    In an eight-node HA environment, when you click on any of the alerts generated by the system, the following error occurs: Error retrieving alarm resource for alerts.

  • Alerts might not get cancelled
    When an alert definition is based on an instanced symptom definition and the symptom definition cancels, the alert might not get cancelled.

  • Alert definition does not get cancelled
    The One or more virtual machine guest systems are running out of disk space alert definition is not cancelled when the symptom changes from Warning to Info.

  • The file system database status does not reflect the correct status after disk re-balancing
    After disk re-balancing is completed from the vRealize Operations Manager user interface, the file system database status remains the same.

  • Nodes are synchronized for a long duration
    Nodes in vRealize Operations Manager are continuously synchronized for a long duration.

  • Management Pack for NSX for vSphere alerts cannot be disabled
    You cannot disable alerts in the Management Pack for NSX for vSphere.

  • Objects are not accurately displayed in the Top-N widget
    The Top-N widget does not display objects accurately when the metric value is either 0 or 1.

  • Data migration fails
    Data migration from vRealize Operations Manager 5.8.2 to 6.0.2 fails during file system database rollup.
  • Top of Page

    Known Issues

    This section contains known issues for this release.

    Installation and Upgrade Issues

    • 6.0.1 hot fix 2 re-spin
      If you applied the older version of vRealize Operation Manager 6.0.1 hot fix 2, vRealize_Operations_Manager-HP2-6.0.1.2702059.pak, on a vRealize Operation Manager 6.0.1 cluster, and then upgraded to vRealize Operation Manager 6.0.3, upgrade will fail.
      Workaround: Apply the steps in KB 2116366.

    • Addition of a vRealize Operations Manager 6.0.3 node to an existing cluster fails
      If you upgrade a vRealize Operations Manager 6.0.1 or 6.0.2 cluster that has hot fixes or patches installed, to vRealize Operations Manager 6.0.3, and then add a vRealize Operations Manager 6.0.3 node to the existing cluster, node addition fails.
      Workaround: After you upgrade the cluster to vRealize Operations Manager 6.0.3 complete the following steps:
      1. Navigate to the following locations on each existing node and delete the vRealize Operations Manager 6.0.1 or 6.0.2 hot fix or patch that was stored.
        • On vApp and RHEL clusters: $STORAGE/db/casa/pak/dist_pak_files
        • On Windows clusters: %STORAGE%\db\casa\pak\dist_pak_files
      2. Remove the failed node from the cluster.
      3. Add a new vRealize Operations Manager 6.0.3 node to the cluster.

    • Upgrade fails to respond on a Red Hat Enterprise Linux (RHEL) system
      Upgrade fails to respond on a Red Hat Enterprise Linux (RHEL) system at step 5 of 9. The cluster goes offline.
      Workaround: Re-apply the upgrade .pak file using the Force option. The upgrade completes with no interruption.

    • Unable to start vRealize Operations Manager services on a Red Hat Enterprise Linux (RHEL) 6.5 x64 system
      After you install vRealize Operations Manager, when you attempt to connect to the vRealize Operations Manager Web interface and start vRealize Operations Manager, the cluster is not online. The following message is displayed: Waiting for analytics to start.
      The analytics.log in the /data/log/vcops/log folder contains the following error message: ERROR [Analytics Main Thread ] com.integrien.analytics.AnalyticsMain.uncaughtException - Thread Analytics Main Thread threw an uncaught exception. Exception was: java.lang.UnsatisfiedLinkError: /usr/lib/vmware-vcops/common/bin/libAliveJNI.so: libaio.so.1: cannot open shared object file: No such file or directory.
      Workaround: Install the libaio-0.3.107-10.el6.x86_64 package or the package version supported with the RHEL version.

    • Migration of vCenter Operations Manager 5.8.x to vRealize Operations Manager 6.0.x fails
      When you migrate vCenter Operations Manager 5.8.x to vRealize Operations Manager 6.0.x, migration fails because of check sum errors.
      Workaround: Apply the steps in KB 2030160 and restart migration.

    • Migration of vCenter Operations Manager 5.8.x to vRealize Operations Manager 6.0.x fails
      When you migrate vCenter Operations Manager 5.8.x to vRealize Operations Manager 6.0.x, migration fails because of a data corruption error. The migration log contains an error similar to the following: ERROR: compressed data is corrupt.
      Workaround: None.

    • 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.

    • 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.

    • After upgrading to vRealize Operations Manager 6.0.3, badge values do not appear in the vSphere Web Client
      After you upgrade vRealize Operations Manager from 6.0 to 6.0.3, the vSphere Web Client for the machine that is being monitored by vRealize Operations Manager 6.0.3 does not display the Health, Risk, and Efficiency badges.
      Workaround: Register the vRealize Operations Manager 6.0.3 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.3 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.

    • Top of Page

    Cluster Management Issues

    • 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:

        db.role=MASTER
        db.driver=/data/vcops/xdb/vcops.bootstrap

      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

    • String values cannot be entered in the Scoreboard and Sparkline widgets
      When you edit a Scoreboard or Sparkline widget and add a metric that is of string type, you cannot enter string values to set the color range for yellow, red, and orange bounds.
      Workaround: None.

    • Alerts are not displayed in the user interface of vRealize Operations Manager
      vRealize Operations Manager 6.0.x nodes with an IPv6 address do not support successful configuration of the product. If a vRealize Operations Manager node binds to an IPv6 address, you can reassign the IPv4 addresses and the cluster might come online, but alarms are not displayed. This happens because the vPostgres database is deleted. You might also see the following in the analytics log:
      WARN [C3P0PooledConnectionPoolManager[identityToken->z8kflt9b13bhzrj20fhq4|1c1e9fdc]-HelperThread-#2 ] com.mchange.v2.resourcepool.BasicResourcePool.forceKillAcquires - Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@52012927 is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests. WARN [C3P0PooledConnectionPoolManager[identityToken->z8kflt9b13bhzrj20fhq4|1c1e9fdc]-HelperThread-#13 ] com.mchange.v2.resourcepool.BasicResourcePool.run - com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@23244f40 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception: org.postgresql.util.PSQLException: FATAL: password authentication failed for user "vcops" at org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:400) at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:173)
      Workaround: If a vRealize Operations Manager node binds to an IPv6 address during deployment or installation, discard the node and install or create a fresh node with an IPv4 address for proper configuration and use.

    • Not all metrics instanced under the Network|Port Statistics resource group for vSphere Distributed Virtual Port Groups are collected
      Because vRealize Operations Manager creates many metrics for a dynamic environment with vSphere Distributed Virtual Port Groups, instanced metric collection under Network|Port Statistics is disabled by default.
      Workaround: To enable the collection of all metrics, perform the following steps 1 to 4 on all cluster nodes, then restart the cluster:
      1. Log in to the console as root.
      2. Open $VCOPS_BASE/user/plugins/inbound/vmwarevi_adapter3/conf/exclusionlist.txt in a text editor.
      3. Comment out the line with LWDistributedVirtualPortgroup|network|port_statistics|*::-.
      4. Save the file.

    • The SNMP adapter cannot monitor an interface index metric for a MIB file
      The SNMP adapter cannot monitor interface level metrics for MIB resources.
      Workaround: None.

    • REST API call getUsers does not return the default admin and other internal users
      When the REST API sends a call getUsers, vRealize Operations Manager does not return admin and other internal users in the response. If you use the REST API call getUsers, you cannot view the all the users of vRealize Operations Manager.
      Workaround: None.

    • Widget interaction is restricted in dashboards
      When you create a dashboard in vRealize Operations Manager with four or more widgets and select a parent object in the first widget, the corresponding child objects appear in upto three widgets.
      Workaround: Refresh the browser to view the corresponding child objects in all the widgets.

    • The configuration for the content pack for Log Insight is overwritten
      When you change the configuration details in the loginsight-agent file or from the user interface of vRealize Operations Manager, the configuration for the content pack for Log Insight is modified or overwritten. The ports from 9000 to 514 might be reset and the protocol changes to syslog instead of cfapi.
      Workaround: Disable the remote logging option from the vRealize Operations Manager user interface before you modify the loginsight-agent file. Do not save the changes again from the user interface when you use the content pack for Log Insight.

    • Upgrading hosts that are monitored by vRealize Operations Manager, to ESXi 5.1 Update 3 causes some metrics to move to other groups
      After you upgrade to ESXi 5.1 Update 3 or later the virtual disk Read Rate and Write Rate metrics appear under the Virtual Disk group instead of the Aggregate all Instance group.
      Workaround: Reconfigure the dashboards that use these metrics.

    • The content in the Summary page does not refresh
      The contents of the Summary page of the vRealize Operations Manager user interface are not updated when you click an object.
      Workaround: Refresh the Summary page.

    • 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.
          $ALIVE_BASE/user/conf/configuration.properties
        2. Add the following line to the properties.
          extensionUseDNS=true
          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 significantly different in version 6.0.3
      Following an upgrade to version 6.0.3, the vRealize Operations Manager Generated self-metric count value appears significantly lower than in version 6.0.
      Workaround: None. In version 6.0.3, 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, 6.0.1, 6.0.2, or 6.0.3 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.

    • 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.

    • 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

    • 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.

    • 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.

    • 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

    • 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 .
      Workaround:None.

    • 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

      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

    • Top of Page

    Documentation Issues

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

    • Best practices when migrating to vRealize Operations Manager
      When you migrate to vRealize Operations Manager, follow these best practices to ensure that migration does not fail because of resource constraints.
      • Disable the dynamic threshold calculation in vCenter Operations Manager 5.8 vApp using KB 2040008.

      • Set up a vRealize Operations Manager 6.0.x cluster on hosts that have sufficient resources and with no performance issues.

    • 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

    Top of Page