System Management Services (SMS) Installation Guide

Transcription

1 System Management Services (SMS) Installation Guide Sun Microsystems, Inc Network Circle Santa Clara, CA U.S.A Part No April 2004, Revision A Submit comments about this document at:

2 Copyright 2004 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at and one or more additional patents or pending patent applications in the U.S. and in other countries. This document and the product to which it pertains are distributed under licenses restricting their use, copying, distribution, and decompilation. No part of the product or of this document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, AnswerBook2, docs.sun.com, Sun Fire, OpenBoot, Java, Sun Remote Services Net Connect, and Solaris are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and Sun Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun s written license agreements. Use, duplication, or disclosure by the U.S. Government is subject to restrictions set forth in the Sun Microsystems, Inc. license agreements and as provided in DFARS (a) and (a) (1995), DFARS (c)(1)(ii) (Oct. 1998), FAR (a) (1995), FAR , or FAR (ALT III), as applicable. DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. Copyright 2004 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, Etats-Unis. Tous droits réservés. Sun Microsystems, Inc. a les droits de propriété intellectuels relatants à la technologie incorporée dans le produit qui est décrit dans ce document. En particulier, et sans la limitation, ces droits de propriété intellectuels peuvent inclure un ou plus des brevets américains énumérés à et un ou les brevets plus supplémentaires ou les applications de brevet en attente dans les Etats-Unis et dans les autres pays. Ce produit ou document est protégé par un copyright et distribué avec des licences qui en restreignent l utilisation, la copie, la distribution, et la décompilation. Aucune partie de ce produit ou document ne peut être reproduite sous aucune forme, parquelque moyen que ce soit, sans l autorisation préalable et écrite de Sun et de ses bailleurs de licence, s il y ena. Le logiciel détenu par des tiers, et qui comprend la technologie relative aux polices de caractères, est protégé par un copyright et licencié par des fournisseurs de Sun. Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l Université de Californie. UNIX est une marque déposée aux Etats-Unis et dans d autres pays et licenciée exclusivement par X/Open Company, Ltd. Sun, Sun Microsystems, le logo Sun, AnswerBook2, docs.sun.com, Sun Fire, OpenBoot, Java, Sun Remote Services Net Connect, et Solaris sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d autres pays. Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux Etats-Unis et dans d autres pays. Les produits protant les marques SPARC sont basés sur une architecture développée par Sun Microsystems, Inc. L interface d utilisation graphique OPEN LOOK et Sun a été développée par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sun reconnaît les efforts de pionniers de Xerox pour la recherche et le développment du concept des interfaces d utilisation visuelle ou graphique pour l industrie de l informatique. Sun détient une license non exclusive do Xerox sur l interface d utilisation graphique Xerox, cette licence couvrant également les licenciées de Sun qui mettent en place l interface d utilisation graphique OPEN LOOK et qui en outre se conforment aux licences écrites de Sun. LA DOCUMENTATION EST FOURNIE "EN L ÉTAT" ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L APTITUDE A UNE UTILISATION PARTICULIERE OU A L ABSENCE DE CONTREFAÇON.

3 Contents Preface vii 1. Introduction 1 SMS Software on the SC 1 SMS Software Requirements 2 Default Stop Sequence 3 Software Combinations 3 Other Documentation and Requirements 7 Example Conventions 7 2. SMS Software Installation 9 Preparing to Perform a Reinstallation or Fresh OS/SMS Installation (Type 1) 9 Performing a Type 1 Installation 10 Downloading SMS Software 11 Backing Up Your SMS Environment 11 Installing the Solaris Operating Environment 13 Installing SMS Packages 14 Restoring Your SMS Configuration on the Spare SC 16 Configuring the MAN Network on the Spare SC 17 Switching Control to the Spare SC 22 iii

4 Updating the Flash PROMs on the SC and the System Boards 23 Reinstalling the Former Main SC 25 Installation of the Solaris Operating Environment on the Former Main SC 26 Installing SMS Software on the Former Main SC 27 Restoring Your SMS Configuration on the Former Main SC 29 Configuring the MAN Network on the Former Main SC 30 Rebooting the Former Main SC 35 Updating the Flash PROMs on the Former Main SC 35 Verifying the Chassis Serial Number 37 Enabling Failover on the Main SC (SC1) SMS Software Upgrade 39 Preparing to Perform an OS/SMS Upgrade (Type 2) Installation 40 Performing a Type 2 Upgrade 40 Downloading SMS Software 41 Preparing Your SMS Environment for Upgrade 42 Upgrading the Solaris Operating Environment 44 Upgrading SMS Packages 45 Switching Control to the Spare SC 48 Updating the Flash PROMs on the SC and the System Boards 49 Upgrading the Former Main SC 51 Upgrade the Solaris Operating Environment on the Spare SC 52 SMS Software on the Former Main SC 53 Rebooting the Former Main SC 57 Updating the Flash PROMs on the Former Main SC 57 Enabling Failover on the Main SC (SC1) SMS Additional Software Instructions 61 Adding Users to SMS 61 iv System Management Services (SMS) Installation Guide April 2004

5 Installing SMS Patches 65 Installing Additional Software Packages 67 Network Time Protocol (NTP) Information 69 Stopping and Starting SMS 70 Mounting the CD-ROM over NFS SMS Security Options SMS Software and Domains 75 Setting Up and Installing the Solaris Operating Environment for the Domain 75 Unconfigured Domains 81 Creating a Domain 83 Making Changes to a Domain 89 Index 93 Contents v

6 vi System Management Services (SMS) Installation Guide April 2004

7 Preface This guide contains installation and upgrade instructions for the System Management Services (SMS) software. Before You Read This Book This guide is intended for the Sun Fire high-end system administrator, who has a working knowledge of UNIX systems, particularly those based on the Solaris operating environment. If you do not have such knowledge, read the Solaris User and System Administrator documentation provided with this system, and consider UNIX system administration training. All members of the next-generation Sun Fire server family can be configured as loosely coupled clusters. However, it is currently outside of the scope of this document to address system management for Sun Fire cluster configurations. How This Book Is Organized This guide contains the following information: Chapter 1 introduces installation for SMS Chapter 2 describes SMS software reinstallation. Chapter 3 describes SMS software upgrade. Chapter 4 describes additional SMS software instructions. vii

8 Chapter 5 describes security option instructions. Chapter 6 describes SMS software and domains. Using UNIX Commands This document might not contain information on basic UNIX commands and procedures such as shutting down the system, booting the system, and configuring devices. See the following for this information: Software documentation that you received with your system Solaris operating environment documentation, which is at Typographic Conventions Typeface or Symbol AaBbCc123 AaBbCc123 AaBbCc123 Meaning The names of commands, files, and directories; on-screen computer output What you type, when contrasted with on-screen computer output Book titles, new words or terms, words to be emphasized. Replace command-line variables with real names or values. Examples Edit your.login file. Use ls -a to list all files. % You have mail. % su Password: Read Chapter 6 in the User s Guide. These are called class options. To delete a file, type rm filename. viii System Management Services (SMS) Installation Guide April 2004

9 Shell Prompts Shell C shell C shell superuser Prompt sc_name:sms-user:> or domain_id:sms-user:> sc_name:# or domain_id:# Bourne shell and Korn shell > Bourne shell and Korn shell superuser # Related Documentation Application Title Part Number Release Notes System Management Services (SMS) Release Notes Overview Sun Fire High-End Systems Software Overview Guide Administrator Guide System Management Services (SMS) Administrator Guide Reference (manpages) System Management Services (SMS) Reference Manual Options System Management Services (SMS) 1.4 Dynamic Reconfiguration User Guide Sun Fire High-End Systems Dynamic Reconfiguration User Guide System Administration Guide: IP Services OpenBoot 4.x Command Reference Manual Sun Fire 15K/12K System Site Planning Guide Preface ix

10 Application Title Part Number Sun Fire Link Fabric Administrator s Guide Securing the Sun Fire 12K and 15K System Controllers: Updated for SMS 1.4 Securing the Sun Fire 12K and 15K Domains: Updated for SMS Accessing Sun Documentation You can view, print, or purchase a broad selection of Sun documentation, including localized versions, at: Contacting Sun Technical Support If you have technical questions about this product that are not answered in this document, go to: Sun Welcomes Your Comments Sun is interested in improving its documentation and welcomes your comments and suggestions. You can submit your comments by going to: Please include the title and part number of your document with your feedback: System Management Services (SMS) Installation Guide, part number x System Management Services (SMS) Installation Guide April 2004

11 CHAPTER 1 Introduction This chapter describes what s involved in the reinstallation and upgrade of the SMS software. Instructions are provided in subsequent chapters. SMS 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 Partition SMS Software Approximate Partition Sizes Size 0 /(root) 8 Gbytes 1 /swap 2 Gbyte 4 OLDS/LVM database (metadb) 5 OLDS/LVM database (metadb) 10 Mbytes 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. 1

12 SMS Software Requirements The Solaris 8 version of SMS requires: The 02/02 version of the Solaris 8 operating environment. The same version of SMS software on both system controllers (SCs). Installation of the Entire Distribution software group of the Solaris operating environment. The same version of the Solaris operating environment, including update version and installed patches, on both SCs is strongly recommended. All patches are available from : The patch. The patch for Solaris 8 on each domain (not required for SC). The patch for Solaris 8 on each domain (not required for SC). The Solaris 8 version of SMS has binary dependencies on these Solaris libraries: /usr/lib/libnvpair.so.1 /usr/lib/libuuid.so.1 /usr/lib/fm/libdiagcode.so.1 The fixes for these libraries are available respectively through patches , , , or better. These patches are available through: Installation of SMS 1.4_s8 version requires all three of these libraries to be present on the system controllers and the domains. Otherwise, the SMS daemons will not start. Java installed in the default directory (/usr/java1.2/bin/java). Java is normally installed in this directory during Solaris Entire Distribution installation. Caution If you are using the Sun Fire Interconnect and Java is not installed, or not installed in its default directory, SMS will fail to load. Note After installing Java 1.2.2, be sure to stop and restart SMS. The Solaris 9 version of SMS requires: The 4/04 version of the Solaris 9 operating environment. The same version of SMS software on both system controllers (SCs). Installation of the Entire Distribution software group of the Solaris operating environment. 2 System Management Services (SMS) Installation Guide April 2004

13 The same version of the Solaris operating environment, including update version and installed patches, on both SCs is strongly recommended. The patch, available from: Either Solaris 9 12/03 or patch for all Solaris 9 domains (not required on the SC) Java installed in the default directory (/usr/java1.2/bin/java). Java is normally installed in this directory during Solaris Entire Distribution installation. Caution If you are using the Sun Fire Interconnect and Java is not installed, or not installed in its default directory, SMS will fail to load. Note 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: Chapter 1 Introduction 3

14 sms1.2_s8 sms1.3_s8 sms1.4.1_s8 Solaris 8 SMS 1.2 SMS 1.3 SMS Solaris 9 SMS 1.2 SMS 1.3 SMS sms1.2_s9 sms1.3_s9 sms1.4.1_s9 sms1.4_s8 sms1.4.1_s8 Solaris 8 SMS 1.4 SMS Solaris 9 SMS 1.4 sms1.4_s9 SMS sms1.4.1_s9 FIGURE 1-1 SMS Upgrade Paths Note 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 Note The upgrade from SMS 1.4 to SMS 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 System Management Services (SMS) Installation Guide April 2004

15 Solaris 8 OR SMS 1.2 sms1.2_s8 sms1.3_s8 OS upgrade: none SMS Upgrade: must upgrade to 1.3, first Instructions: See SMS 1.3 documentation SMS sms1.4.1_s8 SMS 1.3 SMS 1.4 sms1.4_s8 OS upgrade: none SMS Upgrade: Type 2 Instructions: Performing a Type 2 Upgrade on page 40 SMS sms1.4.1_s8 sms1.3_s8 OR SMS 1.3 SMS 1.4 sms1.4_s8 OS upgrade: Fresh install Solaris 9 or upgrade to Solaris 9 SMS upgrade: Type 2 Instructions: back up SMS configuration, install/upgrade Solaris 9, install/upgrade SMS 1.4.1_s9, restore SMS configuration SMS sms1.4.1_s9 SMS sms1.4.1_s8 OS upgrade: Fresh install Solaris 9 or upgrade to Solaris 9 SMS Upgrade: Type 2 Instructions: Performing a Type 2 Upgrade on page 40 SMS sms1.4.1_s9 FIGURE 1-2 SMS Upgrade Instructions - Solaris 8 Chapter 1 Introduction 5

16 Solaris 9 SMS 1.2 OS upgrade: none SMS upgrade: no direct upgrade; first upgrade to SMS 1.3. Instructions: see SMS 1.3 documentation. SMS sms1.4.1_s9 SMS 1.3 OS upgrade: none SMS sms1.3_s9 SMS upgrade: Upgrade Procedure: Performing a Type 2 Upgrade on page 40 Instructions: back up SMS configuration, upgrade to SMS 1.4.1_s9, restore SMS configuration sms1.4.1_s9 FIGURE 1-3 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 Java Web 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 or you could misconfigure SMS and lose functionality. Note SMS 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. 6 System Management Services (SMS) Installation Guide April 2004

17 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. Solaris 9 Installation Guide Sun Fire 15K/12K System Site Planning Guide Refer to the Sun Fire 15K/12K System Site Planning Guide when reconfiguring your MAN network. You will need the following information from your worksheets: Platform name Chassis serial number Hostname IP addresses and submask for the I1 internal network Hostname IP addresses and submask for the I2 internal network Community hostname IP addresses and submask for the external network Hostname IP address for the SC logical interface Community hostname addresses for the domains Note We recommend that you install the release-appropriate Solaris Patch Cluster available at to ensure that SMS runs properly. Any patches to the Solaris operating environment should be applied before re-installing or upgrading the SMS software. Check the Solaris 9 (SPARC Platform Edition) Release Notes, the Solaris 9 Release Notes Supplement for Sun Hardware, the System Management Services (SMS) 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: Chapter 1 Introduction 7

18 Prompt sc0:# sc1:# domain_id:# sc_name:sms-user:> domain_id:sms-user:> Definition Superuser on SC0, initially the main SC Superuser on SC1, initially the spare SC Superuser on the domain User prompt on the SC sms-user is the user-name of an administrator, operator, configurator, or service personnel logged in to the SC. User prompts on the domain sms-user is the user-name of the administrator, operator, configurator, or service personnel logged in to the domain. 8 System Management Services (SMS) Installation Guide April 2004

19 CHAPTER 2 SMS Software Installation This chapter contains instructions for reinstalling SMS 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. This chapter includes: To Download Software From the Web To Back Up Your SMS Environment To Install the Solaris Operating Environment (optional) To Install the SMS Software Packages Using smsinstall To Restore Your SMS Configuration To Configure the Management Network (MAN) Using the smsconfig(1m) Command To Verify the Chassis Serial Number To Enable Failover Preparing to Perform a Reinstallation or Fresh OS/SMS Installation (Type 1) The SMS 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. 9

20 Performing a Type 1 Installation 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: Task Reference Page Download your SMS packages To Download Software From the Web To Download Software From a CD-ROM 9 Backup SMS software - Turn off failover on the main SC (SC0) - Stop SMS on the spare SC (SC1) - Backup the current SMS software using smsbackup on the spare To Backup Your SMS Environment 10 Install Solaris operating environment Solaris Installation Guide Install SMS software packages on the spare SC (SC1) To Install the SMS Software Packages Using smsinstall 12 Restore your SMS configuration on the spare SC To Restore Your SMS Configuration 15 Configure the MAN network on the spare SC To Configure the Management Network (MAN) Using smsconfig(1m) 16 Configure your SMS user groups on the spare SC (optional) To Add Users to SMS Groups and Configure Directory Access 63 Switch control to the spare SC To Switch Control to the Spare SC 21 Update the SC and CPU flash PROMs on the new spare SC Updating the Flash PROMs 22 Reinstall the former main SC - Backup the current SMS software using smsbackup on the former main SC - Install Solaris operating environment - Install SMS software packages on the former main SC To Reinstall the Former Main SC 25 Restore your SMS configuration on the former main SC To Restore Your SMS Configuration 29 Configure the MAN network on the former main SC To Configure the Management Network (MAN) Using smsconfig(1m) 30 Configure your SMS user groups for the former main SC (optional) To Add Users to SMS Groups and Configure Directory Access 63 Reboot the former main SC (SC0) To Reboot the Former Main SC 36 Update the SC flash PROMs on the new spare SC To Update the Flash PROMs 36 Verify the chassis serial number To Verify the Chassis Serial Number 37 Turn on failover on the new main SC (SC1) To Enable Failover System Management Services (SMS) Installation Guide April 2004

21 To begin, proceed to Downloading SMS Software on page 11. Downloading SMS Software You can retrieve SMS software from the web. To Download Software From the Web 1. Using your web browser, go to 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: sc1:# cd /download_directory 6. Extract the downloaded file by typing: sc1:# unzip sms_1_4_1_sparc.zip The SMS 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 on page 11. 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: To Back Up Your SMS Environment On the main SC: Chapter 2 SMS Software Installation 11

22 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. 3. Deactivate failover: sc0:sms-user:> /opt/sunwsms/bin/setfailover off On the spare SC: 1. Log in to the spare as superuser. 2. Stop SMS on the spare SC (SC1): sc1:# /etc/init.d/sms stop 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. 12 System Management Services (SMS) Installation Guide April 2004

23 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. sc1:# /opt/sunwsms/bin/smsbackup directory_name where: 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: sc1:# /usr/bin/df -F ufs directory_name 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 on page 13. If you are reinstalling SMS software proceed to Installing SMS Packages on page 14. Installing the Solaris Operating Environment Note Make sure you have the proper release of the Solaris operating environment, including patches (see SMS Software Requirements on page 2). Without the proper version and patches, the availability daemons on the SC will not start, causing SMS daemon startup failures and an unusable SC. Chapter 2 SMS Software Installation 13

24 To Install the Solaris Operating Environment 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 on page 7. 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. 2. Verify that Java 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 is not installed in the default directory, SMS will not start. 3. Stop and Restart SMS. See To Manually Stop and Restart SMS on page Once your operating environment has been successfully installed proceed to Installing SMS Packages on page 14. 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 on page 14. 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: sc1:# cd /download_dir/sms_1_4_1_sparc/system_management_services_1.4.1/tools 14 System Management Services (SMS) Installation Guide April 2004

25 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 on page 11. Here is an example: sc1:# smsinstall directory_name Installing SMS packages. Please wait... pkgadd -n -d "directory_name" -a /tmp/smsinstall.admin SUNWSMSr SUNWSMSop SUNWSMSdf SUNWSMSjh SUNWSMSlp SUNWSMSmn SUNWSMSob SUNWSMSod SUNWSMSpd SUNWSMSpo SUNWSMSpp SUNWSMSsu SUNWscdvr.u SUNWufrx.u SUNWufu SUNWwccmn Copyright 2004 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. 205 blocks Installation of <SUNWSMSr> was successful... Installation of <SUNWSMSop> was successful... Installation of <SUNWSMSdf> was successful... Installation of <SUNWSMSjh> was successful... Installation of <SUNWSMSlp> was successful... Installation of <SUNWSMSmn> was successful... Installation of <SUNWSMSob> was successful... Installation of <SUNWSMSod> was successful... Installation of <SUNWSMSpd> was successful... Installation of <SUNWSMSpo> was successful... Installation of <SUNWSMSpp> was successful. Installation of <SUNWSMSsu> was successful. Installation of <SUNWscdvr> was successful... Reboot client to install driver. type=ddi_pseudo;name=flashprom uflash\n0 Installation of <SUNWufrx> was successful. Chapter 2 SMS Software Installation 15

26 Installation of <SUNWufu> was successful. Installation of <SUNWwccmn> was successful. Verifying that all SMS packages are installed.ok Setting up /etc/init.d/sms run control script for SMS New SMS version is active Attempting to start daemon picld /etc/init.d/picld start smsupgrade complete. Log file is /var/sadm/system/logs/smsinstall. 3. Proceed to To Restore Your SMS Configuration on page 16. Restoring Your SMS Configuration on the Spare SC 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. sc1:# /opt/sunwsms/bin/smsrestore filename where: 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. 2. For a fresh install: Proceed to To Configure the Management Network (MAN) Using the smsconfig(1m) Command on page 17. For reinstallation: During reinstallation the SMS group file was restored. Proceed to To Add Users to SMS Groups and Configure Directory Access on page 63 only if you will be changing user group memberships. Otherwise, proceed to To Switch Control to the Spare SC on page System Management Services (SMS) Installation Guide April 2004

27 Configuring the MAN Network on the Spare SC To Configure the Management Network (MAN) Using the smsconfig(1m) Command To correctly configure the management network, you need to do the following: Run smsconfig -m Edit the /etc/nsswitch.conf Edit your Solaris Naming software. Reboot the SC. 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: sc1:# /opt/sunwsms/bin/smsconfig -m 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. Caution The IP addresses shown in the following example are examples only. Refer to your Sun Fire 15K/12K System Site Planning Guide for valid IP addresses for your network. Using invalid network IP addresses could, under certain circumstances, render your system unbootable! Chapter 2 SMS Software Installation 17

28 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) Administrator Guide and the smsconfig man page. sc1:# smsconfig -m The platform name identifies the entire host machine to the SMS software. The platform name occupies a different name space than domain names (hostnames of bootable systems). What is the name of the platform this SMS will service [sun15]? sun15 Configuring the External Network for Community C1 Do you want to define this Community? [y,n] y Two network interfaces controllers (NICs) are required for IPMP network failover. Enter NICs associated with community C1 [eri0 eri1]: [Return] Enter hostname for eri0 [sun15-sc1-eri0]:[return] Enter IP address for eri0: Enter hostname for eri1 [sun15-sc1-eri1]:[return] Enter IP address for sun15-sc1-eri1: The Logical/Floating IP hostname and address will "float" over to whichever system controller (SC0 or SC1) is acting as the main SC. Enter Logical/Floating IP hostname for community C1 [sun15-sc- C1]:[Return] Enter IP address for sun15-sc-c1: Enter Netmask for community C1: Enter hostname for community C1 failover address [sun15-sc1-c1- failover]:[return] Enter IP address for sun15-sc1-c1-failover: Hostname IP Address (platform=sun15) sun15-sc-c sun15-sc1-c1-failover sun15-sc1-eri sun15-sc1-eri System Management Services (SMS) Installation Guide April 2004

29 Do you want to accept these network settings? [y,n] y Configuring the External Network for Community C2 Do you want to define this Community? [y,n] n Configuring I1 Management Network - I1 is the Domain to SC MAN. MAN I1 Network Identification Enter the IP network number (base address) for the I1 network: Enter the netmask for the I1 MAN network [ ]:[Return] Hostname IP Address (platform=sun15) netmask-i sun15-sc-i sun15-a sun15-b sun15-c sun15-d sun15-e sun15-f sun15-g sun15-h sun15-i sun15-j sun15-k sun15-l sun15-m sun15-n sun15-o sun15-p sun15-q sun15-r Do you want to accept these network settings? [y,n] y Configuring I2 Management Network - I2 is for SC to SC MAN. MAN I2 Network Identification Enter the IP network number (base address) for the I2 network: Enter the netmask for the I2 MAN network [ ]:[Return] Chapter 2 SMS Software Installation 19

30 Hostname IP Address (platform=sun15) netmask-i sun15-sc0-i sun15-sc1-i Do you want to accept these settings? [y,n] y Creating /.rhosts to facilitate file propagation...done MAN Network configuration modified! Changes will take effect on next reboot. The following changes are about to be applied to the "/etc/hosts" hosts file ADD: sun15-a #smsconfig-entry# ADD: sun15-b #smsconfig-entry# ADD: sun15-c #smsconfig-entry# ADD: sun15-d #smsconfig-entry# ADD: sun15-e #smsconfig-entry# ADD: sun15-f #smsconfig-entry# ADD: sun15-g #smsconfig-entry# ADD: sun15-h #smsconfig-entry# ADD: sun15-i #smsconfig-entry# ADD: sun15-j #smsconfig-entry# ADD: sun15-k #smsconfig-entry# ADD: sun15-l #smsconfig-entry# ADD: sun15-m #smsconfig-entry# ADD: sun15-n #smsconfig-entry# ADD: sun15-o #smsconfig-entry# ADD: sun15-p #smsconfig-entry# ADD: sun15-q #smsconfig-entry# ADD: sun15-r #smsconfig-entry# ADD: sun15-sc-i1 #smsconfig-entry# ADD: sun15-sc-c1 #smsconfig-entry# ADD: sun15-sc1-c1-failover #smsconfig-entry# ADD: sun15-sc1-eri0 #smsconfig-entry# ADD: sun15-sc1-eri1 #smsconfig-entry# ADD: sun15-sc0-i2 #smsconfig-entry# ADD: sun15-sc1-i2 #smsconfig-entry# Update the hosts file, "/etc/hosts", with these changes? [y,n] y Hosts file "/etc/hosts" has been updated. The following information is about to be applied to the "/etc/netmasks" file ADD network: , mask: ADD network: , mask: ADD network: , mask: System Management Services (SMS) Installation Guide April 2004

31 Update the netmasks file, "/etc/netmasks", with these changes? [y,n] y Netmasks files etc/netmasks has been updated. smsconfig complete. Log file is /var/sadm/system/logs/smsconfig sc1:# 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. Chapter 2 SMS Software Installation 21

32 10. Configure SMS groups. See To Add Users to SMS Groups and Configure Directory Access on page 63. 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 on page 22. Switching Control to the Spare SC To Switch Control to the Spare SC 1. Log in to the main SC (SC0) as superuser. 2. Stop SMS on the main SC: sc0:# /etc/init.d/sms stop 3. Log in to the spare SC (SC1) and drop to the OpenBoot PROM prompt. sc1:# shutdown -y -g0 -i0...[system message] ok 4. Boot the spare SC. ok boot -rv 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. 5. Next: For reinstallation of SMS 1.4.1, proceed to To Reinstall the Former Main SC on page 25. If you are fresh installing a system which previously ran SMS 1.3, proceed to To Update the Flash PROMs on page System Management Services (SMS) Installation Guide April 2004

33 Updating the Flash PROMs on the SC and the System Boards To Update the Flash PROMs When you fresh install SMS on system previously running SMS 1.3 or SMS 1.4, you must update the flash PROMs on: The main SC The spare SC Each system board 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) Reference Manual or the flashupdate man page. Note In order to update your SC PROMs you must have access to the following drivers: sc#:# ls -l /dev/uflash* lrwxrwxrwx 1 root other 62 Oct 12 20:30 /dev/uflash0 ->../devices/pci@1f,0/pci@1,1/ebus@1/flashprom@10,400000:uflash0 lrwxrwxrwx 1 root other 62 Oct 12 20:30 /dev/uflash1 ->../devices/pci@1f,0/pci@1,1/ebus@1/flashprom@10,800000:uflash1 If the drivers are not available you must run the following command as superuser on each SC: sc#:# /usr/sbin/devfsadm -i uflash 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: sc0:sms-user:> flashupdate -f /opt/sunwsms/firmware/scobpimg.di sc0/fp0 3. Upgrade the fp1 Flash PROM, using the appropriate image for the type of board. Chapter 2 SMS Software Installation 23

34 For the CP1500 board, use flashupdate with the nsscpost.di image. For example: sc0:sms-user:> flashupdate -f /opt/sunwsms/firmware/nsscpost.di sc0/fp1 For the CP2140 board, use flashupdate with the osscpost.di image: sc0:sms-user:> flashupdate -f /opt/sunwsms/firmware/osscpost.di sc0/fp1 4. 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 5. Upgrade the CPU Flash PROMs on each system board. Use flashupdate. sc1:sms-user:> flashupdate -f /opt/sunwsms/hostobjs/sgcpu.flash location where: 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 SB(0...17), SB(0...8) IO(0...17), IO(0...8) SC(0 1), SC(0 1) The following FPROM_id forms are accepted: FP(0 1), FP(0 1) 24 System Management Services (SMS) Installation Guide April 2004

35 6. Drop to the OpenBoot PROM prompt. sc1:sms-user:> su - password: [superuser passwd] sc1:# shutdown -y -g0 -i0...[system message] ok 7. Reboot the SC. Type: ok boot -rv 8. Proceed to To Reinstall the Former Main SC on page 25. Reinstalling the Former Main SC 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. Chapter 2 SMS Software Installation 25

36 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. sc0:# /opt/sunwsms/bin/smsbackup directory_name where: 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: sc0:# /usr/bin/df -F ufs directory_name A UFS file system will return directory information. Any other type of file system will return a warning. 3. Next: To fresh install the Solaris 9 operating environment, proceed to Installation of the Solaris Operating Environment on the Former Main SC on page 26. To reinstall SMS 1.4.1, proceed to Installing SMS Software on the Former Main SC on page 27. Installation of the Solaris Operating Environment on the Former Main SC Note Make sure you have the proper release of the Solaris operating environment, including patches (see SMS Software Requirements on page 2). Without the proper version and patches, the availability daemons on the SC will not start, causing SMS daemon startup failures and an unusable SC. 26 System Management Services (SMS) Installation Guide April 2004

37 To Install the Solaris Operating Environment 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 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 on page 7. 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. 2. Verify that Java 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 is not installed in the default directory, SMS will not start. 3. Stop and Restart SMS. See To Manually Stop and Restart SMS on page Once your operating environment has been successfully installed proceed to Installing SMS Software on the Former Main SC on page 27. Installing SMS Software on the Former Main SC To install SMS software packages, perform the steps in the following procedure. To Install the SMS Software Packages Using smsinstall 1. Log in to the former main SC as superuser. 2. Change directory to the location of smsinstall: Type: sc0:# cd /download_dir/sms_1_4_1_sparc/system_management_services_1.4.1/tools Chapter 2 SMS Software Installation 27

38 Note smsinstall(1m) command 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. Install packages using the smsinstall(1m) command. directory_name is the /Product directory location of the SMS packages from Downloading SMS Software on page 11. Here is an example. sc0:# smsinstall directory_name Installing SMS packages. Please wait... pkgadd -n -d "directory_name" -a /tmp/smsinstall.admin SUNWSMSr SUNWSMSop SUNWSMSdf SUNWSMSjh SUNWSMSlpUNWSMSmn SUNWSMSob SUNWSMSod SUNWSMSpd SUNWSMSpo SUNWSMSpp SUNWSMSsuUNWscdvr.u SUNWufrx.u SUNWufu SUNWwccmn Copyright 2004 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. 205 blocks Installation of <SUNWSMSr> was successful... Installation of <SUNWSMSop> was successful... Installation of <SUNWSMSdf> was successful... Installation of <SUNWSMSjh> was successful... Installation of <SUNWSMSlp> was successful... Installation of <SUNWSMSmn> was successful... Installation of <SUNWSMSob> was successful... Installation of <SUNWSMSod> was successful... Installation of <SUNWSMSpd> was successful... Installation of <SUNWSMSpo> was successful... Installation of <SUNWSMSpp> was successful. Installation of <SUNWSMSsu> was successful. Installation of <SUNWscdvr> was successful... Reboot client to install driver. type=ddi_pseudo;name=flashprom uflash\n0 Installation of <SUNWufrx> was successful. 28 System Management Services (SMS) Installation Guide April 2004

39 Installation of <SUNWufu> was successful. Installation of <SUNWwccmn> was successful. Verifying that all SMS packages are installed.ok Setting up /etc/init.d/sms run control script for SMS New SMS version is active Attempting to start daemon picld /etc/init.d/picld start smsupgrade complete. Log file is /var/sadm/system/logs/smsinstall. 4. Proceed to To Restore Your SMS Configuration on page 29. Restoring Your SMS Configuration on the Former Main SC To Restore Your SMS Configuration 1. Restore your SMS configuration on the former main SC. Run smsrestore. Note Once smsrestore completes you will see the following message: Please set the desired SMS failover state. Ignore this message. sc0:# /opt/sunwsms/bin/smsrestore filename where: 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. 2. For a fresh install: Proceed to To Configure the Management Network (MAN) Using the smsconfig(1m) Command on page 30. For reinstallation: During reinstallation the SMS group file was restored. Proceed to To Add Users to SMS Groups and Configure Directory Access on page 63 only if you will be changing user group memberships. Otherwise, proceed to To Reboot the Former Main SC on page 35. Chapter 2 SMS Software Installation 29