|C H A P T E R 9|
Intelligent Platform Management Interface
ILOM supports the Intelligent Platform Management Interface (IPMI), which enables you to use a command-line interface to monitor and control your server platform, as well as to retrieve information about your server platform.
This chapter includes the following sections:
The Intelligent Platform Management Interface (IPMI) is an open industry-standard interface that was designed primarily for out-of-band management of server systems over a number of different types of networks. IPMI functionality includes field-replaceable unit (FRU) inventory reporting, system monitoring, logging of system events, system recovery (including local and remote system resets and power on and power off capabilities), and alerting. IPMI functions independently of the main processor and operating system.
The independent monitoring, logging, and access functions available through IPMI provide a certain amount of manageability that is built into the platform hardware. IPMI also supports systems when there is no system management software available for a particular operating system or when you elect not to install or load the system management software.
ILOM is compliant with IPMI v1.5 and v2.0.
Additional information, including detailed specifications about IPMI, is available at the following sites:
IPMI defines a specific way for embedded management subsystems to communicate. IPMI information is exchanged through Baseboard Management Controllers (BMCs), which are located on IPMI-compliant hardware components. Using low-level hardware intelligence rather than the operating system has two main benefits: first, this configuration enables out-of-band server management, and second, the operating system is not burdened with transporting system status data.
The service processors (SPs) on your server or blades are IPMI v2.0 compliant. You can acess IPMI functionality through the command line using the IPMItool utility either in-band or out-of-band. Additionally, you can generate IPMI-specific traps from the ILOM web interface, or manage the SP’s IPMI functions from any external management solution that is IPMI v1.5 or v2.0 compliant.
IPMItool is an open-source, simple command-line interface (CLI) utility for managing and configuring IPMI-enabled devices. IPMItool can manage the IPMI functions of either the local system or a remote system. You can use the IPMItool utility to perform IPMI functions with a kernel device driver or over a LAN interface. You can download IPMItool from this site:
You can do the following with IPMItool:
Detailed information about IPMItool is provided in a man page that is available from this site:
ILOM supports alerts in the form of IPMI Platform Event Trap (PET) alerts. Alerts provide advance warning of possible system failures. Alert configuration is available from the SP on your server or blade. IPMI PET alerts are supported on all Sun server platforms and modules, with the exception of the Chassis Monitoring Module (CMM).
Each Sun server platform is equipped with a number of IPMI-compliant sensors that measure voltages, temperatures, and other service-related attributes of the system. ILOM automatically polls these sensors and posts any events crossing a threshold to an ILOM event log. In addition, ILOM generates alert messages to one or more alert destinations that you specify with IP address(es). The alert destination specified must support the receipt of IPMI PET messages. If the alert destination does not support IPMI PET messages, the alert recipient will not be able to decode the alert message.
When configuring IPMI PET alerts, you must also specify an alert level, which filters alert messages so that alert recipients only recieve those messages that they are most interested in receiving. ILOM provides five alert levels, with Minor being the lowest alert offered:
For information about managing alert rule configurations, including how to modify an alert rule, disable and alert rule, and generate a test alert, see Manage Alert Rule Configurations Using the ILOM Web Interface and Manage Alert Rule Configurations Using the ILOM CLI.
For a description of ILOM CLI commands for managing alert rule configurations, see CLI Commands for Managing Alert Rule Configurations.
The following are examples of how you can use IPMItool. In the examples, 10.8.136.165 is the IP address of ILOM. The interface can be bmc, lan, or lanplus on Solaris systems; open on Linux systems; and ms on Windows systems. When you use the ipmitool command on a Windows system, you need to add the .exe extension to the ipmitool command (ipmitool.exe). The commands are common to all platforms. However, the output (sensor names, values, thresholds, and so forth) are platform specific.
$ ipmitool -H 10.8.136.165 -I lanplus -U root -P changeme sdr list /SYS/T_AMB | 24 degrees C | ok /RFM0/FAN1_SPEED | 7110 RPM | ok /RFM0/FAN2_SPEED | 5880 RPM | ok /RFM1/FAN1_SPEED | 5880 RPM | ok /RFM1/FAN2_SPEED | 6360 RPM | ok /RFM2/FAN1_SPEED | 5610 RPM | ok /RFM2/FAN2_SPEED | 6510 RPM | ok /RFM3/FAN1_SPEED | 6000 RPM | ok /RFM3/FAN2_SPEED | 7110 RPM | ok /RFM4/FAN1_SPEED | 6360 RPM | ok /RFM4/FAN2_SPEED | 5610 RPM | ok /RFM5/FAN1_SPEED | 5640 RPM | ok /RFM5/FAN2_SPEED | 6510 RPM | ok /RFM6/FAN1_SPEED | 6180 RPM | ok /RFM6/FAN2_SPEED | 6000 RPM | ok /RFM7/FAN1_SPEED | 6330 RPM | ok /RFM7/FAN2_SPEED | 6330 RPM | ok /RFM8/FAN1_SPEED | 6510 RPM | ok /RFM8/FAN2_SPEED | 5610 RPM | ok
|Note - The above output was shortened. The actual output displays 163 sensors.|
$ ipmitool -H 10.8.136.165 -v -I lanplus -U root -P changeme sensor get /SYS/T_AMB Locating sensor record... Sensor ID : /SYS/T_AMB (0x8) Entity ID : 41.0 Sensor Type (Analog) : Temperature Sensor Reading : 24 (+/- 0) degrees C Status : ok Lower Non-Recoverable : 0.000 Lower Critical : 4.000 Lower Non-Critical : 10.000 Upper Non-Critical : 35.000 Upper Critical : 40.000 Upper Non-Recoverable : 45.000 Assertions Enabled : lnc- lcr- lnr- unc+ ucr+ unr+ Deassertions Enabled : lnc- lcr- lnr- unc+ ucr+ unr+
$ ipmitool -H 10.8.136.165 -v -I lanplus -U root -P changeme chassis power on
$ ipmitool -H 10.8.136.165 -v -I lanplus -U root -P changeme chassis power off
$ ipmitool -H 10.8.136.165 -v -I lanplus -U root -P changeme chassis power cycle
$ ipmitool -H 10.8.136.165 -v -I lanplus -U root -P changeme chassis power soft
$ ipmitool -H 10.8.136.165 -v -I lanplus -U root -P changeme fru print FRU Device Description : Builtin FRU Device (ID 0) Board Product : ASSY,ANDY,4SKT_PCI-E,BLADE Board Serial : 0000000-7001 Board Part Number : 501-7738-01 Board Extra : AXX_RevE_Blade Product Manufacturer : SUN MICROSYSTEMS Product Name : ILOM FRU Device Description : /SYS (ID 4) Chassis Type : Rack Mount Chassis Chassis Part Number : 541-0251-05 Chassis Serial : 00:03:BA:CD:59:6F Board Product : ASSY,ANDY,4SKT_PCI-E,BLADE Board Serial : 0000000-7001 Board Part Number : 501-7738-01 Board Extra : AXX_RevE_Blade Product Manufacturer : SUN MICROSYSTEMS Product Name : SUN BLADE X8400 SERVER MODULE Product Part Number : 602-0000-00 Product Serial : 0000000000 Product Extra : 080020ffffffffffffff0003baf15c5a FRU Device Description : /P0 (ID 5) Product Manufacturer : ADVANCED MICRO DEVICES Product Part Number : 0F21 Product Version : 2 FRU Device Description : /P0/D0 (ID 6) Product Manufacturer : MICRON TECHNOLOGY Product Name : 1024MB DDR 400 (PC3200) ECC Product Part Number : 18VDDF12872Y-40BD3 Product Version : 0300 Product Serial : D50209DA Product Extra : 0190 Product Extra : 0400 FRU Device Description : /P0/D1 (ID 7) Product Manufacturer : MICRON TECHNOLOGY Product Name : 1024MB DDR 400 (PC3200) ECC Product Part Number : 18VDDF12872Y-40BD3 Product Version : 0300 Product Serial : D50209DE Product Extra : 0190 Product Extra : 0400
$ ipmitool -H 10.8.136.165 -I lanplus -U root -P changeme sel list 100 | Pre-Init Time-stamp | Power Unit #0x78 | State Deasserted 200 | Pre-Init Time-stamp | Power Supply #0xa2 | Predictive Failure Asserted 300 | Pre-Init Time-stamp | Power Supply #0xba | Predictive Failure Asserted 400 | Pre-Init Time-stamp | Power Supply #0xc0 | Predictive Failure Asserted 500 | Pre-Init Time-stamp | Power Supply #0xb4 | Predictive Failure Asserted 600 | 04/05/2007 | 12:03:24 | Power Supply #0xa3 | Predictive Failure Deasserted 700 | 04/05/2007 | 12:03:25 | Power Supply #0xaa | Predictive Failure Deasserted 800 | 04/05/2007 | 12:03:25 | Power Supply #0xbc | Predictive Failure Deasserted 900 | 04/05/2007 | 12:03:26 | Power Supply #0xa2 | Predictive Failure Asserted a00 | 04/05/2007 | 12:03:26 | Power Supply #0xa8 | Predictive Failure Deasserted b00 | 04/05/2007 | 12:03:26 | Power Supply #0xb6 | Predictive Failure Deasserted c00 | 04/05/2007 | 12:03:26 | Power Supply #0xbb | Predictive Failure Deasserted d00 | 04/05/2007 | 12:03:26 | Power Supply #0xc2 | Predictive Failure Deasserted e00 | 04/05/2007 | 12:03:27 | Power Supply #0xb0 | Predictive Failure Deasserted f00 | 04/05/2007 | 12:03:27 | Power Supply #0xb5 | Predictive Failure Deasserted 1000 | 04/05/2007 | 12:03:27 | Power Supply #0xba | Predictive Failure Asserted 1100 | 04/05/2007 | 12:03:27 | Power Supply #0xc0 | Predictive Failure Asserted 1200 | 04/05/2007 | 12:03:28 | Power Supply #0xa9 | Predictive Failure Deasserted 1300 | 04/05/2007 | 12:03:28 | Power Supply #0xae | Predictive Failure Deasserted 1400 | 04/05/2007 | 12:03:28 | Power Supply #0xb4 | Predictive Failure Asserted 1500 | 04/05/2007 | 12:03:28 | Power Supply #0xbe | Predictive Failure Deasserted