C H A P T E R 8 - Managing the Host Using the CLI

C H A P T E R 8

Managing the Host Using the CLI

This chapter describes how to use the ILOM's command-line interface (CLI) to manage the host. The sections include:

Section 8.1, Controlling Power to the Host Server

Section 8.2, Starting and Stopping the Host Console

Section 8.3, Viewing System Components, Indicators, and Sensors

Section 8.4, Setting the Locate LED

Section 8.5, Managing ILOM Alerts

Section 8.6, Viewing and Clearing Event Logs

8.1 Controlling Power to the Host Server

To power on the host, type:

start /SYS

To power off the host, type:

stop /SYS

To reset the host, type:

reset /SYS

Note - Entering reset /SYS does not affect the power state of the host.

To send a break to the host, type:

Escape + B (press the Escape key and type upper case B).

8.2 Starting and Stopping the Host Console

Type the start command to start a session to the server console:

start /SP/console

Type the stop command to terminate a server console session started by another user:

stop /SP/console

Note - Before connecting to the console, the ILOM must be set to its default settings (9600 baud, 8N1 [eight data bits, no parity, one stop bit], no flow control).

If the host is booting, you will see its bootup messages.

8.3 Viewing System Components, Indicators, and Sensors

On the CLI, components, indicators (LEDs), and sensors are located in /SYS.

Note - When displayed on the WebGUI, the components, indicators, and sensors are divided into separate screens. They are described in:
Section 9.2, Viewing Replaceable Component Information
Section 9.3, Viewing Sensors
Section 9.4, Viewing Indicator LEDs and Controlling the Locate LED.

The following display shows the contents of a typical /SYS.

Note - The displays in this section are examples. For exact sensor information, see your platform supplement.

-> show /SYS

 /SYS

    Targets:

        INTSW

        BIOS

SP

        REAR_SVC

        TOP_SVC

        TEMP_FAULT

        POWER

        LOCATE

        SERVICE

        V_+12V

        V_+1V2

        V_+3V3

        V_+3V3STBY

        V_+5V

FP

BP

FT0

FT1

FT2

FT3

        PROC

IO

PS0

PS1

PS2

HD

Properties

       (additional information appears here)

->

To display information about a particular sensor, indicator or component, use the show command.

In this example, /SYS/SASBP represents the disk backplane. It has the following targets:

-> show /SYS/SASBP

 /SYS/SASBP

    Targets:

ID0

ID1

        T_AMB

        HDD0

        HDD1

        HDD2

        HDD3

    Properties:

        type = Disk Backplane

    Commands:

cd

        show

->

The following display shows a device (HDD0) and a temperature sensor (T_AMB).

-> show /SYS/HD/HDD0

 /SYS/HD/HDD0

    Targets:

        STATE

        FAIL

        OK2RM

    Properties:

        type = Hard Disk FRU

        product_name = (none)

        product_manufacturer = HITACHI

        product_version = V44OA94A

        product_part_number = HDS7225SBSUN250G

        product_serial_number = VDK41DT4EG9GNK

    Commands:

cd

        show

-> show /SYS/HD/T_AMB

 /SYS/HD/T_AMB

    Targets:

    Properties:

        type = Temperature

        class = Threshold Sensor

        value = 25.000 degree C

        upper_nonrecov_threshold = 43.00 degree C

        upper_critical_threshold = 38.00 degree C

        upper_noncritical_threshold = 33.00 degree C

        lower_nonrecov_threshold = 0.00 degree C

        lower_critical_threshold = 0.00 degree C

        lower_noncritical_threshold = 0.00 degree C

    Commands:

cd

        show

->

8.4 Setting the Locate LED

The locate LED is a white LED that you can light to help you find your server in a crowded equipment room. It has two states, fast blink and Off.

To turn off the LED, type:

set /SYS/LOCATE value=Off

To turn on the LED, type:

set /SYS/LOCATE value=Fast_Blink

8.5 Managing ILOM Alerts

The system is equipped with a number of sensors that measure voltages, temperatures and other things. ILOM polls the sensors and posts an event in the event log (SEL) when they cross a threshold. Some of these readings are also used to perform actions such as adjusting fan speeds, illuminating LEDs, and powering off the chassis.

The alert management view allows you to configure the system to send alerts to IP addresses.

Caution - The ILOM tags all events or actions with LocalTime=GMT (or UDT). Browser clients show these events in LocalTime. This can cause apparent discrepancies in the event log. When an event occurs on the ILOM, the event log shows it in UDT, but a client would show it in local time.

An alert is an IPMI Platform Event Trap (PET) generated when a sensor crosses the specified threshold. For example, if you configure an alert for critical thresholds, the ILOM sends an IPMI trap to the specified destination when any sensor crosses the upper or lower critical (CT) threshold.

All alerts are IPMI PET traps, as defined in the Intelligent Platform Management Interface (IPMI) v2.0.

A special criteria, informational, is reserved for system events that are not related to sensors.

The mapping between alert levels and sensors is:

TABLE 8-1 Mapping Between Alerts and Sensors
Alert	Sensor
Warning	Upper non-critical, lower non-critical
Critical	Upper critical, lower critical
Non recoverable	Upper non-recoverable, lower non-recoverable
Informational	System events not related to sensors

8.5.1 Displaying Alerts

Type the following command to display alerts:

show /SP/alert/rules

Type the following to display information about a single alert:

show /SP/alert/rules/N

where N is 1 to 15.

8.5.2 Configuring Alerts

Use the set command to change properties and values for alerts.

8.5.2.1 Syntax

set target [propertyname=value]

8.5.2.2 Targets, Properties, and Values

The following targets, properties, and values are valid for IPMI PET alerts.

TABLE 8-2 Valid Targets, Properties, and Values for IPMI Pet Alerts
Target	Property	Value	Default
`/SP/alert/rules/1...15`	destination level	<ipaddress> disable\|information\|warning\| critical\|non-recoverable	(none) disable

The parameters are:

rule - The number of the alert rule; a number from 1 to 15.

ipaddress - The IP address to which the alert will be sent.

level - The severity level of the alert (see TABLE 8-3).

TABLE 8-3 Alert Levels
Alert Levels	Name in Sensor Readings View	Description
informational	N/A	This level traps system events that are not related to sensors, such as "The host has booted."
warning	NC	The sensor is outside of its normal range but not critical.
critical	CT	The sensor has crossed a critical threshold.
non-recoverable	NR	The sensor has reached a threshold beyond the tolerance level of the corresponding component(s).
disable	N/A	Don't send alerts at this level.

Examples

To configure an alert, type:

-> set /SP/alert/rules/1 destination=128.145.77.21 level=critical

To change an alert level to critical, type:

-> set /SP/alert/rules/1 level=critical

To turn off an alert, type:

-> set /SP/alert/rules/1 level=disable

8.5.3 Sending Test Alerts

The CLI allows you to send test alerts. It sends one alert for every rule that is configured.

1. Navigate to /SP/alert/rules

2. Type the command set testalert=true.

This sends a test alert for every rule that is not disabled.

8.6 Viewing and Clearing Event Logs

This section describes how to view and clear the system event log (SEL).

Caution - The system event log accumulates various events, including administration changes to the ILOM, software events, and warnings and alerts. It also accumulates events from the IPMI log.The ILOM tags all events or actions with LocalTime=GMT (or UDT). Browser clients show these events in LocalTime. This can cause apparent discrepancies in the event log. When an event occurs on the ILOM, the event log shows it in UDT, but a client would show it local time.

1. Navigate to /SP/logs/event.

2. From the CLI, type show list.

The event log scrolls onto your screen.

-> cd /SP/logs/event

/SP/logs/event

-> show list

  /SP/logs/event/list

    Targets:

    Properties:

    Commands:

        show

ID     Date/Time                 Class     Type      Severity

-----  ------------------------  --------  --------  --------

1522   Sun Jul 30 01:11:36 2006  Audit     Log       minor

       root : Close Session : object = /session/type : value = www : success

1521   Sun Jul 30 01:05:34 2006  Audit     Log       minor

       root : Close Session : session ID = 1307912184 : success

3. To scroll down, press any key except q.

4. To stop displaying the log, press q.

5. To clear the event log, type set clear=true.

The CLI asks you to confirm.

6. Type y.

The CLI clears the event log.

For example:

-> set clear=true

Are you sure you want to clear /SP/logs/event (y/n)? y

Set 'clear' to 'true'

->

Note - The SEL accumulates many types of events, including copies of entries that IPMI posts to the IPMI log. Clearing the SEL clears all entries, including the copies of the IPMI log entries. However, clearing the SEL does NOT clear the actual IPMI log. You must use IPMI commands to view and clear the IPMI log.

8.7 Sending Logs to Other Machines

You can send logs to other machines. After an address is configured, new messages are sent to the destination machine(s) in syslog format.

1. Navigate to /SP/clients/syslog.

2. Enter the IP address of the receiving machine:

-> cd syslog

/SP/clients/syslog

-> show

 /SP/clients/syslog

    Targets:

    Properties:

        destination_ip1 = (none)

        destination_ip2 = (none)

    Commands:

cd

set

        show

-> set destination_ip1 = nn.nn.nn.nn