|C H A P T E R 1|
Advanced Lights Out Manager (ALOM) CMT Introduction
This chapter provides an overview of the Advanced Lights Out Manager (ALOM) for your server. This version of ALOM is designed to support systems with chip multithreading (CMT). The following topics are discussed:
Subsequent chapters contain detailed instructions for configuring and using ALOM CMT.
The Advanced Lights Out Manager (ALOM) CMT enables you to remotely manage and administer your server.
The ALOM CMT software comes preinstalled on your server. Therefore ALOM CMT works as soon as you install and power on the server. You can then customize ALOM CMT to work with your particular installation. See Configuring ALOM CMT.
ALOM CMT enables you to monitor and control your server either over a network or by using a dedicated serial port for connection to a terminal or terminal server. ALOM CMT provides a command-line interface that you can use to remotely administer geographically distributed or physically inaccessible machines, see ALOM CMT Shell Commands.
In addition, ALOM CMT enables you to run diagnostics, such as power-on self-test (POST), remotely, that would otherwise require physical proximity to the server's serial port. See Using ALOM CMT to Troubleshoot Server Problems. You can also configure ALOM CMT to send email alerts of hardware failures, hardware cautions, and other events related to the server or to ALOM CMT.
The system controller's circuitry runs independently of the server, using the server's standby power. Therefore, ALOM CMT firmware and software continue to function when the server operating system goes offline or when the server is powered off.
This section shows some of the components that ALOM CMT can monitor on the server.
Whether a fan is present, fan speed, and whether the fans report OK status
The temperature measured at the CPU, and any thermal warning or failure conditions
System ambient temperature, as well as any enclosure thermal caution or failure conditions
The ALOM CMT software comes preinstalled on your host server. Therefore, ALOM CMT works as soon as you install and power on the server. You can connect an external ASCII terminal to the serial management port (SER MGT) and start using ALOM CMT right away without configuring the ALOM CMT software. For more information about connecting an external terminal, refer to the installation guide that came with your host server.
You can use the ALOM CMT software to monitor the host server in which the system controller is installed. This means that you can monitor only the host server, but not other servers on the network. Multiple users can monitor the host server, but only one user at a time has write access to the console. The other connections are read-only. Other users may issue commands that enable them to view the system console and ALOM CMT output, but they may not change any settings.
There are several ways to connect to the system controller:
1. Connect an ASCII terminal directly to the SER MGT port. See Serial Management Port.
2. Use the telnet or ssh command to connect to the system controller through the Ethernet connection attached to the network management (Ethernet) (NET MGT) port. See Network Management (Ethernet) Port.
3. Connect a port on a terminal server to the SER MGT port, and then use the ssh or telnet commands to connect to the terminal server.
When you first apply power to the server, ALOM CMT automatically begins monitoring the system and displaying output to the system console using the preconfigured default account. The default account is called admin, and has full (cuar) permissions. Refer to userperm for more information on permissions.
To log in to ALOM CMT and to specify a password for admin, perform the following step:
If you do not log in before ALOM CMT times out, ALOM CMT reverts to the system console and displays the following message:
If desired, after you log in to ALOM CMT, you can customize ALOM CMT to work with your particular installation. Refer to Configuring ALOM CMT.
You can now perform some common administrative tasks, such as adding ALOM CMT user accounts. Refer to Common Tasks.
All SPARC® Enterprise servers show two operational states that you can view and monitor using ALOM: ok and failed. Some servers have an additional operational state: faulty. This section explains the differences between the faulty state and the failed state.
A faulty state indicates that a device is operating in a degraded state, but the device is still fully operational. Due to this degradation, the device might not be as reliable as a device that does not show a fault. A device in the faulty state is still able to perform its primary function.
For example, a power supply shows a faulty state when an internal fan has failed. However, the power supply can still provide regulated power as long as its temperature does not exceed the critical threshold. In this faulty state, the power supply might not be able to function indefinitely, depending on the temperature, load, and efficiency. Therefore, it is not as reliable as a nonfaulted power supply.
A failed state indicates that a device is no longer operational as required by the system. A device fails due to some critical fault condition or combination of fault conditions. When a device enters a failed state, it ceases to function and is no longer available as a system resource.
Using the example of the power supply, the power supply is considered failed when it ceases to provide regulated power.
Before you update the ALOM CMT firmware using the flashupdate command, ensure that:
For more information, refer to the installation guide that came with your system.
Copyright © 2007, Sun Microsystems, Inc. All Rights Reserved.