VMware vRealize Operations Management Pack for Cloud Provider Pod 3.2 Release Notes

VMware vRealize Operations Management Pack for Cloud Provider Pod | 15 OCT 2020 | Build 17010459

What's in the Release Notes

The release notes cover the following topics:

• Introduction
• What's New
• Highlights
• Compatibility
• Resolved Issues
• Known Issues

Introduction

The VMware vRealize Operations Management Pack for VMware Cloud Provider Pod 3.2 monitors the health of VMware vCloud Director and the underlying infrastructure.

What's New

The VMware vRealize Operations Management Pack for VMware Cloud Provider Pod 3.2 has been upgraded to use the SDK of vRealize Operations Manager 8.2. There are no enhancements in the functionality of this Management Pack.

Highlights

• VMware Cloud Provider Pod 3.2 includes refactoring code to support latest APIs.
• VMware vRealize Operations Management Pack for VMware Cloud Provider Pod 3.2 monitors the health of VMware vCloud Director and the underlying infrastructure.
• Single pane of glass for monitoring, checking availability, product effectiveness and configuration monitoring
• Provides out of the box dashboards for Cloud Provider Pod Management Health Overview, Historic Trend and vRealize Operations Sizing

Compatibility

For compatibility between products, please refer to the VMware Product Interoperability Matrices.

 

Known Issues

• Cloud Provider Pod Management Pack contains the vRealize Automation details.

  The Cloud Provider Pod Management Pack displays the details of vRealize Automation Health object in the Cloud Provider Pod Products - Health Overview widget. The object type details is also displayed under Cloud Provider Pod Health Adapter Inventory.

  Workaround: None

• vSAN Cluster is shown as service under vCloud in Cloud Provider Pod Management Overview

  In VMware Cloud Provider Pod Management Pack only one vSAN cluster is displayed as a service, even though two vCloud Directors have a cluster each.

  Workaround: None

• Cloud Provider Pod Health instance is not created on newly added vRealize Operations Node

  When you install the Cloud Provider Pod Management Pack and try adding a data node to the vRealize Operations cluster, the Cloud Provider Pod Health adapter instance is not created

  Workaround: Create a Cloud Provider Pod Health adapter instance manually from the UI after the adding the data node.

• VMware Site Recovery Management instances are not shown in the instance healthy widget in Cloud Provider Pod Management Health Overview dashboard

  The VMware Site Recovery Management instances are not displayed in the  “Are Instances Healthy?” widget.

  Workaround: None

• Health issue that occurs in logical router service does not reflect for service and affects only the parent health

  When a router service fails, the health is still green and only the router service parent health changes. This happens because the alert is triggered on router instead of service. In this case, focus on the router health and ignore the health of the router service.

  Workaround: None

• Cloud Provider Pod Management Health dashboard overrides the generic notification alert defined out-of-the box (OOTB) in VMware vRealize Operations Manager

  If the policy is not applied for all Cloud Provider Pod Management health objects, then vRealize Operations generates duplicate notification alerts. These alerts are generated from out-of-the-box (OOTB) and Cloud Provider Pod Health MP. In general, these policies are not assigned to the Cloud Provider Pod health group by default. Cloud Provider Pod Health MP creates a custom policy Cloud Provider Pod health Policy, which disables OOTB alerts and a custom group Cloud Provider Pod Health Group.

  Workaround:

  1. Edit Cloud Provider Pod Health Group from Custom Group and assign Cloud Provider Pod health policy from the Policy drop-down menu.
  2. Select the Keep group membership up to date check box.
  3. Click Save.
• When configuring vCenter Host OS credentials in the Inventory Explorer, a notification alert is triggered on the vCenter deployment object

  Earlier, the Cloud Provider Pod health solution did not use credentials separately for collecting appliance services. Whereas with Cloud Provider Pod 2.0, data related to an appliance is not collected when creating a vCenter adapter instance.

  Workaround: To generate data related to appliance service:

  1. Click the Administration, click Configuration and select Inventory Explorer.
  2. Select the Cloud Provider Pod Health Adapter Instance with a vCenter server object type with the name as FQDN/IP given during vCenter adapter instance creation.
  3. Edit the object and provide the details of a local OS credential where shell is enabled.
• "Cluster Node load (%)" and "Cluster Object load (%)" metrics not available for extra small multi-node setup

  Cloud Provider Pod Sizing dashboard does not display the "Cluster Node load (%)" and "Cluster Object load (%)" fields for vROps cluster that is made of more than one extra small node. This is because the sizing guidelines for vROps cluster made up of more than one extra small node does not publish Object and Metric processing capability

  Workaround: Ensure that the XS vROps cluster does not have more than one node

• No data displayed for NTP Server and Backup Job Services in “Are Services Healthy?” widget

  For NTP Server and Backup Job Services, no data is displayed in the “Are Services Healthy?” widget under “Cloud Provider Pod Management Health Overview” dashboard.

  Workaround: None

• Management Pack for Cloud Provider Pod contains the vRealize Automation inventory.

  The Management Pack for Cloud Provider Pod displays the details of vRealize Automation inventory under its inventory. However, the Management Pack for Cloud Provider Pod does not collect data for the vRealize Automation Management Pack.

  Workaround: None

• The dashboards of the Management Pack for Cloud Provider Pod 2.0 do not display data after installation

  After installing the Management Pack for Cloud Provider Pod 2.0, the dashboards do not display any data and keeps loading with the configuration.

  Workaround:

  • Enable vcenter and vSAN NMP
  • Install and configure the adapter instances for NSX-T MP and vCD MP
• Multiple vRO instances of Cloud Pod object are created 

  Multiple vRO instances of Cloud Pod object are created if the host IP contains space. Also, this vRO instance will not be displayed under vRO Health.

  Workaround:

  Delete the original and duplicate adapter instance of vRO and reconfigure the vRO instance without adding space in host IP.

• Management Pack for VMware Cloud Provider Pod does not monitor the vCloud vCenter and vCloud hosts for vCloud Director 9.7 and later versions

  Management Pack for VMware Cloud Provider Pod does not monitor the health of vCloud vCenter and vCloud hosts as the vCloud Director 9.7 and later versions have deprecated the relationship between cloud cells and vCenter.

  Workaround: None