| System Management Services (SMS) 1.4 Installation Guide |    
|
| System Management Services (SMS) 1.4 Installation Guide |
|
| C H A P T E R 3 |
|
SMS 1.4 Software Upgrade |
This chapter contains upgrade instructions for System Management Services (SMS) 1.4 software under the Solaris operating environment. These instructions apply to the Sun Fire high-end server systems.
SMS 1.4 requires the Solaris 9 12/03 operating environment. If you are using the Solaris 8 operating environment, you must apply Solaris KU Patch 24.The SMS upgrade focuses on setting up group IDs used for credential checking, and setting up and running control scripts that start SMS when the Solaris operating environment boots.
To Upgrade the Solaris Operating Environment (optional)
To Upgrade the Former Main SC (optional)
To Upgrade the Solaris Operating Environment (optional)
To Reboot the Former Main SC on the Former Main
|
Note - SMS 1.1 is not available on the Sun Fire 12K system. The SMS 1.1 upgrade information refers to the Sun Fire 15K system only. |
The SMS 1.4 installation instructions in this section assume that you are upgrading the Solaris 9 operating environment and SMS software, or SMS software alone.
To upgrade the Solaris operating environment software from Solaris 8 with SMS 1.3_s8 software or 1.4_s8; or to upgrade from Solaris 9 with SMS1.3_s9 software, you will be performing the following procedures:
To begin Type 2 upgrade, proceed to Downloading SMS Software.
You can retrieve SMS software from either the web or on the Software Supplement CD.
1. Using your web browser, go to http://www.sun.com/servers/sw/
2. Click the System Management Services (SMS) link.
3. Click the Click here to download link.
The file that is then downloaded is named sms_1_4_sparc.zip.
4. Log in to the SC as superuser.
5. Change directory to the location where you downloaded the software:
6. Extract the downloaded file by typing:
The SMS 1.4 packages are located in /download_directory/sms_1_4_sparc/System_Management_Services_1.4/Product.
7. Proceed to Preparing Your SMS Environment for Upgrade.
1. Insert the Software Supplement for the Solaris 9 Operating Environment CD-ROM into the CD-ROM drive.
Allow time for the Volume Manager to mount the CD-ROM.
The SMS 1.4 packages are located in /cdrom/cdrom0/System_Management_Services_1.4/Product.
2. Log in to the system controller as superuser.
3. Change to the Product installation directory:
4. Proceed to Preparing Your SMS Environment for Upgrade.
If this SC has a working SMS environment, you should do the following before attempting to reinstall the SMS software:
1. Make certain your configuration is stable.
Being stable means no commands are running and no hardware is changed during the reinstallation or upgrade process.
2. Log in to the main SC as a user with platadmn privileges.
1. Log in to the spare as superuser.
2. Stop SMS on the spare SC (SC1):
3. Backup the system on the spare SC (optional).
smsupgrade backs up and restores your SMS environment, however, if you will be upgrading your Solaris software and are unfamiliar with that process, we recommend you make a backup of your SMS environment prior to the Solaris upgrade. Save the resulting file off the local system for redundancy.
|
Note - The sms_backup.X.X.cpio file of one SC cannot be used by the other SC. They are SC specific files and non-interchangeable. |
directory_name is the name of the directory in which the backup file is created. The directory_name requires the absolute path name for the file. This file can reside in any directory on the system, connected network or tape device to which you have read/write privileges. If no directory_name is specified, a backup file is created in /var/tmp.
The directory_name specified must be mounted on as a UFS file system. Specifying a TMPFS file system, such as /tmp, will cause smsbackup to fail. If you are not certain that your directory_name is mounted as a UFS file system, type:
A UFS file system will return directory information. Any other type of file system will return a warning.
4. Upgrade to Solaris 9 or install the KU Patch 24 to Solaris 8.
SMS 1.4 requires the 12/03 release of the Solaris operating environment or the KU Patch 24 to the Solaris 8 operating environment. Have your Solaris 9 Installation Guide available and proceed to To Upgrade the Solaris Operating Environment.
If you are already running the 12/03 release of the Solaris 9 operating environment, and only wish to upgrade your version of SMS, proceed to Upgrading SMS Packages.
SMS 1.4 requires the Solaris 9 12/03 operating environment. If you are using the Solaris 8 operating environment, you must apply Solaris KU Patch 24.
1. Upgrade the Solaris 9 operating environment according to the Solaris installation instructions in the Solaris 9 Installation Guide.
The instructions below assume that your system is running the Entire Distribution software group (or higher) of the Solaris 9 operating environment. All patches should be applied according to each patch's instructions. Several Solaris patches are required for SMS to run properly. See Other Documentation and Requirements.
|
Note - You must select the English, `C,' locale when reinstalling the Solaris operating environment on a system controller. SMS does not support any Solaris locale other than English on the SC. |
Once you have upgraded your Solaris software and rebooted you may see krtld (kern.notice) and kstat and scman ifconfig error messages. You can disregard them.
2. Stop SMS on the spare SC (SC1):
3. Proceed to Upgrading SMS Packages.
To upgrade SMS software packages, follow the steps in the procedure To Upgrade the SMS Software Packages.
1. Log in to the spare SC as superuser.
2. Change directory to the location of smsupgrade:
If you downloaded software from the Web, type:
If you are installing software from the CD-ROM; place the Solaris 9 Supplemental CD into the SC's CD-ROM drive and type:
|
Note - smsupgrade(1M) automatically installs the online System Management Services (SMS) Reference Manual (man) pages in /opt/SUNWSMS/man/sman1m. To avoid conflicts, do not change this location. |
3. Upgrade SMS using the smsupgrade(1M) command.
directory_name is the /Product directory from Downloading SMS Software.
smsupgrade backs up and restores any existing SMS environment. The backup file resides in /var/tmp/sms_backup.1.x.cpio.
The following SMS 1.4 example runs from CD-ROM.
4. Proceed to To Switch Control to the Spare SC.
1. Log in to the main SC (SC0) as superuser.
3. Log in to the spare SC (SC1) and drop to the OpenBoot PROM prompt.
You must reboot the SC in order for the changes to take effect. Once you have rebooted the system, network configuration is complete and SMS will start and SC1 will become the main SC.
Proceed to To Update the Flash PROMs.
When you upgrade the SMS software you must update the SC flash PROMs on both SCs. You must also update the CPU flash PROMs on the system boards. You must have platform privileges to run the flashupdate(1M) command. In the following example the sc# prompt indicates both the main or spare SC.
|
Note - In order to update your SC PROMs you must have access to the following drivers: |
|
Note - If the drivers are not available you must run the following command as superuser on each SC: |
1. Log in to the new main SC as a user with platadmn privileges.
2. Upgrade the SC Flash PROMs.
Update the SC PROMs using flashupdate.
For more information on flashupdate(1M) refer to the System Management Services (SMS) 1.4 Reference Manual or the flashupdate man page.
3. Upgrade the CPU Flash PROMs.
Update all CPU Flash PROMs using flashupdate.
location is the FPROM location.
The FPROM location consists of board_loc/FPROM_id, separated by a forward slash.
The FPROM_id is specified only when you want to update a particular FPROM (FP0 or FP1) on a CPU board and the system controller (SC).
For example, the location, SB4/FP0, indicates the FPROM 0 on the CPU board in slot 4.
The following FPROM_id forms are accepted:
For more information on flashupdate(1M) refer to the System Management Services (SMS) 1.4 Reference Manual or the flashupdate man page.
4. Drop to the OpenBoot PROM prompt.
6. Proceed to To Upgrade the Former Main SC.
1. Log in to the former main as superuser.
2. Stop SMS on the former main SC:
3. Backup the system on the former main SC (optional).
smsupgrade backs up and restores your SMS environment, however, if you will be upgrading your Solaris software and are unfamiliar with that process, we recommend you make a backup of your SMS environment prior to the Solaris upgrade. Save the resulting file off the local system for redundancy.
|
Note - The sms_backup.X.X.cpio file of one SC cannot be used by the other SC. They are SC specific files and non-interchangeable. |
directory_name is the name of the directory in which the backup file is created. The directory_name requires the absolute path name for the file. This file can reside in any directory on the system, connected network or tape device to which you have read/write privileges. If no directory_name is specified, a backup file is created in /var/tmp.
The directory_name specified must be mounted on as a UFS file system. Specifying a TMPFS file system, such as /tmp, will cause smsbackup to fail. If you are not certain that your directory_name is mounted as a UFS file system, type:
A UFS file system will return directory information. Any other type of file system will return a warning.
4. You are now ready to upgrade.
If you wish to upgrade the Solaris 9 operating environment on the former main SC, have your Solaris 9 Installation Guide available. Proceed to To Upgrade the Solaris Operating Environment.
If you are already running Solaris 9 software and only wish to upgrade SMS proceed to To Upgrade the SMS Software Packages.
SMS 1.4 requires the Solaris 9 12/03 operating environment. If you are using the Solaris 8 operating environment, you must apply Solaris KU Patch 24.
1. Upgrade the Solaris 9 operating environment according to the Solaris installation instructions. Refer to the Solaris 9 Installation Guide for detailed installation instructions.
The instructions in the following sections assume that your system is running the Entire Distribution software group (or higher) of the Solaris 9 operating environment. SMS 1.4_s9 does not run under software releases earlier than Solaris 9 or software groups less than Entire Distribution. All patches should be applied according to each patch's instructions. Several Solaris patches are required for SMS to run properly. See Other Documentation and Requirements.
|
Note - You must select the English, `C,' locale when reinstalling the Solaris operating environment on a system controller. SMS does not support any Solaris locale other than English on the SC. |
Once you have upgraded your Solaris software and rebooted you may see krtld (kern.notice) and kstat and scman ifconfig error messages. You can disregard them.
2. Stop SMS on the former main SC:
3. Proceed to To Upgrade the SMS Software Packages.
To upgrade SMS software packages, follow the steps in the procedure To Upgrade the SMS Software Packages.
1. Log in to the former main SC as superuser.
2. Change directory to the location of smsupgrade (1M):
If you downloaded software from the Web, type:
If you are installing software from the CD-ROM; place the Solaris 9 Supplemental CD into the SC's CD-ROM drive and type:
3. Upgrade packages using the smsupgrade(1M) command.
directory_name is the /Product directory from Downloading SMS Software.
smsupgrade backs up and restores any existing SMS environment. The backup file resides in /var/tmp/sms_backup.1.x.cpio.
The following example runs from CD-ROM.
4. Proceed to To Reboot the Former Main SC.
1. Log in to the former main SC (SC0) as superuser and drop to the OpenBoot PROM prompt.
You must reboot the SC in order for the changes to take effect. Once you have rebooted the system, network configuration is complete.
Proceed to To Update the Flash PROMs on the Former Main.
When you upgrade the SMS software you must update the SC flash PROMs on both SCs.
|
Note - You do not need to update the CPU flash PROMs. This was done earlier and is not repeated. |
You must have platform privileges to run the flashupdate(1M) command.
|
Note - In order to update your SC PROMs you must have access to the following drivers: |
|
Note - If the drivers are not available you must run the following command as superuser on each SC. In the following example the sc# prompt indicates both the main or spare SCs: |
1. Log in to the main SC as a user with platadmn privileges.
2. Upgrade the SC Flash PROMs.
Update the SC PROMs using flashupdate.
For more information on flashupdate(1M) refer to the System Management Services (SMS) 1.4 Reference Manual or the flashupdate man page.
3. Drop to the OpenBoot PROM prompt.
4. Reboot the main SC (SC0). Type:
5. Proceed to To Enable Failover on the New Main SC (SC1).
The chassis serial number is a unique alphanumeric text string, up to 20 characters in length, that identifies a Sun Fire high-end system. This serial number is displayed on a label located on the front of the system chassis, near the bottom center.
If you are upgrading from an SMS release earlier than SMS 1.4, you must verify that the chassis serial number was recorded, as explained in the following procedure.
|
|
1. Login to the new main SC (SC1) as a user with platform admin privileges.
2. Run the showplatform -p csn command and review the output to determine whether a chassis serial number was assigned to your Sun Fire high-end system.
If a chassis serial number was previously recorded, the chassis serial number will be displayed in the output, for example:
Proceed to To Enable Failover on the New Main SC (SC1). If the chassis serial number is not displayed, proceed to step 3.
3. Record the chassis serial number.
where the chassis_serial_number is the number that identifies your Sun Fire high-end system. You obtain the chassis serial number from a label located on the front of your system chassis, near the bottom center.
Proceed to To Enable Failover on the New Main SC (SC1).
Enabling Failover on the Main SC (SC1)1. Login in the new main SC (SC1) as a user with platadmn privileges.
Your upgrade is now complete! To secure the SCs proceed to SMS 1.4 Security Options. If you do not wish to secure the SCs, you can proceed to Creating a Domain.
| System Management Services (SMS) 1.4 Installation Guide | 817-3055-10 |
|
Copyright © 2003, Sun Microsystems, Inc. All rights reserved.
To Download Software From the Web