| Sun Fire T2000 Server Administration Guide |    
|
| Sun Fire T2000 Server Administration Guide |
|
| C H A P T E R 2 |
|
Managing RAS Features and System Firmware |
This chapter describes how to manage reliability, availability, and serviceability (RAS) features and system firmware, including ALOM CMT on the system controller, and automatic system recovery (ASR). In addition, this chapter describes how to unconfigure and reconfigure a device manually, and introduces multipathing software.
This chapter contains the following sections:
|
Note - This chapter does not cover detailed troubleshooting and diagnostic procedures. For information about fault isolation and diagnostic procedures, refer to the service manual for your server. |
The ALOM system controller supports a total of nine concurrent sessions per server, eight connections available through the network management port and one connection through the serial management port.
After you log in to your ALOM CMT account, the ALOM system controller command prompt (sc>) appears, and you can enter ALOM system controller commands. If the command you want to use has multiple options, you can either enter the options individually or grouped together, as shown in the following example. The commands are identical.
All environmental monitoring and control is handled by ALOM CMT on the ALOM system controller. The ALOM system controller command prompt (sc>) provides you with a way of interacting with ALOM CMT. For more information about the sc> prompt, see ALOM CMT sc> Prompt.
For instructions on connecting to the ALOM system controller, see:
|
Note - This procedure assumes that the system console is directed to use the serial management and network management ports (the default configuration). |
1. If you are logged in to the system console, type #. (Pound-Period) to get to the sc> prompt.
Press the Pound key, followed by the Period key. Then press the Return key.
2. At the ALOM CMT login prompt, enter the login name and press Return.
The default login name is admin.
3. At the password prompt, enter the password and press Return twice to get to the sc> prompt.
|
Note - There is no default password. You must assign a password during initial system configuration. For more information, refer to the installation guide and ALOM CMT guide for your server. |
|
Caution - In order to provide optimum system security, best practice is to change the default system login name and password during initial setup. |
Using the ALOM system controller, you can monitor the system, turn the Locator LED on and off, or perform maintenance tasks on the ALOM system controller card itself. For more information, refer to the ALOM CMT guide for your server.
1. Log in to the ALOM system controller.
2. Use the showenvironment command to display a snapshot of the server's environmental status.
The information this command can display includes temperature, power supply status, front panel LED status, and so on.
|
Note - Some environmental information might not be available when the server is in standby mode. |
|
Note - You do not need ALOM system controller user permissions to use this command. |
The behavior of LEDs on the Sun Fire T2000 Server conform to the American National Standards Institute (ANSI) Status Indicator Standard (SIS). These standard LED behaviors are described in TABLE 2-1.
The LEDs have assigned meanings, described in TABLE 2-2.
You control the Locator LED from the sc> prompt or by the locator button on the front of the chassis.
To turn on the Locator LED, from the ALOM system controller command prompt, type:
To turn off the Locator LED, from the ALOM system controller command prompt, type:
To display the state of the Locator LED, from the ALOM system controller command prompt, type:
|
Note - You do not need user permissions to use the setlocator and showlocator commands |
The introduction of Universal Serial Bus (USB) keyboards with the newest Sun systems has made it necessary to change some of the OpenBoot emergency procedures. Specifically, the Stop-N, Stop-D, and Stop-F commands that were available on systems with non-USB keyboards are not supported on systems that use USB keyboards, such as the Sun Fire T2000 Server. If you are familiar with the earlier (non-USB) keyboard functionality, this section describes the analogous OpenBoot emergency procedures available in newer systems that use USB keyboards.
The following sections describe how to perform the functions of the Stop commands on systems that use USB keyboards, such as the Sun Fire T2000 Server server. These same functions are available through Sun Advanced Lights Out Manager (ALOM) system controller software.
Stop-A (Abort) key sequence works the same as it does on systems with standard keyboards, except that it does not work during the first few seconds after the server is reset. In addition, you can issue the ALOM system controller break command. For more information, see Reaching the ok Prompt.
Stop-N functionality is not available. However, the Stop-N functionality can be closely emulated 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.
1. Log in to the ALOM system controller.
2. Type the following command:
|
Note - If you do not issue the poweroff and poweron commands or the reset command within 10 minutes, the host server ignores the bootmode command. |
You can issue the bootmode command without arguments to display the current setting
sc> bootmode Bootmode: reset_nvram Expires WED SEP 09 09:52:01 UTC 2005 bootscript="setenv auto-boot? false" |
3. To reset the system, type the following commands:
4. To view console output as the system boots with default OpenBoot configuration variables, switch to console mode.
5. Type set-defaults to discard any customized IDPROM values and to restore the default settings for all OpenBoot configuration variables.
The Stop-F functionality is not available on systems with USB keyboards.
The Stop-D (Diags) key sequence is not supported on systems with USB keyboards. However, the Stop-D functionality can be closely emulated by setting the virtual keyswitch to diag, using the ALOM CMT setkeyswitch command. For more information, refer to the ALOM CMT guide for your server.
The system provides for automatic system recovery (ASR) from failures in memory modules or PCI cards.
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. An auto-configuring capability designed into the system firmware enables the system to unconfigure failed components and to restore system operation. As long as the system is capable of operating without the failed component, the ASR features enable the system to reboot automatically, without operator intervention.
|
Note - ASR is not activated until you enable it. See Enabling and Disabling Automatic System Recovery. |
For more information about ASR, refer to the service manual for your server.
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 Sun 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. Therefore, the Sun Fire T2000 Server OpenBoot firmware provides a second setting, auto-boot-on-error?. This setting controls whether the system will attempt a degraded boot when a subsystem failure is detected. Both the auto-boot? and auto-boot-on-error? switches must be set to true to enable an automatic degraded boot. To set the switches, type:
|
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. |
Error handling during the power-on sequence falls into one of the following three cases:
For more information about troubleshooting fatal errors, refer to the service manual for your server.
Three ALOM CMT configuration variables, diag_mode, diag_level, and diag_trigger, control whether the system runs firmware diagnostics in response to system reset events.
The standard system reset protocol bypasses POST completely unless the virtual keyswitch or ALOM CMT variables and are set as follows:
The default settings for these variables are:
Therefore, ASR is enabled by default. For instructions, see Enabling and Disabling Automatic System Recovery.
The ALOM CMT commands are available for obtaining ASR status information and for manually unconfiguring or reconfiguring system devices. For more information, see:
The automatic system recovery (ASR) feature is not activated until you enable it. Enabling ASR requires changing configuration variables in ALOM CMT as well as OpenBoot.
|
Note - For more information about OpenBoot configuration variables, refer to the service manual for your server. |
3. To cause the parameter changes to take effect, type:
The system permanently stores the parameter changes and boots automatically when the OpenBoot configuration variable auto-boot? is set to true (its default value).
|
Note - To store parameter changes, you can also power cycle the system using the front panel Power button. |
2. To cause the parameter changes to take effect, type:
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 automatic system recovery (ASR) feature, it is not activated again until you re-enable it.
Use the following procedure to retrieve information about the status of system components affected by automatic system recovery (ASR).
In the showcomponent command output, any devices marked disabled have been manually unconfigured using the system firmware. The showcomponent command also lists devices that have failed firmware diagnostics and have been automatically unconfigured by the system firmware.
To support a degraded boot capability, the ALOM CMT firmware provides the disablecomponent command, which enables you to unconfigure system devices manually. This command "marks" the specified device as disabled by creating an entry in the ASR database. Any device marked disabled, whether manually or by the system's firmware diagnostics, is removed from the system's machine description prior to the hand-off to other layers of system firmware, such as OpenBoot PROM.
|
Where the asr-key is one of the device identifiers from TABLE 2-5
|
Note - The device identifiers are not case sensitive. You can type them as uppercase or lowercase characters. |
|
where the asr-key is any device identifier from TABLE 2-5
|
Note - The device identifiers are not case sensitive. You can type them as uppercase or lowercase characters. |
You can use the ALOM CMT enablecomponent command to reconfigure any device that you previously unconfigured with the disablecomponent command.
ALOM CMT software lets you display current valid system faults. The showfaults command displays the fault ID, the faulted FRU device, and the fault message to standard output. The showfaults command also displays POST results. For example:
Adding the -v option displays the time:
For more information about the showfaults command, refer to the ALOM CMT guide for your server.
|
Multipathing software lets you define and control redundant physical paths to I/O devices, such as storage devices and network interfaces. If the active path to a device becomes unavailable, the software can automatically switch to an alternate path to maintain availability. This capability is known as automatic failover. To take advantage of multipathing capabilities, you must configure the server with redundant hardware, such as redundant network interfaces or two host bus adapters connected to the same dual-ported storage array.
For the Sun Fire T2000 Server, three different types of multipathing software are available:
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 instructions on how to configure and administer Solaris IP Network Multipathing, consult the IP Network Multipathing Administration Guide provided with your specific Solaris release.
For information about VVM and its DMP feature, refer to the documentation provided with the VERITAS Volume Manager software.
For information about Sun StorEdge Traffic Manager, refer to your Solaris OS documentation.
|
| Sun Fire T2000 Server Administration Guide | 819-2549-12 |
|
Copyright © 2007, Sun Microsystems, Inc. All Rights Reserved.
To Log In To ALOM CMT