C H A P T E R

C H A P T E R 6

Falling Back to a Previous SSP Release

This chapter describes the procedures for reverting from SSP 3.5 to a previous version of SSP.

SSP Fall Back

If you have installed SSP 3.5 or have upgraded to SSP 3.5, you can fall back to a previous SSP version (SSP 3.2, 3.3, or 3.4) using the following procedure.

Note - Before you begin the fall back process, be sure that you have an SSP backup file from a previous SSP release.

To Fall Back to a Previous SSP Release

1. If you have a spare SSP, log in to the spare SSP as superuser and stop the SSP daemons on the spare SSP.

ssp# /etc/init.d/ssp stop

2. Perform the following steps on the main SSP to prevent possible arbstops on your domains after you fall back to a previous SSP version:

Caution Caution - If you are absolutely sure that your hardware state and domain configuration have not changed since SSP installation or upgrade, you can skip Steps a, b, and c. However, if the hardware state and domain configuration have changed, and you skip these steps, your domains can arbstop.

a. Schedule downtime for your domains and shut down the domains on the main SSP by using the standard shutdown (1M) command.

b. Log in as user ssp and remove all domains on the main SSP by using the domain_remove (1M) command.

ssp% domain_remove -d domain_name

c. Power off all system boards.

ssp% power -off -all

3. Log in to the main SSP as superuser and back up the SSP.

ssp# /opt/SUNWssp/bin/ssp_backup backup_directory

This creates a backup file of the SSP 3.5 environment, ssp_backup.cpio , in the specified backup directory. Do not use this file to restore a previous SSP environment.

4. Uninstall the SSP 3.5 software.

a. Log in to the main SSP as user ssp and switch to the platform name.

ssp% domain_switch platform_name

b. If you are falling back to SSP 3.2, prepare the SSP for downgrading. Otherwise, proceed to Step c.

ssp% ssp_downgrade

c. Log in to the main SSP as superuser and stop the SSP daemons:

ssp# /etc/init.d/ssp stop

d. Remove the SSP packages.

ssp# pkgrm SUNWsspid SUNWsspdo SUNWsspdr SUNWssppo SUNWsspob \

SUNWsspr SUNWsspst SUNWsspdf SUNWsspmn SUNWsspop SUNWsspue \

SUNWsspfp

For the SUNWsspr, SUNWsspdf, SUNWsspop, and SUNWsspue packages, a message indicates that the package contains scripts that will be executed with superuser permission during package removal.

e. For the SUNWsspr, SUNWsspdf, SUNWsspop, and SUNWsspue packages, type y when you are asked if you want to continue with the removal of the package.

f. If the SSP AnswerBook package is installed, remove it by typing

ssp# pkgrm SUNWuessp

g. Remove the following directories:

/var/opt/SUNWssp
/opt/SUNWssp
/etc/opt/SUNWssp

h. Reboot the SSP.

5. Reinstall a previous SSP release.

Refer to the appropriate version of the Sun Enterprise 10000 SSP Installation Guide and Release Notes for details on installing the previous version of the SSP software.

6. Restore the backup file of a previous SSP release.

ssp# /opt/SUNWssp/bin/ssp_restore backup_file

7. Run ssp_config (1M) to make the SSP as the main or spare:

ssp# /opt/SUNWssp/bin/ssp_config

The following is an example configuration session that shows the prompts and responses displayed:

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.

8. Reboot the SSP.

9. If you performed Step 2, do the following after the main SSP comes up:

a. Verify that there are no configured domains by using the domain_status (1M) command.

ssp% domain_status

No domains configured

b. If there are domains, remove those domains using the domain_remove (1M) command.

c. Run the ssp_backup (1M) command on the main SSP to save the SSP configuration.

Use this backup file to restore the environment on the spare SSP when you fall back on the spare.

10. If you need to revert to a previous SSP release on the spare SSP, repeat Steps 4 through 8 on the spare SSP.

When you perform Step 6, be sure to use the SSP backup file created in Step 9c to restore the SSP environment on the spare.