TABLE
TABLE
Entity | Primary NTP Server | Time Synchronization Method |
|
|
|
XSCF | No connection | The XSCF time is the time in the initial system setting or the |
|
| time set with the setdate command. |
| External NTP server | XSCF operates as an NTP client. The XSCF time is adjusted to |
|
| the time of the external NTP server. |
Domain | XSCF | XSCF operates as the NTP server. The domain time is |
|
| adjusted to the time of the XSCF. |
| External NTP server | The domain time is adjusted to the time of the external NTP |
|
| server. |
|
|
|
When domains are powered on, they synchronize their clocks to the NTP server.
If the domain and the Service Processor are using the same time source, one benefit is that events logged in the Solaris OS and on the Service Processor can be correlated based on their timestamp; if the domain and Service Processor use different NTP servers, their times may drift, and correlating log files could become difficult. If you connect a domain to an NTP server other than the one used by the Service Processor, be sure both are
Every NTP server and every NTP client must have an ntp.conf file, in /etc/inet/ntp.conf. The Service Processor has a default ntp.conf file. If you are using NTP, you must create an ntp.conf file on each domain.
If you are using the Service Processor as the NTP server for the domains, create an ntp.conf file on each domain similar to the following:
CODE EXAMPLE
server ip_address slewalways yes disable pll enable auth monitor
driftfile /var/ntp/ntp.drift statsdir /var/ntp/ntpstats/
filegen peerstats file peerstats type day enable filegen loopstats file loopstats type day enable filegen clockstats file clockstats type day enable
where ip_address is the IP address you configured for the Service Processor on the DSCP network. To display the Service Processor’s IP address, use the showdscp
24 SPARC Enterprise Mx000 Servers Administration Guide • November 2007