vRealize Operations Manager 6.2 Release Notes

VMware vRealize Operations Manager 6.2 Release Notes | 02 Feb 2016 | Build 3445568

Check frequently for additions and updates to these release notes.

What's in the Release Notes?

The release notes cover the following topics:

What's New?

vRealize Operations Manager 6.2 is the latest release of the VMware integrated vRealize 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.

  • Enhanced Distributed Resource Scheduler (DRS) Integration
    vRealize Operations now offers enhanced integration with the vCenter Distributed Resource Scheduler (DRS) when making and executing workload placement recommendations. The vRealize Operations Manager analytics determine cross-cluster placement opportunities, while vCenter Distributed Resource Scheduler determines the best destination within clusters. The enhanced integration uses all DRS rules, constraints, and enterprise-class capabilities.

  • New Workload Utilization Dashboard
    The Workload Utilization Dashboard enables you to see the object workload utilization for Cluster, DataCenter, and Custom DataCenter containers. The new dashboard incorporates an updated Utilization widget, capable of operating in either a capacity or workload utilization mode.

  • Ability to Import Single Sign-On Users
    As an Administrator, you can now add and authorize new users for vRealize Operations Manager by importing them from a Single Sign-On source.

  • Telemetry Enablement on Upgrade
    This release includes a one-time dialog after you upgrade that allows you to participate in the VMware Customer Experience Improvement Program. This program collects anonymous product configuration and usage data to enhance future versions of vRealize Operations.

  • Portable Licensing
    The portable licensing feature adds the ability for customers to license use of the product in vSphere as well as non-vSphere environments.

For more information on each of these features see vRealize Operations Manager 6.2

Top of Page

System Requirements

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
  • vRealize 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
  • vRealize Hyperic 5.8.4.x

Browser Support

This vRealize Operations Manager release supports all current web browsers, although only the following browsers have been tested with this release:

  • Google Chrome: Version 46 and 47
  • Mozilla Firefox: Version 42 and 43
  • Safari: Version 9
  • Internet Explorer: Version 11
  • Note: Slower performance has been observed on Internet Explorer 10 or 11.

The minimum supported resolution is 1024 x 768.

Applying License Keys

vRealize Operations Manager 6.2 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 calculations that provide a recommendation based on the number of objects and metrics you expect to monitor.

Top of Page

Installing vRealize Operations Manager

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

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

Adapter Support

In addition to the VMware adapters (vSphere, Endpoint Operations Manager, vRealize Operations Management Pack for Storage Devices, vRealize Log Insight, vRealize Configuration Manager, vRealize Infrastructure Navigator, vRealize Hyperic, vRealize Automation, and Horizon View), you can see the supported adapters here.

Each of these adapters works with Virtual Appliance Single Node, Virtual Appliance Multiple Node, RHEL Single Node, RHEL Multiple Node, Windows Single Node, and Windows Multiple Node configurations.

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

Top of Page

Upgrading From the Previous Version

Separate processes are required for upgrading vRealize Operations Manager and for upgrading the Endpoint Operations Management Agent.

Upgrading the Endpoint Operations Management Agent

Before you can upgrade an Endpoint Operations Management agent, various prerequisites must be satisfied. A specific process must be followed to ensure successful upgrade. The necessary information is documented in KB 2137709.

Upgrading vRealize Operations Manager

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.
      Virtual appliance clusters

      The virtual appliance 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 virtual appliance clusters, the file is: vRealize_Operations_Manager-VA-xxx.pak
      Virtual Appliance heterogeneous clusters

      The virtual appliance 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, virtual appliance or non-virtual appliance.
    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

Known Issues

The known issues are grouped as follows:

Installation and Upgrade Issues

  • Python language bindings for the vRealize Operations public REST API are missing after upgrade from version 6.1 to 6.2
    For improved security, vRealize Operations Manager 6.2 includes a new Python version. During the upgrade process, the directory containing the Python language or client bindings for the vRealize Operations public REST API is deleted. As a result, the subsequent installation of any management pack or solution that uses the vRealize Operations public REST API fails with an error.
    Workaround: Reinstall the Python language bindings that still exist on the vRealize Operation Manager instance. Log in (SSH/RDP) to vRealize Operations Manager and execute the following command on every node in the cluster:
    $VMWARE_PYTHON_BIN $ALIVE_BASE/user/conf/install/installSuiteApiPythonBindings.py

  • Maintenance schedule disappears after upgrading from version 6.0 to 6.2
    Your maintenance schedule can become disassociated from an object or policy after an upgrade. There are two different scenarios where this can occur. In the first scenario, you have assigned a maintenance schedule to a specific object. In the second scenario, you have created a maintenance schedule and enabled it in a specific policy. After that, you created a custom group with several objects and associated it with the policy. In both of these situations, the maintenance schedule is not associated with the object or the policy after the upgrade.
    Workaround: Update the policy manually after an upgrade. For more information about managing policies, see Managing and Administering Policies for vRealize Operations Manager.

  • After an upgrade, adapters are unexpectedly listed as stopped
    An upgrade might unexpectedly leave adapters in a Stopped state and Unknown status. The problem occurs because vRealize Operations Manager does not store the state of resources that are in a transition state of starting or stopping. When an upgrade causes a node to restart, and a transition was in progress, the resources revert to a previous state of Stopped.
    Workaround: After the upgrade, start adapters as needed.

  • External calls might cause upgrade to fail
    In some cases, program calls generated by scripts or user actions external to vRealize Operations Manager might cause the vRealize Operations Manager Gemfire monitor process to restart a node. If such a restart occurs during an upgrade, the upgrade fails.
    Workaround: Bring the cluster online, and rerun the upgrade.

  • Upgrade fails when disk space is too low
    When disk space is too low to upgrade to this version of vRealize Operations Manager, the upgrade fails its pre-upgrade validation script, and the following error appears in the Software Update wizard:
       The PAK action "validate" script "/usr/lib/vmware-vcopssuite/python/bin/python validate.py" failed
    To reveal how much disk is needed, search for DISK SPACE CHECK FAILED in the following log file:
       $STORAGE/log/vcops/log/pakManager/vcopsPakManager.root.post_validate.log
    Workaround: Before running the update, remove files from the partition that is too full, or add disk space by following the guidelines in Knowledge Base article 2016022.

  • RHEL uninstallation does not fully remove user accounts
    After you uninstall vRealize Operations Manager from Red Hat Enterprise Linux (RHEL), vRealize Operations Manager admin and postgres users still appear in the /etc/passwd file.
    Workaround: None. You may manually remove the users from the file if desired.

  • Removal of directories might affect upgrade
    In some cases, users have manually removed vRealize Operations Manager directories, such as directories where logs are stored. For example:
    /storage/log/vcops/log/vcopscli
    /storage/log/vcops/log/dbcli
    /storage/log/vcops/log/opscli

    The upgrade process requires vRealize Operations Manager directories to exist. If the directories are missing, the upgrade might fail by preventing vRealize Operations Manager services from starting, or in other unpredictable ways.
    Workaround: None. Do not manually remove vRealize Operations Manager directories.

  • Residual files prevent reinstallation on RHEL and Windows
    After you uninstall vRealize Operations Manager from Red Hat Enterprise Linux (RHEL) or Windows, files such as logs might not be completely removed. If residual files exist, reinstallation might fail.
    Workaround: Before reinstalling, manually remove residual files and directories from the vRealize Operations Manager install and data directories. The following are the default directories:
    RHEL
     Install   /usr/lib
     Data   /data
    Windows
     Install   C:\vmware\vrealize-operations
     Data   C:\data
  • Windows uninstallation does not remove everything
    After you uninstall vRealize Operations Manager from Windows, you might find programs such as vmware-casa or vmware-vcops still listed under the Control Panel option for managing your programs. In addition, you might find residual vRealize Operations Manager services in the Windows Services interface. When you reinstall, you might also see an extra NTP server in the master node configuration wizard.
    Workaround: None of these items are known to affect the system, but you may manually remove them if desired.

  • Postgres upgrade fails on Windows remote collector
    When upgrading a Windows remote collector to this release of vRealize Operations Manager, the upgrade fails, and the following error appears in VMware-Postgres.msi_upgrade.log:
    Service 'vRealize Operations vPostgres Database' (vPostgres) failed to start.
    Workaround: Before starting the upgrade, take the following steps:
    1. Open %STORAGE_DB_VCOPS%\vpostgres\data\postgresql.conf in Notepad, and change shared_buffers=0MB to shared_buffers=640MB.
    2. Open %STORAGE_DB_VCOPS%\vpostgres\data\postgresql.conf.auto in Notepad, and comment out the shared_buffers = '0 MB' line.

  • Non-ASCII Windows user account cannot install
    Installation of vRealize Operations Manager on Windows fails if the logged in user has an account name that contains non-ASCII characters.
    Workaround: None. Before installing on Windows, log in with an account name that only contains ASCII characters.

  • 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. Manually delete files, or perform the following steps using the administration interface or product interface:
    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

  • 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

  • Removing a node from a High Availability cluster prevents the next node from coming online
    If you remove a node from a cluster where the High Availability feature has been enabled, the remaining nodes should come back online without any problems. However, if you remove a node from a cluster in this release where the High Availability feature is enabled, the next node will not come online automatically.
    Workaround: Bring the remaining nodes online manually.
    1. Look at the $VCOPS_BASE/user/log/cassandra/validate_cluster.log and verify that the last line is a call to nodetool removenode without a response.
    2. On the command line, perform a ps -ef | grep nodetool to verify that nodetool is still running.
    3. On the command line, run the following command: $VCOPS_BASE/cassandra/apache-cassandra-/bin/nodetool -p 9008 removenode force.
    4. Look at the $VCOPS_BASE/user/log/cassandra/validate_cluster.log and verify that the command returned and the script finished.

  • Node controls are enabled while cluster is starting
    In the vRealize Operations Manager administration interface, the controls to take a node online or offline are not disabled before or while the cluster is starting. If you try to start the cluster using the node controls to take nodes online instead of the Start vRealize Operations Manager button, the cluster fails to start.
    Workaround: None. You must use the Start vRealize Operations Manager button to start the cluster.

  • Removal of remote collector affects solutions
    After removing an inaccessible remote collector node, in Administration > Solutions, you might not be able to edit the configuration of a solution. The problem occurs because the solution includes an adapter instance on the removed remote collector.
    Workaround: Delete the solution, and re-add it.

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

  • 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

  • "Unable to create a new license" error appears when adding a new license
    When using the Add License feature to enter, validate, and save a new license, an error indicating that the license key has already been installed appears in the dialogue box.
    Workaround: None. After a few seconds, the Add License dialogue box disappears with the new license key successfully saved.

  • Redirecting syslog files to the Log Insight feature also redirects garbage collection files
    In this release, it is possible for you to redirect the system logs (syslog files) to the Log Insight feature. However, this action also redirects all log-related files, including the garbage collection files.
    Workaround: If you do not have ample storage for garbage collection log files, manually disable garbage collection log redirection:
    1. In a text editor, open /var/lib/loginsight-agent/liagent.ini.
    2. Locate the entry [filelog|ANALYTICS-analytics] and set the property: exclude=analytics*-gc.log*.
    3. Save and close the file.
    4. To restart the service, type the command: service liagentd restart.

  • Application pool data for our Internet Information Services (IIS) Solution not available for Windows 2008, 32-bit Servers
    One of the performance counters that the Internet Information Services (IIS) Solution uses to fetch application pool data is not available in Windows 2008 32-bit (IIS Version 7.0). This works fine in Windows 2008 R2.
    Workaround: Upgrade to Windows 2008 R2, before installing the IIS Solution.

  • vCenter Server Web Client does not work if you disable TLS 1.0 (Transport Layer Security)
    If you disable TLS 1.0 in vCenter Server and vRealize Operations Manager, vRealize Operations Manager will not be able to receive data from the vCenter Server Web Client. Note: You can still use TLS 1.1 and TLS 1.2 if you are only running vCenter Server, but they are not currently supported for use with vRealize Operations Manager.
    Workaround: Enable TLS 1.0 for vRealize Operations Manager.

  • Relationship between vCenter Server and SSO server not created
    In an environment in which more than one vCenter Server is using the same SSO, relationships between one or more servers and the SSO might not be created.
    Workaround: None.

  • DRS must be enabled on clusters
    Your vCenter Server instance must have a cluster that passes a DRS enabled check for the Rebalance Container action to appear in the Actions drop-down menu.
    To get the Rebalance Container action from a custom data center or data center, and the related alerts, you must have the following:
    • A vCenter Adapter and a vCenter Python Actions Adapter for each vCenter Server instance
    • A vCenter Server instance with at least one cluster that is DRS enabled
    If your cluster does not have DRS fully automated, the Rebalance Container action notifies you that one or more clusters under the selected container do not have DRS set to fully automated.
    Workaround: To ensure that the Rebalance Container action is available in your environment, you must add DRS. Then, wait one collection cycle for the Rebalance Container action to appear.

  • An attempt to move virtual machines across data centers results in an error
    The Move VM action can fail if you attempt to move virtual machines across a data center. This failure could be caused by the network compatibility of the destination data center. When you choose a destination, ensure that the virtual machine is not moving across a data center.
    Workaround: None

  • When no workload resource containers are enabled in the policy, the balance of the selected container cannot be improved
    If the workload calculation for a policy does not include memory or CPU resource containers, an error message might occur, which indicates that the balance of the selected container cannot be improved.
    Workaround:
    To include resources in the workload calculation so that the Rebalance Container action can improve the rebalance plan, you must select one or all of the required resource containers for the workload calculation.
    1. Select Administration > Policies, and select Policy Library.
    2. Select your policy, and click Edit.
    3. In the policy workspace, select Analysis Settings, and expand Workload.
    4. Select Memory Demand, Memory Consumed, and CPU Demand.
    5. Then run the Rebalance Container action again.

  • Deploying virtual machines to a failover host is not allowed
    After you configure a failover host in a cluster and select the failover host in the navigation tree, then go to Analysis > Capacity Remaining, create a custom profile for virtual machines, and enable the custom profile for all policies, you can view the number of virtual machines that will fit on the host.
    Although the custom profile indicates that a number of virtual machines will fit on the host, you cannot power-on virtual machines deployed in failover hosts.
    Workaround: None

  • Symptom set details cannot be retrieved for some alerts
    When an alert triggers based on a set of population based symptom sets, and one or more symptom set could not be evaluated due to lack of enough resources to evaluate the population condition, an error occurs. The error message indicates that the complete symptom set details for that alert cannot be retrieved for that particular symptom set. This error only occurs on population based alerts and only if enough resources were not available to evaluate the condition.
    Workaround: None

  • Metric configuration list does not appear on first attempt to modify the Metric Chart widget configuration options
    After you install vRealize Operations Manager, on your first attempt to edit the Metric Chart widget and select a metric from the list of configuration options, the list does not appear.
    Workaround: Exit the widget configuration, then attempt to modify the widget configuration options again. The list opens as expected.

  • Alert Details summary links below the top link do not link to objects
    When you view the alert details for an alert that has received symptoms from many objects, such as an alert on a host that has symptoms from virtual machine child objects, then you expand the drop-down arrow for the alert cause, you can see the list of symptoms. Because the alert is generated with symptoms received from many objects, you see a list of links to those objects with relevant symptom descriptions. The links to the objects located below the first object do not work. This problem is relevant for all browsers, except for Internet Explorer.
    Workaround: Manually find the object you need. For example, use the global search text box in the top toolbar to search for the object.

  • Visualization chart does not show data for World or Custom Group objects
    The Visualization Chart does not appear for World or custom group objects.
    Workaround: None.

  • Self-monitoring badges did not start automatically for 16-node cluster
    Some adapter instances (particularly Container and vRealize Operations Manager adapter instances) might change their collection state to stopped. As a result, some badges might show question marks "?" (for Universe, World, and other resources).
    When the collector is down/unavailable, and the system is not consistent (for example, the nodes/collectors are under pressure and/or restarting frequently) the adapter failover might not complete successfully, and as a result Adapter Instances might remain in an "intermediate" stopped state. As a result, the related resource badges might not display data. In this case, you will not see an error message in the UI. This issue might happen only for adapter instances that are not pinned to any specific collector, but are configured to be run on a collector group (the system is running vRealize Operations Manager and Container adapter instances on the default collector group).
    Workaround: Check the adapter instances collection states. If they are in the stopped state and they were not stopped manually, and they are running on a collector group, then this is probably what has caused the issue. You must manually start monitoring of the stopped adapter instance resources.

  • The behavior of the workload placement does not change after making a change in the Consolidation policy setting
    In this release, the Consolidation policy setting does not affect the placement of virtual machines across clusters.
    Workaround: None

  • Virtual Machines will not Power On, even though vRealize Operations Manager reports capacity remaining
    In cases where one virtual machine is larger than the others in the cluster, the size discrepancy from this single virtual machine 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: Determine the slot size and then increase the buffer threshold using policies.

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

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

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

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

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

  • 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

  • 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

  • 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 up to 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 Administration > 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/inbound/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 virtual appliance 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

  • 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

  • When manually running a backup job for vRealize Operations Manager 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

  • Deletion Scheduling Interval setting does not change behavior
    If you use the Administration > Global Settings > Deletion Scheduling Interval or the REST API to change the default value of the Deletion Scheduling Interval from every 24 hours to another value, the user interface will register the changed value, but the actual interval of object deletion will not change. The Deletion Scheduling Interval value defines how often objects that have been deleted are actually removed from the system. Therefore, you might think you have set the interval to delete objects every 12 hours, but the server is still using the default value of every 24 hours.
    Note: If you have upgraded to 6.2 from an earlier version of vRealize Operations Manager, the system will still be using your previous setting (which was maintained during the upgrade). But now that you're on version 6.2, any additional changes to the interval value will not take effect. This is because the changed value will register on the UI, but the actual value will remain as it was before you migrated to 6.2.
    Workaround: None.

  • Pagination for Alert/Symptoms views does not work
    If you view a list from the Alert/Symptoms page, you will only see the first page of the list data, even if there is enough data returned to fill multiple pages.
    Workaround: None.

  • Migration may fail if datastore is not accessible to network
    VM migration across clusters may fail during a rebalance action with the message "Unable to access the virtual machine configuration: Unable to access file".
    Workaround: Ensure that all hosts in every cluster participating in a rebalance action share the same datastores that every VM in every cluster participating in the rebalance action resides on.

  • Main menu icons not responsive (until page is refreshed manually)
    In vRealize Operations Manager, you may experience a freeze, where the main menu icons are not responsive. Workaround: Refresh the view.

  • Adding new user in vRealize Operations Manager after filtering names can create duplicate users
    After you add new users with the vRealize Operations Manager Administration view, you can sort the users with a Filter field in the upper-right corner of the User Accounts tab. If you add more users after you have performed a sort, and then you delete the sorting filter, duplicate users may appear in the User Accounts list.
    Steps to reproduce:
    1. Login to vRealize Operations Manager as an Admin User.
    2. Select Access Control from the left side menu.
    3. Choose the User Accounts tab.
    4. Enter an existing User Name in the Quick filter field in the upper-right corner.
    5. Use the Enter key to add the new search filter.
    6. Create a new user (just the name and password).
    7. Remove the filter you created by clicking on the red 'x' next to the filter icon.
    8. The User records might have been duplicated.
    Workaround: Refresh your browser and the list of users will display correctly.

  • Cannot retrieve Alerts related to removed objects
    You cannot retrieve alert data for historical purposes after you have removed the object that caused an alert.
    For example, if you're working with a configuration that contains a master node, a data node, and a remote collector node, and the remote collector goes offline, you will receive an alert that the collector is offline. This is expected behavior.
    However, if you remove the inaccessible node and then try to access the alert again, you will receive an error similar to the following, "Error retrieving the complete symptom set details for alert."
    Workaround: None.

  • Filtering Dashboard Widgets by Alerts does not save filter data
    If you create a dashboard that includes the Environment Overview Widget, you can add a filter to show only red badges. However, if you try to include this new dashboard in a report, the report will include all badges - not just the red badges.
    This is because the filters in the Environment Overview Widget are not stored permanently.
    Workaround: None.

  • Cannot delete log files from COLLECTOR/adapter subfolders
    When you are in the Administration view of the vRealize Operations Manager, you can select the Logs menu item in the far left column to review the log files. After you have selected the Logs menu item, you will see a list of the log folders in the center pane.
    Under the COLLECTOR folder, you will see an adapters subfolder. Under the adapters subfolder, you will see a subfolder for the default VMwareAdapter, plus folders for any other adapters that you have entered.
    However, if you try to delete files from these sub-folders, you may see the error, "Failed to delete the selected files."
    Workaround: Use operating system (OS) tools to delete these files.

  • Item count in Environment Overview page might not match the total number of items
    When you choose the Environment menu or icon from the Home page in vRealize Operations Manager, you will see the Environment Overview window. The Groups tab of the Environment Overview window does not display the correct number of items in the lower right corner.
    Workaround: None.

  • Incorrect count in the 'Workload in Related Objects' section of the Analysis tab
    From the Home page in the vRealize Operations Manager, you can select the Environment menu or icon to change to the Environment Overview. In this window, if you choose an object from the Inventory Tree section, you can evaluate the state of that object by selecting the Analysis tab. However, the Peer object count in the 'in Related Objects' section may be incorrect.
    Workaround: None.

  • Sorting policy order does not work as anticipated
    When you are using the Administration view of vRealize Operations Manager, you can choose the Policies menu item to create new policies or apply existing policies to groups.
    You can use the far right column of the Active Policies tab to re-order (and therefore re-prioritize) the policies by dragging them to a new position. However, even though it seems like you can drag a custom policy below the default policy, you actually cannot. The default policy is always the last policy in the list after the view is refreshed.
    Workaround: None.

  • Capacity values when using High Availability are not as expected for new Project
    If you create a new Project in vRealize Operations Manager while you have the High Availability feature enabled, you might expect the current object values (memory, disk capacity, and CPU) to add up to the total capacity (current values = total capacity). However, some of the capacity is actually cached because it has to be reserved for the possibility of migration. Therefore, the actual equation is: current values = total capacity - amount reserved for High Availability.
    Workaround: None.

  • Select Preview Source popup can disappear
    You can edit Views in vRealize Operations Manager by choosing Administration > Views from the Home page. Select a view and then click the pencil icon to edit a view. You can follow the steps on the left side of the screen to edit the view.
    Sometimes when you click the Select Preview Source... link, the Select an Object window will open and the Select Preview Source window may disappear until your data is returned.
    Workaround: Refresh the page.

  • 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

Endpoint Operations Management Agent Issues

  • MSSQL resource monitoring stops after an Endpoint Operations Management agent is reinstalled
    If you reinstall an Endpoint Operations Management agent, including deleting the data folder, MSSQL resources might stop receiving data.
    Workaround: Edit the problematic resources and click OK.

  • Endpoint Operations Management adapter fails to restart after data node is brought back online
    If you take a data node that is part of a multi-node cluster offline and then bring it back online, the Endpoint Operations Management adapter does not automatically come back online.
    Workaround: Select the Endpoint Operations Management adapter in the Inventory Explorer and click the Start Collector icon.

  • ICMP check on Linux machine does not succeed
    If the user running an Endpoint Operations Management agent that is performing an ICMP check on a Linux machine does not have sufficient permissions, the check cannot succeed.
    Workaround: Ensure that the user has root permissions.

  • Unable to start Endpoint Operations Management agent on SuSE 12.x platforms
    If you installed an Endpoint Operations Management agent, using the RPM installer, on a machine running SuSE 12.x, you cannot start the agent using service epops-agent start.
    Workaround: Start the Endpoint Operations Management agent from a console, using the [EP Ops Home]/bin/ep-agent.sh start command.

  • Endpoint Operations Management solution plug-ins appear following an unsuccessful solution installation
    When you attempt to install an Endpoint Operations Management solution in vRealize Operations Manager, and the installation fails, plug-ins related to the solution might appear in the Content > Plug-ins page of vRealize Operations Manager, even though the solution is not installed and does not appear on the Administration > Solutions page.
    Workaround: Run the solution installation again.

  • On Windows Server 2008 R2 and 2012 R2, the Endpoint Operations Management agent might use an obsolete JRE
    Because of a known issue with Windows, on Windows Server 2008 R2 and 2012 R2, Windows services might keep old values of system variables, even though they have been updated or removed. As a result, updates or removal of the HQ_JAVA_HOME system variable might not be propagated to the Endpoint Operations Management Agent service. In this event, the Endpoint Operations Management agent might use an obsolete value for HQ_JAVA_HOME, which will cause it to use the wrong JRE version.
    Workaround: Restart the machine on which the issue occurred, to make sure that changes made to system variables have propagated correctly.

  • Unable to use the same version of an upgrade bundle multiple times to upgrade agents
    If you attempt to use the same version of an Endpoint Operations Management agent upgrade bundle for multiple upgrades, the upgrade fails. When such an attempt is made, a time stamp is appended to the bundle folder name, which prevents automatic name resolution during subsequent upgrade attempts.
    Workaround: Open KB 2137709 and use the syntax for upgrading agents using the specific agent bundle file name that appears in step 2 of the upgrade procedure.

  • Unable to install Endpoint Operations Management agent on 32-bit machines using 32-bit RPM installer
    When you attempt to install the Endpoint Operations Management agent on an 32-bit machine using the 32-bit RPM installer, the installation fails and the message package epops-agent-6.2.0-<Build number>.x86 is intended for a x86 architecture is displayed.
    Workaround: Override the default architecture constraint by adding the --ignorearch option in the format. rpm -i vRealize-Endpoint-Operations-Management-Agent-x86-linux-6.2.0-<Build number>.rpm --ignorearch

  • Unable to see metrics for agent upgrade time frame
    Measurements might be delayed or lost around the time of an agent upgrade.
    Workaround: None

  • Unable to prepare a Windows template using preconfigured Endpoint Operations Management agent that will autostart without a Windows login
    If you try to install an Endpoint Operations Management agent and provide the required properties in the agent.properties file when creating a template, at startup the agent does not automatically start on the machine propagated from the template, because the start service does not behave in the same way as ep-agent.bat start.
    Workaround: Create a batch file (for example, startup-script.bat) that contains the command ep-agent.bat setup and define it as a startup script, as follows.
    1. Type gpedit.msc at the command line prompt to open the policy editor.
    2. Navigate to Computer Configuration > Windows Settings > Scripts (Startup/Shutdown) and add the batch file under startup.
    The agent replaces the agent's client certificate and runs the setup every time the virtual machine is restarted, therefore the agent.properties file must retain all the details (including the encrypted password) throughout the virtual machine's life.

  • Interruption during download of Endpoint Operations Management agent upgrade bundle causes upgrade process to fail
    During the download of an Endpoint Operations Management agent upgrade bundle, any interruption in the download, for example a long network disconnection, will cause the upgrade process to fail.
    Workaround: Verify that all prerequisites for the upgrade have been satisfied, and re-run the upgrade script for the agent. See KB 2137709.

  • Endpoint Operations Management agent in TCP remote check configuration cannot contain spaces in hostname
    Leading or trailing spaces in the hostname of a machine causes remote checks to fail.
    Workaround: Specify the IP address of the machine on which the remote check is to run, not the host name.

  • Windows agent service JRE is not upgraded if the user does not have permissions to write to the registry
    The Endpoint Operations Management agent JRE is not upgraded when the user running the upgraded agent service does not have permission to write to the Windows registry. If the agent was being run on a Windows OS by a user other than the root user, and the user does not have registry Write permissions, the JRE appears to be upgraded but, after the service or machine is restarted, the old JRE is used because the registry still contains the old HQ_JAVA_HOME entry.
    Workaround: Update the registry entry. Under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\End Point Operations Management Agent, remove set.HQ_JAVA_HOME=... from the data of ImagePath value.

  • Unable to extract installation path for an EndPoint Operations Management agent on a Linux machine
    When trying to install an Endpoint Operations Management 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.

  • Roll back of Windows Endpoint Operations Management agent service upgrade does not roll back JRE
    If you upgrade a Windows Endpoint Operations Management agent service to version 6.2 and the upgrade fails, the upgrade rolls back to version 6.1. However, the JRE that was upgraded as part of the upgrade process does not roll back to its earlier version.
    Workaround: Restart the agent service. The earlier version of the JRE is invoked.

  • Blank password not accepted for Postgres user
    The embedded Postgres database for a vCenter Server appliance is shipped without a default password for the postgres user. If you do not set the password in the vcdb.properties file, you are unable to log in as the Postgres user because the Endpoint Operations Management agent will not allow you to log in with a blank password. You might experience this problem if you are trying to monitor the Postgres database after importing the Endpoint Operations Management Adapter.
    Workaround: Use the Postgres DB credentials stored in /etc/vmware-vpx/vcdb.properties for the Virtual Appliance and C:\ProgramData\VMware\vCenterServer\cfg\vmware-vpx\vcdb.properties for Windows. More configuration information is published in KB 2133716. It is not necessary to enter the default (blank) Postgres password.

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

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

  • Error message logged after installing non-JRE version of agent
    Following the installation of a non-JRE version of the Endpoint Operations Management 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 Endpoint Operations Management agent or add Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy files to your Java version.

  • The Endpoint Operations Management agent stops responding while starting with the vCenter 6.0 Appliance
    The Endpoint Operations Management 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.

  • Receiving generic error message after installing non-JRE version of agent
    After installing a non-JRE version of the Endpoint Operations Management agent, or when attempting to use a Java version other than that provided with the Endpoint Operations Management 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 Endpoint Operations Management agent or add Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy files to your Java version.

  • Endpoint Operations Management agent did not install correctly in Windows environment
    You used a Windows installer to install an agent in an environment in which either an Endpoint Operations Management 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 Endpoint Operations Management or vRealize Hyperic agent installed on your environment before running the agent Windows installer.

  • Endpoint Operations Management 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 Endpoint Operations Management 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 Endpoint Operations Management 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 Endpoint Operations Management 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 Endpoint Operations Management agent.

  • Unable to install Endpoint Operations Management agent from an EXE installer to a path containing non-ASCII characters
    A known issue in Oracle prevents the installation of the Endpoint Operations Management 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 do not release allocated resources
    Unless a shut down method is implemented before a new version of a plug-in is deployed, the existing version of the plug-in does not shut down so that a new instance is created. As a result, allocated resources such as static threads are not released.
    Workaround: Implement a shutdown method for the following plug-ins:
    • Plug-ins that use third-party libraries
    • Plug-ins that use native libraries
    • Plug-ins that use connection pools
    • Plug-ins that might lock files, which might cause problems on Windows operating systems
    It is good practice that plug-ins do not use threads, third-party libraries, or static collection.

  • Agent did not install correctly in Windows environment
    You used a Windows installer to install an agent in an environment in which either an Endpoint Operations Management 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 Endpoint Operations Management or vRealize Hyperic agent installed on your environment before running the agent Windows installer.

  • Over-riding 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 Endpoint Operations Management agent is started using Windows Services
    If you stop an Endpoint Operations Management 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 Endpoint Operations Management 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 Endpoint Operations Management agent. The metrics are fully reported.
    Workaround: None

  • Previously detected objects no longer monitored after reinstalling an Endpoint Operations Management agent
    When you reinstall an Endpoint Operations Management 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 Endpoint Operations Management agent until the plug-in synchronization is complete.

  • Unable to extract installation path for an Endpoint Operations Management agent on a Linux machine
    When trying to install an Endpoint Operations Management 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 Endpoint Operations Management 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 Endpoint Operations Management 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 Endpoint Operations Management agent does not register and the following error appears: Connection failed. Server may be down (or wrong IP/port were used). Waiting for 10 seconds before retrying.
    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 Endpoint Operations Management agent in an environment that supports both IPv4 and IPv6
    You cannot register an Endpoint Operations Management agent in an environment that supports both IPv4 and IPv6. In the event that you attempt to do so, the following error appears: 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

  • Endpoint Operations Management Agent already running message
    When you attempt to start an Endpoint Operations Management 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

Resolved Issues

This section contains the titles of previous Known Issues that have been resolved in this release.

  • Plug-ins that were imported from vRealize Hyperic did not work correctly in vRealize Operations Manager on Windows platforms
  • Endpoint Operations Management vCenter solution failed to discover single sign-on on Linux
  • SSO users logging out of vRealize Operations Manager cannot log out of the vSphere Web Client
  • SSO with Active Directory over LDAP does not support domain trust
  • After an upgrade of vRealize Operations Manager to the previous release, accessing the views named Alerts that are currently active and Symptoms results in an internal server error
  • Workload placement excludes virtual machines that participate in DRS and SDRS affinity rules
  • Rebalance on cluster might not present all hosts in rebalance plan
  • Virtual machine migration fails in vCenter Server during Rebalance Container action
  • Dashboards cannot export and import related data
  • When you take an object to resource maintenance mode, the applied policy changes to vSphere Solution's Default Policy
  • VVOL datastores are masked
  • Project scenarios with the same effective date can conflict and be overwritten
  • The out-of-the-box Classic Summary dashboard does not display content in widgets
  • Not all metrics instanced under the Network|Port Statistics resource group for vSphere Distributed Virtual Port Groups are collected
  • An object goes to maintenance after you delete the maintenance schedule
  • Previous migration log might affect upgrade
  • Upgrade on Windows does not complete with multiple upgrades
  • Upgrade does not complete
  • Upgrade fails when vRealize Operations Manager 6.0.1 included hot fixes

Top of Page