| Sun Blade X6275 Server Module Diagnostics Guide |    
|
| C H A P T E R 7 |
|
Using IPMItool to View System Information |
This chapter contains information about using the Intelligent Platform Management Interface (IPMI) to view monitoring and maintenance information for your server.
IPMI is an open-standard hardware management interface specification that defines a specific way for embedded management subsystems to communicate. IPMI information is exchanged though baseboard management controllers (BMCs), which are located on IPMI-compliant hardware components. Using low-level hardware intelligence instead of the operating system has two main benefits: first, this configuration allows for out-of-band server management, and second, the operating system is not burdened with transporting system status data.
Your ILOM Service Processor (SP) is a BMC that is IPMI v2.0 compliant. You can access IPMI functionality through the command line with the IPMItool utility either in-band or out-of-band. Additionally, you can generate an IPMI-specific trap from the web interface, or manage the server's IPMI functions from any external management solution that is IPMI v1.5 or v2.0 compliant. For more information about the IPMI v2.0 specification, go to http://www.intel.com/design/servers/ipmi/spec.htm#spec2.
IPMItool is included on the X6275 blade’s Tools and Drivers CD image. IPMItool is a simple command-line interface that is useful for managing IPMI-enabled devices. You can use this utility to perform IPMI functions with a kernel device driver or over a LAN interface. IPMItool enables you to manage system hardware components, monitor system health, and monitor and manage the system environment, independent of the operating system.
Locate IMPItool and its related documentation on your Tools and Drivers CD image, or download this tool from the following URL: http://ipmitool.sourceforge.net/
After you install the IPMItool package, you can access detailed information about command usage and syntax from the man page that is installed. From a command line, type this command:
To connect over a remote interface you must supply a user name and password. The default user with admin-level access is root with password changeme. This means you must use the -U and -P parameters to pass both user name and password on the command line, as shown in the following example:
ipmitool -I lanplus -H <IPADDR> -U root -P changeme chassis status
| Note - In the example commands shown in this appendix, the default user name, root, and default password, changeme are shown. Type the user name and password that has been set for the server. |
| Note - Enabling anonymous user using IPMItool, is not supported in ILOM 3.0. |
To enable the Anonymous/NULL user you must alter the privilege level on that account. This lets you connect without supplying a -U user option on the command line. The default password for this user is anonymous.
ipmitool -I lanplus -H <IPADDR> -U root -P changeme channel setaccess 1 1 privilege=4 ipmitool -I lanplus -H <IPADDR> -P anonymous user list
You can also change the default passwords for a particular user ID. First get a list of users and find the ID for the user you wish to change, and then supply it with a new password, as shown in the following command sequence:
ipmitool -I lanplus -H <IPADDR> -U root -P changeme user list
ID Name Callin Link Auth IPMI Msg Channel Priv Limit
2 root false false true ADMINISTRATOR
ipmitool -I lanplus -H <IPADDR> -U root -P changeme user set password 2 newpass
ipmitool -I lanplus -H <IPADDR> -U root -P newpass chassis status
where IPADDR is IP address of the server.
For more information about supported IPMI 2.0 commands and the sensor naming for this server, also refer to the Sun Integrated Lights Out Manager User’s Guide and the Integrated Lights-Out Manager Supplement for Sun Blade X6275 Server Module.
There are a number of ways to read sensor status, from a broad overview that lists all sensors, to querying individual sensors and returning detailed information on them. See the following sections:
To get a list of all sensors in these servers and their status, use the sdr list command with no arguments. This returns a large table with every sensor in the system and its status.
The four fields of the output lines, as read from left to right are:
4. Sensor status, indicating which thresholds have been exceeded.
2 |
|/SYS/SLOTID |
| 0x02 |
| ok |
3 |
|HOSTPOWER |
| 0x02 |
| ok |
4 |
|CMM/PRSNT |
| 0x02 |
| ok |
5 |
|PEM/PRSNT |
| 0x02 |
| ok |
Although the default output is a long list of sensors, it is possible to refine the output to see only specific sensors. The sdr list command can use an optional argument to limit the output to sensors of a specific type. TABLE 7-1 describes the available sensor arguments.
|
1. Use the following command, with the full argument:
ipmitool -I lanplus -H <IPADDR> -U root -P changeme sdr elist full
| Note - In the example above, the elist parameter was used rather than list. elist provides the same information as list, with the addition of the entity ID and asserted discrete states. |
You can also generate a list of all sensors for a specific Entity. Use the list output to determine which entity you are interested in seeing, then use the sdr entity command to get a list of all sensors for that entity. This command accepts an entity ID and an optional entity instance argument. If an entity instance is not specified, it displays all instances of that entity.
The entity ID is given in the fifth field of the output, as read from left to right. For example, in the output shown in the previous example, all the fans are entity 29. The fan listed (29.5) is entity 29, with instance 5:
2a |FM5/F0/TACH | 76h | ok | 29.5 | 5300 RPM
|
1. Use the following command that uses the entity 29 argument:
ipmitool -I lanplus -H <IPADDR> -U root -P changeme sdr entity 29
Other queries can include a particular type of sensor. The command in the following example returns a list of all Temperature type sensors in the SDR.
ipmitool -I lanplus -H <IPADDR> -U root -P changeme sdr type temperature
0 |
|MB/T_AMB_FRONT |
| 2Ah |
| ok |
| 7.0 |
| 26 degrees C |
0 |
|MB/T_AMB_REAR |
| 2Bh |
| ok |
| 7.1 |
| 35 degrees C |
The ILOM SP System Event Log (SEL) provides storage of all system events. You can view the SEL with IPMItool. See the following sections:
Depending on which IPMI command you use, the sensor number that is displayed for an event might appear in slightly different formats. See the following examples:
The output from certain commands might not display the sensor name along with the corresponding sensor number. To see all sensor names in your server mapped to the corresponding sensor numbers, you can use the following command:
ipmitool -H 129.144.82.21 -U root -P changeme sdr list
/SYS/SLOTID |
| 0x04 |
| ok |
HOSTPOWER |
| 0x02 |
| ok |
CMM/PRSNT |
| 0x02 |
| ok |
PEM/PRSNT |
| 0x01 |
| ok |
P0/PRSNT |
| 0x02 |
| ok |
......... |
|
|
In the sample output above, the sensor name is in the first column and the corresponding sensor number is in the second column.
For a detailed explanation of each sensor, listed by name, refer to the Integrated Lights Out Manager Supplement For Sun Blade X6275 Server Module.
There are two different IPMI commands that you can use to see different levels of detail in the SEL.
|
1. View the ILOM SP SEL with a minimal level of detail by using the sel list command:
ipmitool -I lanplus -H <IPADDR> -U root -P changeme sel list
| Note - When you use this command, an event record gives a sensor number but does not display the name of the sensor for the event. For example, in line 16 in the sample output above, the sensor number 0x30 is displayed. For information about how to map sensor names to the different sensor number formats that might be displayed, see Sensor Numbers and Sensor Names in SEL Events. |
View the ILOM SP SEL With a Detailed Event Output by Using the sel elist Command. The sel elist command cross-references event records with sensor data records to produce descriptive event output. It takes longer to execute because it must be read from both the SEL and the Static Data Repository (SDR).
Certain qualifiers are available to refine and limit the SEL output. If you want to see only the first NUM records, use the first qualifier to the command. If you want to see the last NUM records, use the last qualifier.
|
1. Use the sel list command with the last qualifier:
ipmitool -I lanplus -H <IPADDR> -U root -P changeme sel list last 3
| 06:32:00 |
| System Firmware| Progress |
| System boot| initiated |
| Asserted |
||
| 06:35:12 |
| Temperature #0x30 |
| Upper Critical going high |
|||
| 06:35:20 |
| Voltage #0x60 |
| Lower Critical going low |
|||
If you want to get more detailed information on a particular event, you can use the sel get ID command, in which you specify an SEL record ID. For example:
ipmitool -I lanplus -H <IPADDR> -U root -P changeme sel get 0x0a00
In the example above, this particular event describes that the host is currently in the process of booting.
|
ipmitool -I lanplus -H <IPADDR> -U root -P changeme sel clear
Clearing SEL. |
Please allow a few seconds to erase. |
You can view information about system hardware components. The software refers to these components as field-replaceable unit (FRU) devices.
|
On these servers, you must first have the FRU ROMs programmed. After that is done, you can see a full list of the available FRU data by using the fru print command, as shown in the following example (only two FRU devices are shown in the example, but all devices would be shown).
ipmitool -I lanplus -H <IPADDR> -U root -P changeme fru print
In these servers, the SP is responsible for the I2C commands that control the LEDs.
|
ipmitool -I lanplus -H <IPADDR> -U root -P changeme sunoem led get all
| Sun Blade X6275 Server Module Diagnostics Guide | 820-6850-11 |
|
Copyright © 2009 Sun Microsystems, Inc. All rights reserved.
To See Only the Temperature, Voltage, and Fan Sensors