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:
Verify NTP settings and that NTP sources can be
reached.
Ensure ntpd service is running.
Verify the content of the /etc/ntp.conf file is
correct for the server.
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.
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.
If ntp peer is reachable, restart the ntpd service.
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.