SPARC® Enterprise T5140 and T5240 Servers Administration Guide Manual Code : C120-E498-01EN Part No.
Copyright 2008 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 2008 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 1.
▼ To Modify the /etc/remote File 16 Accessing the System Console Through an Alphanumeric Terminal ▼ To Access the System Console Through an Alphanumeric Terminal 18 Accessing the System Console Through a Local Graphics Monitor ▼ 22 Access Through Multiple Controller Sessions Reaching the -> Prompt OpenBoot ok Prompt 23 24 24 Reaching the ok Prompt Graceful Shutdown 25 25 ILOM set /HOST send_break_action=break, start /SP/console Commands, or Break Key Manual System Reset 28 28 System Console
OpenBoot Emergency Procedures for SPARC Enterprise T5140 and T5240 Systems 37 Stop-N Functionality ▼ 38 To Restore OpenBoot Configuration Defaults Stop-F Functionality 39 Stop-D Functionality 39 Automatic System Recovery 39 Auto-Boot Options 40 Error Handling Summary Reset Scenarios 40 41 Automatic System Recovery User Commands 42 Enabling and Disabling Automatic System Recovery ▼ To Enable Automatic System Recovery ▼ To Disable Automatic System Recovery 43 44 ▼ To Unconfigure a Devic
Disk Volumes 49 RAID Technology 50 Integrated Stripe Volumes (RAID 0) Integrated Mirror Volumes (RAID 1) Hardware Raid Operations 50 51 52 Physical Disk Slot Numbers, Physical Device Names, and Logical Device Names for Non-RAID Disks 53 4.
Figures FIGURE 1-1 Directing the System Console Input and Output 4 FIGURE 1-2 Rear I/O Panel of the SPARC Enterprise T5140 Chassis.
x SPARC Enterprise T5140 and T5240 Servers Administration Guide • February 2008
Tables TABLE 1-1 Ways of Communicating With the System 2 TABLE 1-2 Pin Crossovers for Connecting to a Typical Terminal Server TABLE 1-3 Ways of Accessing the ok Prompt TABLE 1-4 OpenBoot Configuration Variables That Affect the System Console TABLE 2-1 Standard LED Behaviors and Values TABLE 2-2 System LED Behaviors with Assigned Meanings TABLE 2-3 ILOM Property Settings for Reset Scenario TABLE 2-4 Virtual Keyswitch Setting for Reset Scenario TABLE 2-5 Device Identifiers and Devices TABL
xii SPARC Enterprise T5140 and T5240 Servers Administration Guide • February 2008
Preface This manual is for experienced system administrators. This manual includes general descriptive information about the SPARC EnterpriseTM T5140 and T5240 servers, and detailed instructions for configuring and administering the servers. 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: ■ Chapter 1 describes the system console and how to access it. ■ Chapter 2 describes the tools used to configure system firmware, including system controller environmental monitoring, Automatic System Recovery (ASR), and multipathing software. In addition, the chapter describes how to unconfigure and reconfigure adevice manually.
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.
Using UNIX Commands This document might not contain information about 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 This manual uses the following fonts and symbols to express specific types of information.
Prompt Notations The following prompt notations are used in this manual.
Fujitsu Welcomes Your Comments We would appreciate your comments and suggestions to improve this document. You can submit your comments by using "Reader's Comment Form.
Reader's Comment Form Preface xix
FOLD AND TAPE NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO 741 SUNNYVALE CA POSTAGE WILL BE PAID BY ADDRESSEE FUJITSU COMPUTER SYSTEMS AT TENTION ENGINEERING OPS M/S 249 1250 EAST ARQUES AVENUE P O BOX 3470 SUNNYVALE CA 94088-3470 FOLD AND TAPE xx SPARC Enterprise T5140 and T5240 Servers Administration Guide • February 2008
CHAPTER 1 Configuring the System Console This chapter explains what the system console is, describes the different ways of configuring it on a SPARC Enterprise T5140 or T5240 server, and helps you understand the relationship between the system console and the service processor.
The serial management port (SER MGT) is the default port for accessing the system console upon initial system installation. After installation, you can configure the system console to accept input from and send output to different devices. TABLE 1-1 lists these devices and where they are discussed in this document.
What the System Console Does The system console displays status and error messages generated by firmware-based tests during system startup. After those tests run, you can enter special commands that affect the firmware and alter system behavior. For more information about tests that run during the boot process, refer to the service manual for your server. Once the operating system is booted, the system console displays UNIX system messages and accepts UNIX commands.
You must also ensure that the system console is directed to the appropriate port on the server’s back panel, generally, the one to which your hardware console device is attached (see FIGURE 1-1). You do this by setting the input-device and outputdevice OpenBoot configuration variables.
Typically, you connect one of the following hardware devices to the serial management port: ■ Terminal server ■ Alphanumeric terminal or similar device ■ Tip line connected to another computer These devices provide for secure access at the installation site.
FIGURE 1-2 Rear I/O Panel of the SPARC Enterprise T5140 Chassis. Figure Legend Management Ports, ttya port, and Locator LED on the SPARC Enterprise T5140.
The serial management port is not a general-purpose serial port. If you want to use a general-purpose serial port with your server (to connect a serial printer, for instance) use the standard 9-pin serial port on the back panel of the SPARC Enterprise T5140 and T5240. The Solaris OS sees this port as ttya. ■ For instructions on accessing the system console through a terminal server, see “Accessing the System Console Through a Terminal Server” on page 11.
Accessing the System Console Through a Graphics Monitor The SPARC Enterprise T5140 or T5240 server is shipped without a mouse, keyboard, monitor, or frame buffer for the display of bitmapped graphics. To install a graphics monitor on the server, you must install a graphics accelerator card into a PCI slot, and attach a monitor, mouse, and keyboard to the appropriate front or rear USB ports. After starting the system, you might need to install the correct software driver for the PCI card you have installed.
■ No parity ■ 1 stop bit ■ No handshaking 2. Establish an ILOM service processor session. See the ILOM user’s guide for instructions. 3. To connect to the system console, at the ILOM command prompt, type: -> start /SP/console The start /SP/console command switches you to the system console. 4. To switch back to the -> prompt, type the #. (Pound-Period) escape sequence. ok #. Characters are not echoed to the screen.
Note – The network management port is a 10/100BASE-T port. The IP address assigned to the network management port is a unique IP address, separate from the main server IP address, and is dedicated for use only with the ILOM service processor. ▼ To Activate the Network Management Port 1. Connect an Ethernet cable to the network management port. 2. Log in to the ILOM service processor through the serial management port. See the ILOM user’s guide for instructions. 3.
■ If you have configured your server to use static IP addresses, but want to reset your network to use Dynamic Host Configuration Protocol (DHCP), type the following commands: -> set /SP/network pendingipdiscovery=dhcp Set ’pendingipdiscovery’ to ’dhcp’ -> set /SP/network commitpending=true Set ’commitpending’ to ’true’ -> 4.
▼ To Access The System Console Through a Terminal Server 1. Complete the physical connection from the serial management port to your terminal server. The serial management port on the SPARC Enterprise T5140 or T5240 server is a data terminal equipment (DTE) port. The pinouts for the serial management port correspond with the pinouts for the RJ-45 ports on the serial interface breakout cable supplied by Cisco for use with the Cisco AS2511-RJ terminal server.
FIGURE 1-4 Patch Panel Connection Between a Terminal Server and a SPARC Enterprise T5140 or T5240 Server If the pinouts for the serial management port do not correspond with the pinouts for the RJ-45 ports on the terminal server, you must make a crossover cable that connects each pin on the SPARC Enterprise T5140 or T5240 server serial management port to the corresponding pin in the terminal server’s serial port. TABLE 1-2 shows the crossovers that the cable must perform.
2. Open a terminal session on the connecting device, and type: % ssh IP-address-of-terminal-server port-number For example, for a SPARC Enterprise T5140 or T5240 server connected to port 10000 on a terminal server whose IP address is 192.20.30.10, you would type: % ssh 192.20.30.
FIGURE 1-5 Tip Connection Between a SPARC Enterprise T5140 or T5240 Server and Another System ▼ To Access the System Console Through the Tip Connection 1. Connect the RJ-45 serial cable and, if required, the DB9 or DB25 adapter provided. The cable and adapter connect between another system’s serial port (typically ttyb) and the serial management port on the back panel of the SPARC Enterprise T5140 or T5240 server. 2. Ensure that the /etc/remote file on the other system contains an entry for hardwire.
3. In a shell tool window on the other system, type: % tip hardwire The system responds by displaying: connected The shell tool is now a Tip window directed to the SPARC Enterprise T5140 or T5240 server through the system’s serial port. This connection is established and maintained even when the server is completely powered off or just starting up. Note – Use a shell tool or a terminal window (such as dtterm), not a command tool. Some Tip commands might not work properly in a command tool window.
■ If the number displayed by the uname -r command is 5.0 or higher: The Solaris OS software shipped with an appropriate entry for hardwire in the /etc/remote file. If you have reason to suspect that this file was altered and the hardwire entry modified or deleted, check the entry against the following example, and edit it as needed.
▼ To Access the System Console Through an Alphanumeric Terminal 1. Attach one end of the serial cable to the alphanumeric terminal’s serial port. Use a null modem serial cable or an RJ-45 serial cable and null modem adapter. Connect this cable to the terminal’s serial port connector. 2. Attach the opposite end of the serial cable to the serial management port on the SPARC Enterprise T5140 or T5240 server. 3. Connect the alphanumeric terminal’s power cord to an AC outlet. 4.
■ Supported USB mouse ▼ To Access the System Console Through a Local Graphics Monitor 1. Install the graphics card into an appropriate PCI slot. Installation must be performed by a qualified service provider. For further information, refer to the service manual for your server or contact your qualified service provider. 2. Attach the monitor’s video cable to the graphics card’s video port. Tighten the thumbscrews to secure the connection. 3. Connect the monitor’s power cord to an AC outlet. 4.
You can now issue system commands and view system messages using your local graphics monitor. Continue with your installation or diagnostic procedure, as needed. If you want to redirect the system console back to the serial management and network management ports, see “System Console OpenBoot Configuration Variable Settings” on page 29.
FIGURE 1-6 Separate System Console and Service Processor Channels Network management or Serial management port start/SP/console ok -> # #. System console prompt Service processor prompt If the system console is configured to be accessible from the serial management and network management ports, when you connect through one of these ports you can access either the ILOM command-line interface or the system console.
The prompt displayed on the terminal or shell tool tells you which channel you are accessing: ■ The # or % prompt indicates that you are at the system console and that the Solaris OS is running. ■ The ok prompt indicates that you are at the system console and that the server is running under OpenBoot firmware control. ■ The -> prompt indicates that you are at the service processor. Note – If no text or prompt appears, it might be because no console messages were recently generated by the system.
Note – To view ILOM service processor boot messages, you must establish a connection using a serial device (such as an alphanumeric terminal) to the serial management port before connecting AC power cords to the SPARC Enterprise T5140 or T5240 server. You can log in to the ILOM service processor at any time, regardless of system power state, as long as AC power is connected to the system and you have a way of interacting with the system.
Reaching the -> Prompt There are several ways to get to the -> prompt: ■ If the system console is directed to the serial management and network management ports, you can type the ILOM escape sequence (#.). ■ You can log in directly to the service processor from a device connected to the serial management port. See “Accessing the Service Processor” on page 8. ■ You can log in directly to the service processor using a connection through the network management port.
■ When a serious hardware problem develops while the system is running, the operating system transitions smoothly to run level 0. ■ When you deliberately place the system under firmware control in order to execute firmware-based commands. The last scenario most often concerns you as an administrator, since there will be times when you need to reach the ok prompt. Several ways to do this are outlined in “Reaching the ok Prompt” on page 25.
You can also use the system Power button to initiate a graceful system shutdown. ILOM set /HOST send_break_action=break, start /SP/console Commands, or Break Key When it is impossible or impractical to shut down the system gracefully, you can get to the ok prompt, if you have an alphanumeric terminal attached to the SPARC Enterprise T5140 or T5240 server, by pressing the Break key. 1. Type set /HOST send_break_action=break to force a running SPARC Enterprise T5140 or T5240 server to drop to a menu.
Note – These methods of reaching the ok prompt will only work if the system console has been left in the default setting of virtual-console. For details, see “System Console OpenBoot Configuration Variable Settings” on page 29. Manual System Reset Caution – Forcing a manual system reset results in loss of system state data, and should be attempted only as a last resort.
▼ To Obtain the ok Prompt 1. Decide which method you need to use to reach the ok prompt. See “OpenBoot ok Prompt” on page 24 for details. 2. Follow the appropriate instructions in TABLE 1-3. TABLE 1-3 Ways of Accessing the ok Prompt Access Method What to Do Graceful shutdown of the Solaris OS From a shell or command tool window, issue an appropriate command (for example, the shutdown or init 0 command) as described in Solaris system administration documentation.
System Console OpenBoot Configuration Variable Settings On the SPARC Enterprise T5140 and T5240 servers, the system console is directed to the serial management and network management ports (SER MGT and NET MGT) by default. However, you can redirect the system console to a local graphics monitor, keyboard, and mouse. You can also redirect the system console back to the serial management and network management ports.
30 SPARC Enterprise T5140 and T5240 Servers Administration Guide • February 2008
CHAPTER 2 Managing RAS Features and System Firmware This chapter describes how to manage reliability, availability, and serviceability (RAS) features and system firmware, including ILOM on the service processor, and automatic system recovery (ASR). In addition, this chapter describes how to unconfigure and reconfigure a device manually, and introduces multipathing software.
All environmental monitoring and control is handled by ILOM on the ILOM service processor. The ILOM service processor command prompt (->) provides you with a way of interacting with ILOM. For more information about the -> prompt, see “ILOM -> Prompt” on page 22. Logging In To ILOM After you log in to your ILOM account, the ILOM service processor command prompt (->) appears, and you can enter ILOM service processor commands.
▼ To Log In To ILOM 1. At the ILOM login prompt, enter the login name and press Return. The default login name is root. Integrated Lights Out Manager 2.0 Please login: root 2. At the password prompt, enter the password and press Return to get to the -> prompt. Please Enter password: -> Note – The default user is root and the password is changeme. For more information, refer to the installation guide, the ILOM user’s guide, and the ILOM supplement for your server.
Interpreting System LEDs The behavior of LEDs on the SPARC Enterprise T5140 and T5240 servers conform to the American National Standards Institute (ANSI) Status Indicator Standard (SIS). These standard LED behaviors are described in TABLE 2-1. TABLE 2-1 Standard LED Behaviors and Values LED Behavior Meaning Off The condition represented by the color is not true. Steady on The condition represented by the color is true.
TABLE 2-2 Color Green System LED Behaviors with Assigned Meanings (Continued) Behavior Definition Description Steady On Steady state The amber indicator stays on until the service action is completed and the system returns to normal function. Off Steady state Standby blink Repeating The system is running at a minimum level and is sequence ready to be quickly revived to full function. consisting of a Example: the System Activity LED. brief (0.1 sec.) on flash followed by a long off period (2.
FIGURE 2-1 Locator Button (Top Button) on SPARC Enterprise T5140 Chassis FIGURE 2-2 Locator Button (Top Button) on SPARC Enterprise T5240 Chassis 36 SPARC Enterprise T5140 and T5240 Servers Administration Guide • February 2008
▼ To Control the Locator LED ● To turn on the Locator LED, from the ILOM service processor command prompt, type: -> set /SYS/LOCATE value=Fast_Blink ● To turn off the Locator LED, from the ILOM service processor command prompt, type: -> set /SYS/LOCATE value=off ● To display the state of the Locator LED, from the ILOM service processor command prompt, type: -> show /SYS/LOCATE Note – You do not need Administrator permissions to use the set /SYS/LOCATE and show /SYS/LOCATE commands OpenBoot Emergency
Stop-N Functionality Stop-N functionality is not available. However, you can closely emulate the Stop-N functionality by completing the following steps, provided the system console is configured to be accessible using either the serial management port or the network management port. ▼ To Restore OpenBoot Configuration Defaults 1. Log in to the ILOM service processor. 2.
4. To view console output as the system boots with default OpenBoot configuration variables, switch to console mode. -> start -script /SP/console Serial console started. To stop, type #. Stop-F Functionality The Stop-F functionality is not available on systems with USB keyboards. Stop-D Functionality The Stop-D (Diags) key sequence is not supported on systems with USB keyboards.
Auto-Boot Options The system firmware stores a configuration variable called auto-boot?, which controls whether the firmware will automatically boot the operating system after each reset. The default setting for SPARC Enterprise platforms is true. Normally, if a system fails power-on diagnostics, auto-boot? is ignored and the system does not boot unless an operator boots the system manually. An automatic boot is generally not acceptable for booting a system in a degraded state.
■ Memory failure. Given a failed DIMM, the firmware will unconfigure the entire logical bank associated with the failed module. Another nonfailing logical bank must be present in the system for the system to attempt a degraded boot. Note – If POST or OpenBoot firmware detects a nonfatal error associated with the normal boot device, the OpenBoot firmware automatically unconfigures the failed device and tries the next-in-line boot device, as specified by the boot-device configuration variable.
The virtual keyswitch can be used to run full POST diagnostics without having to modify the aforementioned properties.
▼ To Enable Automatic System Recovery 1. At the -> prompt, type: -> set /HOST/diag mode=normal -> set /HOST/diag level=max -> set /HOST/diag trigger=power-on-reset error-reset 2. At the ok prompt, type: ok setenv auto-boot? true ok setenv auto-boot-on-error? true Note – For more information about OpenBoot configuration variables, refer to the service manual for your server. 3.
Obtaining Automatic System Recovery Information ▼ To Retrieve Information About the Status of System Components Affected by ASR. ● At the -> prompt, type: -> show /SYS/component component_state In the show /SYS/component component_state command output, any devices marked disabled have been manually unconfigured using the system firmware. The command output also shows devices that have failed firmware diagnostics and have been automatically unconfigured by the system firmware.
▼ To Unconfigure a Device Manually ● At the -> prompt, type: -> set Device_Identifier component_state=disabled where the Device_Identifier is one of the device identifiers from TABLE 2-5 Note – The device identifiers are case sensitive.
You can use the ILOM set Device_Identifier component_state=enabled command to reconfigure any device that you previously unconfigured with the set Device_Identifier component_state=disabled command. Displaying System Fault Information ILOM software enables you to display current valid system faults. ▼ To Display Current Valid System Faults ● Type: -> show /SP/faultmgmt This command displays the fault ID, the faulted FRU device, and the fault message to standard output.
▼ To Clear a Fault ● Type: -> set /SYS/component clear_fault_action=true Setting clear_fault_action to true clears the fault at the component and all levels below it in the /SYS tree. Storing FRU Information ▼ To Store Information in Available FRU PROMs ● At the -> prompt type: -> set /SP customer_frudata=”data” Multipathing Software Multipathing software enables you to define and control redundant physical paths to I/O devices such as storage devices and network interfaces.
■ Sun StorageTek Traffic Manager is an architecture fully integrated within the Solaris OS (beginning with the Solaris 8 release) that enables I/O devices to be accessed through multiple host controller interfaces from a single instance of the I/O device. For More Information For instructions on how to configure and administer Solaris IP Network Multipathing, consult the IP Network Multipathing Administration Guide provided with your specific Solaris release.
CHAPTER 3 Managing Disk Volumes This chapter describes redundant array of independent disks (RAID) concepts, and how to configure and manage RAID disk volumes using the SPARC Enterprise T5140 or T5240 server’s on-board serial attached SCSI (SAS) disk controller.
Once you create a volume, the operating system uses and maintains the volume as if it were a single disk. By providing this logical volume management layer, the software overcomes the restrictions imposed by physical disk devices. The on-board disk controller of the SPARC Enterprise T5140 or T5240 server provides for the creation of as many as two hardware RAID volumes.
Integrated stripe volumes provide for a logical unit (LUN) that is equal in capacity to the sum of all its member disks. For example, a three-disk IS volume configured on 72-gigabyte drives will have a capacity of 216 gigabytes. FIGURE 3-1 Graphical Representation of Disk Striping Caution – There is no data redundancy in an IS volume configuration. Thus, if a single disk fails, the entire volume fails, and all data is lost. If an IS volume is manually deleted, all data on the volume is lost.
FIGURE 3-2 Graphical Representation of Disk Mirroring Whenever the operating system needs to write to a mirrored volume, both disks are updated. The disks are maintained at all times with exactly the same information. When the operating system needs to read from the mirrored volume, it reads from whichever disk is more readily accessible at the moment, which can result in enhanced performance for read operations.
Physical Disk Slot Numbers, Physical Device Names, and Logical Device Names for Non-RAID Disks To perform a disk hot-plug procedure, you must know the physical or logical device name for the drive that you want to install or remove. If your system encounters a disk error, often you can find messages about failing or failed disks in the system console. This information is also logged in the /var/adm/messages files.
▼ To Create a Hardware Mirrored Volume 1. Verify which hard drive corresponds with which logical device name and physical device name, using the raidctl command: # raidctl No RAID volumes found. See “Physical Disk Slot Numbers, Physical Device Names, and Logical Device Names for Non-RAID Disks” on page 53. The preceding example indicates that no RAID volume exists.
For example, an IM with a secondary disk that has been removed from the chassis appears as: # raidctl RAID Volume RAID RAID Disk Volume Type Status Disk Status -----------------------------------------------------c0t0d0 IM DEGRADED c0t0d0 OK c0t1d0 MISSING See the raidctl(1M) man page for additional details regarding volume and disk status. Note – The logical device names might appear differently on your system, depending on the number and type of add-on disk controllers installed. 2.
3. To check the status of a RAID mirror, type the following command: # raidctl RAID Volume RAID RAID Disk Volume Type Status Disk Status -------------------------------------------------------c0t0d0 IM RESYNCING c0t0d0 OK c0t1d0 OK The preceding example indicates that the RAID mirror is still resynchronizing with the backup drive. The following example shows that the RAID mirror is synchronized and online.
This section describes the procedure required to create a hardware RAID volume containing the default boot device. Since the boot device always has a mounted file system when booted, an alternate boot medium must be employed, and the volume created in that environment. One alternate medium is a network installation image in single-user mode (refer to the Solaris 10 Installation Guide for information about configuring and using network-based installations). 1. Determine which disk is the default boot device.
▼ To Create a Hardware Striped Volume 1. Verify which hard drive corresponds with which logical device name and physical device name. See “Disk Slot Numbers, Logical Device Names, and Physical Device Names” on page 53. To verify the current RAID configuration, type: # raidctl No RAID volumes found. The preceding example indicates that no RAID volume exists. Note – The logical device names might appear differently on your system, depending on the number and type of add-on disk controllers installed. 2.
3. To check the status of a RAID striped volume, type the following command: # raidctl RAID Volume RAID RAID Disk Volume Type Status Disk Status -------------------------------------------------------c0t1d0 IS OK c0t1d0 OK c0t2d0 OK c0t3d0 OK The example shows that the RAID striped volume is online and functioning. Under RAID 0 (disk striping), there is no replication of data across drives. The data is written to the RAID volume across all member disks in a round-robin fashion.
2. Select the disk name that represents the RAID volume that you have configured. In this example, c0t2d0 is the logical name of the volume. # format Searching for disks...done 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.
3. Type the type command at the format> prompt, then select 0 (zero) to auto configure the volume. For example: format> type AVAILABLE DRIVE TYPES: 0. Auto configure 1. DEFAULT 2. SUN72G 3. SUN72G 4. other Specify disk type (enter its number)[3]: 0 c0t2d0: configured with capacity of 68.23GB selecting c0t2d0 [disk formatted] 4. Use the partition command to partition, or slice, the volume according to your desired configuration.
7. Exit the format utility. The volume can now be used in the Solaris OS. Note – The logical device names might appear differently on your system, depending on the number and type of add-on disk controllers installed. ▼ To Delete a Hardware RAID Volume 1. Verify which hard drive corresponds with which logical device name and physical device name. See “Disk Slot Numbers, Logical Device Names, and Physical Device Names” on page 53. 2.
3. To delete the volume, type the following command: # raidctl -d mirrored-volume For example: # raidctl -d c0t0d0 RAID Volume ‘c0t0d0’ deleted If the RAID volume is an IS volume, the deletion of the RAID volume is interactive, for example: # raidctl -d c0t0d0 Deleting volume c0t0d0 will destroy all data it contains, proceed (yes/no)? yes Volume ’c0t0d0’ deleted. # The deletion of an IS volume results in the loss of all data that it contains.
▼ To Perform a Mirrored Disk Hot-Plug Operation 1. Verify which hard drive corresponds with which logical device name and physical device name. See “Disk Slot Numbers, Logical Device Names, and Physical Device Names” on page 53. 2. To confirm a failed disk, type the following command: # 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 a RAID rebuild, type the following command: # raidctl For example: # raidctl RAID Volume RAID RAID Disk Volume Type Status Disk Status -------------------------------------------------------c0t1d0 IM RESYNCING c0t1d0 OK c0t2d0 OK This example indicates that RAID volume c0t1d0 is resynchronizing.
2. Type the following command: # cfgadm -al For example: # cfgadm -al Ap_Id c0 c0::dsk/c0t0d0 c0::dsk/c0t1d0 c0::dsk/c0t2d0 c0::dsk/c0t3d0 c1 c1::dsk/c1t0d0 usb0/1 usb0/2 usb1/1.1 usb1/1.2 usb1/1.3 usb1/1.
This warning is issued because these commands attempt to quiesce the (SAS) SCSI bus, but the server firmware prevents it. This warning message can be safely ignored in the SPARC Enterprise T5140 or T5240 server, but the following step avoids this warning message altogether. 3. Remove the hard drive from the device tree. Type the following command: # cfgadm -c unconfigure Ap-Id For example: # cfgadm -c unconfigure c0::dsk/c0t3d0 This example removes c0t3d0 from the device tree.
7. Configure the new hard drive. Type the following command: # cfgadm -c configure Ap-Id For example: # cfgadm -c configure c1::dsk/c0t3d0 The green Activity LED flashes as the new disk at c1t3d0 is added to the device tree. 8. Verify that the new hard drive is in the device tree. Type the following command: # cfgadm -al Ap_Id c0 c0::dsk/c0t0d0 c0::dsk/c0t1d0 c0::dsk/c0t2d0 c0::dsk/c0t3d0 c1 c1::dsk/c1t0d0 usb0/1 usb0/2 usb1/1.1 usb1/1.2 usb1/1.3 usb1/1.
CHAPTER 4 Logical Domains Software SPARC Enterprise servers support the Logical Domains (LDoms) 1.0.2 software that is used to create and manage logical domains. The software comprises LDomsenabling 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.
A logical domain is a discrete logical grouping with its own operating system, resources, and identity within a single computer system. Applications software can run in logical domains. Each logical domain can be created, destroyed, reconfigured, and rebooted independently. There are several roles that logical domains can perform as shown in the following table.
■ (Required) Solaris 10 11/06 Operating System – Refer to the Solaris 10 Collection for more information. ■ (Required) Solaris 10 11/06 OS patches: ■ 124921-02, which contains updates to the Logical Domains 1.0 drivers and utilities. Logical Domains networking will be broken without this patch. ■ 125043-01, which contains updates to the console (qcn) drivers. This patch depends on KU 118833-36, so if this is not already updated on your system, you will need to do so.
72 SPARC Enterprise T5140 and T5240 Servers Administration Guide • February 2008
APPENDIX A OpenBoot Configuration Variables TABLE A-1 describes the OpenBoot firmware configuration variables stored in nonvolatile memory on the system.
TABLE A-1 OpenBoot Configuration Variables Stored on the System Configuration Card (Continued) Variable Possible Values Default Value Description output-device virtualconsole, screen virtualconsole Power-on output device. input-device virtualconsole, keyboard virtualconsole Power-on input device. auto-boot-on-error? true, false false If true, boots automatically after system error. load-base 0-n 16384 Address.
Index Symbols B /etc/remote file, 15 modifying, 16 -> commands reset /SYS, 38 set /HOST/bootmode, 38 set /SYS/LOCATE, 37 show /SYS/LOCATE, 37 -> prompt about, 22, 31 accessing from network management port, 24 accessing from serial management port, 24 multiple sessions, 23 system console escape sequence (#.
Activity, 68 OK-to-Remove, 67 logical device names, table, 53 disk hot-plug mirrored disk, 64 nonmirrored disk, 65 disk slot number, reference, 53 disk volumes about, 49 deleting, 63 dtterm (Solaris utility), 16 Dynamic Host Configuration Protocol (DHCP) client on network management port, 11 E enabling a device, 45 environmental information, viewing, 33 error handling, summary, 40 escape sequence (#.
O R ok prompt about, 24 accessing with Break key, 26 accessing with graceful system shutdown, 25 accessing with ILOM set /HOST break_action=break command, 26 accessing with ILOM set /HOST send_break_action=break command, 25 accessing with manual system reset, 25, 27 risks in using, 27 suspension of Solaris operating system, 27 ways to access, 25 OK-to-Remove (disk drive LED), 67 OpenBoot commands go, 27 probe-ide, 26 probe-scsi-all, 26 reset-all, 19 setenv, 19 OpenBoot configuration variables auto-boot, 2
system console -> prompt, switching between, 20 accessing with alphanumeric terminal, 17 accessing with graphics monitor, 18 accessing with terminal server, 2, 11 accessing with tip connection, 14 alphanumeric terminal connection, 2, 17 alternate configurations, 7 configuring local graphics monitor to access, 18 connection using graphics monitor, 8 default configuration explained, 2, 5 default connections, 4 defined, 1 Ethernet attachment through network management port, 2 graphics monitor connection, 2, 8
