VMware vRealize Operations Manager Appliance 7.5 | 11 April 2019 | Build 13165949
VMware vRealize Operations Manager 7.5 PAK Updates | 11 April 2019 | Build 13165947
VMware vRealize Operations Manager 7.5 Endpoint Operations Agents | 11 April 2019 | Build 13055136
VMware vRealize Operations Manager 7.5 Endpoint Operations Agents PAK Updates | 11 April 2019 | Build 13056189
VMware vRealize Operations Manager 7.5 Pre-Upgrade Assessment Tool | 11 April 2019 | Build 13176775
VMware vRealize Application Remote Collector 7.5 | 11 April 2019 | Build 13122748
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?
- System Requirements
- Installing and Updating vRealize Operations Manager
- Resolved Issues
- Known Issues
The vRealize Operations Manager 7.5 release focuses on ease of use, faster time to value, and extensibility to your environment through new and enhanced integrations. Alongside the existing pillars of performance, capacity, configuration, and compliance, this release also brings in new features around application-aware monitoring and troubleshooting, which helps you manage your multi-cloud environments, hosting both traditional and modern applications.
- Simplified workflows to monitor and troubleshoot off-the-shelf applications.
- Newer Telegraf agents for application and OS monitoring.
- Telegraf agent life-cycle management.
Continuous Performance Optimization
- Ability to run workload optimization on vSAN clusters with support for vSAN datastores (aliased datastores will be supported in future releases).
- Ability to visualize business-intent tag violations for both cluster and host-based placement in workload optimization.
- Ability to assess CPU and memory workload for host groups created with host-based intent for efficient placement decisions.
Efficient Capacity and Cost Management
- Capacity Monitoring Enhancements
- New capacity management use cases with allocation-aware capacity analytics.
- Enhanced custom VM profiles to track the virtual machines remaining.
- New capacity workflows to visualize allocation-based analytics, capacity remaining, and virtual machines remaining for simplified capacity management.
- Capacity Optimization Enhancements
- New capacity reclamation workflow to identify and reclaim orphaned VMDKs and report potential savings (supported from vCenter Server 6.5 onwards).
- Capacity Planning Enhancements
- New and enhanced What-If scenarios for efficient capacity planning.
- Enhanced capacity planning landing page with workload planning, physical infrastructure planning, hyper-converged infrastructure planning, and migration planning scenarios.
- Options to remove VMs and remove hosts to support scenarios such as VM or hardware decommissioning, hardware refresh, and hardware upgrade.
- Ability to run scenarios for adding new vSAN-ready nodes in a vSAN cluster.
- Support for Microsoft Azure, Google Cloud, and IBM Cloud in migration planning.
- Ability to add third-party cloud providers with custom rate cards and to run migration planning scenarios.
- Enhanced migration planning workflows for multi-cloud comparison.
- Ability to combine multiple saved scenarios and stack them to visualize the impact on capacity and to plan efficiently.
- Cost Management Enhancements
- Allocation-aware cost models to compute cluster base rates and virtual machine costs.
- Allocation-aware costs for reclamation of wasted resources such as powered off VMs, idle VMs, and snapshots.
- New cost models for vSAN-ready nodes (HCI) which include storage costs.
- Granular cost control by using the ability to specify costs for individual servers within an existing batch.
- Ability to add ELA based or lump sum cost for licenses, facilities, maintenance, labor, and network.
- Enhanced object relationship topology for complete line-of-sight from applications to infrastructure in the All Metrics tab and in dashboards.
- Accelerated root cause analysis using metric correlation to find positive and negative correlation of desired metrics in the All Metrics tab.
- Ability to preview super metrics using the new super metrics preview functionality in the All Metrics tab.
- Simplified alert workflow with options to group recent alerts by 1-hour and 4-hour time-frames.
- New alerts to monitor and troubleshoot issues related to Proactive HA in vCenter and VASA providers.
- Integration with Service Now using an out-of-the-box Service Now plugin in the outbound alert settings.
- New summary pages for important vSAN objects for quick and easy troubleshooting.
SDDC Configuration and Compliance
- Ability to define, edit, and delete custom compliance templates based on pre-defined or custom compliance alerts.
- Refreshed content in order to support the vSphere Security Configuration Guide 6.7 Update 1.
- New wizard-based super metrics editor to create, preview, and enable super metrics in a simplified workflow. Includes auto-complete hints to easily create complex super metrics.
- Ability to create custom properties for any object that uses smart filtering in the inventory or auto-assign them using the custom groups membership.
- Ability to use custom properties for reporting and filtering.
- New solutions Repository page to enable and disable native solutions with one-click. You can also add new marketplace solutions.
- Enhanced audit capabilities to track user activities such as create, modify, and delete through audit logs.
- New search options to search by notifications and recommendations.
- All new Views navigation to pin and run favorite views.
- Inline editing of global settings for a better user experience.
- Support for VMware Tools version in a sequence-based identifier format (10.3.5) rather than its numeric build number (10249), with updates to the Summary|Guest Operating System|Tools Version property.
- New options in global settings:
- Ability to set the retention time for generated reports (in months).
- Enable/disable non-imported VMware Identity Manager (vIDM) users to be created automatically as read-only users on first access.
- Ability to set custom retention periods for different object types.
- Ability to disable concurrent user login sessions.
- Ability to specify a time period for orphan disk collection.
- REST API enhancements
- A new public API for custom groups has been implemented in this release. Custom group related internal APIs are deprecated and will be removed in the next release.
- Ability to change the admin password.
- Ability to get audit reports in XML and JSON formats.
- Ability to delete a stale certificate.
- Ability to compress large API responses.
Report and Views Enhancements
- Report scheduling enhancements:
- Ability to schedule report delivery with custom time options.
- Ability to schedule report delivery daily.
- Ability to add Copy (CC) and Blind Copy (BCC) for report delivery via emails.
- Table cell coloring capability is extended to PDF formatted reports.
- New option to configure a single custom designed cover page for all out-of-the-box and custom PDF reports.
- Views are enhanced to track changes in metrics and properties over time, with relative and absolute timestamps.
- Ability to group List views based on parent or descendant objects. Summaries at sub-groups levels are also available in views and reports.
Dashboard and Widgets Enhancements
- Wizard-based workflow with consistent widget and views configuration to simplify learning of widgets capabilities.
- Output filter functionality in widgets for increased control over the information displayed.
- Ability to specify the depth of a relationship, beyond simply parent or children.
- New relationship widgets to provide full stack visibility from application to infrastructure.
- Overlay of active alerts based on events, logs, anomalies, and metrics threshold breaches.
- Quick understanding of upstream and downstream impact of a health issue across the stack, to zero down on the root cause.
- Ability to filter objects within dashboard widgets using smart filters based on metrics and properties.
- Ability to copy one or more existing widgets, along with the configuration, while creating new or editing existing dashboards.
- Single-click option to set a pre-configured time for all the widgets with the dashboard level time.
- New out-of-the-box dashboards to monitor and troubleshoot:
- vSphere compute stack
- vSphere storage stack
- vSphere network stack
- Stretched vSAN clusters
- New out-of-the-box reports:
- vSphere Cluster Allocation
- New out-of-the-box alerts to monitor:
- VASA Providers (vSphere APIs for Storage Awareness)
- vSphere Proactive HA
- vSAN encryption status
The Apache version has been upgraded to version 2.2.34 in this release.
This release of vRealize Operations Manager does not support RHEL upgrade.
Microsoft Internet Explorer
Support for Internet Explorer in vRealize Operations Manager 7.5 is limited, and Internet Explorer will not be supported in the next major release of vRealize Operations Manager. It is recommended to switch to another supported browser. See KB 67539 for more details.
Metrics and Properties Enhancements
The following KB article describes all the metrics and properties that have been added in vRealize Operations Manager 7.5:
New Management Packs and Compliance Packs:
- The new VMware Management Packs and Compliance Packs for vRealize Operations Manager 7.5 are:
- vRealize Operations Management Pack for NSX-T 2.0
- vRealize Operations Management Pack for vRealize Orchestrator 3.0
- vRealize Operations Management Pack for Cloud Provider Pod 2.0
- vRealize Operations Management Pack for AWS 3.1
- vRealize Operations Management Pack for VMware Identity Manager 1.0
- VMware SDDC Health Monitoring Solution 6.0
- vRealize Operations Compliance Pack for PCI 1.0.2
Refer to the VMware Product Interoperability Matrix for all VMware Management Packs supported with vRealize Operations Manager 7.5.
The 3rd party authored Management Packs that are supported with 7.5 are listed in the VMware Compatibility Guide.
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. This 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.
Note: In this release, there is an approximate improvement in upgrade time by 10 minutes and an approximate 15% CPU usage improvement across the cluster, which is an additional performance improvement.
You can deploy vRealize Operations Manager 7.5 with VMware virtual appliance.
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 6.0 or later and managed by VMware vCenter Server 6.0 or later. If you have vRealize Operations Manager virtual appliance deployed on ESXi 5.5 hosts, you must first upgrade the vCenter Server to a newer version and then upgrade to vRealize Operations Manager 7.5.
Applying License Keys
IMPORTANT: A new license key is required for vRealize Operations Manager 7.0 and later versions. All license keys except vSOM Enterprise Plus and its add-ons are invalidated. The product will work in evaluation mode until a new valid license key, which can be obtained from the MyVMware portal, is installed. After you log in to the user interface of vRealize Operations Manager, if you see that you are using an evaluation license, consider applying for a new license before the end of the 60-day evaluation period.
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.
You can install multiple Advanced and Enterprise editions in the same vRealize Operations Manager deployment. You 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:
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. To be compliant, you need enough licenses to cover average powered-on VMs over trailing 365 days.
vRealize Operations Standard edition does not entitle you to create or edit views, dashboards, super metrics, reports, and automated actions. It does not entitle you to send application metrics to Wavefront. The vRealize Operations Standard edition also does not entitle business intent-based automated and schedulable workload balancing. This functionality was enforced by EULA in previous editions of vRealize Operations. Starting with vRealize Operations 7.0, this functionality is enforced through the user interface and not just the EULA. For more details on entitlement, please see the Edition Compare table from the following link: https://www.vmware.com/products/vrealize-operations.html.
To ensure compliance of your vSphere 6.7, 6.5, and 6.0 objects, vRealize Operations Manager 7.5 includes compliance alerts for VMware vSphere Hardening Guide versions 6.7 Update 1, 6.5, and 6.0. These hardening guide alerts are based on the corresponding object types. Some of the alerts and symptoms are available only for backward compatibility with older versions of vSphere, even though the current release supports the latest vSphere Security Configuration Guide 6.7 Update 1.
In addition to the VMware solutions (vSphere, Endpoint Operations Management, and vRealize Log Insight), see the Solution Exchange marketplace for many more solutions. These solutions work with Virtual Appliance single or multiple nodes.
When you upgrade your vRealize Operations Manager instance to 7.5, both TLS 1.0 and TLS 1.1 are disabled on all the vRealize Operations Manager nodes. TLS 1.2 is the only protocol that will be supported by default. However, if you want to lower the security bar and enable TLS 1.0 and 1.1, you can still do so, see KB 67108 for more information.
VMware Product Compatibility
Note: The VMware Product Interoperability Matrix provides details about the compatibility of vRealize Operations Manager with VMware products.
This vRealize Operations Manager release supports all current Web browsers, although only the following browsers were tested with this release:
- Google Chrome: Version 72 and 73
- Mozilla Firefox: Version 65 and 66
- Microsoft Edge 17
- Safari 11 and 12
- Internet Explorer 11 (limited support)
Unless upgrading from vRealize Operations Manager 6.7 or above, it is imperative that you run the Pre-Upgrade Assessment tool. A pre-upgrade assessment report that is generated will provide you with the recommended replacements. This tool provides you with an impact analysis following the reduction of metrics in various versions of the product. For more details on using the Pre-Upgrade Assessment Tool, see KB 67663. It is always recommended to run the Pre-Upgrade Assessment tool before an upgrade.
Refer to the vRealize Operations Upgrade Center that has information about upgrading vRealize Operations. Refer to the VMware Lifecycle Product Matrix for information about supported versions of vRealize Operations Manager.
Refer to the vRealize Operations Manager vApp Deployment and Configuration Guide that provides guidance for a vRealize Operations Manager virtual appliance, before you install or update vRealize Operations Manager:
Upgrading to vRealize Operations Manager 7.5, resets out-of-the-box content as part of the 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 are overwritten. You need to clone or backup the content before you upgrade to vRealize Operations Manager 7.5.
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 can also install vRealize Operations Manager by using vRealize Suite Lifecycle Manager. For more information, see Creating an Environment. To automate installation, configuration, upgrade, patch, configuration management, drift remediation and health from within a single pane of glass, you can use vRealize Suite Lifecycle Manager. If you are a new user, click here to install vRealize Suite Lifecycle Manager. This provides IT managers or cloud admin resources to focus on business-critical initiatives, while improving time to value (TTV), reliability, and consistency.
See the Installation and Upgrade Issues section for issues related to installing vRealize Operations Manager or updating the software.
- Cluster management shows that HA is enabled when the process of enabling HA is still in progress
Data synchronization takes some time depending on the number of objects.
The known issues are grouped as follows.Installation and Upgrade Issues
- In a pure IPv6 environment, DNS servers are missing from the /etc/resolv.conf file
DNS servers are missing from the /etc/resolv.conf file when a new node is deployed in a pure IPv6 environment. As a result, the node cannot resolve FQDNs to IP addresses.
Workaround: With the help of your network administrator, manually set the DNS servers in the /etc/resolv.conf file.
- Joining a node to a cluster fails if the IPv6 address after the last colon contains only a numeric
In an IPv6 environment, while trying to join a node to the vRealize Operations Manager cluster, the configuration stalls with a message and times out after one-hour with a node install failure message.
Workaround: Re-deploy the node.
- Missing text in the Pre-Update System Validation Dialog Box
Irrespective of whether the check is successful or not, text is not displayed in the Pre-Update System Validation dialog box while verifying the locking status on the node for the admin and root accounts. You will see a generic error message at the top of the dialog box and the error key is displayed in the Software Update page of the Admin user interface.
- Upgrade might fail if any of the nodes are running on VMs with US/Pacific-New timezone
PostgreSQL database systems no longer support the US/Pacific-New timezone, which was just an alias for America/Los_Angeles timezone. If any of the vRealize Operations Manager nodes are running on VMs with US/Pacific-New timezone, upgrade might fail.
Workaround: Change VM timezones from US/Pacific-New to America/Los_Angeles, and then upgrade.
Some object alerts are not enabled after upgrading to the current release of vRealize Operations Manager
After users upgrade to version 7.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.
- What-If analysis is based on the utilization model
What-If analysis is based on the utilization model for both capacity and cost calculations even if you enable the allocation model.
- The state of a service in a non-existing state remains as is even when it starts collecting data
If you edit the configuration of a service in a non-existing state, the service remains in a non-existing state even when it starts collecting data.
Workaround: Restart the application adapter instance.
- Advanced filtering conditions are ignored in the Environment Status widget
In the Environment Status widget, the advanced filtering conditions are ignored if an option is selected in the tag filter.
- Inconsistent tag violations in the Workload Optimization page
When there is more than one tag assigned to a cluster and cluster-based intent is enabled, there is an inconsistent tag violation in the Workload Optimization page.
- The Logs tab displays a message that states that vRealize Operation Manager is not integrated with Log Insight
If the VMware vRealize Log Insight Management Pack has not been activated from the Administration > Solutions > Repository page, the Logs tab displays a message.
Workaround: Activate the VMware vRealize Log Insight Management Pack from the Administration > Solutions > Repository page.
- Application services are in a stopped state when you start an agent during application monitoring
The application services activated in vRealize Operations Manager 7.0 are in a stopped state after you stop and then start an agent. This occurs when vRealize Operations Manager is upgraded to 7.5 and vRealize Application Remote Collector is upgraded to 7.5.
Workaround: Start the application services manually each time you stop and then start the agent or reactivate the application services once, and the start/stop function of the agent will work as expected.
- After you upgrade from VMware Application Proxy 1.1 to vRealize Application Remote Collector 7.5, services are not discovered
After you upgrade from VMware Application Proxy 1.1 to vRealize Application Remote Collector 7.5, even if the application services are running, vRealize Application Remote Collector does not discover them.
Workaround: Restart the vRealize Application Management Pack adapter after you upgrade from VMware Application Proxy 1.1 to vRealize Application Remote Collector 7.5.
- Agent Installation on Windows Server 2012 fails
You cannot install agents on Windows Server 2012 if you have Visual C++ older than version 14.
Workaround: Perform the following steps to update your Windows Server 2012 machine:
- Make sure Update Manager is enabled in the Windows Server 2012 machine.
- Check for updates. If checking for update fails, perform the steps listed here: https://support.microsoft.com/en-us/help/947821/fix-windows-update-errors-by-using-the-dism-or-system-update-readiness.
- Run the Update Manager again and install the patches.
- Restart the Windows Server 2012 machine and check for updates again. Install additional updates.
- The Windows Server 2012 machine should be patched till April 2014 update rollup for Windows Server 2012 R2 (2919355).
- Download the file from https://www.microsoft.com/en-us/download/details.aspx?id=49063.
- Run the msu using windows update.
- Restart the Windows Server machine.
- Objects such as images and icons related to the Management Pack for SDDC Health, Management Pack for OpenStack, and Management Pack for SRM are not displayed
After you upgrade vRealize Operations Manager, if you scale a vRealize Operations Manager cluster with the Management Pack for OpenStack 5.0, or Management Pack for SRM 8.1, or Management Pack for SDDC Health 5.0 installed and add another vRealize Operations node, some objects such as images and icons related to the management packs are missing.
Workaround: Users with an instance of the Management Pack for OpenStack, or Management Pack for SRM, or Management Pack for SDDC Health must uninstall the management packs, before upgrading vRealize Operations Manager.
- Objects such as images and icons related to the Management Pack for vRealize Orchestrator are not displayed
After you upgrade vRealize Operations Manager, if you scale a vRealize Operations Manager cluster with the Management Pack for vRealize Orchestrator 2.0 installed and add another vRealize Operations node, some objects such as images and icons related to the Management Pack for vRealize Orchestrator 2.0 are missing.
Workaround: Upgrade the Management Pack for vRealize Orchestrator to version 3.0 before upgrading vRealize Operations Manager.
- VVOL datastores are masked
If a VM, host, cluster, datacenter, or vCenter Server object with VVOL datastores is selected, an incorrect datastore count appears on the Environment Objects Map or the Troubleshooting All Metrics page. And if a VM is deployed on a VVOL datastore, raw or derived metrics may be missing.
Workaround: None. The VVOL datastores are masked because vRealize Operations Manager does not yet implement the VVOL datastore metrics. However, the VVOL datastores are included in the count.
- Compliance for vCenter Server workloads on VMware Cloud on AWS is not affected by rules for out-of-the-box alerts
Even if you enable the vSphere Hardening Guide Alerts option when you configure a vCenter adapter instance in vRealize Operations Manager or if you enable vSphere Hardening Guide alerts in some other way, the compliance score for vCenter Server workloads on VMware Cloud on AWS will not be affected by rules for out-of-the-box alerts. At the same time, rules for custom alerts are considered in compliance score calculation for these workloads.
Workaround: Create one or more custom alerts and include those in the custom compliance scorecard calculation.
- Cost is not computed for a VMware Cloud vCenter Server endpoint in vRealize Operations Manager 7.5
In vRealize Operations Manager 7.5, when you add a VMware Cloud vCenter Server endpoint and specify the cloud type as VMware Cloud on AWS, cost is not computed for the VMware Cloud vCenter Server endpoint. However, if you add a VMware Cloud vCenter Server without specifying the cloud type as VMware Cloud on AWS, then the cost is computed.
Workaround: In vRealize Operations Manager 6.7, if you specified the VMware Cloud vCenter Server cloud type as VMware Cloud on AWS, then after you upgrade to vRealize Operations Manager 7.5, you must manually set the cost per server for the VMware Cloud vCenter Server hardware groups to zero.
- Interactions in a distribution type of view, work only for the Current type of transformation
When you create a distribution type of view and select a transformation type that is not Current, the list view is not displayed.
Workaround: Change the selected metric transformation to Current to see the list view. You can add the same metric as an additional
column with a relevant transformation (for example, maximum) and view the result of the transformation in the list view.
- Alerts from the vSAN adapter that correspond to vSAN health check tests are not canceled if the test is removed from the vSAN Health Service.
vRealize Operations Manager cannot detect and cancel deleted alerts.
Workaround: Manually cancel the alert from the user interface of vRealize Operations Manager.
- When using Internet Explorer 11 to access the Log Insight tab pages and dashboards, the data is blocked
When using Internet Explorer 11 to access the Log Insight tab pages and dashboards, data is blocked and the page remains blank.
Workaround: Use the Firefox or Chrome browser.
- Generated reports may be blank
If you log in to vRealize Operations Manager with vCenter Server credentials and generate a report, the generated report is always blank.
- The dashboard link cannot be opened when you use Internet Explorer on Windows 7
When you try to open a dashboard that is a shared URL, the page does not open.
Workaround: You must not use Internet Explorer with Windows 7. Open the link using other browsers.
- Hardcoded string in the Assign Permissions to Role dialog box.
PluginActivation_hadoop is hardcoded in the Assign Permissions to Role dialog box.
- The Last Year option in the date picker is not intuitive
The Last Year option in the date picker indicates that the time range starts from the end of the previous month and goes back a year. It does not indicate a time range that spans one year from the current date or the whole previous year.
- The filter menus in the Policies workspace step called 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 irrespective 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 the data in the widget.
Workaround: Increase the height of the widget in the dashboard to fit all the data.