C H A P T E R

C H A P T E R 5

After SSP Installation or Upgrade

After you have completed an SSP installation or upgrade, you may need to do the following:

Edit some of the initialization files in the /export/home/ssp directory.

If you made changes to the files, you did not restore the environment during the fresh install or upgrade, and you want to retain your changes, see Editing Initialization Files .
Configure the Network Time Protocol (NTP) daemon (see Configuring the Network Time Protocol Daemon ).

Editing Initialization Files

When you run ssp_upgrade or ssp_restore , the following files are copied and saved with a .__upgrade suffix. If you have made changes to these files, you can incorporate these changes into the new versions of the files when you have completed the upgrade or install procedure.

The default blacklist (4) file found in /var/opt/SUNWssp/etc is backed up by ssp_backup and restored by ssp_restore . However, if you have created a .postrc file that changes the location of the blacklist file, the relocated blacklist file is not backed up by ssp_backup .

The following files are copied and saved when you run ssp_upgrade or ssp_restore .

/export/home/ssp/.Xdefaults
/export/home/ssp/.xinitrc
/export/home/ssp/.drtclrc
/export/home/ssp/.redxrc
/export/home/ssp/.cshrc
/export/home/ssp/.login
/export/home/ssp/.postrc
/var/opt/SUNWssp/.ssp_private/ssp_resource
/var/opt/SUNWssp/adm/.logger

Note - Be sure that the .cshrc and .login files for user ssp do not contain stty(1M) commands to ensure that the SSP data synchronization feature functions correctly.

The following additional files are copied and saved only when ssp_restore is run:

/export/home/ssp/.ssp_env
/export/home/ssp/.dtprofile
/export/home/ssp/.dt/dtwmrc
/export/home/ssp/.dt/user.dtwmrc

If you made changes to the Ultra-Enterprise-10000.snmpd.cnf file that is in the /etc/opt/SUNWssp/snmp/agt directory, you will have to incorporate your changes into the file installed on the restored system.

Configuring the Network Time Protocol Daemon

If the SSP is to function as a time server, configure the Network Time Protocol (NTP) daemon.

The NTP daemon, xntpd(1M) for the Solaris 2.6, 7, 8, or 9 operating environments, provides a mechanism for keeping the time settings synchronized between the SSP and the domains. OpenBoot trademark PROM obtains the time from the SSP when the domain is booted, and NTP keeps the time synchronized from that point on.

The configuration is based on information provided by the system administrator. If the Sun Enterprise 10000 system is not currently running in an NTP subnet, does not have access to the Internet, and is not going to use a radio clock, you can set up the Sun Enterprise 10000 system to use its own internal time-of-day clock as the reference clock. Usually, however, the SSP uses its internal time-of-day clock for the Sun Enterprise 10000 system.

The NTP packages are compiled with support for a local reference clock. This means that your system can poll itself for the time instead of polling another system or network clock. The poll is done through the network loopback interface. The numbers in the IP address are 127.127.1.0.

Note that NTP can also keep track of the drift (difference) between the external clock and the internal clock. NTP corrects the local clock if it loses contact with the external clock, provided that you have a driftfile declaration in the ntp.conf file. The driftfile declaration specifies to the NTP daemon the name of the file that stores the error in the clock frequency computed by the daemon. See the following procedure for an example of the driftfile declaration in an ntp.conf file.

When setting the SSP and the domains, set the SSP to stratum 8. Set up the domains as peers to the SSP and set the local clock two stratums higher.

If the ntp.conf file does not exist, create it as described below.

To Create the ntp.conf File

1. Log in as superuser.

2. Copy the /etc/inet/ntp.server file to the /etc/inet/ntp.conf file.

# cp /etc/inet/ntp.server /etc/inet/ntp.conf

3. Using a text editor, edit the /etc/inet/ntp.conf file created in the previous step, as explained in the following paragraphs.

The ntp.conf file for the Solaris 2.6, 7, 8, or 9 operating environments is located in /etc/inet . If you are running the Solaris 2.5.1 operating environment, the ntp.conf file is located in the /etc/opt/SUNWxntp directory. You must have an ntp.conf file on the SSP and on each domain.

a. On the SSP, edit the server lines in the ntp.conf file to synchronize clocks.

The following example shows how server lines in an ntp.conf file on the SSP can be set. The peer machine1 and peer machine2 lines are optional and refer to external time servers, if available. Also note the driftfile declaration, which identifies the file that contains the amount of clock error computed by the NTP daemon.

# /etc/inet/ntp.conf for the SSP

server 127.127.1.0

fudge 127.127.1.0 stratum 8

driftfile /var/ntp/ntp.drift

peer machine1

peer machine2

peer spare-ssp2

b. On domains running the Solaris 2.6, 7, 8, or 9 operating environment, edit the /etc/inet/ntp.conf file (or on domains running the Solaris 2.5.1 operating environment, edit the /etc/opt/SUNWxntp/ntp.conf file), and add lines similar to the following example:

# /etc/inet/ntp.conf for the Sun Enterprise 10000 domain

server 127.127.1.0

fudge 127.127.1.0 stratum 10

driftfile /var/ntp/ntp.drift

peer main-ssp

peer spare-ssp2

Note Note - If you do not have any server lines in the ntp.conf file other than the local clock, it might take up to 25 minutes for NTP to synchronize at boot time. For a workaround, refer to Bug 4325813.

For more information on the NTP daemon, refer to the xntpd (1M) man page in the Solaris 9 Reference Manual Collection.

4. Start the xntpd (1M) daemon by typing:

# /etc/init.d/xntpd start