C H A P T E R 6

Monitoring System Components

Topics
Description | Links
--- | ---
View and configure LEDs and system indicators | View Sensor Readings Configure System Indicators
Set the clock and timezone | Configure Clock Settings
Filter, view, and clear event logs | Filter Event Log Output View and Clear the ILOM Event Log
Set remote syslog receiver IP address | Configure Remote Syslog Receiver IP Addresses
View or clear faults | View and Clear Faults Using the CLI
View the SP Console History Log | View and Manage SP Console History Log Entries Using the ILOM CLI

Related Topics
For ILOM | Chapter or Section | Guide
--- | --- | ---
Concepts | System Monitoring and Alert Management | Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide (820-6410)
Web interface | Monitoring System Sensors, Indicators, and ILOM Event Log | Oracle Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide (820-6411)
IPMI and SNMP hosts | Inventory and Component Management | Oracle Integrated Lights Out Manager (ILOM) 3.0 Management Protocols Reference Guide (820-6413)
The ILOM 3.0 Documentation Collection is available at: `http://docs.sun.com/app/docs/prod/int.lights.mgr30#hic`.

##

Monitoring System Sensors, Indicators, and ILOM Event Logs

Topics
Description | Links | Platform Feature Support
--- | --- | ---
View and configure LEDs and system indicators | View Sensor Readings Configure System Indicators | x86 system server SP SPARC system server SP CMM
Set the clock and timezone | Configure Clock Settings
Filter, view, and clear event logs | Filter Event Log Output View and Clear the ILOM Event Log Configure Remote Syslog Receiver IP Addresses
View fault status | View and Clear Faults Using the CLI | Most x86 system server SP Most SPARC system server SP CMM

### View Sensor Readings

Follow these steps to view sensor readings:

1. Log in to the ILOM SP CLI or the CMM CLI.

2. Type the following commands to navigate to the sensor target and then to view the sensor properties:

->`cd` target

->`show`

For example, on some server platforms, you can specify the following path to view a temperature reading of a server’s ambient air intake:

`->``cd /SYS/T_AMB`

`->``show`

The properties describing the sensor target appear. For example:

     type = Temperature
            class = Threshold Sensor
            value = 27.000 degree C
            upper_nonrecov_threshold = 45.00 degree C
            upper_critical_threshold = 40.00 degree C
            upper_noncritical_threshold = 35.00 degree C
            lower_noncritical_threshold = 10.00 degree C
            lower_critical_threshold = 4.00 degree C
            lower_nonrecov_threshold = 0.00 degree C
            alarm_status = cleared

For specific details about the type of threshold sensor targets you can access, as well as the paths to access them, consult the user documentation provided with the Sun server platform.

3. To view a discrete sensor reading, type the following commands:

    ->cd target
    ->show

For example, on some Sun server platforms, you can determine whether a hard disk drive is present in slot 0 by specifying the following path:

    ->cd /SYS/HDD0_PRSNT
    ->show

The properties describing the discrete sensor target appear. For example:

- `Type = Entity Presence`

- `Class = Discrete Indicator`

- `Value = Present`

For specific details about the type of discrete sensor targets you can access, as well as the paths to access them, consult the user documentation provided with the Sun server platform.

### Configure System Indicators

#### Before You Begin

- To configure system indicators, you need the User Management (`u`) role enabled.

Follow these steps to configure system indicators:

1. Log in to the ILOM SP CLI or the CMM CLI.

2. To determine whether you can change the state of a system indicator, type the following commands:

`->cd /SYS` or`cd /CH`

->`show`

Targets, properties, and commands associated with the system indicator appear.

For example:

     /SYS
        Targets:
            BIOS
            OK2RM
            SERVICE

        Properties:
            type = Host System
            chassis_name = SUN BLADE 8000 CHASSIS
            chassis_part_number = 602-3235-00
            chassis_serial_number = 00:03:BA:CD:59:6F
            chassis_manufacturer = SUN MICROSYSTEMS
            fault_state = OK
            clear_fault_action = (none)
            power_state = Off

        Commands:
            cd
            reset
            set
            show
            start
            stop

If the `set` command appears in the `Commands` list, you can modify the state of the system indicator.

3. To modify the state of the system indictor, type the following command:

    ->set property=state_name

For more information about which system indicators are supported on your system, and the paths for accessing them, consult the user documentation provided with the Sun server platform.

### Configure Clock Settings

#### Before You Begin

- To view and set clock settings, you need the Admin (`a`) role enabled.

Follow these steps to configure clock settings:

1. Log in to the ILOM SP CLI or the CMM CLI.

2. To view ILOM clock settings, type:

    ->show /SP/clock

3. To manually set the ILOM clock settings, type:

    -> set target property_name=value

For example:

    -> set /SP/clock datetime=MMDDhhmmYYYY

4. To configure the ILOM clock settings to synchronize with other systems on your network by setting an IP address of an NTP server:

a. To set the IP address of an NTP server, type the following command.

    ->set /SP/clients/ntp/server/1 address=ip_address

b. To enable NTP synchronization, type:

    ->set /SP/clock usentpserver=enabled

Consult your Sun server platform user documentation for platform-specific clock information about whether:

- The current time in ILOM persists across reboots of the SP.

- The current time in ILOM can be synchronized with the host at host boot time.

- There is a real-time clock element that stores the time.

### Filter Event Log Output

Follow these steps to filter event log output:

1. Log in to the ILOM SP CLI or the CMM CLI.

2. At the command prompt, type the following:

`-> show /SP/logs/event/list Class==(`value`) Type==(`value`) Severity==(`value`)`

### View and Clear the ILOM Event Log

#### Before You Begin

- To view or clear the event log, you need the Admin (`a`) role enabled.

Follow these steps to view and clear the ILOM event log:

1. Establish a local serial console connection or SSH connection to the server SP or CMM.

2. Type one of the following commands to set the working directory:

- For a rackmounted server SP: cd /SP/logs/event

- For a blade server SP in chassis: cd /CH/BL n/SP/logs/event

- For a CMM: cd /CMM/logs/event

3. Type the following command to display the event log list:

`->``show list`

The contents of the event log appear.

For example:

    ID     Date/Time                 Class     Type      Severity
    -----  ------------------------  --------  --------  --------
    578    Wed Jun 11 06:39:47 2008  Audit     Log       minor
           user1 : Open Session : object = /session/type : value = shell : success
    577    Wed Jun 11 06:34:53 2008  Audit     Log       minor
           user1 : Set : object = /clients/activedirectory/userdomains/3/domain : value = <USERNAME>@joe.customer.example.sun.com : success
    576    Wed Jun 11 06:25:06 2008  Audit     Log       minor
           user1 : Open Session : object = /session/type : value = www : success
    575    Wed Jun 11 06:07:29 2008  Audit     Log       minor
           user1 : Close Session : object = /session/type : value = www : success
    574    Wed Jun 11 06:02:01 2008  Audit     Log       minor
           root : Set : object = /clients/activedirectory/dnslocatorqueries/2/service : value = _ldap._tcp.pc._msdcs.<DOMAIN>.<PORT:636> : success
    573    Wed Jun 11 06:01:50 2008  Fault     Fault     critical
           Fault detected at time = Wed Jun 11 06:01:41 2008. The suspect component:/CH/PS3/EXTERNAL/AC_INPUT has fault.powersupply.no_ac with probability=100 Please consult the Sun Blade 8000 Fault Diagnosis Document (Document ID: 85878) at http://sunsolve.sun.com to determine the correct course of action.

4. In the event log, perform any of the following tasks:

- Scroll down the list to view entries - Press any key except ‘q’. The following table provides descriptions about each column appearing in the log.

Column Label | Description
--- | ---
Event ID | The number of the event, in sequence from number 1.
Class/Type | Audit/ Log - Commands that result in a configuration change. Description includes user, command, command parameters, and success/fail. IPMI/Log - Any event that is placed in the IPMI SEL is also put in the management log. Chassis/State - For changes to the inventory and general system state. Chassis/Action - Category for shutdown events for server module/chassis, hot insert/removal of a FRU component, and Reset Parameters button pushed. Fault/Fault - For Fault Management faults. Description gives the time fault was detected and suspect component. Fault/Repair - For Fault Management repairs. Description gives component.
Severity | Debug, Down, Critical, Major, or Minor
Date/Time | The day and time the event occurred. If the Network Time Protocol (NTP) server is enabled to set the ILOM time, the ILOM clock will use Universal Coordinated Time (UTC).
Description | A description of the event.

5. To dismiss the event log (stop displaying the log), press the ‘q’ key.

6. To clear entries in the event log, perform the following steps:

a. Type: set clear=true

A confirmation message appears.

b. Type one of the following:

- To clear the entries, type: y.

- To cancel clearing the log, type: n.

Note - The ILOM event log accumulates many types of events, including copies of IPMI entries. Clearing the ILOM event log will clear all entries in the log, including the IPMI entries. However, clearing the ILOM event log entries will not clear the actual entries posted directly to an IPMI log.

### Configure Remote Syslog Receiver IP Addresses

#### Before You Begin

- To configure remote syslog receiver IP addresses, you need the Admin (`a`) role enabled.

Follow these steps to configure remote syslog receiver IP addresses:

1. Establish a local serial console connection or SSH connection to the server SP or CMM.

2. Type one of the following commands to set the working directory:

- For a rackmounted server SP: cd /SP/clients/syslog

- For a blade server SP in chassis: cd /CH/BL n/SP/clients/syslog

- For a CMM: cd /CMM/clients/syslog

3. Type the `show` command to display the syslog properties.

The properties appear. For example, accessing the syslog properties for the first time on an SP would appear as follows:

    /SP/clients/syslog/1
    Targets:
    Properties:
       address = 0.0.0.0

    Commands:
       cd
       set
       show

4. Use the `set` command to identify a destination IP address for IP 1 (and, if applicable, IP 2).

For example, to set an IP destination to IP address 111.222.33.4, you would type:

`->``set destination_ip1=111.222.33.4`

5. Press Enter for the setting to take effect.

The results of setting the IP address appear. For example, if you set the destination IP address to 111.222.33.4, the following would appear:

`Set ‘destination_ip1’ to ‘111.222.33.4’`

View and Clear Faults Using the CLI

#### Before You Begin

- To clear faults in ILOM, the Admin (`a`) role must be enabled and the server SP or CMM must have ILOM firmware 3.0.3 or later installed.

Follow these steps to view and clear faults using the ILOM CLI.

1. Log in to the ILOM SP CLI or the CMM CLI.

2. To view a list of components that have been faulted, type:

- From a server:
  `->``show /SP/faultmgmt`

- From the CMM:
  `->``show /CMM/faultmgmt`

3. To display fault messages in the ILOM event log, type:

- From the server:
  `->``show /SP/logs/event/list`

- From the CMM:
  `->``show /CMM/logs/event/list`

4. Fix or replace the faulted component.

5. To clear a fault on a component, type the following command:

    ->set component_path clear_fault_action=true
    Are you sure you want to clear component_path (y/n)?  y
    Set ’clear_fault_action’ to ’true’

Where component_path is one of the following faulted components:

- Processor

- Memory

- Motherboard

- Fan Module

- Power Supply

- CMM

- NEM

- PCI card

For example, to clear a processor fault, you would type the following:

`->``set /SYS/MB/P0 clear_fault_action=true` `Are you sure you want to clear /SYS/MB/P0 (y/n)?` `y` `Set ’clear_fault_action’ to ’true’`

##

Viewing the SP Console History Log

Topics
Description | Links | Platform Feature Support
--- | --- | ---
Review the prerequisites | Before You Begin | x86 system server SP SPARC system server SP
View the SP Console History Log | View and Manage SP Console History Log Entries Using the ILOM CLI

Note - The SP Console History Log feature is not available for use from the ILOM web interface.

For instructions about how to display log entries in the SP Console History Log file, see the following procedure.

### Before You Begin

- You must have Console (`c`) role user account to display the entries stored in the SP Console History Log file.

- You must be using ILOM 3.0.8 or a later version of ILOM to view the SP Console History Log on Oracle x86 servers. Prior to ILOM 3.0.8, the SP Console History Log file was only viewable in ILOM on Oracle SPARC servers.

### View and Manage SP Console History Log Entries Using the ILOM CLI

1. Log in to the ILOM SP CLI.

2. Use the `show` command to display the SP Console target, properties, and commands.

For example:

    -> show /SP/console

     /SP/console
        Targets:
            history

        Properties:
            line_count = 0
            pause_count = 0
            start_from = end

        Commands:
            cd
            show
            start
            stop
    ->

3. Use the `help` command to view details about the SP Console target and properties.

For example:

    -> help /SP/console

     /SP/console: Redirection of console stream to SP
        Targets:
            history: console history

        Properties:
            line_count: total number of lines to display
            line_count: Possible values = 0-2048 where 0 means no limit
            line_count: User role required for set = c

            pause_count: number of lines to display before each pause
            pause_count: Possible values = 0-2048 where 0 means no limit
            pause_count: User role required for set = c

            start_from: from which end of the available history to list
            start_from: Possible values = beginning,end
            start_from: User role required for set = c

4. Use the `set` command to specify the property values that you want ILOM to use when displaying the entries in the SP Console History Log file.

For example:

- `set` command usage:

`set [target] <property>=<value> [<property>=<value>...]`

- At the prompt, you would type the SP console target and one or more display property values as follows:

-> `set /SP/console` property`=`value``

-> `set /SP/console` property`=`value`` property`=`value

-> `set /SP/console` property`=`value`` property`=`value`` property`=`value

Where property and value can be any of the following parameters specified in the following table.

Property | Values | Example
--- | --- | ---
`line_count` | Accepts a line value within the range of `0` to `2048`, where `0` means no limit. Note - The default value for `line_count` is `0`. | To specify ILOM to display four lines of the SP Console History Log, you would type: -`> set /SP/console line_count=4` ``
`pause_count` | Accepts a pause value within the range of `0` to `2048`, where `0` means not to pause the display. Note - The default value for `pause_count` is `0`. | To specify ILOM to display four lines of the SP Console History Log and pause the display after displaying two lines, you would type: -> `set /SP/console line_count=4 pause_count=2`
`start_from` | Values include: `end` - The last line (most recent) in the history log. `beginning` - The first line in the history log. Note - The default value for `start_from` is `end`. | To specify ILOM to display the first four lines of the SP Console History Log and pause the display after displaying two lines, you would type: -> `set /SP/console line_count=4 pause_count=2 start_from=beginning`

The UTC timestamps recorded in the SP Console History Log reflect the local time configured on the server.

Copyright © 2010, Oracle and/or its affiliates. All rights reserved.