1. Alarms and KPIs
  2. Alarms and Events
  3. Platform (31000-32800)
  4. 32117 - TPD NTP offset check failure

3.18.124 32117 - TPD NTP offset check failure

Alarm Group:
PLAT
Description:
This alarm indicates the NTP offset of the server currently being synced to is greater than the critical threshold.
Severity:
Critical
Instance:
May include AlarmLocation, AlarmId, AlarmState, AlarmSeverity, and bindVarNamesValueStr
HA Score:
Normal
Auto Clear Seconds:
0 (zero)
OID:
eagleXgDsrNtpOffsetCheckFailureNotify
Alarm ID:
TKSPLATCR18
Cause:
The NTP offset of the server currently being synced to is greater than the critical threshold.
Diagnostic Information:
Run ntpstat command to diagnose the alarm.

Recovery:

  1. Verify NTP settings and NTP sources can be reached.
    1. Ensure ntpd service is running using ps -ef | grep or service ntpd status.
    2. Verify the content of the /etc/ntp.conf file is correct for the server.
    3. Type /usr/sbin/ntpdc -c sysinfo to check the current state of the ntpd daemon.
    4. 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.
    5. 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 the peer can be reached.
  2. If ntp peer is reachable, then restart the ntpd service.
  3. If problem persists, then a reset of 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. Confirm to recommended NTP topology and strategy.
    • No fewer than tree references are recommended.
    • If selecting a different number, the number should be odd.
    • No intermediate reference should be a virtualized server.
    • Additional recommendations and topology are available in the NTP strategy section in the DSR Hardware and Software Installation 1/2 customer document.
  5. If the problem persists, it is recommended to contact My Oracle Support.