C H A P T E R 1 - Overview of SMS 1.6 Installation or Upgrade

C H A P T E R 1

Overview of SMS 1.6 Installation or Upgrade

This chapter provides background and planning information to prepare for installing the SMS 1.6 software:

Types of Installations

Valid Upgrade Paths

Space Requirements

Board Compatibility

SC Software Requirements

Conventions Used in Installation Examples

Note - All members of the Sun Fire server family can be configured as loosely coupled clusters. This document, however, does not address system management for clusters of Sun Fire high-end systems.

Types of Installations

SMS 1.6 arrives preinstalled on the system controllers (SCs) of Sun Fire high-end systems. You must manually install or upgrade to SMS 1.6 only when you:

Make a fresh installation

Restore previously installed versions of Solaris OS and SMS

Upgrade to SMS 1.6

FIGURE 1-1 illustrates the three types of SMS installations.

FIGURE 1-1 Reasons for Manually Installing SMS 1.6

SMS 1.6 is offered in the following packages:

SMS 1.6 for the Solaris 9 Operating System

SMS 1.6 for the Solaris 10 1/06 Operating System

Each set runs only the operating system for which it was designed. For instance, you cannot install the Solaris 9 packages of SMS 1.6 on a system controller that is running Solaris 10 software. If you do, you will receive a fatal error message, as described in the following section.

Fatal Error Messages

Caution - If you attempt to install an SMS 1.6 OS-specific package on an SC with a different OS, you will receive a fatal error, as described in this section.

Installing SMS 1.6 for Solaris 10 OS on SC With Solaris 9 OS

If you attempt to install SMS 1.6 for Solaris 10 OS on an SC that has Solaris 9 OS, you receive the following message.

Fatal error: One or more SMS packages are not installed.

Log file is /var/sadm/system/logs/smsinstall. Exiting.

Reason: Attempting to install SMS1.6 for Solaris 10 OS (SMS1.6-S10) on an SC that has Solaris 9 OS running.

Action: Install the correct package, SMS1.6-S9, for the SC with Solaris 9 OS running.

Installing SMS 1.6 for Solaris 9 OS on SC With Solaris 10 OS

If you attempt to install SMS 1.6 for Solaris 9 OS on an SC that has Solaris 10 OS, you receive the following message.

Fatal error: Package SUNWscdvr does not support Solaris 5.10.

Log file is /var/sadm/system/logs/smsinstall. Exiting.

Reason: Attempting to install SMS1.6 for Solaris 9 OS (SMS1.6-S9) on an SC that has Solaris 10 OS running.

Action: Install the correct package, SMS1.6-S10, for the SC with Solaris 10 OS running.

Valid Upgrade Paths

FIGURE 1-2 illustrates the valid SMS software upgrade paths on the SCs for the Solaris 8 OS, Solaris 9 OS, and Solaris 10 OS.

FIGURE 1-2 SMS Upgrade Paths

Caution - You can upgrade the Solaris OS from Solaris 8 OS to Solaris 10 OS or Solaris 9 OS to Solaris 10 OS before you upgrade SMS. If you do, you will receive an error until you upgrade SMS.

Note - SMS 1.1, SMS 1.2, SMS 1.3, and SMS 1.4 are no longer supported. Upgrade to SMS 1.5 or 1.6 as soon as possible. The only direct upgrade path to SMS 1.6 is from SMS 1.5. You must upgrade previous versions of SMS as shown in FIGURE 1-2.

TABLE 1-1 is a list of SMS versions and the corresponding package names by Solaris OS version.

TABLE 1-1 SMS Versions and Package Names by Solaris OS Version
SMS Version	Solaris 8 OS Package Name	Solaris 9 OS Package Name	Solaris 10 OS Package Name
SMS 1.2	sms1.2_s8	sms1.2_s9	None
SMS 1.3	sms1.3_s8	sms1.3_s9	None
SMS 1.4	sms1.4_s8	sms1.4_s9	None
SMS 1.4.1	sms1.4.1_s8	sms1.4.1_s9	None
SMS 1.5	sms1.5_s8	sms1.5_s9	None
SMS 1.6	None	sms1.6_s9	sms1.6_s10

Valid Paths for Version Switching

You can use the smsversion script to switch to any version of SMS that is still installed on your system, with these exceptions:

Upgrade from SMS 1.4 to SMS 1.4.1 is permanent. Once you upgrade to SMS 1.4.1, you cannot return to SMS 1.4.

If you upgrade from SMS 1.4 to SMS 1.4.1, SMS 1.5, and then to SMS 1.6, you cannot switch back to SMS 1.4 or 1.4.1, only to SMS 1.5.

If you upgrade from SMS 1.5 to SMS 1.6, you can switch back to SMS 1.5.

If you upgrade both SMS and the operating system, you cannot switch to the previous version of SMS unless you first reinstall the previous version of the operating system.

If you switch from SMS 1.6 to SMS 1.5, you must manually undo the hardening on the SCs using the Solaris Security Toolkit, and then reharden and reboot.

This switching of SMS versions only applies if you have the same Solaris OS version running. The version switching does not apply if you have upgraded the Solaris OS version. Refer to previous versions of SMS Installation Guides for installation instructions prior to SMS 1.6.

Note - Hardening the SCs manually after upgrading to SMS 1.6 has security implications. See Switching SMS Versions.

Space Requirements

The SMS packages require approximately 8 gigabytes (GB) of disk space on each system controller (SC) and domain. TABLE 1-2 provides details by partition.

TABLE 1-2 SMS 1.6 Recommended Partition Sizes
Partition	Size
`0 /(root)`	8 GB
`1 /swap`	4 GB (2 GB and 4.5 GB also supported)
4 OLDS/LVM database (`metadb)`	32 MB ^[1]
5 OLDS/LVM database (`metadb`)	32 MB*
7 `/export/install`	Remains free

Board Compatibility

Caution - SMS does not support mixed configurations of CP1500 and CP2140 boards on the SCs. You cannot use a CP1500 board on one SC and a CP2140 board on the other. Both SCs must use the same type of board.

SC Software Requirements

These are the minimum software requirements for SMS 1.6 on the system controllers. They vary by operating system.

Note - SMS 1.6 does not support Solaris 8 OS on the SCs.

Solaris 9 OS Requirements for SCs

As a minimum, the Solaris 9 OS version of SMS 1.6 requires:

Solaris 9 4/04 OS release

Same version of SMS software on both system controllers

Installation of the Entire Distribution software group of the Solaris OS, including update version and installed patches, on both SCs. All patches are available at:

http://sunsolve.sun.com

Patches:

113027-03 patch

111712-12 patch (for UltraSPARC^® IV+ 1800 MHz only)

Solaris 10 OS Requirements for SCs

As a minimum, the Solaris 10 OS version of SMS 1.6 requires:

Solaris 10 1/06 OS release

Same version of SMS software on both system controllers

Installation of the Entire Distribution software group of the Solaris OS, including update version and installed patches, on both SCs. All patches are available at:

http://sunsolve.sun.com

Patches:

121946-01 patch

Domain Software Requirements

These are the minimum software requirements for SMS 1.6 on domains. They vary by operating system.

Solaris 8 OS Requirements for Domains

As a minimum, the Solaris 8 OS requires:

Solaris 8 2/02 OS release

Patches:

117002-01 patch

110826-09 patch

111335-18 patch

Solaris 9 OS Requirements for Domains

As a minimum, the Solaris 9 OS requires:

Solaris 9 4/04 OS release.

Patches:

113027-03 patch

112233-09 patch

Solaris 10 OS Requirements for Domains

As a minimum, the Solaris 10 OS requires:

Solaris 10 3/05 (minimum for UltraSPARC III+, UltraSPARC III++, and UltraSPARC IV)

Solaris 10 3/05 HW1 (minimum for UltraSPARC IV+ 1500 MHz and 1800 MHz only)

The Solaris 10 1/06 OS release is supported on the domains on all processors.

Conventions Used in Installation Examples

The examples in this installation guide use the following conventions to show the SC and domain user prompts.

Prompt	Definition
`sc0:#`	Superuser on SC0, initially the main SC.
`sc1:#`	Superuser on SC1, initially the spare SC.
domain_id.#	Superuser on the domain.
sc_name.sms-user.>	User prompt on the SC. sms-user is the `user-name` of an administrator, operator, configurator, or service personnel logged in to the SC.
domain_id.domain-user.>	User prompts on the domain. domain-user is the `user-name` of the administrator, operator, configurator, or service personnel logged in to the domain.

^{1 (TableFootnote) SMS requires two disk partitions of at least 32 MB each, dedicated to storing the SC's state information (metadevice state) during failover.}