Trusted Solaris 7 Installation and Configuration on the Sun Enterprise 10000

Installing a Dual SSP Configuration

The following table shows the supported combinations of SSP software for dual SSP configurations:

Table 3-1 Supported Dual SSP Configurations


SSP version on the Main SSP	SSP Version on the Spare SSP
3.1	3.1 or 3.1.1
3.1.1	3.1 or 3.1.1

To Install Trusted Solaris SSP 3.1.1 on the Spare SSP

On the spare SSP (referred to here as SSP2), log in as a user who can assume the root and secadmin roles. Assume the root role.

As root at label admin_low, perform "Installing from a CDROM" if you have not done so.

Change directory to the Tools directory:
```
ssp# cd /cdrom/root/Tools
```

Install the Trusted Solaris SSP 3.1.1 software on SSP2 by typing:
```
ssp# ./ssp_install pathname
```
Where pathname specifies the path to the Product directory, /cdrom/root/Product.

When you are asked if you want to install the SSP 3.1.1 AnswerBook (the SUNWuessp package), type y to install it; otherwise, type n.

If you install the SSP 3.1.1 Answerbook, you must respond to the following prompts:
1. When you are requested to select an installation option, type 2 (heavy installation): Select an installation option: 2
2. When requested to specify the parent path for the AnswerBook2 Collection, type the path to the directory in which you want to put the SSP 3.1.1 AnswerBook.
  
  It is suggested that you install it in /opt. Specify the parent path of this AnswerBook2 Collection directory: /opt
3. Type y at this prompt:
```
This package contains scripts which will be executed with superuser 
permission during the process of installing this package. 

Do you want to continue with the installation of <SUNWuessp> [y,n,?]  y
```

When you are asked if you want to install the SUNWsspfp package, type y to the prompts.

Do you want to install the SUNWsspfp package? (y/n) y
This package contains scripts which will be executed with superuser 
permission during the process of installing this package. 

Do you want to continue with the installation of <SUNWsspfp> [y,n,?]  y

Remove the /cdrom/root/Tools/ssp_install command from the Custom Root Role profile.
1. Assume the secadmin role. At label admin_low, open the Profile Manager application.
2. In the Profile Manager: Load window, select none for the Name Service then click the OK button.
3. In the Profile Manager: Open window select Custom Root Role, then click the Modify button.
4. In the Profile Manager main window, select View from the menu bar, then select Commands from the submenu.
5. Select the /cdrom/root/Tools/ssp_install command from the Include list and move it to the Exclude list.
6. Select Profiles from the Profile Manager main window menu bar then select Save Profile from the submenu to save the profile.
For more details on removing commands from a role's profile, see "To Remove a Command from a Role's Profile" section in Trusted Solaris Installation and Configuration.

Assume the root role, at label admin_low to unmount /cdrom/root using the following command:
ssp# umount /cdrom/root

In the root role, at label admin_low, use the Device Allocation Manager to deallocate the CDROM drive. Remove the CDROM.

Do not use the Volume Manager, it is disabled in the Trusted Solaris environment.

If you have a backup file from the main SSP, restore it on SSP2.
1. In the root role, at label admin_low, copy the ssp_backup.cpio file to a backup directory on SSP2.
2. Type:
  ssp# /opt/SUNWssp/bin/ssp_restore \ backup_directory/ssp_backup.cpio
  Where backup_directory is the directory to which you copied the ssp_backup.cpio file in Step a. This restores the SSP environment on the spare SSP.

Configure the main SSP (referred to here as SSP1) to be a spare SSP using ssp_config(1M).
1. On SSP1, log in as superuser if SSP1 is running Solaris software. If SSP1 is running Trusted Solaris software, log in as a user who can assume the root role, and assume it.
2. Type:
  ssp# /opt/SUNWssp/bin/ssp_config Beginning setup of this workstation to act as a MAIN or SPARE SSP. Are you currently configuring the MAIN SSP? (y/n)n SPARE SSP configuration completed.
3. If SSP1 is currently running SSP 3.1, kill the rarpd process:
  ssp# ps -ef | grep rarpd ssp# kill -9 rarpd_pid
  Where rarpd_pid is the process ID shown by the ps command for rarpd. Killing the rarpd process prevents the SSP from responding to control board boot requests.

Change SSP2 to be the main SSP.
1. On SSP2, log in as a user who can assume the root role, and assume it.
2. Type:
  ssp# /opt/SUNWssp/bin/ssp_config 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 Name the Platform and Control Board" for details.

Reboot SSP2.

Log in as the user install who can assume the role ssp on SSP2. The password for install is install.

The installation of Trusted Solaris SSP 3.1.1 created the ssp role, and assigned the ssp role to the install user.

Assume the role ssp. The password for the ssp role is ssp.

In the ssp role, open a terminal window and check the log message:
ssp% tail -f $SSPLOGGER/messages
Wait for the "Startup of SSP programs complete" message.

On each domain, perform the following steps as root.

If the domain is running Trusted Solaris software, the following steps need to be run from the root role. See Step 1 for how to access a Trusted Solaris domain from the root 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 SSP1 with the host name of SSP2.
2. Switch console communication from SSP1 to SSP2.
  
  If the domain is running Trusted Solaris 7 or Solaris 7 5/99 release or later, issue the following:
```
# /etc/init.d/cvc stop
# /etc/init.d/cvc start
```
  If the domain is running Solaris 2.5, 2.6 or the Solaris 7 3/99 release or earlier, issue the following:
```
# ps -ef | grep cvcd
# kill -9 cvcd_pid
# cvcd_path/cvcd
```
  where cvcd_path is /sbin under the Solaris 2.5 and 2.6 operating environments, and cvcd_path is /platform/SUNW,Ultra-Enterprise-10000/lib/cvcd under the Solaris 7 operating environment.

On the SSP2, perform the steps in "Configuring Trusted Solaris SSP 3.1.1".

If alternate pathing is desired on install the Trusted Solaris AP 2.2 as described in Chapter 5, Trusted Solaris Alternate Pathing 2.2 on the Sun Enterprise 10000 Server.

After SSP2 is installed and configured, you can install SSP1.
1. Install Trusted Solaris 7, Trusted Solaris SSP 3.1.1, and Trusted Solaris AP 2.2 on SSP1.
2. If you have made changes to the SSP environment or SSP2, synchronize the two SSPs using new backup files.
  1. In the root role at label admin_low, create a backup file on SSP2.
    ssp# /opt/SUMWssp/bin/ssp_backup target_directory
  2. In the root role at label admin_low, restore the backup file on SSP1.
    ssp# /opt/SUMWssp/bin/ssp_restore \ backup_directory/ssp_backup.cpio