Owner's Manual

Troubleshooting and Recovery 431
If an ‘*’ is not displayed against one of the configured servers, something may
not be set up properly. The output of the above command also contains
detailed NTP statistics that may be useful in debugging why the server does
not synchronize. If you attempt to configure an NTP server that is Windows
based, it may help to increase the MaxDist parameter for ntpd. Before
changing this parameter, read and understand all implications of doing so,
especially since the default setting should be large enough to work with most
NTP servers. To modify the parameter type the following command:
racadm config –g cfgRemoteHosts –o cfgRhostsNtpMaxDist 32
After making the change, restart the ntpd by disabling NTP, waiting 5-10
seconds, then enabling NTP again.
NOTE: NTP may take an additional 3 minutes to try and synchronize again.
To disable NTP, type:
racadm config –g cfgRemoteHosts –o cfgRhostsNtpEnable 0
To enable NTP, type:
racadm config –g cfgRemoteHosts –o cfgRhostsNtpEnable 1
If the NTP servers are configured correctly and this entry is present in the
trace log, then this confirms that CMC is unable to synchronize with any of
the configured NTP servers.
There may be other NTP related trace log entries to assist in your
troubleshooting effort. If it is a NTP server IP address misconfiguration
problem, you may see an entry similar to the following:
Jan 8 19:59:24 cmc ntpd[1423]: Cannot find existing
interface for address 1.2.3.4 Jan 8 19:59:24 cmc
ntpd[1423]: configuration of 1.2.3.4 failed
If an NTP server setting has been configured with an invalid host name, you
may see a trace log entry as follows:
Aug 21 14:34:27 cmc ntpd_initres[1298]: host name not
found: blabla Aug 21 14:34:27 cmc ntpd_initres[1298]:
couldn't resolve `blabla', giving up on it
See "Using the Diagnostic Console" on page 425 for information on how to
enter the gettracelog command to review the trace log using the CMC
GUI.