Alert : "NTP Servers are not reachable" is referring to an old configuration
search cancel

Alert : "NTP Servers are not reachable" is referring to an old configuration

book

Article ID: 415188

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

  • After changing NTP server for the Cluster nodes and Cloud Proxy, the old NTP server is still present and not reachable in the vRealize Operations Cloud Proxy and vRealize Operations Cloud Node metrics as per below screenshot:



  • The NTP has been changed from the Aria operations Admin UI as per documentation Configuring the Global Network Time Protocol (NTP) Settings
  • The NTP has been also edited in vCenter on vApp Custom Properties for the Virtual Machine as per documentation at  OVF Authoring Options for a Virtual Machine

Environment

Aria Operations 8.18.x

Cause

By default the metrics tree shows the metrics if there has been collection for it for last 7 days.

Resolution

After 7 days from the date the NTP was changed, the old/removed NTP should not be reported under the vRealize Operations Cloud Proxy and vRealize Operations Node anymore.

Additional Information

To prevent the alert generation for the old/removed NTP server, the old NTP server has to be added to the exclude list in the symptom definition as below:

  1. On the Aria Operations product UI expand Operations from the left menu and click Configurations.
  2. Search and click on the Symptom Definitions tab.
  3. Search for the below symptoms definitions:

    NTP Servers not reachable from cloud proxy
    NTP Servers are not reachable from node

  4. Select the symptoms definition, click on the three vertical ellipsis and click Edit
  5. Click “Advanced Settings” to expand it.
  6. From the right-side panel, drag and drop the unreachable metrics for the corresponding old/removed NTP server into the exclude list.
  7. Save your changes.