C H A P T E R  1

Introduction

This chapter describes what's involved in the reinstallation and upgrade of the SMS 1.4.1 software. Instructions are provided in subsequent chapters.


SMS 1.4.1 Software on the SC

Versions of SMS 1.4.1software are available for both the Solaris 9 and the Solaris 8 operating environment. Each version is distinct, and will run only on the operating environment for which it was designed.

The SMS packages use approximately 18 Gbytes each of disk space on two disks on the system controller (SC). The following table lists the total size of the SMS software by partition.


TABLE 1-1 SMS Software Approximate Partition Sizes

Partition

Size

0 /(root)

8 Gbytes

1 /swap

2 Gbyte

4 OLDS/LVM database (metadb)

10 Mbytes

5 OLDS/LVM database (metadb)

10 Mbytes

7 /export/install

8 Gbytes


SMS requires two disk partitions, of at least 10 Mbytes, be dedicated to each metadevice state database copy for disk mirroring.

SMS 1.4.1 Software Requirements

The Solaris 8 version of SMS requires:



caution icon

Caution - If you are using the Sun Fire Interconnect and Java 1.2.2 is not installed, or not installed in its default directory, SMS will fail to load.



After installing Java 1.2.2, be sure to stop and restart SMS.

The Solaris 9 version of SMS requires:



caution icon

Caution - If you are using the Sun Fire Interconnect and Java 1.2.2 is not installed, or not installed in its default directory, SMS will fail to load.



After installing Java 1.2.2, be sure to stop and restart SMS.

Default Stop Sequence

Since SMS 1.3, the default sequence to stop the system (STOP-A) has been changed to the following alternate:

[Return][tilde][CTRL-B] 

This was done to facilitate failover. Solaris 8 introduced this new feature which gives the system the ability to force a hanging system to halt when required without allowing random or spurious breaks to cause an unintentional stop.



Note - This is true only with serial devices acting as consoles and not for systems with keyboards of their own. There must be an interval of more than 0.5 seconds between characters, and the entire string must be entered in less than 5 seconds.



Software Combinations

These are the valid SMS software upgrade paths for the Solaris 8 and Solaris 9 operating environments:

Figure depicting SMS upgrade paths.

SMS Upgrade Paths

SMS 1.1 is no longer supported. Also note that there is no upgrade path from SMS 1.3 to SMS 1.4. The equivalent upgrade is SMS 1.3 to SMS 1.4.1.

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

To upgrade from SMS software from the Solaris 8 operating environment, follow the procedures summarized in FIGURE 1-2. To upgrade SMS software from the Solaris 9 operating environment, follow the procedures summarized in FIGURE 1-3.

Figure depicting SMS upgrade instructions for the Solaris 8 operating environment.

SMS Upgrade Instructions - Solaris 8

Figure depicting SMS upgrade instructions for the Solaris 9 operating environment.

SMS Upgrade Instructions - Solaris 9



Note - In the1.4.1 release of SMS for Solaris 9, smsversion does not support a return to SMS 1.1, SMS 1.2_s8 or SMS 1.3_s8. To return to SMS 1.1, SMS 1.2_s8 or SMS 1.3_s8 you must return to the applicable Solaris 8 operating environment.



Previous versions of SMS documented the use of the JavatrademarkWeb Start GUI and the pkgadd command to install the SMS packages on to the Sun Fire high-end system. SMS 1.3 introduced the smsinstall and smsupgrade scripts, which simplify and streamline the installation and upgrade process. As a result, Web Start and pkgadd are no longer recommended and are not documented in this manual. Do not use any method not documented in this manual to install or upgrade SMS 1.4.1 or you could misconfigure SMS and lose functionality.

SMS 1.4.1 does not support mixed configurations of CP1500 and CP2140 boards on the SC's. In other words, you cannot use a CP1500 board on one SC, and a CP2140 board on the other. Both SC's must use the same type of board.

Other Documentation and Requirements

The following chapters contain overviews of the reinstallation and upgrade process, which require you to use sections from different publications and files. You should ensure that you have the following publications, printouts and patches before you start the reinstallation or upgrade.

Check the Solaris 9 (SPARC Platform Edition) Release Notes, the Solaris 9 Release Notes Supplement for Sun Hardware, the System Management Services (SMS) 1.4.1 Release Notes and sunsolve.sun.com for the latest information on issues, late-breaking news, and patch availability.



Note - During installation, or whenever the other SC is at the Open Boot PROM prompt or not running SMS, you may see "SC clocks NOT phase locked" messages in the platform log. You can ignore them.



Example Conventions

For the examples in this guide:

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:sms-user:>

User prompts on the domain

sms-user is the user-name of the administrator, operator, configurator, or service personnel logged in to the domain.