32534 - TPD NTP Source Is Bad Warning

Alarm Group:

PLAT

Description:

This alarm indicates that an NTP source has been rejected by the NTP daemon and is not being considered as a time source.

Severity:

Minor

Instance:

May include AlarmLocation, AlarmId, AlarmState, AlarmSeverity, and bindVarNamesValueStr

HA Score:

Normal

Auto Clear Seconds:

0 (zero)

OID:

tpdNTPSourceIsBad

Alarm ID:

TKSPLATMI35

Recovery:

1. Verify NTP settings and that NTP sources can be reached.
   1. Ensure ntpd service is running.
   2. Verify the content of the /etc/ntp.conf file is correct for the server.
   3. Verify the ntp peer configuration; execute ntpq -p and analyze the output. Verify peer data, (such as tally code (first column before "remote"), remote, refid, stratum (st), and jitter), are valid for server.
   4. Execute ntpstat to determine the ntp time synchronization status. If not synchronized or the stratum is not correct for server then ping the ntp peer to determine if peer can be reached.
2. If ntp peer is reachable, restart the ntpd service.
3. If problem persists then a reset the NTP date may resolve the issue.

   Note:

   Before resetting the ntp date, the applications may need to be stopped; and subsequent to the ntp reset, the application restarted.
   1. To reset date:
   • sudo service ntpd stop
   • sudo ntpdate <ntp server ip>
   • sudo service ntpd start
4. If the problem persists, it is recommended to contact unresolvable-reference.htm#GUID-DD0927BD-FD0B-4CEB-86E9-98A33C12D4E0.