Trusted Solaris 8 Installation and Configuration on the Sun Enterprise 10000

Installing SSP 3.3 on a Trusted Solaris 8 Operating Environment

Before installation, all of the preparatory work in Chapter 3, Preparing for SSP 3.3 Installation should be complete. If you plan to install a spare SSP and a main SSP, install the spare SSP first.

To Create a New Trusted Solaris SSP 3.3 Disk

All tasks are performed by the system administrator (admin role) at the label admin_low.

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

In the admin role, finish setting up the CD-ROM if you have not done so.

See Setting up a CD-ROM if you are unfamiliar with the procedure.

Change directory to the Tools directory:

ssp$ cd /cdrom/admin-cdrom_0/trusted_sol_8_sup1/System_Service_Processor_3.3/Tools

Install the Trusted Solaris SSP software by typing:
ssp$ ./ssp_install ../Product

When you are asked to install the SUNWsspfp (the SSP flash prom image) package, type y.

The installation process verifies the disk space available and checks for any conflicts with packages already installed.

If conflicting files exist, type y when you are asked if you want to install these conflicting files.

Use the Device Allocation Manager to deallocate the CD-ROM drive. Remove the CD.

If you are unfamiliar with the steps, see Deallocating the CD-ROM.

If you have a backup file of a previous SSP environment, restore this file by typing:
ssp$ /opt/SUNWssp/bin/ssp_restore backup_directory/ssp_backup.cpio
where the backup_directory is the directory in which the ssp_backup.cpio file resides. For information on backing up the SSP, see To Create an SSP Backup File.

Configure the SSP as a main or spare using the ssp_config(1M) command.
ssp$ /opt/SUNWssp/bin/ssp_config
The subsequent prompts and information displayed will vary depending on whether you restored a backup file in Step 9.

The following is an example session that shows the prompts and responses displayed if you restored an SSP backup file and you are configuring the main SSP:
```
Beginning setup of this workstation to act as a MAIN or SPARE SSP.
Are you currently configuring the MAIN SSP? (y/n)y
MAIN SSP configuration completed.
```

If you did not restore the SSP environment during the install procedure, you will be prompted for system information. See To Enter SSP System Information for details.

Reboot the SSP.

Enter the the value for the SUNW_HOSTNAME variable (the platform name) when you are prompted to do so.

If you have just configured the spare SSP, stay in the admin role to perform the following steps on each domain.

If the domain is running Trusted Solaris software, the following steps need to be run from the admin role. See Step 1 for how to access a Trusted Solaris domain from the admin role.

If the domain is running Solaris software, you can get to the domain's root user via netcon(1M) then logging in as root.
1. Edit the /etc/ssphostname file to replace the host name of the main SSP with the host name of the spare SSP.
2. Switch console communication from the main SSP to the spare SSP by typing:
  $ /etc/init.d/cvc stop $ /etc/init.d/cvc start
3. Configure the spare SSP by following the steps in Configuring Trusted Solaris SSP 3.3.

If you have just configured the main SSP, do the following:
1. Monitor the platform message file by typing:
  ssp% tail -f $SSPLOGGER/messages
2. Before proceeding, wait for the “Startup of SSP programs complete” message to appear in the log.
  
  The platform message file displays information about various SSP processes that are started. If you did not restore an SSP backup file, the thermcaldata.tcl database is generated during SSP startup, which may take some time to complete.
3. Check the platform message file and verify that the correct flash PROM version (3.46) is installed.
  
  For information on updating the control board prom, see the cb_prom(1M) man page.
Note –
If an error occurs during installation, use the pkgrm(1M) command to remove all SSP 3.3 software packages that were installed, and return to the beginning of the SSP 3.3 installation procedure.

To Install and Synchronize Spare and Main SSPs

The main SSP is installed after the spare SSP is installed and configured.

Install Trusted Solaris 8, Trusted Solaris SSP 3.3, and Trusted Solaris AP 2.3 on the main SSP.

If you have made changes to the SSP environment on the spare SSP, synchronize the two SSPs using new backup files.
1. In the admin role at label admin_low, create a backup file on the spare.
  ssp$ /opt/SUNWssp/bin/ssp_backup backup_directory
2. In the admin role at label admin_low, restore the backup file on the main SSP.
  ssp$ /opt/SUNWssp/bin/ssp_restore backup_directory/ssp_backup.cpio