Sun Blade™ T6300 Server Module Administration Guide Sun Microsystems, Inc. www.sun.com Part No. 820-0277-10 April 2007, Revision A Submit comments about this document at: http://www.sun.
Copyright 2007 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 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 http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.
Contents Preface 1.
▼ To Access the System Console Through an Alphanumeric Terminal Switching Between the ALOM System Controller and the System Console ALOM sc> Prompt 10 Access Through Multiple Controller Sessions Reaching the sc> Prompt OpenBoot ok Prompt 11 12 12 Methods to Reach the ok Prompt Graceful Shutdown 13 13 ALOM System Controller break or console Command L1-A (Stop-A) Keys or Break Key Manual System Reset Obtaining the ok Prompt 14 15 15 To Obtain the ok Prompt 16 System Console OpenBoot Configura
Automatic System Recovery User Commands 24 Enabling and Disabling Automatic System Recovery ▼ To Enable Automatic System Recovery ▼ To Disable Automatic System Recovery 25 26 Obtaining Automatic System Recovery Information ▼ To Obtain ASR Information 27 ▼ To Unconfigure a Device Manually 27 ▼ To Reconfigure a Device Manually 27 ▼ 28 To Display System Fault Information Multipathing Software 28 29 For More Information on Multipathing Software Storing FRU Information ▼ A.
vi Sun Blade T6300 Server Module Administration Guide • April 2007
Figures FIGURE 1-1 Switching Between ALOM System Controller and System Console 9 vii
viii Sun Blade T6300 Server Module Administration Guide • April 2007
Tables TABLE 1-1 Pin Crossovers for Connecting the Server to a Terminal Server 5 TABLE 1-2 Ways of Accessing the ok Prompt TABLE 1-3 OpenBoot Configuration Variables That Affect the System Console TABLE 2-1 LED Behavior and Meaning TABLE 2-2 LED Behaviors With Assigned Meanings TABLE 2-3 Virtual Keyswitch Setting for Reset Scenario TABLE 2-4 ALOM Variable Settings for Reset Scenario TABLE 2-5 Device Identifiers and Devices 16 17 20 20 24 24 27 ix
x Sun Blade T6300 Server Module Administration Guide • April 2007
Preface The Sun Blade T6300 Server Module Administration Guide is written for experienced system administrators. This guide includes general descriptive information about the Sun Blade™ T6300 server module and detailed instructions for configuring and administering the server module. To use the information in this guide, you must have working knowledge of computer network concepts and terms and advanced familiarity with the Solaris™ Operating System (Solaris OS).
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 OS documentation, which is at: http://docs.sun.
Typographic Conventions Typeface* Meaning Examples AaBbCc123 The names of commands, files, and directories; on-screen computer output Edit your.login file. Use ls -a to list all files. % You have mail. AaBbCc123 What you type, when contrasted with on-screen computer output % su Password: AaBbCc123 Book titles, new words or terms, words to be emphasized. Replace command-line variables with real names or values. Read Chapter 6 in the User’s Guide. These are called class options.
Documentation, Support, and Training Sun Function URL Documentation http://www.sun.com/documentation/ Support http://www.sun.com/support/ Training http://www.sun.com/training/ Third-Party Web Sites Sun is not responsible for the availability of third-party web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources.
CHAPTER 1 Configuring the System Console This chapter explains what the system console is, describes the different ways of configuring it on your server, and helps you understand its relation to the system controller.
What the System Console Does The system console displays status and error messages generated by firmware-based tests during system startup. After running those tests, you can enter special commands that affect the firmware and alter system behavior. After the operating system is booted, the system console displays UNIX system messages and accepts UNIX commands. You can access the system console using the ALOM console command.
These constraints provide for secure access at the installation site. Using a TIP line enables you to use windowing and operating system features on the system making the connection to your server. ■ For instructions on accessing the system console through a terminal server, see “Accessing the System Console Through a Terminal Server” on page 4.
▼ To Use the Serial Port 1. Ensure that the serial port on your connecting device is set to the following parameters: ■ ■ ■ ■ ■ 9600 baud 8 bits No parity 1 stop bit No handshaking 2. Establish an ALOM system controller session. For instructions on how to use the ALOM system controller, see the Advanced Lights Out Management (ALOM) CMT v1.3 Guide.
▼ To Access The System Console Through a Terminal Server 1. Complete the physical connection from the serial port to your terminal server. The serial port on the server is a data terminal equipment (DTE) port. The pinouts for the serial 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.
For example, for a server connected to port 10000 on a terminal server whose IP address is 192.20.30.10, you would type: % telnet 192.20.30.10 10000 Accessing the System Console Through a TIP Connection Use this procedure to access the server system console by connecting the dongle serial port to the serial port of another Sun system. ▼ To Access the System Console Through a TIP Connection 1. Connect the RJ-45 serial cable and, if required, a DB-9 or DB-25 adapter.
Modifying the /etc/remote File This procedure might be necessary if you are accessing the server module using a TIP connection from a Sun system running an older version of the Solaris OS software. You might also need to perform this procedure if the /etc/remote file on the Sun system has been altered and no longer contains an appropriate hardwire entry. Log in as superuser to the system console of a Sun system that you intend to use to establish a TIP connection to the server module.
Note – If you intend to use the Sun system’s serial port A rather than serial port B, edit this entry by replacing /dev/ttyb with /dev/ttya. If you have redirected the system console to TTYB and want to change the system console settings back to use the serial port and network management ports, see “System Console OpenBoot Configuration Variable Settings” on page 17.
Switching Between the ALOM System Controller and the System Console If the system console is directed to the virtual-console device (its default configuration), the serial port and the network management port provide access to both the system console and the ALOM system controller (see FIGURE 1-1). Network management or Serial management port console ok sc> # #.
The prompt displayed on the terminal or shell tool indicates 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 sc> prompt indicates that you are at the ALOM system controller. Note – If no text or prompt appears, it might be that no console messages were recently generated by the system.
Note – When you access the ALOM system controller for the first time and you issue an administrative command, you must create a password for the default username, admin, for subsequent access. After this initial configuration, you will be prompted to enter a user name and password every time you access the ALOM system controller.
Reaching the sc> Prompt There are several ways to obtain the sc> prompt: ■ You can log in directly to the ALOM system controller from a device connected to the serial port. See “Accessing the System Controller” on page 3. ■ You can log in directly to the ALOM system controller using a connection through the network management port. See “Activating the Network Management Port” on page 4.
■ 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 of these scenarios most often concerns you as an administrator, since there will be times when you need to reach the ok prompt. The section “Methods to Reach the ok Prompt” on page 13 lists several ways.
Gracefully shutting down the system prevents data loss, enables you to warn users beforehand, and causes minimal disruption. You can usually perform a graceful shutdown, provided the Solaris OS is running and the hardware has not experienced serious failure. ALOM System Controller break or console Command Typing break from the sc> prompt forces a running server to drop into OpenBoot firmware control.
Using these commands results in the loss of all system coherence and state information. A manual system reset could corrupt the server’s file systems, although the fsck command usually restores them. Use this method only when nothing else works. Caution – Accessing the ok prompt suspends the Solaris OS. When you access the ok prompt from a functioning server, you are suspending the Solaris OS and placing the system under firmware control.
Caution – Forcing the server to the ok prompt suspends all application and operating system software. After you issue firmware commands and run firmwarebased tests from the ok prompt, the system might not be able to resume where it left off. If at all possible, back up system data before starting this procedure. Also exit or stop all applications and warn users of the impending loss of service.
System Console OpenBoot Configuration Variable Settings Certain OpenBoot configuration variables control from where system console input is taken and to where its output is directed. The table below shows how to set these variables in order to use the serial port and network management port.
18 Sun Blade T6300 Server Module Administration Guide • April 2007
CHAPTER 2 Managing RAS Features and System Firmware This chapter describes how to manage reliability, availability, and serviceability (RAS) features and system firmware, including the Sun Advanced Lights Out Manager (ALOM) system controller, and Automatic System Recovery (ASR). In addition, this chapter describes how to unconfigure and reconfigure a device manually, and introduces multipathing software.
Interpreting System LEDs The behavior of LEDs on your server conforms to the American National Standards Institute (ANSI) Status Indicator Standard (SIS). These standard LED behaviors are described in TABLE 2-1. TABLE 2-1 LED Behavior and Meaning LED Behavior Meaning Off The condition represented by the color is not true. Steady on The condition represented by the color is true. Standby blink The system is functioning at a minimal level and ready to resume full function.
TABLE 2-2 Color LED Behaviors With Assigned Meanings (Continued) Behavior Definition Description Standby blink Repeating sequence consisting of a brief (0.1 sec.) on flash followed by a long off period (2.9 sec.) The system is running at a minimum level and is ready to be quickly revived to full function (for example, the System Activity LED). Steady on Steady state Status normal. System or component functioning with no service actions required.
▼ To Display the State of the Locator LED From the ALOM System Controller Command Prompt ● Type: sc> showlocator Locator LED is on. Note – You do not need user permissions to use the setlocator and showlocator commands. Automatic System Recovery Automatic System Recovery functionality enables the system to resume operation after experiencing certain nonfatal hardware faults or failures. When ASR is enabled, the system’s firmware diagnostics automatically detect failed hardware components.
▼ To Enable an Automatic Degraded Boot ● Set the switches by typing: ok setenv auto-boot? true ok setenv auto-boot-on-error? true Note – The default setting for auto-boot-on-error? is false. The system will not attempt a degraded boot unless you change this setting to true. In addition, the system will not attempt a degraded boot in response to any fatal nonrecoverable error, even if degraded booting is enabled. For examples of fatal nonrecoverable errors, see “Error Handling Summary” on page 23.
■ If a fatal error is detected by POST or OpenBoot Diagnostics, the system does not boot regardless of the settings of auto-boot? or auto-boot-on-error?.
■ ■ ■ “Unconfiguring and Reconfiguring Devices” on page 27 “To Reconfigure a Device Manually” on page 27 “Obtaining Automatic System Recovery Information” on page 26 Enabling and Disabling Automatic System Recovery The ASR feature is not activated until you enable it. Enabling ASR requires changing configuration variables in ALOM as well as OpenBoot firmware. ▼ To Enable Automatic System Recovery 1.
▼ To Disable Automatic System Recovery 1. At the ok prompt, type: ok setenv auto-boot-on-error? false 2. To cause the parameter changes to take effect, type: ok reset-all The system permanently stores the parameter change. Note – To store parameter changes, you can also power cycle the system using the front panel Power button. After you disable the ASR feature, it is not activated again until you re-enable it.
Unconfiguring and Reconfiguring Devices To support a degraded boot capability, the ALOM firmware provides the disablecomponent command, which enables you to unconfigure system devices manually. This command flags the specified device as disabled by creating an entry in the ASR database. ▼ To Unconfigure a Device Manually ● At the sc> prompt, type: sc> disablecomponent asr-key The asr-key is one of the device identifiers from TABLE 2-5 Note – The device identifiers are not case-sensitive.
Note – The device identifiers are not case-sensitive. You can type them as uppercase or lowercase characters. You can use the ALOM enablecomponent command to reconfigure any device that you previously unconfigured with the disablecomponent command. Displaying System Fault Information ALOM software enables you to display current valid system faults. The showfaults command displays the fault ID, the faulted FRU device, and the fault message to standard output.
Adding the –v option displays additional information, sc> showfaults -v ID Time FRU 0 MAY 20 10:47:32 FT0.F2 Fault SYS_FAN at FT0.F2 has FAILED. For more information about the showfaults command, refer to the Advanced Lights Out Management (ALOM) CMT v1.3 Guide. Multipathing Software Multipathing software enables you to define and control redundant physical paths to I/O devices, such as storage devices and network interfaces.
For information about VVM and its DMP feature, refer to the documentation provided with the VERITAS Volume Manager software. For information about Sun StorageTek Traffic Manager, refer to your Solaris OS documentation. Storing FRU Information The setfru command enables you to store information on FRU PROMs. For example, you might store information identifying the server in which the FRUs have been installed.
APPENDIX A OpenBoot Configuration Variables TABLE A-1 describes the OpenBoot firmware configuration variables stored in nonvolatile memory on the system. The OpenBoot configuration variables are printed here in the order in which they appear when you issue the showenv command.
TABLE A-1 OpenBoot Configuration Variables Stored on the System Processor (Continued) Variable Possible Values Default Value Description ttya-mode 9600,8,n,1,- 9600,8,n,1,- Serial management port (baud rate, bits, parity, stop, handshake). The serial management port only works at the default values. output-device virtualconsole, ttya virtualconsole Power-on output device. input-device virtualconsole, ttya virtualconsole Power-on input device.
TABLE A-1 OpenBoot Configuration Variables Stored on the System Processor (Continued) Variable Possible Values Default Value Description diag-switch? true, false false If true: • OpenBoot verbosity is set to maximum. • After a boot request, boot diag-file from diag-device. If false: • OpenBoot verbosity is set to minimum. • After a boot request, boot boot-file from boot-device. error-reset-recovery boot, sync, none boot Command to execute following a system reset generated by an error.
34 Sun Blade T6300 Server Module Administration Guide • April 2007
Index Symbols /etc/remote file, 6 modifying, 7 console (sc> command), 14 console configuration, connection alternatives explained, 10 console -f (sc> command), 11 A Advanced Lights Out Manager (ALOM) escape sequence (#.
input-device (OpenBoot configuration variable), 17 K keyboard sequences L1-A, 13, 14, 16 L L1-A keyboard sequence, 13, 14, 16 LEDs Locator (system status LED), 21 system, interpreting, 20 Locator (system status LED) controlling, 21 controlling from sc> prompt, 21, 22 M manual device reconfiguration, 27 manual device unconfiguration, 27 manual system reset, 14, 16 multiple ALOM sessions, 11 N network management port, activating, 4 O ok prompt about, 12 accessing through ALOM break command, 13 accessing
as default communication port on initial startup, 1 configuration parameters, 4 using, 3 SERIAL MGT, See serial management port setlocator (sc> command), 21 showenv (OpenBoot command), 31 shutdown (Solaris command), 13, 16 Solaris commands fsck, 15 init, 13, 16 shutdown, 13, 16 tip, 6 uadmin, 13 uname, 7 uname -r, 7 suspending the operating system software, 15 system console accessing through alphanumeric terminal, 8 accessing through terminal server, 4 accessing through TIP connection, 6 accessing via TIP
38 Sun Blade T6300 Server Module Administration Guide • April 2007