Sun Microsystems Sun SPARC Enterprise M3000 User Manual page 96

The XSCF Unit can be optionally configured to be an NTP client. If you do not
configure the XSCF Unit as an NTP client, the XSCF Unit will run its internal
realtime clock (RTC) based on the setdate(8) command alone.
Domains can be configured to use a time-of-day management policy on an
individual basis, so that each domain can manage its own time-of-day in a different
manner. Domain time-of-day policies include:
If no time or date configuration is done on the Solaris OS domain (that is, you do
■
not set up the system as an NTP client and you do not use the Solaris OS date
command to set the domain's date), the Solaris OS domain will obtain its initial
time-of-day from the XSCF Unit.
A Solaris OS domain can be set up as an NTP client with the XSCF Unit being the
■
NTP server. In this case, the XSCF Unit must be set up as an NTP server. In this
case, the Solaris OS domain will obtain its initial time-of-day from the XSCF NTP
server, which will then be used to keep the Solaris domain and the XSCF unit in
sync.
A Solaris domain can be set up as an NTP client from an external NTP server. In
■
this case, the initial time for Solaris OS will be obtained from the XSCF Unit. If
you connect the domain to an external NTP server, connect a high rank NTP
server that supplies the time at the same accuracy for the domain as for XSCF.
If you use the Solaris OS date command to set the time on a Solaris OS domain,
■
the time offset between the Solaris OS domain and the XSCF Unit will be
preserved over reboots. Whenever the Solaris OS domain boots, its initial time-of-
day will be the XSCF Unit time adjusted by the time offset created the last time
the Solaris OS date command was used on the domain.
TABLE 2-7
2-44 SPARC Enterprise Mx000 Servers XSCF User's Guide • August 2009
lists the settings and the corresponding shell commands.