C H A P T E R  3

Installing SSP 3.5 on a New Disk

Before installation, review the SSP 3.5 requirements explained in Chapter 2 .



Note - If you are currently running SSP version 3.2, 3.3, or 3.4, it is suggested that you use ssp_upgrade(1M) to upgrade to SSP 3.5. For details, see Chapter 4.




SSP 3.5 Installation Process

Creating a new SSP 3.5 disk involves the following tasks:

The following sections provide detailed descriptions of the SSP 3.5 installation steps using Solaris Web Start or the ssp_install command.


Using Solaris Web Start

You can use Solaris Web Start to install the SSP 3.5 software. You can use Solaris Web Start to perform a fresh install from CD-ROM or from files you have downloaded from the Web.

The following procedure describes the steps involved when you use Solaris Web Start to install SSP software on either the main or spare SSP.


procedure icon  To Create a New SSP 3.5 Disk Using Solaris Web Start



Note - If an error occurs during installation, manually remove all the SSP 3.5 software packages that were installed by using the pkgrm(1M) command and return to the beginning of this installation procedure. For details on removing packages, see Chapter 6.



1. Log in as superuser on the machine that is to be the main SSP.

2. Set the DISPLAY environment variable.

For sh (1) or ksh (1), type:

ssp# DISPLAY=hostname:0
ssp# export DISPLAY

where hostname is the host name of the machine used to graphically display Solaris Web Start.

3. Begin Solaris Web Start by typing:

ssp# cd base_directory 
ssp# ./installer

where base_directory specifies one of the following:

4. Select Custom Install, then select the System Service Processor 3.5 software.

With custom installation, only the products that you select are installed.

5. Verify that you have sufficient disk space to cover the requirements displayed on the Ready to Install dialog.

ssp# df -k

6. Click the Install Now button.

Wait until the installation is complete and the Installation Summary dialog is displayed.



Note Note - The /var/sadm/install/logs directory contains all the Solaris Web Start log files.



7. Configure the SSP using the ssp_config (1M) command.

ssp# /opt/SUNWssp/bin/ssp_config

During the configuration process, the floating IP address for the host name of the main SSP is verified. If this floating IP address is not valid, you will be prompted for the IP address. You will also be prompted for the following system information:

You must specify what type of processor modules you have installed in your
Enterprise-10000 platform. If you have a mixture of processors, select the
option corresponding to the lowest processor speed in your configuration. Please
select one of the options below.
1) 250 MHz processors
2) 336 MHz processors
3) 400 MHz processors
4) 466 MHz processors
5) Unlisted (manually enter clock values)
What speed of processors do you have installed? 2
Your selections are apparently for a 336 MHz processor.
Is this correct? (y/n) y
The platform name identifies the entire host machine to the SSP software. The
platform name occupies a different name space than domain names (hostnames of
bootable systems).
What is the name of the platform this SSP will service? allxf4
Please enter the floating host name of the main SSP [allxf4-ssp-main]: allxf4-ssp-main
main SSP name = allxf4-ssp-main
main SSP address = 192.168.95.109
Is this correct? (y/n) y
Do you have a control board 0? (y/n)y
Please enter the host name of the control board 0 [allxf4cb0]: xf4-cb0
Do you have a control board 1? (y/n)y
Please enter the host name of the control board 1 [allxf4cb1]: xf4-cb1
Please identify the primary control board.
Is Control Board 0 [xf4-cb0] the primary? (y/n)y
Platform name     = allxf4
Control board 0 = xf4-cb0 => 192.168.151.123
Control board 1 = xf4-cb1 => 192.168.152.123
Primary Control Board = 0
Is this correct? (y/n)y
SSP configuration completed.

8. If you have an SSP backup file (ssp_backup.cpio) , restore the backup file using the ssp_restore (1M) command.

ssp# /opt/SUNWssp/bin/ssp_restore backup_directory/ssp_backup.cpio

where the backup_directory is the directory in which the backup file resides.



caution icon

Caution Caution - If you specify a non-SSP 3.5 backup file, the $SSPVAR/data and $SSPVAR/ict directories are not restored, which prevents corruption of the hardware database. If a warning message tells you to run the autoconfig(1M) command, be sure to shut down your domains before running the autoconfig command. Otherwise, your running domains stop arbitrarily (arbstop).



If you do not have a backup file, but you have a main SSP running version SSP 3.5 software, you can create an SSP 3.5 backup file using the ssp_backup (1M) command on the main SSP. For details, see To Create an SSP Backup File .

9. Reboot the SSP.

10. Log in to the SSP as user ssp and specify a new password when you are prompted to do so.

11. Enter the SUNW_HOSTNAME (the platform name you specified when configuring the SSP) when you are prompted to do so.

12. If you have just configured the main SSP, do the following:

    a. Monitor the platform message file by typing:

    ssp% tail -f $SSPLOGGER/messages

    b. Before proceeding, wait for the Startup of SSP as MAIN complete message to display.

    It can take several minutes for this message to be displayed while the failover daemon determines the role of the SSP as either the main or spare. 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 might take some time to complete, depending on your configuration.

    c. Check the platform message file and verify that the correct flash PROM version (3.47) is installed.

    For information on updating the control board PROM, see the man page for the cb_prom (1M) command.

13. Be sure that the floating host name is specified in the /etc/ssphostname file for each domain.

    a. From the main SSP, or from another workstation on the network, rlogin to the domain as superuser.

    b. Edit the /etc/ssphostname file to replace the host name of the main SSP with the host name of the floating IP address.

    c. Verify that the floating IP address and the floating host name are in the
    /etc/hosts file.

    d. Redirect console communication to the new floating IP address.

    # ps -ef | grep cvcd
    # kill -9 cvcd_pid
    # cvcd_path/cvcd

    where cvcd_path is /sbin under the Solaris 2.6 operating environment, and cvcd_path is /platform/SUNW,Ultra-Enterprise-10000/lib/ under the Solaris 7, 8, and 9 operating environments.

    e. For each domain, update the /etc/syslog.conf file to replace the host name of the former main SSP with the floating host name.

14. If you have other software that communicates with the main SSP, such as Suntrademark Management Center, be sure to change the communication path (for that software) to the floating IP address.

15. If you need to install the SSP software on the spare SSP, do the following:


Using the ssp_install Command

The ssp_install command is a utility that enables you to install the SSP software from the command line. The following procedure describes the steps involved when you use ssp_install on either the main or spare SSP.


procedure icon  To Create a New SSP 3.5 Disk Using the ssp_install Command



Note Note - If an error occurs during installation, manually remove all the SSP 3.5 software packages that were installed by using the pkgrm(1M) command, and then return to the beginning of this installation procedure. For details on removing packages, see Chapter 6.



1. On the SSP, log in as superuser and change to the Tools directory.

ssp# cd base_directory/System_Service_Processor_3.5/Tools

where base_directory specifies one of the following:

2. Install the SSP software by typing:

ssp# ./ssp_install ../Product

3. 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.

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

5. Configure the SSP using the ssp_config command.

ssp# /opt/SUNWssp/bin/ssp_config

During the configuration process, the floating IP address for the host name of the main SSP is verified. If this floating IP address is not valid, you will be prompted for the IP address. You will also be prompted for the following system information:

6. If you have an SSP backup file (ssp_backup.cpio) , restore the backup file using the ssp_restore (1M) command.

ssp# /opt/SUNWssp/bin/ssp_restore backup_directory/ssp_backup.cpio

where the backup_directory is the directory in which the backup file resides.



caution icon

Caution Caution - If you specify a non-SSP 3.5 backup file, the $SSPVAR/data and
$SSPVAR/ict directories are not restored, which prevents corruption of the hardware database. If a warning message tells you to run the autoconfig(1M) command, be sure to shut down your domains before executing the autoconfig command. Otherwise, your running domains arbstop.



If you do not have a backup file, but you have a main SSP running version SSP 3.5 software, you can create an SSP 3.5 backup file using the ssp_backup (1M) command on the main SSP. For details, see To Create an SSP Backup File .

7. Reboot the SSP.

8. Log in to the SSP as user ssp and specify a new password when you are prompted to do so.

9. Enter the SUNW_HOSTNAME (the platform name you specified when configuring the SSP) when you are prompted to do so.

10. If you have just configured the main SSP, do the following:

    a. Monitor the platform message file by typing:

    ssp% tail -f $SSPLOGGER/messages

    b. Before proceeding, wait for the Startup of SSP as MAIN complete message to display.

    It can take several minutes for this message to be displayed while the failover daemon determines the role of the SSP as either the main or spare. 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, depending on your configuration.

    c. Check the platform message file and verify that the correct flash PROM version (3.47) is installed.

    For information on updating the control board PROM, see the man page for the cb_prom (1M) command.

11. Be sure that the floating host name is specified in the /etc/ssphostname file for each domain.

    a. From the main SSP or from another workstation on the network, rlogin to the domain as superuser.

    b. Edit the /etc/ssphostname file to replace the host name of the main SSP with the host name of the floating IP address.

    c. Verify that the floating IP address and the floating host name are in the
    /etc/hosts file.

    d. Redirect console communication to the new floating IP address.

    # ps -ef | grep cvcd
    # kill -9 cvcd_pid
    # cvcd_path/cvcd

    where cvcd_path is /sbin under the Solaris 2.6 operating environment, and cvcd_path is /platform/SUNW,Ultra-Enterprise-10000/lib/cvcd under the Solaris 7, 8, and 9 operating environments.

    e. For each domain, update the /etc/syslog.conf file to replace the host name of the former main SSP with the floating host name.

12. If you have other software that communicates with the main SSP, such as Sun Management Center, be sure to change the communication path (for that software) to the floating IP address.

13. If you need to install the SSP software on the spare SSP, do the following: