Updated on: 11 APR 2019

VMware SDDC Health Monitoring Solution Release Notes | 11 APR 2019 | Build 13254623

What's in the Release Notes

The release notes cover the following topics:

Introduction

The VMware SDDC Health Monitoring Solution 6.0 monitors the health of VMware SDDC components in the SDDC stack. Version 6.0 of the SDDC Health Solution monitors the following components:

  • VMware vCenter Server
  • VMware vRealize Operations Manager
  • VMware vRealize Automation
  • VMware NSX for vSphere
  • VMware vSAN
  • VMware vRealize Business for Cloud
  • VMware vRealize Log Insight
  • VMware Site Recovery Management
  • VMware Orchestrator Management
  • VMware NSX-T
  • VMware Identity Manager

What's New

  • Health of VMware Identity Manager resources like  Certificates, Disk space, Database connections, and so on
  • Health of additional NSX-T components like transport nodes
  • Updated sizing dashboard based on new recommendations
  • VMware vRealize Operations Management Pack for NSX-T is no longer bundled with the SDDC Health Monitoring Solution and is available as a separate Management Pack in the Marketplace

Compatibility

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

Limitations

The upgrade from VMware SDDC Health Monitoring Solution 5.0 to 6.0 is supported with certain limitations. For details, see VMware SDDC Health Monitoring Solution Guide.

Resolved Issues

  • 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

Known Issues

  • SDDC Health instance is not created on newly added vRealize Operations Node

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

    Workaround: Create an SDDC 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 SDDC Management Health Overview dashboard

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

  • SDDC 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 SDDC Management health objects, then vRealize Operations generates duplicate notification alerts. These alerts are generated from out-of-the-box (OOTB) and SDDC Health MP.  In general, these policies are not assigned to the SDDC health group by default. SDDC Health MP creates a custom policy SDDC health Policy, which disables OOTB alerts and a custom group SDDC Health Group. 

    Workaround:

    1. Edit SDDC Health Group from Custom Group and assign SDDC 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 SDDC health solution did not use credentials separately for collecting appliance services. Whereas with SDDC 6.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 SDDC 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.
  • The number of children for all vRealize Automation Application nodes are not the same.

    Health configurations node does not list all vRealize Automation Application nodes. The nodes are  present in only one of vRealize Automation Application nodes. This issue is seen only in vRealize Automation 7.4 HA environment. 

    Workaround: None

  • Object topology does not list all the discovered objects

    The object topology does not list all the discovered objects when navigating to vRealize Automation health from SDDC management health. This issue is seen only when you use vRealize Automation 7.3.

    Workaround: None

  • Duplicate content such as dashboards, alert, and symptom definitions are created

    If you do not select Reset Default Content check box, the health status of the child node is not rolled up to the parent node and content such as dashboards, alerts, and symptom definitions are duplicated.

    Workaround: None

  • "Cluster Node load (%)" and "Cluster Object load (%)" metrics not available for extra small multi-node setup

    SDDC 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 “SDDC Management Health Overview” dashboard.

    Workaround: None

  • Upgrade of SDDC Health Monitoring Solution does not remove the NSX-T dashboard from vRealize Operations Manager

    After you upgrade from SDDC Health Monitoring Solution 5.0 to 6.0, the NSX-T dashboard will still be present in the vRealize Operations Manager setup.

    Manually delete the NSX-T dashboard.

  • vCenter is monitored by more than one SDDC adapter instance

    When a vCenter instance shifts from one vROps node to another, SDDC creates a new instance to monitor this vCenter but the existing one remains in 'Collecting Status' and changes to 'Data Not Receiving'

    Workaround: None

  • SDDC Health Monitoring Solution displays the details of the vCloud Director Inventory

    The SDDC Health Monitoring Solution displays the details of the vCloud Directory Inventory under its inventory. But the SDDC Health Monitoring Solution does not collect data for the vCD Management Pack.

    Workaround: None

  • Duplicate adapter instance is created when the host name/IP address is saved with an extra space

    If an adapter instance is created with an extra space in the host name/IP address, SDDC duplicates that adapter instance. Also, the configured adapter instance’s hierarchy will not be displayed under SDDC Health.

    Workaround:

    Delete the original and duplicate adapter instance and reconfigure without adding space in host name/IP address.

check-circle-line exclamation-circle-line close-line
Scroll to top icon