"vCenter app health is affected" alert is triggered due to DNS lookup Failed result
search cancel

"vCenter app health is affected" alert is triggered due to DNS lookup Failed result

book

Article ID: 404113

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

As part of the VMware Infrastructure Health (VIH) adapter, on environment with SDDC Manager configured, VIH initiate an API call to the SDDR MGR SOS Utility to retrieve health data such as Forward and Reverse Lookup DNS results. These results can be found on the collector of the vCenter adapter in the following location:

  • /usr/lib/vmware-vcops/user/plugins/inbound/VMwareInfrastructureHealthAdapter/work/Health-results.json

The results are updated as part of the Properties metrics on the VIH vCenter app object.

Sample of the Health-results.json file as followed:

As seen from the vCenter App object screenshot above, the vCenter object is showing the value as FAILED on the "DNS | Forward Lookup Status" properties metric.

However, on the Health-results.json screenshot, the "vCenter Forward DNS lookup check" is showing a PASSED status.  The result is not consistent between the json result vs the Properties of the vCenter app object, leading to the following alert being triggered:

Alert: "vCenter app health is affected"

Symptom: "The Immediate symptom vCenter DNS forward lookup status is not passed has been observed on vCenter vc.example.com DNS|Forward Lookup Status "FAILED" != PASSED"

Environment

Aria Operations 8.x

Cause

This is a known issue on Aria Operations 8.18.x.  The actual values of the Forward and Reverse DNS are being swapped.  The DNS Forward Lookup from the json result is being set to the DNS Reverse Lookup Properties on the vCenter App object.  Similarly, the DNS Reverse Lookup from the json result is being set as the DNS Forward Lookup properties on the vCenter App object.

Resolution

This issue will be fixed and included in future product release.  The development and release date may change.

Meanwhile, the following workaround can be applied to swap and place the DNS records in the correct location.

Note: It is important to take the cluster offline, then take a snapshot (without memory checked) on all analytics nodes prior to performing the changes below.

  1. SSH into Primary Aria Operations appliance.
  2. cd /usr/lib/vmware-vcops/user/plugins/inbound/VMwareInfrastructureHealthAdapter/conf
  3. vi describe.xml
  4. Search for VC_APP, and change the values for the DNS sub-section as followed:
    1. Change "REVERSE_LOOKUP_STATUS" to "FORWARD_LOOKUP_STATUS"
    2. Change "FORWARD_LOOKUP_STATUS" to "REVERSE_LOOKUP_STATUS"
  5. Search for NSX_T_APP and change values for the DNS sub-section as followed:
    1. Change "REVERSE_LOOKUP_STATUS" to "FORWARD_LOOKUP_STATUS"
    2. Change "FORWARD_LOOKUP_STATUS" to "REVERSE_LOOKUP_STATUS"
  6. Save the change
  7. Log into Aria Operations UI as local admin.
  8. Go to Administration > Control > Panel > Redescribe.
    1. Select the NSX adapter.  Click "REDESCRIBE".  Wait for it to complete.
    2. Then select the VMware Infrastructure Health adapter.  Click "REDESCRIBE".

Once the redescribe operation is completed, the change should be reflected in the Forward and Reverse Lookup DNS Properties of the vCenter App object after a few cycles of data collection.

Additional Information

Powered by Wolken Software