vRealize Operations Manager 6.1 Release Notes

VMware vRealize Operations Manager 6.1 Release Notes | 10 SEP 2015 | Build 3038036

Updated on: 17 Dec 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 in vRealize Operations Manager 6.1?

vRealize Operations Manager 6.1 is the latest release of VMware's integrated operations suite. Updates cover all major areas of the product including installation, configuration, licensing, alerting, dashboards, reports, and policies. This release introduces the following enhancements.

New Public Patch

A public patch for vRealize Operations Manager 6.1 addresses the following issues:

  • The object type that is returned from the MethodInstances parameter value is different from earlier versions.
  • Outbound SNMP messages do not contain alert messages when events are alerted via SNMP traps.
  • Upgrade from vRealize Operations Manager 6.0.x to 6.1 fails with the following error: Cluster offline: PAK install failed.
  • Dashboards do not display when the cluster is restarted.
  • A null point exception occurs when you stop the collection of an object.
  • Log Insight 3.0 cannot send alerts to a version of vRealize Operations Manager that is upgraded to 6.1.
  • When new alert notifications are created with a filter, no new alerts are sent out even though new alerts exist. Only canceled alerts are sent out.
  • When you configure outbound plug-ins, a null point exception occurs for instance level metrics.
  • If the description in an alert definition is empty, it results in an error from SNMP messages. This occurs in the Hyperic adapter.
To install the public patch, see KB 2139886

vRealize Hyperic Integrated into vRealize Operations Manager

With the addition of End Point Operations Management, vRealize Hyperic functionality has been extended to the vRealize Operations Manager core product, without the need to deploy vRealize Hyperic.

The new End Point Operations Management agent can:

  • Monitor OS, OS processes, and applications.
  • Autodiscover in-guest services and automatically map them to the infrastructure that is running them.
Previous vRealize Hyperic users should note the following limitations.
  • If you upgrade your vRealize Hyperic agents so that they become vRealize Operations Manager (End Point Operations) agents, new objects/data will appear in vRealize Operations Manager, and data collection for your original vRealize Hyperic resources will no longer receive new data. In addition, there is no utility for merging your original vRealize Hyperic resources/data with the newly-created objects/data.
  • vRealize Operations Manager does not support initiating In-Guest actions such as Service Restart, or initiating Top-N data collection. If you rely on these features, VMware recommends that you continue to use vRealize Hyperic for them.

New Features for vRealize Operations Manager

In addition to End Point Operations Management, version 6.1 of the vRealize Operations Manager features:

  • Custom Capacity Analysis - Time Remaining, Capacity Remaining, and Project Planning available for a user-definable, cross-cluster/cross-VC asset grouping
  • Intelligent Workload Balancing - initial placement, analytically driven workload move and cross-cluster rebalancing
  • 2X scale from 6.0 - Supporting up to 16 Nodes with 120K Objects and 30M Metrics.
  • Policy-driven automated remediation through the Action Framework
  • Alert enhancements - the ability to annotate and add actions to alerts
  • Extended High Availability to data collection through Collector Grouping
  • Removal of xDB for Global DB and KV Store
  • Improved Dashboard and Report design and layout options
  • Certified and documented back-up/restore and SRM-based DR
  • Integration with VMware Telemetry
  • vSphere SSO
  • Support for Pure IPv6 environments
  • Support for Windows Server 2012 R2
  • Management Pack authenticity (certificate) checking
  • Management Pack for Storage

For more information about the features in version 6.1, see the vRealize Operations Manager product page.

Documentation for the vRealize Hyperic, vRealize Infrastructure Navigator, vRealize Configuration Manager, and Storage Devices solutions has been moved from the vRealize Operations Manager documentation center to the VMware Solution Exchange. Documentation for the vSphere solution remains in the vRealize Operations Manager documentation center.

For more information, see the vRealize Operations Manager 6.1 Documentation Center.

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

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 instance, and deploy the vRealize Operations Manager virtual appliance through the vCenter Server instance. 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 6.1 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 Knowledge Base article 2093783 with the most current information about sizing and scaling.

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.

Important: Under Known Issues, see the Installation and Upgrade section for issues that might require a workaround before starting the upgrade.

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 an upgrade, the vSphere Web client might not display Health, Risk, and Efficiency badges for a machine that vRealize Operations Manager is monitoring. If that happens, use the Solutions page in vRealize Operations Manager to re-register vRealize Operations Manager with your vCenter Server:

  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, 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 the vCenter username and password, and click Register.

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 (vSphere, End Point Operations, vRealize Operations Management Pack for Storage Devices, vRealize Log Insight, vRealize Configuration Manager, vRealize Infrastructure Navigator, vRealize Hyperic, vRealize Automation, and Horizon View), the following adapters are supported for this release.

AdaptervApp Single NodevApp Multiple NodeRHEL Single NodeRHEL Multiple NodeWindows Single NodeWindows Multiple Node
AWS 2.0YesYesYesYesYesYes
EMC Smarts 3.1YesYesYesYesYesYes
GSSQL 2.18YesYesYesYesYesYes
Http PostYesYesYesYesYesYes
KeyNote 3.0YesYesYesYesYesYes
NSX for vSphere 2.0YesYesYesYesYesYes
NSX for MH 1.0YesYesYesYesYesYes
OpenStack 1.5YesYesYesYesYesYes
Port 1.1YesYesYesYesYesYes
Relationships 2.4YesYesYesYesYesYes
RepositoryYesYesYesYesYesYes
SNMP 2.1YesYesYesYesYesYes
TeamQuest 2.1YesYesYesYesYesYes
Text File 2.0YesYesYesYesYesYes
vCloud Director 3.0YesYesYesYesYesYes

vRealize Operations Management Pack for Storage Devices 6.0.1 is compatible with vSphere 5.1 Update 2 or later.

Top of Page

Known Issues

The known issues are grouped as follows:

Installation and Upgrade Issues

  • New Previous migration log might affect upgrade to this release
    When upgrading from 6.0.x to this release, vRealize Operations Manager might become unresponsive. The problem can occur if you have performed a migration from vCenter Operations Manager 5.8.x to vRealize Operations Manager 6.0.x, and then perform the upgrade. A migration creates a log file in 6.0.x that might be too large for the upgrade to this version to succeed.
    Workaround: Before running the upgrade, safely replace the log files with dummy files. Follow these steps on every node in the 6.0.x cluster.

    1. Log in to the console as root.
    2. Change directory to $STORAGE_DB_VCOPS/blob/migrationUpgrade.
    3. Copy all of the files to another directory.
    4. Delete all of the files under migrationUpgrade.
    5. In the migrationUpgrade directory, create empty files that have the same names as the deleted files.
    6. For all of the empty files, set the permissions by entering the following command:
      chown admin:admin $STORAGE_DB_VCOPS/blob/migrationUpgrade/*

    You can now run the upgrade from 6.0.x to this version.


  • New Upgrade on Windows does not complete
    When upgrading Windows-based deployments to this release, vRealize Operations Manager might become unresponsive. The problem is related to Python uninstallation and upgrade.
    Workaround: Take the following steps on each Windows node in the cluster. The procedure downloads the SysInternals Process Explorer, verifies that vRealize Operations Manager is stuck waiting for Python, and kills the unresponsive process.

    1. Download the SysInternals Process Explorer ZIP file from the following URL:
      https://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
    2. Extract the Process Explorer, and run it.
    3. In Process Explorer, Click View > Select Columns.
    4. Select Command Line, and click OK.
    5. In the tree of processes, find python.exe with a command line ending in pywin32_postinstall.py -install.

      If the entry does not appear immediately in Process Explorer, wait several minutes. When a multiple node cluster encounters this issue, the unresponsive process might take time to appear on every node.

      If the entry never appears in Process Explorer, do not proceed any further.

    6. To verify that the process is running and unresponsive, wait 5 minutes. When you are encountering this issue, the process never disappears.
    7. Right click the process, and select Kill Process. Take care to only kill this one process.

    The upgrade should now proceed normally.


  • New Upgrade on Windows does not complete with multiple upgrades
    When upgrading Windows-based deployments to this release, vRealize Operations Manager might become unresponsive. The problem is related to Log Insight uninstallation and upgrade, and occurs when more then one upgrade has happened, such as in the following examples:
    6.0.0 > 6.0.1 > 6.1.0
    6.0.0 > 6.0.2 > 6.1.0
    6.0.1 > 6.0.2 > 6.1.0
    The problem should not occur with only one direct upgrade to this version:
    6.0.0 > 6.1.0
    6.0.1 > 6.1.0
    6.0.2 > 6.1.0
    Workaround: Before starting the upgrade, take the following steps on each Windows node in the cluster. The steps uninstall the Log Insight agent and remove the install folder.
    1. Open the command prompt using the Run as Administrator option.
    2. Enter the following commands.
      > cd %ALIVE_BASE%\..\vmware-vcopssuite-installsupport\_strata_installation\msi
      > msiexec /uninstall VMware-Log-Insight-Agent.msi
      > cd %ALIVE_BASE%
      > rmdir /S /Q %ALIVE_BASE%\..\vmware-vcopssuite-installsupport\_strata_installation

    If you have already started an upgrade and encountered this issue, take the following steps on each Windows node in the cluster. The procedure downloads the SysInternals Process Explorer, verifies that vRealize Operations Manager is stuck waiting for the Log Insight agent to uninstall, uninstalls the Log Insight agent, and removes the install folder.

    1. Download the SysInternals Process Explorer ZIP file from the following URL:
      https://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
    2. Extract the Process Explorer, and run it.
    3. In Process Explorer, Click View > Select Columns.
    4. Select Command Line, and click OK.
    5. In the tree of processes, find Uninstall Strata.exe with a command line ending in Uninstall strata.exe -i silent.

      If the entry does not appear immediately in Process Explorer, wait several minutes. When a multiple node cluster encounters this issue, the unresponsive process might take time to appear on every node.

      If the entry never appears in Process Explorer, do not proceed any further.

    6. To verify that the process is running and unresponsive, wait 5 minutes. When you are encountering this issue, the process never disappears.
    7. Open a command prompt using the Run as Administrator option.
    8. Run the following commands to uninstall the Log Insight agent.
      > cd %ALIVE_BASE%\..\vmware-vcopssuite-installsupport\_strata_installation\msi
      > msiexec /uninstall VMware-Log-Insight-Agent.msi
    9. Back in Process Explorer, in the tree of processes, again find Uninstall Strata.exe with the command line ending in Uninstall strata.exe -i silent.
    10. Navigate to the child process below that. The child process name is java.exe with a very long command line.
    11. Right click the child process, and select Kill Process.

      Take care to only kill this one process. It will be the last process under Uninstall Strata.exe.

    12. Back at the command prompt, run the following commands to remove the Log Insight agent install folder.
      > cd %ALIVE_BASE%
      > rmdir /S /Q %ALIVE_BASE%\..\vmware-vcopssuite-installsupport\_strata_installation

    The upgrade should now proceed normally.


  • Upgrade does not complete
    When upgrading an earlier vRealize Operations Manager deployment to this release, the cluster might become unresponsive with the System Status page continuously displaying Waiting for Analytics. The problem occurs if any of your version 6.0.x capacity projects have expired by having an implementation date that is now in the past.
    Workaround: Before starting the upgrade, open the World > Projects page in version 6.0.x. When you display the page, vRealize Operations Manager updates the internal state of expired projects, and the unresponsive upgrade issue does not occur. If you have already started an upgrade and encountered this issue, contact VMware Technical Support for assistance.

  • Software Update fails with insufficient disk space error
    When a PAK file is selected for a software update, an error message appears if there is not enough disk space to upload the file.
    Workaround: The PAK file upload requires 2.5 GB of free space on the /storage/core partition. Delete unrequired files from /storage/core/support. Either manually delete files, or perform the following steps using the admin UI or the product UI:
    1. In the left pane, select Administration > Support.
    2. Select Support Bundles.
    3. Delete the unrequired files from the list that appears.

  • Analytics do not start after an upgrade
    After upgrading an earlier vRealize Operations Manager deployment to this release, the System Status page continuously displays Waiting for Analytics and Running for one or more nodes. In addition, an examination of services on those nodes reveals that all vRealize Operations Manager services are running except the Cassandra database service. The problem occurs when a Cassandra database cache file becomes corrupted.
    Workaround: On each node that continuously displays Waiting for Analytics, follow these steps:
    1. Log in to the console as root.
    2. Open $VCOPS_BASE/user/log/cassandra/system.log in a text editor.
    3. Verify that the last line of the log file is similar to the following:
      INFO [WrapperSimpleAppMain] 2015-08-24 22:16:50,651 AutoSavingCache.java:146 - reading saved cache {storage-location}/db/vcops/cassandra/caches/{cache-file-name}.db
      Note: The storage location varies depending on deployment type and whether you have modified the default. Also, the corrupted cache file name varies.
    4. Delete the corrupted cache file, listed in the last line of the log.
    5. Restart the Cassandra database service:
      service vmware-vcops start cassandra

  • Cluster expansion fails after upgrading vRealize Operations Manager 6.0.1 that included hot fixes
    If you upgrade a vRealize Operations Manager 6.0.1 cluster to this release, and the cluster had hot fixes or patches installed, attempts to add or remove nodes in the upgraded cluster might fail.
    Workaround: After the upgrade, follow these steps:
    1. On each node, delete 6.0.1 hot fixes or patches from the following directories. Only delete version 6.0.1 hot fixes or patches.
      • vApp and RHEL: $STORAGE/db/casa/pak/dist_pak_files
      • Windows: %STORAGE%\db\casa\pak\dist_pak_files
    2. Add or remove nodes.

  • Upgrade fails when vRealize Operations Manager 6.0.1 included hot fixes
    If you upgrade a vRealize Operations Manager 6.0.1 cluster to this release, and the cluster had hot fixes or patches installed, the upgrade might fail with the following error:
    upgrade.pak.failed.pak_manager
    Note: Hot fix HP2-6.0.1.2829977 described in KB 2116366 does not cause this issue.
    Workaround: Follow the steps in KB 2120616.

  • Upgrade fails to respond on Red Hat Enterprise Linux
    An upgrade fails to respond at step 5 of 9 on a Red Hat Enterprise Linux (RHEL) system. The cluster goes offline.
    Workaround: Re-apply the upgrade PAK file, and use the option to install even if the PAK is already installed.

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

  • Migrations require vRealize Operations Manager 6.0.x
    You cannot migrate vCenter Operations Manager directly to this version of vRealize Operations Manager. Instead, you follow a two-step process to migrate and import vCenter Operations Manager 5.8.x into vRealize Operations Manager 6.0.x, then use the vRealize Operations Manager Software Update option to upgrade vRealize Operations Manager 6.0.x to this version.

Top of Page

Cluster Management Issues

  • Cannot expand cluster when nodes are inaccessible
    If any cluster node is inaccessible, such as when network problems occur, you cannot add a data node or remote collector node. If you run the wizard to add a node, the administration interface shows an installation in progress message, but the expansion process never completes.
    Workaround: Before adding nodes, use the administration interface to remove the inaccessible node from the cluster. If you already started adding a node and the process is stalled, first try to restore the connection to the inaccessible node. If you cannot restore the connection, use the administration interface to remove the inaccessible node from the cluster, and delete the inaccessible node virtual machine.

  • Cluster might take longer to come online with master node NTP server
    In some cases, if you selected the option to have the master node serve as the Network Time Protocol (NTP) server, nodes take longer to synchronize with one another, and it takes longer than expected to bring the cluster online. In internal testing, delays as long as 45 minutes have been observed.
    Workaround: Synchronize vRealize Operations Manager to an external NTP server instead of the master node.

  • Adapter information is slow to reappear
    When you take the vRealize Operations Manager cluster offline and bring it back online, large scale deployments might be slow to restore the adapter information that appears in the administration interface. In some cases, it might take up to 10 minutes or more before the display recovers.
    Workaround: None. Refresh the browser until the adapters and status appear.

  • 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 cannot start when node name contains forward slash
    A cluster that includes a node with a forward slash (/) in its name cannot 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.

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

  • 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 Virtual Machines will not Power On, even though vRealize Operations Manager Reports Capacity Remaining
    In cases where there is one virtual machine larger than the others in the cluster, it can result in vRealize Operations Manager reporting that there is capacity and time remaining, yet Admission control in vSphere will not allow the virtual machines to be powered on.
    Workaround: The user needs to determine the slot size and then increase the buffer threshold using policies.

  • New Last Synchronized Column does not get Updated when you click Synchronize User Groups
    Last synchronized column doesn't get updated immediately when you click 'Synchronize User Groups' icon on Authentication Sources page.
    Workaround:None

  • New SSO users logging out of vRealize Operations Manager cannot log out of the vCenter Web Client
    When SSO users are logged into vRealize Operations Manager and the vCenter Web Client, logging out of vRealize Operations Manager and then selecting the vCenter Web Client may cause the Client to hang.
    Workaround:None

  • New SSO users logging out of vRealize Operations Manager cannot log out of the vCenter Web Client
    When SSO users are logged into vRealize Operations Manager and the vCenter Web Client, logging out of vRealize Operations Manager and then selecting the vCenter Web Client may cause the Client to hang.
    Workaround:None

  • New SSO with Active Directory over LDAP does not support domain trust
    If your SSO source has been set up with AD over LDAP, you cannot log in to vRealize Operations Manager using the domain trust. Domain trust is not supported by the LDAP protocol. vRealize Operations Manager enables you to import groups from parent and child domains, but not to log in using child domain user accounts.
    Workaround: None

  • New After an upgrade of vRealize Operations Manager to this release, accessing the views named Alerts that are currently active and Symptoms results in an internal server error
    When you upgrade vRealize Operations Manager from 6.0.1 or 6.0.2 to this release, the upgrade does not overwrite the existing views, including any modifications that you made to them, and does not overwrite any custom views that you created. Because the views named Alerts that are currently active and Symptoms are not upgraded, when you attempt to access these views, an internal server error occurs under the following circumstances.
    • Occurs only if during the upgrade you did not select the check box named Reset predefined content to a newer version provided by this update. User modifications to predefined Alerts, Symptoms, Recommendations, and Policies will be overwritten.
    • Occurs always for each custom view that you created before the upgrade, where the subject is set to Alert and the data metric being used is Alert Info.
    • Occurs always for each custom view that you created before the upgrade, where the subject is set to Symptom and the data metrics being used are Symptom Name and Triggered On.
    Workaround: After the upgrade is finished, follow these steps for each view to ensure that the view performs correctly:
    1. Click the view, click Edit, and navigate to the Data workspace.
    2. In the Data area, click the affected data item for the particular view.
      • For the view named Alerts, click and remove Alert Info.
      • For the view named Symptoms, click and remove Triggered On. If you update this view, you must also expand Symptom Applicable Metrics, and add the metric named Triggered On to the view.
      • For a custom view where the subject is set to Symptom and the data metrics being used are Symptom Name and Triggered On, click and remove Symptom Name, then click and remove Triggered On. If you update this view, you must also expand Symptom Applicable Metrics, and add the metric named Triggered On to the view.
      • For a custom view where the subject is set to Alert and the data metric being used is Alert Info, click and remove Alert Info.
    3. Click Save to save the modified version of this view.
    .
  • New Workload placement excludes virtual machines that participate in DRS and SDRS affinity rules
    Workload placement excludes virtual machines that have DRS or SDRS rules assigned, and considers other virtual machines that have high workloads when determining candidates for the move.
    Workaround: None

  • New Rebalance on cluster might not present all hosts in rebalance plan
    When a cluster has unbalanced stress due to CPU or memory being spread unevenly across the hosts in the cluster, and you click Rebalance Container, the rebalance plan will not present the destination hosts that do not have access to the datastores in which the virtual machines to be vacated currently reside.
    Workaround: Ensure that every host in the cluster shares the same shared datastores, and that every VMDK of every virtual machine in the cluster resides on shared datastores.

  • New Alerts that can be automated do not appear as automatable in policies
    After you configure the vCenter Python Actions Adapter, restart the cluster to ensure that the alerts that have actionable actions are recached properly for the policies that are configured. Failure to do so might result in an incorrect Automate state for the Alert Definitions in your policies.
    Workaround: Restart the cluster to refresh policy data.
    1. Log in to the vRealize Operations Manager Administration user interface, using the format https://<IP address>/admin/login.action.
    2. In the left pane, click System Status.
    3. Click Take Offline, and wait for the cluster to go offline.
    4. Click Bring Online.
    After you log back in to the vRealize Operations Manager instance, you can automate any alert that is automatable.

  • New Rebalance Container action continues to recommend the same rebalance plan after failure
    When a Rebalance Container action fails, and vCenter Server indicates that the operation is not allowed in the current state, the rebalance container action recommends the same rebalance plan.
    Workaround: Correct the problem in your environment, then attempt to run the Rebalance Container action again.

  • New Automate flag is not being reset, which enables an alert to incorrectly revert to the Automate enabled state
    When an alert no longer meets the requirements for automation, the alert should not revert to the Automate enabled state unless you manually place the alert back into the Automate enabled state.
    In the policy alert definitions, the Automate enabled state for the alert definition appears as Local with a green check mark, because it was previously automated. If you change the recommendation for an alert that previously had a recommendation with an action as the highest priority, the alert might return to the Automate enabled state.
    This behavior can occur when you add a second recommendation that does not have an action to the alert, then place the second recommendation as the highest priority recommendation for the alert, and then delete the second recommendation that was previously set to the highest priority.
    Workaround: If the case has occurred where the alert has reverted back to the Automate enabled state, and you do not want to automate your alert, you can modify the Automate value in the associated policy.

  • New Alert recommendation does not indicate how to restart only the remote collector service
    When your environment includes a master node and a remote collector node, and you take the remote collector offline, the alert recommendation that indicated that you take the remote collector node offline and bring it back online does not describe how to restart only the remote collector service.
    Workaround: Log in to the Administration user interface, and select the Remote Collector Node on which the alert triggered. Click Take Offline, and wait for the node to go offline. Then click Bring Online to bring the remote collector services back online.

  • New Virtual machine migration fails in vCenter Server during Rebalance Container action
    When you move virtual machines during the Rebalance Container action, if the amount of changing memory for the virtual machine is greater than the available network bandwidth, the migration fails.
    Workaround: When the virtual machine is not as busy, or when additional network bandwidth is available, try to move the virtual machine again by using the move action.

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

  • When you take an object to resource maintenance mode the applied policy changes to vSphere Solution's Default Policy
    vRealize Operations Manager changes the object policy to vSphere Solution's Default Policy during the maintenance mode. When the maintenance time is complete the object will return to the policy that you applied.
    Workaround: None

  • 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

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

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

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

  • 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 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.
  • Timeout or system error occurs on virtual machine during rebalance plan
    When you run the Rebalance Container action, the connection to the remote host might close. This behavior can occur under the following conditions:
    • A timeout occurs during the move of the virtual machine.
    • A general system error occurs when you migrate the virtual machine to a host, indicating that the action failed because the host was out of memory.
    Workaround: If the rebalance plan fails, use the Move VM action or the vSphere Web Client to manually move the virtual machines that failed during the rebalance action.

  • When vRealize Operations Manager is accessed by the host name only, log in via SSO fails
    When you access vRealize Operations Manager through the hostname, for example, https://ui/index.action#/, the following error is displayed: HTTP Status 400 - Unable to process request.
    Workaround: When you log in via SSO, access vRealize Operations Manager via the IP address or FQDN. For example, https://ui/index.action#/ or https://ui/index.action#/

  • Rebalance Container action is not available if the user does not have access to all objects in the container
    Users who have access to all objects in a cluster, data center, or custom data center, can run the Rebalance Container action to move virtual machines to other hosts. When the user does not have access to all of the objects in the container, the rebalance action is not available.
    Workaround: Verify that you have access to all objects in the container.

  • Workload placement might fail if the ESXi host version is missing
    If vCenter Server fails to provide the ESXi host version number to the vCenter Server properties collector in the vCenter Adapter, a compatibility problem occurs, which can cause the Rebalance Container action and the workload placement to fail. This failure might persist until the vCenter Adapter establishes a new connection to the vCenter Server instance.
    Workaround: Restart the vCenter adapter instance. In the vSphere Web Client, view the summary and version information for the ESXi host machines.

  • Launch in Context cannot be removed after deleting vRealize Log Insight server
    If vRealize Log Insight is integrated with vRealize Operations Manager, it appears as a Launch in Context selection. If the vRealize Log Insight server is deleted, the selection still appears. There is no button to remove the selection.
    Workaround: Select Administration > Inventory Explorer and delete the listed vRealize Log Insight objects. For detailed instructions, see KB 2126679.

  • Presorting the alerts list by criticality displays critical alerts at the top of the list
    By default, alerts are sorted by criticality. If you change the sort order, the sort is saved with your preferences. This behavior applies to the global alerts list, and the Health, Risk, and Efficiency alerts lists.
    Workaround: None

  • Logging out from other SSO-supporting applications does not log you out from vRealize Operations Manager
    When logged into both vRealize Operations Manager and another application through SSO, if you log out from the other application, you remain logged in to vRealize Operations Manager.
    Workaround: Manually log out of vRealize Operations Manager to end the SSO session.

  • SSO registration is not automatically updated when you add a new node if you are using a load balancer
    If you are using a load balancer in your vRealize Operations Manager cluster and you have created an SSO Authentication source, without granting vRealize Operations Manager the Administrator role in PSC, when you add a new node, the node will not automatically register with the SSO server, and you will not be able to log into vRealize Operations Manager using SSO.
    Workaround: Re-register the SSO authentication source after adding a new node.

  • Some symptoms for metrics are not canceled for objects in an unknown or no-data-received state
    When vRealize Operations Manager stops collecting new values for a metric, vRealize Operations Manager cancels symptoms when the last collected value of a metric becomes stale. In some cases, a symptom is not canceled. For example:
    • When an adapter is stopped, vRealize Operations Manager stops processing its objects, including the cancelation of stale symptoms.
    • When a vCenter Server instance is deleted and the adapter instance is not deleted, vRealize Operations Manager stops processing its objects, including the cancelation of stale symptoms.
    vRealize Operations Manager cancels stale symptoms for metrics, but does not cancel symptoms for properties or events, such as faults.
    Workaround: None

  • If an action exceeds confirmation timeout, the confirmation step of the action might fail
    When you perform an action that includes a confirmation step, such as Delete Unused Snapshots for VM, which then confirms that the snapshot was deleted, if vRealize Operations Manager does not confirm that the action occurred in the specified time, it fails the step and displays the failure in the job summary status area in Administration > Recent Tasks.
    Workaround: None

  • Unable to import an LDAP user group
    Attempts to import an LDAP user group that contains users that no longer exist in the LDAP database will fail.
    Workaround: None

  • Unable to extract installation path for an End Point Operations Manager agent on a Linux machine
    When trying to install an End Point Operations Manager agent on a Linux machine, an error message indicates that the installation path cannot be extracted.
    Workaround: Use only ASCII characters when specifying the agent installation path on a Linux machine, or set the encoding of the Linux machine and SSH client application to UTF-8.

  • Icons in the management packs are not displayed after installation
    After you install a management pack and then open the Environment overview pane in the vRealize Operations Manager user interface, the adapter and object type icons do not appear.
    Workaround: Manually redescribe the adapter.
    1. Log in to the vRealize Operations Manager user interface.
    2. In the left pane of vRealize Operations Manager, click the Administration tab and click Support.
    3. Select and click Redescribe.

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

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

  • Self-Metric count is significantly different in version 6.0.2
    Following an upgrade to version 6.0.2, the vRealize Operations Manager Generated self-metric count value appears significantly lower than in version 6.0.
    Workaround: None. In version 6.0.2, 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, or 6.0.2 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

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

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

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

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

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

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

  • Metric for 'Outstanding I/O requests' might be inaccurate on some vSphere object types
    The datastore|demand_oio metric that appears as Datastore|Outstanding I/O 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.
    Workaround: None

  • Some features are missing after you transition to vRealize Operations Manager Standard edition
    After you run vRealize Operations Manager 6.1 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

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

  • 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

  • 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

  • Projects and workload placement do not acknowledge disk I/O and network I/O
    Projects do not impact disk I/O and network I/O metrics. The placement plan might include placing virtual machines on hosts with high disk I/O or network I/O workload, or datastores with high disk I/O workload.
    Workaround: None

  • Historical movement of virtual machines impact might not be reflected in Project Visualization Chart
    Moved or deleted virtual machine impact might not be reflected in the visualization chart which can result in higher demand than expected.
    Workaround: None

  • Workload placement ignores projects reserved to the cluster level
    Projects do not impact descendant objects. As a result placement does not consider capacity reserved by projects created at the ascendants level. For example, if you create a project at cluster level to reserve capacity, the project is not considered when you do placement on the hosts and datastores in the cluster.
    Workaround: None

  • When you do a rebalance on a container with hosts of different capacities, the balance might not be achieved in terms of usage and demand percent
    When you do a rebalance on a container, host candidates with larger absolute available capacity is considered first to place virtual machines. As a result, when hosts are of different capacities, balance may not be achieved in terms of usage and demand percent.
    Workaround: None

  • The Network Share plug-in cannot work with path that contains non-ASCII characters
    If the path in your Network Share plug-in contains non-ASCII characters the connection might fail.
    Workaround: None

  • An object goes to maintenance after you delete the maintenance schedule
    If you apply maintenance schedule to an object through a policy and then delete the maintenance schedule, the objects still goes to maintenance.
    Workaround: Remove the maintenance schedule from the policy before you delete the schedule.

  • When manually running a backup job for vROPs using vSphere Data Protection, the task details might show that the job is stuck at 92%, when in fact it is running.
    When you run manually a backup job in vSphere Data Protection, the task details in the Running tab of the Recent Tasks pane might show that the job is stuck at 92%, when in fact it is still running.
    Workaround: To verify that the backup job is not stuck, follow these steps:
    1. Use SSH to log in as admin to vSphere Data Protection Appliance.
    2. Run the mccli utility in the console.
    3. Run the command: mccli activity show. This command lists all backup and restore jobs and their status.
    4. In the Client column, search the backup ID and the corresponding virtual machines.
    5. In the Status column, verify that the job is still running.

Top of Page

User Interface Issues

  • Applications for HTTP Post adapter are not listed in Open in External Application drop-down menu
    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 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 User Interface
    If an adapter is defined with multiple Launch in Context configurations, only one external application selection is listed in the user interface. The user cannot control the selection, and any of the Launch in Context configurations might be listed.
    Workaround: None

  • Some Report Template tab toolbar options do not work after logging 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 an Internet Explorer 10, Firefox, or Chrome browser.

  • 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

  • The filter menus in Policies workspace step Collect Metrics and Properties do not work correctly
    When you deselect an option from the State, KPI, or DT drop-down menus, the filter hides all attributes no matter of their settings.
    Workaround: Save and reopen the policy.

  • The filters in Content area are not saved when you switch between pages
    If you add a filter to Dashboards, Plug-ins, Actions, or Recommendations in Content area and you leave the page, vRealize Operations Manager does not retain the filter.
    Workaround: None

  • The Projects workspace visualization chart does not work correctly
    When you create a Project and remove a scenario, the visualization chart does not update accordingly.
    Workaround: None

  • The Recommendations dashboard does not show the Health and Efficiency widgets
    When you delete the Universe resource, the Recommendations dashboard doesn't show the Health and Efficiency widgets and displays message Failed to get LDU IDs for specified resources. All widgets configured to show data for Universe resource stop working.
    Workaround: Restart one of the collectors or the cluster and wait for the Universe resource to be recreated. Edit the configuration of each widget in the dashboard, and from the resource tree expand and select the Universe resource.

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

  • A PDF report file might not include all data from a widget that has a scrollbar
    When you generate a report that contains a custom dashboard with a widget that has a scrollbar, the downloaded PDF file might not include all data of the widget.
    Workaround: Increase the height of the widget in the dashboard to fit all the data.

Top of Page

End Point Operations Agent Manager Issues

  • New Self-monitoring Badges did not Start Automatically for 16-Node Cluster
    Some adapter instances (particularly Container and vR Ops adapter instances) may change their collection state to stopped. As a result some badges may show question marks (for Universe, World, and other resources).
    When the collector is down/not available, and the system is not consistent (i.e. the nodes/collectors are under pressure and/or restarting frequently) the adapter failover may not complete successfully, and as a result Adapter Instances may remain in "intermediate" stopped state. As a result the related resource badges may not show data. In this case no any error message expected in the UI. This issue may happen only for adapter instances which are not pinned to any specific collector, but configured to be run on collector group (the system is running vR Ops and Container adapter instances on default collector group).
    Workaround: Check the adapter instances collection states, if they are in stopped state and nobody stopped them manually, and they are running on collector group, then most probably this is the case. You need to manually start monitoring the stopped adapter instance resources.

  • New vRealize Operations Manager Monitoring a Large Scale Environment is not Performing as Expected
    If you have a large scale vRealize Operations Manager monitored environment, you may experience one or more of the following issues:
    • The user interface is responding slowly
    • Metrics are slow to be displayed

    Workaround: Determine the areas of the environment in which the latency is greater than 20 milliseconds and install a remote collector in those areas.

  • New Visualization Chart will not Show Data for World or Custom Group Objects
    The Visualization Chart will not be shown for World or custom group objects.
    Workaround: None.

  • New No data returned when running ICMP check
    When attempting to run an ICMP check for remote monitoring from an Agent running on a Windows platform, no data is returned.
    Workaround: Do not use ICMP checking from an agent that is deployed on a Windows platform.

  • New Error message logged after installing non-JRE version of agent
    Following the installation of a non-JRE version of the End Point Operations Manager agent, the error Cannot support TLS_RSA_WITH_AES_256_CBC_SHA with currently installed providers, or some other similar error, appears in the log files. The error might occur because there is no Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy files in the Java version.
    Workaround: Install a JRE version End Point Operations Manager agent or add Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy files to your Java version.

  • New The End Point Operations Manager agent stops responding while starting with the vCenter 6.0 Appliance
    The End Point Operations Manager agent stops responding while starting with the vCenter 6.0 Appliance because the default shell for root is /bin/appliancesh which impacts the /etc/init.d/epops-agent script used to start the agent.
    Workaround: KB 2133716.

  • End Point Operations Manager vCenter solution fails to discover single sign-on on Linux
    vSphere SSO is not discovered on Linux because file permissions for /var/log/vmware/sso/tcserver.pid only allow root access, and the End Point Operations Manager agent does not run as root by default.
    Workaround: KB 2133716.

  • Use the latest Java version when installing an End Point Operations Manager agent
    When you install a non-JRE version of End Point Operations Manager agent, to avoid being exposed to security risks related to earlier versions of Java, VMware recommends that you only use the latest Java version.

  • Receiving generic error message after installing non-JRE version of agent
    After installing a non-JRE version of the End Point Operations Manager agent, or when attempting to use a Java version other than that provided with the End Point Operations Manager agent, you receive the error message Server might be down (or wrong IP/port were used), and the agent is not registered. The error might occur because there is no Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy files in the Java version.
    Workaround: Install a JRE version End Point Operations Manager agent or add Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy files to your Java version.

  • End Point Operations Manager agent did not install correctly in Windows environment
    You used a Windows installer to install an agent in an environment in which either an End Point Operations Manager or vRealize Hyperic agent was already installed. The agent installation completed without any errors being reported but the agent did not install correctly.
    Workaround: Verify that you do not have any End Point Operations Manager or vRealize Hyperic agent installed on your environment before running the agent Windows installer.

  • End Point Operations Manager agent continues to collect and report metrics on an object in maintenance mode
    While an object is down for maintenance, the vRealize Operations Manager server ignores all incoming data for the object. However, the End Point Operations Manager agent continues to collect metrics on the object and reports those metrics to the server. The server discards the metrics.
    Workaround: When you are performing maintenance operations, it is good practice to stop the End Point Operations Manager agent and to restart it after the maintenance is complete to avoid unnecessary system overhead.

  • There is no data continuity between the MSSQL servers in a cluster after enabling the Microsoft "Failover Cluster Command Interface" feature
    After enabling the Failover Cluster Command Interface feature, there is no data continuity between the MSSQL servers in a cluster that were discovered before the feature was enabled.

    MSSQL clusters are discovered using Microsoft's "Failover Cluster Command Interface" (cluster.exe) feature. This feature must be installed on each node of an MSSQL cluster. If it is not installed on each node, MSSQL servers are discovered as standalone servers instead of part of a cluster. If the feature is installed after the End Point Operations Manager agent, data continuity between a standalone MSSQL server and the clustered ones, is not guaranteed.
    Workaround: Install the Microsoft Failover Cluster Command Interface feature before installing the End Point Operations Manager agent.

  • Unable to install End Point Operations Manager agent from an EXE intaller to a path containing non-ASCII characters
    A known issue in Oracle prevents the installation of the End Point Operations Manager agent into directories with names that contain characters that are not supported by the system locale. For more information, see bug 4895647 in the Oracle knowledge base http://docs.oracle.com/javase/8/docs/technotes/guides/install/windows_jdk_install.html
    Workaround: Verify that the user and system locales are identical, and that the installation path contains only characters that are part of the system locale's code page. You can set user and system locales in the Regional Options or Regional Settings control panel.

  • Plug-ins that were imported from vRealize Hyperic do not work correctly in vRealize Operations Manager on Windows platforms
    Due to differences in the modeling options between vRealize Hyperic plug-ins and vRealize Operations Manager plug-ins, vRealize Hyperic plug-ins that include the <config type="control" platform="Win32"> option might not be discovered or might not work correctly in vRealize Operations Manager Windows platforms without modification.
    Workaround: If your plug-in uses the following sample format
    <config type="control" platform="Win32">
    <option name="service_name"
    description="Apache Service Name (Relevant to Windows only, does not affect other platforms)"/>
    </config>

    change the code as follows
    <config>
    <option name="service_name"
    default="Apache Service Name" description="Apache Service Name (Relevant to Windows only, does not affect other platforms)" platform="Win32" />
    </config>

    Note that this modification causes the service_name to appear as the identifier for the resourceKind.

  • Agent did not install correctly in Windows environment
    You used a Windows installer to install an agent in an environment in which either an End Point Operations Manager or vRealize Hyperic agent was already installed. The agent installation completed without any errors being reported but the agent has not installed correctly.
    Workaround: Verify that you do not have any End Point Operations Manager or vRealize Hyperic agent installed on your environment before running the agent Windows installer.

  • Overrriding agent configuration data for MSSQL objects causes inconsistent behavior
    If you set the value of Override agent configuration data to true when editing an MSSQL object (MSSQL, MSSQL Database, MSSQL Reporting Services, MSSQL Analysis Service, or MSSQL Agent) that runs in a cluster, inconsistent behavior might result.
    Workaround: Do not override the agent configuration data for these MSSQL objects.

  • Metrics are not reported after an End Point Operations Manager agent is started using Windows Services
    If you stop an End Point Operations Manager agent by using Windows Services, and remove the data directory from inside the agent installation directory, when you start the agent again, using Windows Services, no metrics are collected.
    Workaround: If you are deleting the data directory, do not use Windows Services to stop and start an End Point Operations Manager agent. Stop the agent using epops-agent.bat stop. Delete the data directory, then start the agent using epops-agent.bat start.

  • ResourceAvailability metric is not being reported every minute
    Due to rounding in metric time calculation, there can be situations in which the metric is rounded up making it appear that there are gaps in the metrics reported by the End Point Operations Manager agent. The metrics are fully reported.
    Workaround: None

  • Previously detected objects no longer monitored after reinstalling an End Point Operations Manager agent
    When you reinstall an End Point Operations Manager agent on a virtual machine, for example following an upgrade, objects that had previously been detected are no longer monitored.
    Because vRealize Operations Manager already has the machine resources from the earlier installation, the configuration (including the credentials) are not propagated from vRealize Operations Manager server back to the agent, meaning that any objects that require credentials are not monitored, and no metrics are collected from them.
    Workaround: Do not restart the End Point Operations Manager agent until the plug-in synchronization is complete.

  • Unable to extract installation path for an End Point Operations Manager agent on a Linux machine
    When trying to install an End Point Operations Manager agent on a Linux machine, an error message indicates that the installation path cannot be extracted.
    Workaround: Use only ASCII characters when specifying the agent installation path on a Linux machine, or set the encoding of the Linux machine and SSH client application to UTF-8.

  • Relationship objects of a deleted tomcat server object are not monitored following an End Point Operations Manager agent restart.
    If you delete the tomcat server object from a virtual machine, the tomcat service objects are no longer monitored, as expected. However, when you restart the End Point Operations Manager agent, although you can see the related tomcat service objects under the server object in the user interface, the service objects are not monitored.
    Workaround: Select a service object that is not being monitored and click Stop Collecting, then click Start Collecting. Repeat the process for each unmonitored service object.

  • Non-definition of localhost as the loopback address
    If you do not define localhost as the loopback address, the End Point Operations Manager agent does not register and the error Connection failed. Server may be down (or wrong IP/port were used). Waiting for 10 seconds before retrying. is displayed.
    Workaround:
    1. Open the hosts file /etc/hosts on Linux or C:\Windows\System32\Drivers\etc\hosts on Windows.
    2. Modify the file to include a localhost mapping to the IPv4 127.0.0.1 loopback address, using 127.0.0.1 localhost.
    3. Save the file.

  • Registering an End Point Operations Manager agent in an environment that supports both IPv4 and IPv6
    You cannot register an End Point Operations Manager agent in an environment that supports both IPv4 and IPv6. In the event that you attempt to do so, you receive the message Connection failed. Server may be down (or wrong IP/port were used). Waiting for 10 seconds before retrying.
    Workaround:
    1. On the vRealize Operations Manager machine, in the file, $VCOPS_BASE/user/conf/tomcat-enterprise/wrapper.conf (Linux), or %VCOPS_BASE%\user\conf\tomcat-enterprise\wrapper.conf (Windows), change wrapper.java.additional.23=-Djava.net.preferIPv6Addresses=true to wrapper.java.additional.23=-Djava.net.preferIPv6Addresses=false.
    2. Save the file.
    3. Run service vmware-vcops restart api

  • Non-display of "Endpoint Operations Management World"
    After a period of approximately five minutes following the deployment of an End Point Operations Manager agent for the first time, if you do not see "Endpoint Operations Management World" and an "Operating Systems" group entry under the Operating Systems hierarchy, it indicates that these objects have not been created.
    Workaround: Log in to the virtual machine and run service vmware-vcops restart collector.

  • End Point Operations Manager Agent already running message
    When you attempt to start an End Point Operations Manager agent you might receive a message that the agent is already running.
    Workaround: Run ./bin/ep-agent.sh stop before starting the agent.

Top of Page

Documentation Issues

The following items did not make it into the initial documentation for this release.

  • New Visual C++ redistributable packages required on Windows
    Before installing vRealize Operations Manager on Windows, you must have both the 32-bit and 64-bit versions of the Microsoft Visual C++ 2008 SP1 Redistributable Package installed as prerequisites. You can add them by installing VMware Tools or by downloading and installing them separately.
    Visual C++ 2008 SP1 32-bit
    Visual C++ 2008 SP1 64-bit
    Without the Visual C++ redistributable packages, the installation fails.

  • New Change to supported operating systems for End Point Operations
    In the initial vRealize Operations Manager documentation, the topic Supported Operating Systems for the End Point Operations Manager Agent incorrectly stated that the following operating systems are supported:
    Windows 2003 Server R2
    HP-UX 11.11 or higher
    Ubuntu 10.11
    These operating systems are not supported in this release.

Top of Page

Resolved Issues

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

  • 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

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

  • vSphere Web Client goes into an infinite loop when an SSO session is terminated from vRealize Operations Manager
    When you log into the vCenter Web Client in one browser tab, and then log into vRealize Operations Manager in another, if automatic SSO is not enabled, and you are not part of a user group that has been imported into vRealize Operations Manager, login will fail. Selecting the link that is displayed in the error message, will end the SSO session in vRealize Operations Manager, but the vCenter Web Client session in the first tab will enter an infinite loop.

  • Unable to create Text File adapter instance
    You cannot create a Text File adapter instance if the Input Data folder field length exceeds 80 characters. If the field length exceeds 80 character, user interface validation fails.

  • When the name of an SSO user group is changed in the Active Directory, the name change is not updated immediately in the token
    If you change the name of an imported SSO group in the active directory, users belonging to the group should not be unable to log in to vRealize Operations Manager directly after the name change. However, due to a delay in the local LSA caching, users of the group can continue to log in.

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

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

  • 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

  • Logging in to vRealize Operations Manager through the Active Directory (AD) or LDAP authentication sources fails
    If you belong to multiple domains in the same active directory, for example johndoe@parent_domain.com and johndoe@child_domain.com, when you log in to vRealize Operations Manager and you select AD as the authentication source, you must log in with your user name and domain.
    If you log in with just your user name, log in will fail.

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

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

  • The Topology Graph widget does not correctly display the relationship between virtual machines 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 virtual machines have a Runs-on relationship with hosts, the paths between virtual machines and hosts should appear as a single line. The Topology Graph widget incorrectly shows the relationship between a virtual machine and host with a double line.

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

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

  • 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 virtual machines on the host. The host demand aggregates the virtual machine demand with the virtual machine reservation and limit. So the host demand and the total virtual machine demand might appear mismatched. For example, when virtual machines on the host have a large reservation, the host demand is greater than the total virtual machine demand.

  • Display shows no data for Last month, Last 6 months, or Last Year
    Charts with date controls that limit the data displayed to a selected time frame reported no data if the selection was Last month, Last 6 months, or Last Year.

  • Cannot replace the replica node with remote collectors present
    After nominating a new replica node, the cluster status showed that the old node was not removed. You had to remove remote collectors before replacing a replica node.

  • Failed to finish adding remote collector nodes to a running cluster
    When attempting to expand an online cluster, you added a new remote collector node and clicked Finish Adding New Nodes in the administration interface. The cluster state updated to Online, but text beneath the state showed Failed to add new node.

  • Unable to start vRealize Operations Manager services on Red Hat Enterprise Linux 6.5 x64
    After you installed vRealize Operations Manager, when you attempted to connect to the vRealize Operations Manager Web interface and start vRealize Operations Manager, the cluster was not online, and you had to install the libaio package. The package is now documented as a prerequisite.

  • Upgrades require Java on vRealize Operations Manager for Linux
    Before you upgraded vRealize Operations Manager for Red Hat Enterprise Linux (RHEL), you needed to have a default or other version of Java installed, in addition to the Java version that vRealize Operations Manager installed at $VMWARE_JAVA_HOME.

Top of Page