VMware vRealize Operations Manager 6.0

VMware vRealize Operations Manager 6.0 Release Notes

vRealize Operations Manager 6.0 | 9 DEC 2014 | Build 2263109

vRealize Operations Manager Appliance 6.0 | 9 DEC 2014 | Build 2263110

Last Document Update: 13 JANUARY 2015

Check frequently for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

Introduction to vRealize Operations Manager

vRealize Operations Manager 6.0 is the latest release of VMware's integrated operations suite, converging performance, capacity, and configuration management. This release introduces the following enhancements.

  • Scale-Out Deployment Architecture
    This release provides distributed deployment with elastic scale and higher scalability.
  • Unified User Interface
    This release introduces a single user interface to manage vSphere as well as non vSphere domains. You can create powerful, flexible custom dashboards enabling you to bring any information you want into the management console.
  • Licensing Management in 6.0
    vRealize Operations Manager 6.0 has an independent license-management GUI that provides enhanced administration of license keys specific to vRealize Operations. Customers can now deploy mixed editions in a single vRealize Operations 6.0 instance.
  • Smart Alerts
    Smart alerts combine multiple symptoms to generate a single alert that focuses on the underlying issue with clear recommendations and option to take action for remediation.
  • Enhanced Reporting
    Enhanced reporting provides several out-of-the-box reports with the ability to generate fully customizable reports.
  • Capacity Planning and Project Management Capabilities
    New capacity planning and project management capabilities extend beyond vSphere and across physical and application level metrics. Flexible capacity models can be adjusted to meet different business needs.
  • Custom Policies
    Custom policies can applied for specific workload types, applications or clusters enabling more advanced monitoring of performance, capacity and configuration standards.
  • Automated Remediation of Problems
    Integrated action and remediation capabilities with the ability to apply actions according to the recommendation for the alerts.
  • User Access Control Management
    Improved user access control, including granular role-based access control.
  • Unified Storage Visibility
    New storage visibility shows the correlation between the application group and the storage infrastructure supporting it, including HBA's, Fabric and Arrays, along with the ability to trace operational issues all the way to storage.

Before You Begin

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


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

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

Browser Support

This vRealize Operations Manager release supports the following Web browsers:

  • Google Chrome: Latest and most previous release
  • Mozilla Firefox: Latest and most previous release
  • Safari: Latest
  • Internet Explorer for Windows 10 and 11
  • Note: There might be issues with slower performance if Internet Explorer 10 or 11 is used.

The minimum supported resolution is 1024 x 768.

Deployment Requirements

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

  • VMware virtual appliance
  • RHEL and Windows installation packages

Virtual Appliance Deployment

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

Linux and Windows Requirements

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

Licensing Keys

vRealize Operations Manager 6.0 allows customers to install multiple Advanced and Enterprise editions in the same vRealize Operations Manager deployment. This enhancement in 6.0 enables customers to deploy a-la-carte and suite licenses together.

License counting for individual license keys is handled via licensing groups – a feature that is introduced in 6.0. You can mix editions or licensing models in one of the following ways:

  • Customers can deploy vCloud Suite Standard, vSphere with Operations Management, and vRealize Operations Standard together in one deployment.
  • Customers can deploy vCloud Suite Advanced or Enterprise, vSphere with Operations Management Advanced, vRealize Operations Insight, and vRealize Operations Advanced or Enterprise in one deployment.
  • Note that customers 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 resources collected, which includes the number and type of adapters installed, the presence of HA, the duration of data retention, and the quantity of specific data points of interest. VMware updates the following Knowledge Base article with the most current information about sizing and scaling.

Knowledge Base article 2093783

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

Installation Notes for This Release

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

Adapter Support

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

AdaptervApp Single NodevApp Multiple NodeRHEL Single NodeRHEL Multiple NodeWindows Single NodeWindows Multiple NodeUpgrade Migration
AWS 1.0XXXX   
EMC Smarts 3.0XXXX  X
Text File 2.0XXXXXXX
Relationships 2.5XXXXXXX
vCloud Director 2.5XXXXXXX
HP-SiteScope 2.4XXXXXXX
KeyNote 2.1XXXXXX 
TeamQuest 2.0XXXXXXX

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

Known Issues

This section contains known issues for this release.

Installation and Upgrade Issues
  • Upgrading to Version 5.8.1 when preparing for migration
    A migration to this version requires that the source be vCenter Operations Manager 5.8.1 or later. When updating a source to 5.8.1 or later, and when the source uses DHCP, the source deployment might become unresponsive.
    Workaround: Follow the guidelines in Knowledge Base article 1037601.

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

  • Blank metrics and resource counts in multiple-node cluster
    When one node fails to retrieve metrics and resource counts for any reason, other nodes of a multiple-node cluster might also show blank metrics and resource counts. This behavior appears on the Cluster Management page of the administration interface.
    Workaround: None.

  • PAK installation does not prevent cluster modification as expected
    When installing a solution, it is possible to 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.

  • Node names cannot contain forward slash characters
    A cluster that includes a node with a forward slash (/) in the node name does not start.
    Workaround: None. Avoid the forward slash (/) character in cluster node names.

  • External shutdown affects cluster nodes
    When you shut down a data node from outside vRealize Operations Manager, such as by using vSphere, all nodes report a status of inaccessible 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: Never 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 first taking it offline in the vRealize Operations Manager interface.

  • The analytics services fail to start after upgrading
    If the cluster fails to start after about 30 minutes, review the analytics-{node-GUID}.log files for errors in the ActivityDataService. If you find errors, the activity persistence files are corrupted and you must delete them.
    Workaround: To delete the files, use the following steps:
    1. In vRealize Operations Manager Administration UI, take the cluster offline.
    2. Delete all the files in the /storage/db/vcops/activity directory for each node in the cluster. Do not delete the directory, only delete the files in the directory so that it is empty.
    3. Bring the cluster back online.
  • Windows cluster behaves unpredictably after NetBackup restore
    After using NetBackup to perform a successful restore of a vRealize Operations Manager Windows-based cluster node, the application behaves unpredictably.
    Workaround: After successfully restoring a vRealize Operations Manager Windows-based node, restart the Windows operating system.

  • Cannot bring the cluster online with an unresponsive node present
    If a node in a cluster becomes unresponsive, and the cluster is offline, you cannot bring the cluster back online.
    Workaround: Before bringing the cluster online, use the administration interface to remove the unresponsive node. Optionally, also add a new node to avoid losing capacity.

  • The admin account password has been lost
    The admin account password has been lost and needs to be reset.
    Workaround: Run the console command that resets the admin account password.
    vApp and Linux:
    1. Log in to the master node command line console as root.
    2. Enter the following command, and follow the prompts.
      $VMWARE_PYTHON_BIN $VCOPS_BASE/../vmware-vcopssuite/utilities/sliceConfiguration/bin/vcopsSetAdminPassword.py --reset
    1. Open the command prompt using the Run as Administrator option.
    2. Enter the following command, and follow the prompts.
      %VMWARE_PYTHON_BIN% %VCOPS_BASE%\..\vmware-vcopssuite\utilities\sliceConfiguration\bin\vcopsSetAdminPassword.py --reset

  • Cluster restart brings offline nodes online
    Any manual or system action that restarts the vRealize Operations Manager cluster brings all vRealize Operations Manager nodes online, including any nodes that you had taken offline.
    Workaround: None

  • 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 correctly take over the master role.
    Workaround: Manually configure the replica node as the master node.
    1. Take the entire cluster offline, including data nodes.
    2. Log in to the replica node command line console as root.
    3. Open $ALIVE_BASE/persistence/persistence.properties in a text editor.
    4. Locate and set the following properties:


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

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

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

  • Taking a node offline might result in timeout message
    When you take a cluster node offline, the following message might appear:

    Communication Error: Timeout reached while trying to communicate with the server. Try refreshing the UI manually.

    Workaround: Click OK to close the message, and refresh the browser display. The node will eventually go offline as expected.

  • Updated A node or a cluster runs out of disk space
    If a node or a cluster runs out disk space, it will be shut down or you will not be able to bring it online. You will see one of the following messages in the cluster information panel:
    Failed to add new node because one or more nodes are out of disk space.
    Initial installation failed because one or more nodes are out of disk space.
    Cluster failed to come online because one or more slices are out of disk space.
    Unable to bring the cluster online because one or more nodes are out of disk space.

    To increase the disk space on a VA, see Add Disk Space to a vRealize Operations Manager vApp Node.

    To increase the disk space on Red Hat Enterprise Linux and Windows:

    1. Add a new disk to the system, partition and format the disk as needed.
    2. Take the cluster offline.
    3. Stop CaSA.
    4. Move the contents of /storage/db into a directory on the new disk.
    5. Create a link from the new directory back to /storage/db, so that /storage/db now references the new disk.
    6. Start CaSA.
    7. Bring the cluster online.

General Issues
  • Cannot search for notification or hard threshold alert event information messages
    When a notification or hard threshold event is generated, the event message is appended to the alert name. In Alerts lists, you can search using the Quick filter (Name). You can search for notification or hard threshold, but you cannot search for the appended event message.
    Workaround: None

  • Updated Alert list count for generated alerts after high availability failover is incorrect
    In a multinode environment where HA is configured, if the master node goes offline unexpectedly, the alert list count in the lower right does not match the number of displayed alerts in the list. The alerts in the list are correct, only the displayed count in the lower right of the page is incorrect.
    Workaround: None

  • Updated Communication error when creating a support bundle
    Support bundles are created in 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.
    Workaround: Although the error is generated, the support bundle is created and is usable.

  • Support bundle for multiple nodes in a cluster creates file for only one node
    When creating a support bundle, in Administration > Support > Support Bundles or in the Administration user interface, and you select two of your four nodes to include in the support bundle, only one node is included in the bundle.
    Workaround: Create separate support bundles for each node so that you can review them or send them to support services.

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

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

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

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

    Workaround: None
  • Disabled capacity metrics in vCenter Operations Manager 5.8.x are enabled after migration to vRealize Operations Manager 6.0
    Migrated capacity metrics that are disabled for vCenter Server, host systems, virtual machines, and other objects in vCenter Operations Manager 5.8.x, are enabled in vRealize Operations Manager 6.0.
    Workaround: Manually disable the capacity metrics in the vRealize Operations Manager 6.0 policy.

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

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

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

  • vCenter Adapter stops collecting from vCenter Server 5.5
    When the vCenter Server collections fail on a vCenter Server 5.5 instance and the logs show an exception, RuntimeException WstxEOFException, the hosts are enabled with vFlash.
    Workaround: Apply the workaround provided in VMware KB 2072392 (http://kb.vmware.com/kb/2072392).

  • An installed solution does not appear in the solution Add License Key drop-down menu
    If you are licensing an instance of and solution adapter in Administration › Solution › ‹adapter name› license › Configure › Add, and the adapter does not appear in the Add License Key drop-down menu, then the licenses are not refreshing.
    Workaround: To force a refresh of the processor, you must make a cURL request on the master node.
    1. Use SSH to log into 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 admin user.
    The license process refreshes the list.

  • Migrated users might gain additional permissions
    After migrating a 5.x deployment to this version of vRealize Operations Manager, migrated users are able to perform tasks, such as creating dashboards, for which they might not have had permission in version 5.x.
    Workaround: To account for changes in how permissions work in vRealize Operations Manager, migrated users are assigned the PowerUserMinusRemediation role in addition to their 5.x migrated role. After migration, you may remove the PowerUserMinusRemediation role and replace it with ReadOnly. Alternatively, remove PowerUserMinusRemediation and update the permissions in the migrated role.

  • When the applied policy changes for an object group, updates to the capacity badges and metrics are delayed
    When you apply a policy other than Default Policy to an object group, then view the Analysis tabs for an object in the group, updates to the computed badges and metrics do not appear immediately, but instead are delayed for a day.
    Workaround: Update the capacity settings in the policy that is applied to the object group.
    1. Go to Administration > Policies > Policy Library.
    2. Select the policy that is applied to the object group, and click Edit.
    3. In the Edit Monitoring Policy workspace, click Override Analysis Settings.
    4. In the left pane, in the Show changes for drop-down menu, select vCenter Adapter - Virtual Machine, then in the right pane, click the double arrows to expand the list of analysis settings for virtual machines.
    5. Click the override button to enable the Capacity Remaining Time Remaining settings, and expand Capacity Remaining Time Remaining.
    6. Increase the Provisioning Time Buffer setting to add one day.
    7. Click Save to apply your change to the policy, and wait several minutes for the next collection cycle to finish.
  • Database becomes unresponsive when temporary log files fill the disk partition
    When you monitor many active resources and have long data retention times, the vRealize Operations Manager database might stop responding because temporary database log files have filled the disk partition that holds the /storage/log directory. This issue occurs in vRealize Operations Manager vApp deployments.
    Workaround: Follow these steps to move the xDB database logs to the /storage/db directory, and change the associated symbolic links.
    1. Log in to the administration interface.
    2. Take the cluster offline.
    3. Follow these steps on each node of the cluster.
      1. Log in to the console as root.
      2. Remove the current xDB log links using the following commands:
        rm /data/vcops/xdblog
        rm /data/vcops/hisxdblog
        rm /data/vcops/alarmxdblog>
      3. Move directories using the following commands:
        mv /storage/log/vcops/alarmxdblog /storage/db/vcops
        mv /storage/log/vcops/hisxdblog /storage/db/vcops
        mv /storage/log/vcops/xdblog /storage/db/vcops
      4. Create new symbolic links to the log directories using the following commands:
        ln -s /storage/db/vcops/alarmxdblog /data/vcops/alarmxdblog
        ln -s /storage/db/vcops/hisxdblog /data/vcops/hisxdblog
        ln -s /storage/db/vcops/xdblog /data/vcops/xdblog
      5. Log out.
    4. After all nodes are updated, use the administration interface to bring the cluster online.

  • The delta value for some metrics are not correctly calculated
    Some delta metrics for cluster and analytic resources are not calculated correctly. The value is always 0. If you use these metrics to define charts or as alert symptoms, you will not get a correct value or behavior. This problem affects the following metrics:
    vRealize Cluster
    • GemfireCluster|System|GarbageCollectionCountDelta
    • GemfireCluster|System|TotalHitCountDelta
    • GemfireCluster|System|TotalMissCountDelta
    • GemfireCluster|System|Member|JVM|GCTimeMillisDelta
    • GemfireCluster|System|JVMPausesDelta
    • GemfireCluster|Region|Member|MissCountDelta
    • GemfireCluster|Region|Member|HitCountDelta
    vRealize Analytics
    • ReceivedMetricCountDelta
    Workaround: None

  • The "One or more vRealize Operations services are down" alert is not generated when the collector is stopped
    If the collector on which you are running the vRealize Operations Manager adapter stops running, the alert definitions are not evaluated and the alert is not generated.
    Workaround: None

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

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

  • Only one email alert notification is sent by the Standard Email Plug-In, even when there are multiple alerts for which notifications should be sent
    If you create an outbound alert where you configure the Standard Email Plug-In to use TLS, only one email alert notification is sent for an alert. Other notifications are not delivered. The message SSLException: Unrecognized SSL message appears in the log file.
    Workaround: Configure the outbound alert to use SSL.
    1. In the left pane of vRealize Operations Manager, click the Administration icon.
    2. Click Outbound Alert Settings, select the outbound alert, and click the pencil to modify the plug-in.
    3. From the Plug-In Type drop-down menu, select Standard Email Plugin.
    4. From the Secure Connection Type drop-down menu, select SSL.
    5. Click Save.

  • Anomaly Breakdown widget is empty
    If you select the Multiple Mode option when you configure the Anomaly Breakdown widget, no data appears in the widget.
    Workaround: None. The widget will only display data when you configure the Single Mode and select an object.

  • Maximum Observed Transmitted Throughput metric is reset to a lower value after the collector service is restarted
    If the collector service is restarted, the Max Observed Transmitted Throughput metric is reset to the lower default value rather than returning to the previous maximum observed value.
    Workaround: None

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

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

  • License key may be added to Unlicensed group
    The product allows you to associate a license key with the Unlicensed group, which is incorrect.
    Workaround: None. However, the associating of a license key with the Unlicensed group does not license the members of the Unlicensed group.

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

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

  • Some features are missing after you transition to vRealize Operations Manger Standard edition
    If you ran vRealize Operations Manager 6.0 Evaluation, Advanced, or Enterprise edition, either as part of the beta program or because you initially installed one of these editions, and 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.

  • Virtual Infrastructure Navigator requires ASCII credentials for adapter instances
    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

  • A user who has permission to create other user accounts can assign permission to a new or existing user account to access all objects in the environment
    When a user has permission to create user accounts, that user can create a new user account and assign permissions to the new account to give the new user access to all objects in the environment, even if the user who creates the new account has only limited access to objects in the environment.
    For security purposes, the user who has permission to create user accounts must also have the permission to access all objects in the environment before that user can assign permissions to other user accounts to access all objects.
    Workaround: None

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

  • No data is reported for Device on the Workload Breakdown page
    From the Analytics tab, under Workload, there is a Device category with two sub-categories: Reads per second and Writes per second. These sub-categories do not report any data.
    Workaround: None

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

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

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

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

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

  • LDAP test results in success regardless of which common name you select
    When you add an LDAP import source in Administration > LDAP Import Sources, when you select either of the options in the Common Name drop-down menu in the Add Source dialog box, the LDAP test results in success, regardless of whether you selected samAccountName or userPrincipalName. vCenter Operations Manager should only allow you to select one of the options based on the version of Active Directory used in your environment.

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

  • The Text Display widget cannot display some web sites in HTML mode
    The Text Display widget can display web sites that use HTTPS protocol. The work of the Text Display widget with web sites that use HTTP depends on the individual settings of the web sites.
    Workaround: None

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

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

  • The Topology Graph widget shows the connection between two objects in the inventory with double line when using path exploration mode
    The Topology Graph widget shows a Runs-on relationship with a single line and a Connected-to relationship with a double line.
    Since the VMs have a Runs-on relationship with hosts, the paths between VMs and hosts should be with a single solid line.
    The Topology Graph widget currently does not handle this connection correctly and shows the relationship between a VM and host with a double line.
    Workaround: None

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

  • vCenter Operations Manager 5.8.2 custom dashboards migrated to vRealize Operation Manger 6.0 show no data
    When you migrate vCenter Operations Manager 5.8.2 custom dashboards to vRealize Operation Manger 6.0, the dashboards do not show any data.
    Workaround: None

User Interface Issues
  • Some operating system and browser combinations do no 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 the vSphere 5.5 Web Client, 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 the vSphere 5.5 Web Client requires Flash 11.5. Flash 11.5 is not support on Red Hat.
    Workaround: To use the option with a vSphere 5.5 Web Client, use a browser and operating system that supports Flash 11.5. If you are accessing a vSphere Web Client earlier than 5.5, the error down not occur because the earlier Web Clients use earlier versions of Flash.

  • Disabled alert-based compliance standard still appears on the Compliance tab
    If you disable an alert-based compliance standard policy, the standard still appears in the All Standards list on the Compliance tab. The disabled standard does not affect the Compliance badge score, nor are alerts generated.
    Workaround: None

  • In the analysis views, the data transmit rate and receive rate values for virtual machines displays the host system value
    If you monitoring ESXi 5.5 hosts, the data transmit and receive rates that are collected from the host about the virtual machines displays the host transmit and receive rate values rather than the virtual machine values. This problem does not occur if you are monitoring a host other than ESXi 5.5.
    Workaround: None

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

Documentation Issues

The following information did not make it into the release documentation.

  • Updated Add a custom SSL certificate after vRealize Operations Manager is deployed
    If you did not add your own SSL certificate when configuring the vRealize Operations Manager master node, you can add your own SSL certificate after vRealize Operations Manager has been installed.
    1. Log in to the vRealize Operations Manager administration interface.
    2. At the upper right, click the yellow SSL Certificate icon.
    3. In the SSL Certificate window, click Install New Certificate.
    4. Click Browse for certificate.
    5. Locate the certificate file, and click Open to load the file in the Certificate Information text box.
      The certificate file must contain a valid private key and a valid certificate chain.
      The restriction about self-signed certificates that appears in the documentation is incorrect. Certificates can be self-signed. Also, the statement about file extensions is incorrect. The extension must be .pem.
    6. Click Install.

  • Cannot log in using internal vRealize Operations Manager user accounts
    User accounts that are internal to vRealize Operations Manager, such as maintenanceAdmin and migrationAdmin, cannot be used for logging in to the product.

  • Cannot log in to remote console
    For security, remote login is disabled in vRealize Operations Manager by default. To enable remote login, do the following.
    1. Locate the node console in vCenter or by direct access. In vCenter, use Alt+F1 to access the login prompt.
    2. Log in as root. If this is the first time logging in, you must set a root password.
      1. When asked for a password, press Enter.
      2. When asked for the old password, press Enter.
      3. When asked for the new password, enter the root password that you want.
      4. Re-enter the root password.
    3. To enable remote login, enter the following command:
      service sshd start

  • Less data appears after migration
    After a migration, metric data from 5.x should appear in vRealize Operations Manager as expected. Data might be missing, however, because the 5.x metrics were collected using full profile mode, but vRealize Operations Manager is now collecting using a default policy that does not include the full settings from 5.x full profile mode. To collect the full set of metrics going forward, you must create and apply a new policy or expand the collection scope of the default policy.

  • vRealize Operations Manager virtual machine runs out of memory
    When the vRealize Operations Manager virtual machine requests more memory than is available, the Linux kernel might kill the vcops-analytics process, and the product might become unresponsive. If that happens, use the reservation feature in vSphere to specify the guaranteed minimum memory allocation for vRealize Operations Manager virtual machines:
    1. In the vSphere Client inventory, right-click the vRealize Operations Manager virtual machine and select Edit Settings.
    2. Click the Resources tab, and select Memory.
    3. Use the Reservation option to allocate more memory.

  • Open file descriptor metric has different meaning in Windows
    For Windows resources, the vRealize Operations Manager Open file descriptor count metric shows you the open handle count of the relevant process and is not a Linux open file descriptor count.

  • Unregistered vCenter adapter instances on migration source appear on target
    When a migration source includes unregistered vCenter adapter instances, after a migration, those adapter instances appear in the list of solutions on the target. You are free to delete the extra vCenter adapter instances from the Solutions page.

Top of Page