Users Guide

Troubleshooting Network Time Protocol (NTP) Errors
After conguring CMC to synchronize the 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 the clock for the following reasons:
• Problem with the NTP Server 1, NTP Server 2, and NTP Server 3 settings.
• Invalid host name or IP address may have been accidentally entered.
• Network connectivity problem that prevents CMC from communicating with any of the congured NTP servers.
• DNS problem, preventing any of the NTP server host names from being resolved.
To troubleshoot NTP related problems, check the CMC Trace Log. This log contains error messages for NTP related failures. If CMC is not
able to synchronize with any of the congured remote NTP servers, then CMC time is synchronized to the local system clock and 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
If the ‘*’ is not displayed for one of the congured servers, the settings may not be congured correctly. The output of this command
contains detailed NTP statistics that may be useful in debugging the problem.
If you attempt to congure a Windows-based NTP server, it may help to increase the MaxDist parameter for ntpd. Before changing this
parameter, understand all the implications, since the default setting must 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, disable NTP, wait for 5-10 seconds, then enable NTP again:
NOTE
: NTP may take an additional three minutes to 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 congured correctly and this entry is present in the trace log, then this conrms that CMC is not able to synchronize
with any of the congured NTP servers.
If the NTP server IP address is not congured, you may see a trace log 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 was congured 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
For information on how to enter the gettracelog command to review the trace log using the CMC Web interface, see Using Diagnostic
Console.
Interpreting LED Colors and Blinking Patterns
The LEDs on the chassis provide the following component status:
• Steadily glowing, green LEDs indicate that the component is powered on. If the green LED is blinking, it indicates a critical but routine
event, such as a rmware upload, during which the unit is not operational. It does not indicate a fault.
Solución de problemas y recuperación
251