| System Management Services (SMS) 1.4.1 Installation Guide |    
|
| System Management Services (SMS) 1.4.1 Installation Guide |
|
| C H A P T E R 2 |
|
SMS 1.4.1 Software Installation |
This chapter contains instructions for reinstalling SMS 1.4.1 software under the Solaris operating environment or fresh installing Solaris 9 and SMS 1.4.1_s9 software. These instructions apply to Sun Fire high-end systems.
The SMS installation 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 Install the Solaris Operating Environment (optional)
To Configure the Management Network (MAN) Using the smsconfig(1M) Command
The SMS 1.4.1 installation instructions in this section assume that you are fresh installing the Solaris 9 operating environment or your system is already running the Solaris 9 operating environment.
To fresh install Solaris 9 and SMS 1.4.1_s9 software or reinstall the SMS 1.4.1_s9 software on your Sun Fire high-end system, you will need to perform the following procedures:
To begin, proceed to Downloading SMS Software.
You can retrieve SMS 1.4.1 software from the web.
|
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_1_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.1 packages are located in /download_directory/sms_1_4_1sparc/System_Management_Services_1.4.1/Product.
7. Proceed to Backing Up Your SMS Environment.
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.
Run smsbackup before proceeding or have the latest copy of the smsbackup file (sms_backup.X.X.cpio) accessible to the disk.
|
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.
If you are fresh installing the Solaris 9 operating environment, proceed to Installing the Solaris Operating Environment.
If you are reinstalling SMS 1.4.1 software proceed to Installing SMS Packages.
|
Note - Make sure you have the proper release of the Solaris operating environment, including patches (see SMS 1.4.1 Software Requirements). Without the proper version and patches, the availability daemons on the SC will not start, causing SMS daemon startup failures and an unusable SC. |
1. Install 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.1_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. Verify that Java 1.2.2 has been installed in the default directory.The default directory is /usr/java1.2/bin/java. If you are using the Sun Fire Interconnect and Java 1.2.2 is not installed in the default directory, SMS will not start.Stop and Restart SMS.See To Manually Stop and Restart SMS |
4. Once your operating environment has been successfully installed proceed to Installing SMS Packages.
SMS provides a script, smsinstall(1M), to automate software installation. To install SMS software packages, follow the steps in the procedure To Install the SMS Software Packages Using smsinstall.
1. Log in to the spare SC as superuser.
Change directory to the location of smsinstall and type:
|
Note - smsinstall(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. |
2. Install packages using the smsinstall(1M) command.
directory_name is the /Product directory from Downloading SMS Software. Here is an example:
3. Proceed to To Restore Your SMS Configuration.
1. Restore your SMS configuration.
Run smsrestore to restore the smsbackup file.
|
Note - Once smsrestore completes you will see the following message: "Please set the desired SMS failover state." Ignore this message. |
filename is the absolute path to the backup file that was created by smsbackup(1M). The filename must contain the full path name for the file. This file can reside anywhere on the system, connected network or tape device. If no filename is specified, you will receive an error.
Proceed to To Configure the Management Network (MAN) Using the smsconfig(1M) Command.
During reinstallation the SMS group file was restored. Proceed to To Add Users to SMS Groups and Configure Directory Access only if you will be changing user group memberships. Otherwise, proceed to To Switch Control to the Spare SC.
|
|
To correctly configure the management network, you need to do the following:
1. Be sure you have read and filled out the information in the Sun Fire 15K/12K System Site Planning Guide.
|
Note - A domain can be excluded from the I1 network configuration by using the word NONE as the net_id. This applies only to the I1 network. |
2. Read the smsconfig(1M) man page.
3. Log into the spare SC as superuser.
4. To display, review, or change the Management Network settings, type:
5. Answer the questions based on the information gathered for your site in the Sun Fire 15K/12K System Site Planning Guide.
The following example shows IPv4 and accepts the default settings provided with the Solaris 9 Supplemental CD. An IPv6 network example differs slightly. There will be no prompts for netmasks and /etc/ipnodes will be modified in addition to /etc/hosts.
|
Note - The IP addresses on the external network for failover, eri0 and eri1 on each SC must be unique. The floating IP address is the same on both SCs. |
For more information on smsconfig -m refer to the "MAN Configuration" section of the System Management Services (SMS) 1.4.1 Administrator Guide and the smsconfig man page.
|
Note - Any changes made to the network configuration on one SC using smsconfig -m must be made to the other SC as well. Network configuration is not automatically propagated. |
6. Configure the Name Services for SMS
7. Log in to the SC as superuser.
8. Edit the /etc/nsswitch.conf file.
a. The first entry for password, group, hosts, netmasks and ethers should be files. List other naming services in use, such as nis or DNS, next.
The following example shows the correct partial contents of an /etc/nsswitch.conf file on the spare SC. The look-up order for the database entries is first files then naming services.
sc1: # vi /etc/nsswitch.conf ... passwd: files nis group: files nis ... hosts: files nis ... netmasks: files nis ... ethers: files nis ... |
|
Note - smsconfig automatically updates the /etc/netmasks and the /etc/inet/hosts file with all the private host names and logical addresses for the SC. |
9. Update your Solaris Naming software (NIS, NIS+, DNS, etc), as appropriate.
10. Configure SMS groups. See To Add Users to SMS Groups and Configure Directory Access.
During reinstallation this file was restored. Proceed with this step only if you will be changing user group memberships or you have performed a fresh installation.
11. After adding users to your SMS Groups:
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.
For reinstallation of SMS 1.4.1, proceed to To Reinstall the Former Main SC.
If you are fresh installing a system which previously ran SMS 1.3,
proceed to To Update the Flash PROMs.
When you fresh install SMS 1.4.1 on system previously running SMS 1.3 or SMS 1.4, you must update the flash PROMs on:
You cannot update the flash PROM on one SC from the other. You must be logged on to the SC whose prom you want to update.
You must have platform privileges to run the flashupdate(1M) command. For more information on flashupdate(1M) refer to the System Management Services (SMS) 1.4.1 Reference Manual or the flashupdate man page.
|
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 one SC as a user with platadmn privileges.
2. Upgrade the fp0 Flash PROM.
Use flashupdate. This example updates the fp0 prom on sc0:
3. Upgrade the fp1 Flash PROM, using the appropriate image for the type of board.
For the CP1500 board, use flashupdate with the nSSCPOST.di image. For example:
For the CP2140 board, use flashupdate with the oSSCPOST.di image:
Repeat steps 1-3 for the other SC.
Here's an example for a CP2140-based SC:
(log in to other SC)sc1:sms-user:> flashupdate -f /opt/SUNWSMS/firmware/SCOBPing.di sc0/fp0 sc1:sms-user:> flashupdate -f /opt/SUNWSMS/firmware/oSSCPOST.di sc0/fp1 |
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.
Sun Fire 15K/E25K, Sun Fire 12K/E20K
The following FPROM_id forms are accepted:
6. Drop to the OpenBoot PROM prompt.
8. Proceed to To Reinstall the Former Main SC.
1. Log in to the former main as superuser.
2. Backup the system on the former main SC (SC0).
Run smsbackup before proceeding or have the latest copy of the smsbackup file (sms_backup.X.X.cpio) accessible to the disk.
|
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.
To fresh install the Solaris 9 operating environment, proceed to Installation of the Solaris Operating Environment on the Former Main SC.
To reinstall SMS 1.4.1, proceed to Installing SMS 1.4.1 Software on the Former Main SC.
|
Note - Make sure you have the proper release of the Solaris operating environment, including patches (see SMS 1.4.1 Software Requirements). Without the proper version and patches, the availability daemons on the SC will not start, causing SMS daemon startup failures and an unusable SC. |
1. Install 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.1 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.
4. Once your operating environment has been successfully installed proceed to Installing SMS 1.4.1 Software on the Former Main SC. Installing SMS 1.4.1 Software on the Former Main SCTo install SMS software packages, perform the steps in the following procedure. 1. Log in to the former main SC as superuser. 2. Change directory to the location of smsinstall: 3. Install packages using the smsinstall(1M) command. directory_name is the /Product directory location of the SMS packages from Downloading SMS Software. Here is an example. 4. Proceed to To Restore Your SMS Configuration. Restoring Your SMS Configuration on the Former Main SC1. Restore your SMS configuration on the former main SC.
filename is the absolute path to the backup file that was created by smsbackup(1M). The filename must contain the full path name for the file. This file can reside anywhere on the system, connected network or tape device. If no filename is specified, you will receive an error. Proceed to To Configure the Management Network (MAN) Using the smsconfig(1M) Command. During reinstallation the SMS group file was restored. Proceed to To Add Users to SMS Groups and Configure Directory Access only if you will be changing user group memberships. Otherwise, proceed to To Reboot the Former Main SC. Configuring the MAN Network on the Former Main SC
To correctly configure the management network, you need to do the following: 1. Be sure you have read and filled out the information in the Sun Fire 15K/12K System Site Planning Guide.
2. Read the smsconfig(1M) man page. 3. Log into the former main SC as superuser. 4. To display, review, or change the Management Network settings, type: 5. Answer the questions based on the information gathered for your site in the Sun Fire 15K/12K System Site Planning Guide. The following example shows IPv4 and accepts the default settings provided with the Solaris 9 Supplemental CD. An IPv6 network example differs slightly. There will be no prompts for netmasks and /etc/ipnodes will be modified in addition to /etc/hosts.
For more information on smsconfig -m refer to "MAN Configuration" section of the System Management Services (SMS) 1.4.1 Administrator Guide and the smsconfig man page. 6. Configure the Name Services for SMS. 7. Log in to the SC as superuser. 8. Edit the /etc/nsswitch.conf file. a. The first entry for password, group, hosts, netmasks and ethers should be files. List other naming services in use, such as nis or DNS, next. The following example shows the correct partial contents of an /etc/nsswitch.conf file on the spare SC. The look-up order for the database entries is first files then naming services.
9. Update your Solaris Naming software (NIS, NIS+, DNS, etc), as appropriate. 10. Configure SMS groups. See To Add Users to SMS Groups and Configure Directory Access. During reinstallation this file was restored. Proceed with this step only if you will be changing user group memberships or you have done a fresh install of the Solaris operating environment. Otherwise proceed to To Reboot the Former Main SC. 11. After adding users to your SMS Groups: Proceed to To Reboot the Former Main SC. Rebooting the Former Main SC1. 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. For reinstallation of SMS 1.4.1, proceed to To Enable Failover. If you are fresh installing a system that was previously running SMS 1.3 or SMS 1.4 software, proceed to To Update the Flash PROMs. Updating the Flash PROMs on the Former Main SCWhen you fresh install SMS 1.4.1 on a system that was previously running SMS 1.3 or SMS 1.4 software you must update the flash PROMs on:
You cannot update the flash PROM on one SC from the other. You must be logged on to the SC whose prom you want to update. You must have platform privileges to run the flashupdate(1M) command. For more information on flashupdate(1M) refer to the System Management Services (SMS) 1.4.1 Reference Manual or the flashupdate man page.
1. Log in to one SC as a user with platadmn privileges. 2. Upgrade the fp0 Flash PROM. Use flashupdate. This example updates the fp0 prom on sc0: 3. Upgrade the fp1 Flash PROM, using the appropriate image for the type of board. For the CP1500 board, use flashupdate with the nSSCPOST.di image. For example: For the CP2140 board, use flashupdate with the oSSCPOST.di image: Repeat steps 1-3 for the other SC. Here's an example for a CP2140-based SC:
5. Drop to the OpenBoot PROM prompt. 6. Reboot the main SC (SC0). Type: 7. Proceed to To Enable Failover. Verifying the Chassis Serial NumberThe 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. Verify that the chassis serial number has been recorded, as explained in the following procedure.
1. Make sure the centerplane is powered on. If it is not powered on, run poweron cp0. 2. Login to the new main SC (SC1) as a user with platform admin privileges. 3. 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 Enabling Failover on the Main SC (SC1). If the chassis serial number is not displayed, proceed to Step 4. 4. 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 on the front of the system chassis, near the bottom center. Proceed to Enabling Failover on the 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 reinstallation or upgrade is now complete! If you want to secure the SCs, proceed to SMS 1.4.1 Security Options. Otherwise, proceed to Creating a Domain.
Copyright © 2004, Sun Microsystems, Inc. All rights reserved. |
To Download Software From the Web
