Owner's Manual

430 Troubleshooting and Recovery
Troubleshooting Network Time Protocol (NTP)
Errors
After configuring CMC to synchronize its clock with a remote time server
over the network, it may take 2-3 minutes before a change in the date and
time occurs. If after this time there is still no change, it may be necessary to
troubleshoot a problem. CMC may not be able to synchronize its clock for a
number of reasons:
• There could be a problem with the NTP Server 1, NTP Server 2,
and NTP Server 3 settings.
• An invalid host name or IP address may have been accidentally entered.
• There could be a network connectivity problem that prevents CMC from
communicating with any of the configured NTP servers.
• There could be a DNS problem, preventing any of the NTP server host
names from being resolved.
CMC provides tools to troubleshoot these problems, with the primary source
of troubleshooting information being the CMC Trace Log. This log contains
an error message for NTP related failures. If CMC is unable to synchronize
with any of the remote NTP servers that have been configured, then it derives
its timing from the local system clock.
If CMC is synchronized to the local system clock rather than a remote time
server, the trace log contains an entry similar to the following:
Jan 8 20:02:40 cmc ntpd[1423]: synchronized to
LOCAL(0), stratum 10
You can also check the ntpd status by typing the following racadm command:
racadm getractime –n