test

Trusted Solaris 7 Installation and Configuration on the Sun Enterprise 10000

Configuring Trusted Solaris SSP 3.1.1

After you have completed installing Trusted Solaris SSP 3.1.1, you need to check the version of the flash PROM and upgrade if necessary. For SSP 3.1.1, you must upgrade your flash PROM if the version is earlier than 3.46. See "Checking and Upgrading the Control Board Flash PROM" below.

You may also need to:

Checking and Upgrading the Control Board Flash PROM

You need to have the correct version of the flash PROM boot firmware installed on the control boards; the boot firmware is required to download the control board executive (CBE). You must upgrade if the version is earlier than 3.46.

To Check the Flash PROM Version

  1. Log in as a user and assume the ssp role on the main SSP.

  2. Check the version of the flash PROM on your control boards by typing:


    ssp% cb_prom -r -h control_board_name 

Checking PROM revision...3.44

    where control_board_name is the name of the control board as specified in the /etc/hosts configuration file.

    If the version displayed is earlier than 3.46, you must update the flash PROM. To do this, you must upgrade the PROM as described in the following procedure.

To Upgrade the PROM

  1. Type:


    ssp% cb_prom -p /opt/SUNWssp/cbobjs/flash_boot.ima -h \
control_board_name
Programming PROM...complete.

  2. To have the PROM change take effect, type: 


    ssp% cb_reset

Resetting host xf4-cb0...
Resetting host xf4-cb1...
xf4-cb1 is ready...
xf4-cb0 is ready...

    where xf4-cb1 and xf4-cb0 are replaced with the names of the control boards for your system.

  3. Verify the PROM version by typing: 

    ssp% cb_prom -r -h control_board_name
Checking PROM revision...3.46

    where control_board_name is the name of the control board as specified in the /etc/hosts configuration file. The version shown should be 3.46.

Editing Initialization Files

When you run the ssp_restore command, 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 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_restore.

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.

Note -

No copy is made if a file does not exist.

Configuring the Network Time Protocol Daemon

The NTP daemon, ntpd(1M), provides a mechanism for keeping the time settings synchronized between the SSP and the domains. OBP 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 you are not currently running in an NTP subnet, and you do not have access to the Internet, and you are 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 first three numbers in the IP address are 127.127.1. The last numbers in the IP address are the NTP stratum to use for the clock.

When setting up a Sun Enterprise 10000 system and its SSP, set the SSP to stratum 4. Set up the Sun Enterprise 10000 system as a peer to the SSP and set the local clock two strata higher.

If the ntp.conf file does not exist, create it as described in the following procedure.

To Create the ntp.conf File

  1. On the SSP, log in as a user who can assume the root role and assume it.

  2. Create the /etc/inet/ntp.conf file in a text editor.

You must have an ntp.conf file on both the SSP and the platform. The following is an example of server/peer lines in the /etc/inet/ntp.conf file on the SSP. 

server 127.127.1.4

You can add lines similar to the following to the /etc/inet/ntp.conf file on the platform: 

server ssp_name
server 127.127.1.13
fudge 127.127.1.13 stratum 13

For more information on the NTP daemon, refer to the Network Time Protocol User's Guide and the NTP Reference.

Creating a User for the SSP Administrator

The installation of Trusted Solaris SSP 3.1.1 enabled the user install to assume the ssp role. This was done to make it easier to do the rest of the SSP 3.1.1 installation and configuration procedures. However, the user install is not a normal user and should not be used as such. It is highly recommended that a normal user be created for the SSP administrator's login. This user should be able to assume the ssp, root, admin and secadmin roles. For more information on creating a user, see "Using the User Manager to Configure Accounts" in Trusted Solaris Administrator's Procedures.