SPARC Enterprise T5440 Server Administration Guide TM Manual Code C120-E511-01EN Part No.
Copyright © 2009 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. FUJITSU LIMITED provided technical input and review on portions of this material. Sun Microsystems, Inc. and Fujitsu Limited each own or control intellectual property rights relating to products and technology described in this document, and such products, technology and this document are protected by copyright laws, patents and other intellectual property laws and international treaties.
Copyright © 2009 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, Etats-Unis. Tous droits réservés. Entrée et revue tecnical fournies par FUJITSU LIMITED sur des parties de ce matériel. Sun Microsystems, Inc. et Fujitsu Limited détiennent et contrôlent toutes deux des droits de propriété intellectuelle relatifs aux produits et technologies décrits dans ce document.
Contents Preface ix Basic Administrative Tasks Initial System Setup 1 1 Communicating With the System ILOM Overview 2 2 ▼ Log In to ILOM ▼ Log In to the System Console ▼ Display the ok Prompt ▼ Display the ILOM ->Prompt 5 System Console Output Options 5 ▼ 3 4 4 Access the System Console Through a Local Graphics Monitor Performing Common Tasks 7 ▼ Power On the System 7 ▼ Power Off the System 7 ▼ Reset the System ▼ Update the Firmware Manage Disk Volumes 6 8 9 13 Hardwa
▼ Create a Hardware Striped Volume ▼ Configure and Label a Hardware RAID Volume for Use in the Solaris Operating System 18 Disk Slot Numbers 20 Removing Hardware RAID Volumes 21 ▼ Delete a Hardware RAID Volume ▼ Hot-Plug a Mirrored Disk ▼ Hot-Plug a Nonmirrored Disk Manage the System 17 21 23 24 27 Searching for Faults 27 ▼ Log In to ILOM ▼ Display System Faults ▼ Run Full POST Diagnostics on Reset ▼ Locate the System Bypassing Minor Faults 28 28 30 31 Automatic System Recov
Logical Domain Configurations 39 Logical Domains Software Requirements 39 Operating the Solaris OS With Logical Domains 40 OpenBoot Firmware Not Available After Solaris OS Has Started if Domaining Is Enabled 40 Power-Cycle a Server ▼ 40 Save Your Current Logical Domain Configurations to the SC Result of an OpenBoot power-off Command Result of Solaris OS Breaks 41 41 Results From Halting or Rebooting the Control Domain Additional Documentation 41 43 ALOM-to-ILOM Command Reference 45 ILOM and
viii SPARC Enterprise T5440 Server Administration Guide • July 2009
Preface This manual is for experienced system administrators. This manual includes general descriptive information about the SPARC Enterprise™ T5440 server, and detailed instructions for configuring and administering the server. To use the information in this document, you must have working knowledge of computer network concepts and terms, and advanced familiarity with the Solaris™ Operating System (Solaris OS).
Structure and Contents of This Manual This manual is organized as described below: ■ “Basic Administrative Tasks” on page 1 Describes how to communicate with the server, and perform basic administrative tasks. ■ “Manage Disk Volumes” on page 13 Describes how to manage internal disk volumes. ■ “Manage the System” on page 27 Describes how to manage the system remotely. ■ “Use Logical Domains Software” on page 37 Introduces logical domains software.
Related Documentation The latest versions of all the SPARC Enterprise™ Series manuals are available at the following Web sites: Global Site (http://www.fujitsu.com/sparcenterprise/manual/) Japanese Site (http://primeserver.fujitsu.
Title Description Manual Code Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide Information that describes ILOM 3.0 features and functionality C120-E573 Integrated Lights Out Manager (ILOM) 3.0 Getting Started Guide Information and procedures for network connection, logging in to ILOM 3.0 for the first time, and configuring a user account or a directory service C120-E576 Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide Information and procedures for accessing ILOM 3.
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. Refer to the following for this information: ■ Software documentation that you received with your system ■ Solaris™ Operating System documentation, which is at (http://docs.sun.com) Text Conventions Typeface* Meaning Examples AaBbCc123 The names of commands, files, and directories; on-screen computer output Edit your .
Prompt Notations The following prompt notations are used in this manual.
Basic Administrative Tasks This section contains information about common tasks used to manage your system after initial setup. Description Links Refer to your systems’ installation and setup guide for initial setup instructions. “Initial System Setup” on page 1 Access the system using ILOM, or configure alternate ways to communicate with the system.
Communicating With the System This section contains: ■ “ILOM Overview” on page 2 ■ “Log In to ILOM” on page 3 ■ “Log In to the System Console” on page 4 ■ “Display the ok Prompt” on page 4 ■ “Display the ILOM ->Prompt” on page 5 ■ “System Console Output Options” on page 5 ■ “Access the System Console Through a Local Graphics Monitor” on page 6 ILOM Overview Integrated Lights Out Manager (ILOM) is a low-level system management tool used to monitor and manage system components, diagnose problems
▼ Log In to ILOM This procedure assumes the default configuration of the service processor as described in your server’s installation guide. To set up the default service processor configuration, see your server’s installation guide. ● Open an SSH session and connect to the service processor by specifying its IP address. The ILOM default username is root and the default password is changeme. % ssh root@xxx.xxx.xxx.xxx ... Are you sure you want to continue connecting (yes/no) ? yes ...
▼ Log In to the System Console 1. Log in to ILOM. See “Log In to ILOM” on page 3. 2. To access the system console from ILOM, type: -> start /SP/console Are you sure you want to start /SP/console (y/n) ? y Serial console started. To stop, type #. . . . You are logged in to the system console. Perform tasks as needed. Related Information ■ “Display the ok Prompt” on page 4 ■ “Display the ILOM ->Prompt” on page 5 ▼ Display the ok Prompt This procedure assumes the default system console configuration. 1.
System State What To Do OS Unresponsive From the ILOM -> prompt, type the set /HOST send_break_action= break command provided the operating system software is not running and the server is already under OpenBoot firmware control. Then issue the start /SP/console command. OS Unresponsive and Need to Prevent auto-boot From the ILOM -> prompt, type: -> set /HOST/bootmode script=”setenv auto-boot? false” Press Enter.
▼ Access the System Console Through a Local Graphics Monitor After initial system installation, you can install a local graphics monitor and configure it to access the system console. You cannot use a local graphics monitor to perform initial system installation, nor can you use a local graphics monitor to view power-on self-test (POST) messages.
Performing Common Tasks This section contains: ■ “Power On the System” on page 7 ■ “Power Off the System” on page 7 ■ “Reset the System” on page 8 ■ “Update the Firmware” on page 9 ▼ Power On the System 1. Log in to ILOM. See “Log In to ILOM” on page 3. 2. At the ILOM -> prompt, type: -> start /SYS Are you sure you want to start /SYS (y/n) ? y Starting /SYS -> Note – To force a power-on sequence, use the start -script /SYS command.
Jun 12 19:46:57 wgs41-58 syslogd: going down on signal 15 svc.stard: The system is down. syncing file systems...done Program terminated r)eboot o)k prompt, h)alt? 2. Switch from the system console prompt to the service processor console prompt. Type: ok #. -> 3. From the ILOM -> prompt, type: -> stop /SYS Are you sure you want to stop /SYS (y/n)? y Stopping /SYS -> Note – To perform an immediate shutdown, use the stop -force -script /SYS command.
▼ Update the Firmware 1. Ensure that the ILOM service processor network management port is configured. See the server’s installation guide for instructions. 2. Open an SSH session to connect to the service processor. % ssh root@xxx.xxx.xxx.xxx ... Are you sure you want to continue connecting (yes/no) ? yes ... Password: password (nothing displayed) Waiting for daemons to initialize... Daemons ready Integrated Lights Out Manager Version 2.0.0.0 Copyright 2008 Sun Microsystems, Inc. All rights reserved.
■ -script - Does not prompt for confirmation and acts as if yes was specified ■ -source - Specifies the IP address and full path name (URL) to the flash image -> load -source tftp://129.168.10.101/pathname NOTE: A firmware upgrade will cause the server and ILOM to be reset. It is recommended that a clean shutdown of the server be done prior to the upgrade procedure. An upgrade takes about 6 minutes to complete. ILOM will enter a special mode to load new firmware.
eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX. Listening on LPF/eth0/00:14:4f:3f:8c:af Sending on LPF/eth0/00:14:4f:3f:8c:af Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 eth0: link up, 100Mbps Full Duplex, auto-negotiation complete. DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 Hostname: hostname Starting portmap daemon: portmap. Initializing random number generator...done.
12 SPARC Enterprise T5440 Server Administration Guide • July 2009
Manage Disk Volumes This section contains information about creating and removing RAID volumes. Description Links Learn about Hardware RAID support on this system. “Hardware RAID Support” on page 13 Create RAID volumes then configure RAID volumes for use with Solaris.
Related Information ■ “Creating RAID Volumes” on page 14 ■ “Removing Hardware RAID Volumes” on page 21 Creating RAID Volumes This section contains: ■ “Create a Hardware Mirrored Volume” on page 14 ■ “Create a Hardware Mirrored Volume of the Default Boot Device” on page 15 ■ “Create a Hardware Striped Volume” on page 17 ■ “Configure and Label a Hardware RAID Volume for Use in the Solaris Operating System” on page 18 ■ “Disk Slot Numbers” on page 20 ▼ Create a Hardware Mirrored Volume 1.
3. Type yes to confirm creating the RAID volume. # raidctl -c c0t0d0 c0t1d0 Creating RAID volume c0t0d0 will destroy all data on member disks, proceed (yes/no)? yes Volume ‘c0t0d0” created When you create a RAID mirror, the secondary drive (in this case, c0t1d0) disappears from the Solaris device tree. 4.
created in that environment. One alternate medium is a network installation image in single-user mode (refer to the Solaris 10 Installation Guide for more information about configuring and using network-based installations). 1. Determine which disk is the default boot device. From the OpenBoot ok prompt, type the printenv command, and if necessary, the devalias command, to identify the default boot device. For example: ok printenv boot-device boot-device = disk ok devalias disk disk 2.
▼ Create a Hardware Striped Volume 1. Identify the hard drives to be used in the RAID volume. To verify which hard drive corresponds with which logical device name and physical device name, see “Disk Slot Numbers” on page 20. Note – The logical device names might appear differently on your system, depending on the number and type of add-on disk controllers installed. 2. To create the striped RAID volume, type: # raidctl -c -r disk1disk2 The creation of the RAID volume is interactive by default.
Related Information ■ “Hardware RAID Support” on page 13 ■ “Configure and Label a Hardware RAID Volume for Use in the Solaris Operating System” on page 18 ▼ Configure and Label a Hardware RAID Volume for Use in the Solaris Operating System After creating a RAID volume using raidctl, use format(1)to configure and label the volume before attempting to use it in a Solaris operating system. 1.
analyze defect backup verify save inquiry volname volname quit - surface analysis defect list management search for backup labels read and display labels save new disk/partition definitions show vendor, product and revision set 8-character volume name execute , then return 3. Type the type command at the format> prompt, then select 0 (zero) to autoconfigure the volume. format> type AVAILABLE DRIVE TYPES: 0. Auto configure 1. DEFAULT 2. SUN72G 3. SUN72G 4.
6. Verify that the new label has been written by printing the disk list using the disk command. format> disk AVAILABLE DISK SELECTIONS: 0. c0t0d0 /pci@0/pci@0/pci@2/scsi@0/sd@0, 0 1. c0t1d0 /pci@0/pci@0/pci@2/scsi@0/sd@1, 0 2.
Use TABLE: Disk Slot Numbers, Logical Device Names, and Physical Device Names on page 21 to map internal disk slot numbers with the logical and physical device names for each hard drive.
2. To determine the name of the RAID volume, type: # raidctl RAID Volume RAID RAID Disk Volume Type Status Disk Status ------------------------------------------------------------c0t0d0 IM OK c0t0d0 OK c0t0d0 OK In this example, the RAID volume is c0t0d0. 3.
Related Information ■ “Creating RAID Volumes” on page 14 ▼ Hot-Plug a Mirrored Disk 1. Verify which hard drive corresponds with which logical device name and physical device name. See “Disk Slot Numbers” on page 20. 2. To confirm a failed disk, type: # raidctl If the Disk Status is FAILED, then the drive can be removed and a new drive inserted. Upon insertion, the new disk should be OK and the volume should be RESYNCING.
5. To check the status of the RAID rebuild, type: # raidctl For example: # raidctl RAID Volume RAID RAID RAID Volume Type Status Disk Status ----------------------------------------------------------------c0t1d0 IM RESYNCING c0t1d0 OK c0t2d0 OK This example indicated that RAID volume c0t1d0 is resynchronizing. If you issue the command again once synchronization is complete and the disk is back online, the RAID status changes from RESYNCING to OK.
2.
usb0/1 usb0/2 # unknown unknown empty empty unconfigured unconfigured ok ok 5. Remove the hard drive as described in your server’s service manual. 6. Install a new hard drive as described in your server’s service manual. 7. Configure the new hard drive. Type: # cfgadm -c configure Ap-Id For example: # cfgadm -c configure c1::dsk/c0t3d0 The green Activity LED flashes as the new disk at c0t3d0 is added to the device tree. 8. Verify that the new hard drive is in the device tree.
Manage the System This section contains information about basic fault management and managing devices. Description Lilnks Use ILOM to view system faults and set diagnostic levels. “Log In to ILOM” on page 3 “Display System Faults” on page 28 “Run Full POST Diagnostics on Reset” on page 29 “Locate the System” on page 30 Configure your system to resume operation when encountering nonfatal faults.
▼ Log In to ILOM This procedure assumes the default configuration of the service processor as described in your server’s installation guide. ● Open an SSH session and connect to the service processor by specifying its IP address. The ILOM default username is root and the default password is changeme. % ssh root@xxx.xxx.xxx.xxx ... Are you sure you want to continue connecting (yes/no) ? yes ... Password: password (nothing displayed) Waiting for daemons to initialize...
2. At the ILOM -> prompt, type: -> show /SP/faultmgmt This command displays the fault ID, the faulted FRU device, and the fault message to standard output. The show /SP/faultmgmt command also displays POST results.
2. At the ILOM -> prompt, type: -> set /SYS keyswitch_state=diag The system is set to run full POST diagnostics on system reset. 3. To return to your normal diagnostic settings after running POST, type: -> set /SYS keyswitch_state=normal Related Information ■ “Clearing Faults” on page 33 ■ “Bypassing Minor Faults” on page 31 ■ “Managing Devices” on page 34 ■ “Locate the System” on page 30 ▼ Locate the System 1. Log in to ILOM. See “Log In to ILOM” on page 28. 2.
Bypassing Minor Faults This section contains: ■ “Automatic System Recovery” on page 31 ■ “Enable Automatic System Recovery” on page 31 ■ “Disable Automatic System Recovery” on page 32 ■ “View Components Affected by ASR” on page 33 Automatic System Recovery Automatic system recovery (ASR) functionality enables the system to resume operation after experiencing certain non-fatal hardware faults or failures.
2. At the ILOM -> prompt, type: -> set /HOST/diag mode=normal -> set /HOST/diag level=max -> set /HOST/diag trigger=power-on-reset error-reset 3. At the ok prompt, type: ok setenv auto-boot? true ok setenv auto-boot-on-error? true 4. To cause the parameter changes to take effect, type: ok reset-all The systems permanently stores the parameter changes and boots automatically when the OpenBoot configuration variable auto-boot? is set to true (its default value).
4. To cause the parameter change to take effect, type: ok reset-all The system permanently stores the parameter change. After you disable the ASR feature, it is not activated again until you re-enable it. Related Information ■ “Enable Automatic System Recovery” on page 31 ■ “Automatic System Recovery” on page 31 ▼ View Components Affected by ASR 1. Log in to ILOM. See “Log In to ILOM” on page 28. 2.
▼ Clear Component Fault Messages 1. Log in to ILOM. See “Log In to ILOM” on page 28. 2.
▼ Configure a Device Manually 1. Log in to ILOM. See “Log In to ILOM” on page 28. 2. At the ILOM -> prompt, type: -> set Device_Identifier component_state=enabled Related Information ■ “Devices and Device Identifiers” on page 35 ■ “Unconfigure a Device Manually” on page 34 Devices and Device Identifiers The device identifiers are case sensitive.
36 SPARC Enterprise T5440 Server Administration Guide • July 2009
Use Logical Domains Software SPARC Enterprise servers support the Logical Domains (LDoms) 1.0.3 software that is used to create and manage logical domains. The software comprises LDoms-enabling code in the Solaris 10 11/06 OS, LDoms-enabling code in System Firmware 6.4, and the Logical Domains Manager, which is the command-line interface. Description Links Learn about Logical Domains software, configurations and requirements.
■ “Logical Domain Configurations” on page 39 ■ “Logical Domains Software Requirements” on page 39 Logical Domain Software Overview Logical Domains (LDoms) software enables you to allocate the system resources of your server (such as a boot environment, CPUs, memory, and I/O devices) into logical domains.
Logical Domain Configurations The Logical Domain configurations are stored on the service processor (SP). Using Logical Domains Manager CLI commands, you can add a configuration, specify a configuration to be used, and list the configurations on the service processor. You can also use the ILOM set /HOST/bootmode config=configfile command to specify an LDoms boot configuration. For further information about /HOST/bootmode, see your server’s ILOM supplement.
Operating the Solaris OS With Logical Domains This section describes the changes in behavior in using the Solaris OS that occur once a configuration created by the Logical Domains Manager is instantiated; that is, after domaining is enabled. Note – Any discussion about whether domaining is enabled pertains only to UltraSPARC T1–based platforms. Otherwise, domaining is always enabled.
▼ Save Your Current Logical Domain Configurations to the SC ● Use the following command. # ldm add-config config-name Result of an OpenBoot power-off Command The OpenBoot power-off command does not power down a system. To power down a system while in OpenBoot firmware, use your system controller’s or system processor’s poweroff command.
Note – The question in TABLE: Expected Behavior of Halting or Rebooting the Control (primary) Domain on page 42 regarding whether domaining is enabled pertains only to the UltraSPARC T1 processors. Otherwise, domaining is always enabled. TABLE: Expected Behavior of Halting or Rebooting the Control (primary) Domain Command Domaining Enabled? Other Domain Configured? halt Disabled N/A For UltraSPARC T1 Processors: Drops to the ok prompt. Enabled No For UltraSPARC T1 Processors: See message in 02.
Additional Documentation For more information on LDoms software, see the following documents: 1. The Logical Domains (LDoms) 1.0 Documentation (http://www.sun.com/products-n-solutions/hardware/docs/Softwar e/enterprise_computing/systems_management/ldoms/ldoms1_0/index .html) 2. The Beginners Guide to LDoms: Understanding and Deploying Logical Domains (http://www.sun.com/blueprints/0207/820-0832.
44 SPARC Enterprise T5440 Server Administration Guide • July 2009
ALOM-to-ILOM Command Reference ILOM and ALOM CMT Command Comparison The following table provides a command-by-command comparison between the command sets of ALOM CMT and the default ILOM CLI command set. Only the supported ALOM CMT command options are listed in the tables. Where there are ALOM CMT command-line arguments that have no corresponding ILOM properties, those ALOM CMT arguments have been omitted.
Note – By default, when displaying information ALOM CMT commands limit their output to a terse format, offering more verbose output if a –v flag is supplied with the command. ILOM’s show commands do not have a terse output format. They always provide verbose output. ALOM CMT Shell Configuration Commands TABLE: ALOM CMT Command Summary Comparable ILOM Command password Changes the login password of the current user.
TABLE: ALOM CMT Shell Configuration Commands (Continued) ALOM CMT Command Summary showusers show /SP/sessions Displays a list of users currently logged in to ALOM CMT. The display for this command has a similar format to that of the UNIX command who. The –g option pauses the display after the number of lines you specify for No equivalent in ILOM lines. showusers –g lines Comparable ILOM Command show /HOST showhost version Displays version information for host-side components.
TABLE: ALOM CMT Shell Configuration Commands (Continued) ALOM CMT Command Summary Comparable ILOM Command userdel username Deletes a user account from ALOM CMT. The –y option enables you to skip the confirmation question. delete /SP/users/username userpassword [username] Sets or changes a user password. set /SP/users/username password userperm [username] [c] [u] [a] [r] Sets the permission level for a user account.
TABLE: ALOM CMT Shell Status and Control Commands ALOM CMT Command Summary Comparable ILOM Command showenvironment Displays the environmental status of the host server. This information includes system temperatures, power supply status, front panel LED status, hard disk drive status, fan status, voltage, and current sensor status. show –o table –level all /SYS showpower [–v] Displays power metrics for the host server.
TABLE: ALOM CMT Shell Status and Control Commands (Continued) ALOM CMT Command Summary Comparable ILOM Command reset [–c] reset /SYS reset [–y][–c] Attempts to gracefully reset the system. If that fails, this option forcefully reset the system. reset –f Forcefully resets the system. reset –d Attempts to gracefully reset the control domain. If that fails, this option forcefully reset the control domain.
TABLE: ALOM CMT Shell Status and Control Commands (Continued) ALOM CMT Command Summary poweroff stop /SYS Removes the main power from the host server. The –y option enables you to skip the confirmation question. stop –script /SYS ALOM CMT attempts to shut the server down gracefully. The –f option stop –force /SYS forces an immediate shutdown. poweroff –y poweroff –f Comparable ILOM Command Applies the main power to the host server or FRU.
ALOM CMT Shell Automatic System Recovery (ASR) Commands TABLE: ALOM CMT Command Summary Comparable ILOM Command enablecomponent asr-key Removes a component from the asr-db blacklist. set /SYS/component component_state=enabled disablecomponent asr-key Adds a component to the asr-db blacklist. set /SYS/component component_state=disabled showcomponent asr-key Displays system components and their test status (ASR state).
Index hot-plug non-mirrored disk, 24 integrated mirror (IM), 13 integrated striping (IS), 13 use a RAID volume with Solaris, 18 Symbols -> prompt ways to access, 5 A ALOM CMT commands, comparison with ILOM commands, 45 Automatic System Recovery (ASR), 31 components affected, 33 disable, 32 enable, 31 D device configure, 35 identifiers, 35 unconfigure, 34 device names logical|device names physical, 21 disk slot numbers, 20 F faults bypassing, 27 clearing, 33 clearing fault messages, 34 display, 29 I ILO
power off, 8 power on, 7 R reset, 8 S setup, initial system, 1 shutdown (Solaris command), 4 Solaris commands init, 4 shutdown, 4 system console install a local graphics monitor, 6 log in, 4 output options, 5 T troubleshooting, 33 54 SPARC Enterprise T5440 Server Administration Guide • July 2009
