vRealize Operations Manager 6.6 Release Notes
VMware vRealize Operations Manager Appliance 6.6 | 13 June 2017 | Build 5707161
VMware vRealize Operations Manager 6.6 PAK Updates | 13 June 2017 | Build 5707160
VMware vRealize Operations Manager 6.6 Endpoint Operations Agents | 13 June 2017 | Build 5654169
Updated on: 15 Jun 2017
Check frequently for additions and updates to these release notes.
What's in the Release Notes?
The release notes cover the following topics:
vRealize Operations Manager 6.6 focuses on enhancing product usability, accelerating time to value and improving troubleshooting capabilities.
- Simplified usability and faster time to value capabilities:
Watch videos related to the new dashboards that are introduced with vRealize Operations Manager 6.6 here.
- New HTML5 user interface provides an easier and consistent experience.
- The Getting Started dashboard allows for quick navigation.
- Persona based dashboards provides for answers in one place.
Dashboards are separated into categories such as
Operations, Capacity and Utilization, Performance Troubleshooting, Workload Balance, and Configuration and Compliance.
- Out of the box integration with vSAN and vRealize Automation provides quick time to value.
- Added Native vSAN management capabilities:
- Allows for centralized management across stretched clusters.
- Ability for complete vSAN management, which includes administering performance, capacity, logs, and configuration and health.
- Fully Automated Workload Balancing:
Watch this video for a demo about automatic workload placement.
- Ensures performance across the datacenter's with fully automated workload balancing, across clusters and across data stores.
- Ensures DRS Configurations and provides the option to set DRS automation level for individual objects.
- Predictive DRS takes action to preempt resource contention.
- Utilizes operations analytics to optimize initial placement of workloads through vRealize Automation.
- Additional out-of-the-box compliance capabilities:
- Ability to tackle compliance problems through the new vSphere hardening dashboard
- Extends compliance through PCI & HIPAA compliance for vSphere.
- Ensures business configurations through new cluster, host, and VM configuration dashboards
- Adds support for Windows Server 2016 for End Point Operations agents
- The End Point Operations Management agents collect metrics for NFS-mounted file systems.
For more information on these enhancements, see the vRealize Operations Manager 6.6 VMware product page.
Review this section before you install or update vRealize Operations Manager.
Sizing and Scaling
The CPU, memory, and disk requirements that 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 use of HA (High Availability), 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.
You can deploy vRealize Operations Manager 6.6 with VMware virtual appliance.
Note: vRealize Operations Manager 6.5 was the final version of the product to support RHEL installations. If you are running Linux based vRealize Operations Manager 6.5, you can upgrade to vRealize Operations Manager 6.6.
If you are deploying a vRealize Operations Manager virtual appliance, use a VMware vSphere Client to connect to a VMware vCenter Server, and deploy the virtual appliance through the vCenter Server instance. The vRealize Operations Manager virtual appliance must be deployed on hosts that are ESX/ESXi 5.5 or later managed by VMware vCenter Server 5.5 or later.
You can upgrade the standalone version of vRealize Operations Manager on Red Hat Enterprise Linux (RHEL) 6.5, 6.6, and 6.7 operating systems.
Applying License Keys
In addition to the existing per operating system instance (OSI) licensing, vRealize Operations Standard edition is also available on a per processor (CPU) basis. Licensing for other editions of vRealize Operations is unchanged and continues to be available on a per OSI metric.
Customers can install multiple Advanced and Enterprise editions in the same vRealize Operations Manager deployment. Customers can 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 vSphere with Operations Management (any edition) and vRealize Operations Standard together in one deployment.
- Deploy vCloud Suite/vRealize Suite Standard, Advanced or Enterprise and vRealize Operations Advanced or Enterprise edition together in one deployment.
Note: You cannot deploy a vRealize Operations Standard edition license with either an Advanced or Enterprise license in the same deployment.
A license key assigned to a vRealize Operations Manager instance only counts towards virtual machines that are powered on. In order to be compliant, you need enough licenses to cover average powered-on VMs over trailing 365 days.
To ensure compliance of your vSphere 6.0 and 5.5 objects, vRealize Operations Manager 6.6 includes compliance alerts for VMware vSphere Hardening Guide versions 6.0 and 5.5. These hardening guide alerts are based on object type.
In addition to the VMware solutions (vSphere, Endpoint Operations Management, and vRealize Log Insight), see the compatibility table in the Solution Exchange marketplace for many more solutions. These solutions works with Virtual Appliance single or multiple node, RHEL single or multiple node.
Transport Layer Security (TLS) 1.0 is enabled by default in vRealize Operations Manager. TLS 1.0 is a superseded version of TLS and is enabled for vRealize Operations Manager compatibility with external products.
To disable TLS 1.0, see KB 2138007.
VMware Product Compatibility
This vRealize Operations Manager release has been certified as compatible with the following VMware products:
- VMware vSphere 5.5 and later
- vRealize Hyperic 5.8.5 and later
- vRealize Infrastructure Navigator 5.8.5 and later
This vRealize Operations Manager release supports all current Web browsers, although only the
following browsers have been tested with this release:
- Google Chrome: Version 53 and 54
- Mozilla Firefox: Version 48 and 49
- Microsoft Internet Explorer: Version 11
Top of Page
Installing and Updating vRealize Operations Manager
Note: Customers upgrading older versions of vRealize Operations Manager (6.0.x or 6.1) must use a two-step upgrade: They must first upgrade to vRealize Operations Manager 6.3.1 and then upgrade to vRealize Operations Manager 6.6. Customers with recent versions of Realize Operations Manager (6.5, 6.4,6.3.1 6.3, 6.2.1, or 6.2) can upgrade directly to vRealize Operations Manager 6.6.
The vRealize Operations Manager Information Center has detailed information about installation and software updates.
You can also download the vRealize Operations Manager vApp Deployment and Configuration Guide that provides guidance for a vRealize Operations Manager virtual appliance, before installing or updating vRealize Operations Manager:
Upgrading to vRealize Operations Manager 6.6 will reset out-of-the-box content as part of software upgrade process even if the Reset Default Content button is unchecked during the upgrade. This implies that the user modifications made to default content such as alert definitions, symptom definitions, recommendations, policies, views, dashboards, widgets, and reports will be overwritten. You need to clone or backup the content before you upgrade to vRealize Operations Manager 6.6
The vRealize Operations Manager NGC plugin for the vSphere Web Client has been removed in vRealize Operations Manager 6.6.
For information about removing the vRealize Operations Manager plugin from vSphere after upgrading to 6.6, see KB 2150394 .
Note: Under New Known Issues, see the Installation and Update section for issues related to installing vRealize Operations Manager or updating the software. There are also some older known issues regarding installation or upgrading that may be relevant. Please look in the lower toggled set of notes for these issues.
Top of Page
Resolved Issues From Previous Releases
This section contains previous known issues that are resolved in this release:
- Enabling pDRS results in a message similar to the following, when the corresponding python adapter instance might have stopped:
Failed to configure predictive DRS. Please close the Manage Solution Window and try again.
New Known Issues in This Release
The new known issues that have been identified since the previous release of the product are grouped as follows:
New Installation and Update Issues
User Interface screens appear blank or with old components after an upgrade.
If customers do not clean the browser cache after an upgrade, user interface screens might appear blank or display old components due to conflicts with the current browser cache.
Workaround: Clean the browser cache after upgrading.
New User Interface Issues
Error messages might appear during initial setup of nodes
During vRealize Operation Manager 6.6 installation, when performing operations that involve initial setup of nodes, such as new installation, expanding an existing installation, or enabling HA for the first time, an error message similar to Error:Permission denied to access property"timeStamp" might appear. There is no impact of this error on the cluster. This is an user interface issue.
New General Issues
Custom vSphere tags are not displayed in vRealize Operations Manager for vSphere versions 6.0 and higher
Custom tags set in vSphere version 6.0 and higher, fail to appear in vRealize Operations Manager. The issue is applicable for both newly deployed and upgraded vCenter Servers.
Workaround: See KB 2144602.
The Delete Unused Snapshots for VM action appears to have failed due to timeout in vRealize Operations Manager.
When users perform the Delete Unused Snapshots for VM action through vRealize Operations Manager, and the snapshot removal process lasts for more than 120 seconds, the status of this actions appears as failed.
However, the snapshot removal process continues to progress to completion on vCenter Server.
- vRealize Automation Env Overview dashboard continues to display vCenter cluster data even after the vRealize Automation adapter instance is removed.
When a vRealize Automation adapter instance is removed or deleted, the relationships that the adapter built between the vCenter cluster compute resource managed by vRealize Automation and the managed resource entities are not deleted. The vRealize Automation Env Overview dashboard continues to displays vCenter cluster data.
Workaround: Manually delete the relationship between vCenter clusters managed by the particular vRealize Automation adapter instance and the managed resource entity.
The Log tab might not launch the vRealize Log Insight user interface to display logs for all objects.
The Log tab displays log information for only those object types that have their launch configs defined in the describe.xml file of the Log Insight adapter, such as the vCenter adapter objects. For object types that are not defined in the adapter, the Log tab displays an error message similar to the following:
This vROps is not integrated with a Log Insight yet.
Workaround: The View Logs action in the action list of such an object, will lead you to its logs in Log Insight
Top of Page
Known Issues From Previous Releases
For a list of previously known vRealize Operations Manager issues, click here.
Installation and Upgrade Issues
EP OPs agent upgrade from 6.3 to 6.6 might fail.
EP Ops agent upgrade from 6.3 to 6.5 might fail on a few agents in case of large environments. This is shown in the summary report available in the vRealize Operations user interface
Workaround: Try the agent upgrade again by checking the option Install the PAK file even if it is already installed.
- Upgrades from 6.3 to 6.4 may fail.
A PAK upgrade from 6.3 may fail due to a node in a state of waiting for analytics and not responding.
Workaround: Before upgrading from 6.3 to 6.4, customers must take clusters offline.
- Upgrade endpoint operations agent after upgrading the product.
Customers must upgrade the vRealize Operations product to 6.5 before upgrading the endpoint operations agent to 6.5.
Workaround: Customers should consult KB article 2138748 and KB article 2137709 before starting to upgrade.
- Default policy setting may disable some containers.
The default policy setting does not enable the memory "Demand" and "Allocation" containers at installation.
Workaround: To enable these containers, do one of these two steps:
- Disable the memory "Consuming" container in the default policy and enable memory "Demand" and "Allocation" containers.
- Go to Administration -> Policies and select the "Default Policy" policy as the system default.
- Inaccurate numbers of member objects in custom groups after upgrading.
The preview count of the members of a custom group is inconsistent with the actual number of members if the group has any Endpoint Operations objects when you upgrade to vRealize Operations Manager 6.5. This will only occur during upgrades, not for new installations.
Workaround: Customers need to use a VMware script to delete the Postgres self relationship for the Endpoint Operations objects. Contact Technical Support to obtain the script.
- The "Reset default content" checkbox in the "Select Software Update" section does not work correctly.
Customers who are upgrading to 6.5 may find that the "Reset default content" checkbox in the "Select Software Update" section, which is a method for overriding the default content that is normally installed during an upgrade, does not work correctly.
Workaround: After the upgrade completes, go to Administration > Solutions, select the vCenter Server solution, and click Modify. Pay attention to upper right corner.
- vRealize Operations Manager calculates workloads for data center and custom data center objects differently from cluster objects, basing on provisioned capacity instead of entitlement
Entitlement is the HA capacity of a cluster. vRealize Operations Manager suggests workload placements across clusters based on the entitlement provisioned to each cluster, which depends on whether HA is enabled or disabled on the cluster.
Although the workload calculations for cluster objects are based on entitlement, the workload calculations for data center and custom data center objects are based on provisioned capacity. As a result, the workloads for data center and custom data center objects are not calculated correctly when HA is enabled, and do not match the workload calculations for cluster objects.
- When HA is disabled, the entitlement is equal to the hardware provisioned capacity of the cluster. The workload is equal to (Demand + Overhead) ÷ (Provisioned Capacity).
- When HA is enabled, the entitlement is equal to the sum of the cluster overhead and the currently computed HA capacity, minus the HA reservation. The workload is equal to (Demand + Overhead) ÷ (Entitlement).
- Some object alerts not enabled after upgrading to the current release of vRealize Operations Manager.
After users upgrade to version 6.3, 6.4, or 6.5 from an earlier version that had vSphere Hardening Guide alerts enabled, users will not see alerts related to distributed port groups, distributed virtual switches, or vCenter objects as these alerts are not enabled by default on upgrade.
Workaround: Choose one of the following:
- Enable hardening guide alerts from the adapter configuration.
- Go to the policy library, edit the active policy to enable alerts for these three objects.
- vRealize Operations Manager alerts trigger when the Management Pack for vCenter Configuration Manager (VCM) is integrated
When the Management Pack for VCM is installed and the vSphere Hardening Guide alerts are enabled for 5.5 or 6.0 objects, some of the native compliance alerts inadvertently trigger in vRealize Operations Manager. The compliance score for a selected object displays the violated native compliance rules in the Compliance tab, which results in an incorrect compliance badge score.
Workaround: Disable the native compliance alerts with these steps:
- To see the native compliance alerts that are enabled in the policy, click Content > Alerts.
- Click Administration > Policies > Policy Library.
- Edit the policy applied to the objects and disable the native compliance alerts.
- Watchdog might restart Tomcat
If there are multiple agents registered to a master node directly, then Watchdog might restart Tomcat whenever there is a need, where UI runs on it. There is, however, no such implication on the product or the cluster.
Workaround: Register agents to remote collector or a load balancer instead of to a Master node.
- 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:
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: Do not manually remove vRealize Operations Manager directories.
- It might be unclear that an update has failed
If a customer reboots a node or kills some active processes during a software update, the update process continues to show that the update is still underway even though it has failed.
Top of Page
Top of Page
User Interface Issues
- 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.
- 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
- 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:
Workaround: Determine the areas of the environment in which the latency is greater than 20 milliseconds and install a remote collector in those areas.
- The user interface is responding slowly
- Metrics are slow to be displayed
Top of Page