Oracle Integrated Lights Out Manager (ILOM) 3.0 Supplement for Sun Fire X4470 Server

Oracle ILOM 3.0 operates on many platforms, supporting features that are common to all platforms. Some Oracle ILOM 3.0 features belong to a subset of platforms and not to all. This chapter describes the features that are specific to Oracle’s Sun Fire X4470 Server.

For detailed information about Oracle ILOM features that are common to all server platforms, see the Oracle Integrated Lights Out Manager (ILOM) 3.0 Documentation Collection, as described in Oracle ILOM 3.0 Common Feature Set Documentation Collection.

Oracle ILOM features discussed in this chapter, which are specific to the Sun Fire X4470 Server, are as follows:

• Supported Sun Fire X4470 Server Firmware
• Hardware Management Pack for Single Server Management
• Power Management Policies
• Oracle ILOM Sideband Management
• Switch Serial Port Output Between SP and Host Console
• Server Chassis Intrusion Sensor
• Fault Management
• Sensors and Indicators Reference Information
• SNMP and PET Message Reference Information

---

Supported Sun Fire X4470 Server Firmware

TABLE 2-1 identifies the supported Oracle ILOM and BIOS firmware versions supported on the Sun Fire X4470 Server.

For information about how to update the firmware on your server, refer to the Oracle ILOM 3.0 Common Feature Set Documentation Collection at:

http://www.oracle.com/pls/topic/lookup?ctx=E19860-01&id=homepage

---

Hardware Management Pack for Single Server Management

The Sun Server Hardware Management Pack (Hardware Management Pack) from Oracle provides tools to help you manage and configure your Oracle servers from the host operating system. To use these tools, you must install the Hardware Management Pack software on your server. After installing the Hardware Management Pack software, you will be able to perform the following server management tasks described in TABLE 2-2.

Download Hardware Management Pack Software

Navigate to the following web site to download the Hardware Management Pack software.

http://support.oracle.com

Hardware Management Pack Documentation

For instructions for installing the management pack software or using its components, see the following Hardware Management Pack documentation:

• Sun Server Hardware Management Pack 2.0 User’s Guide
• Sun Server Management Agent 2.0 User’s Guide
• Sun Server CLI Tools and IPMItool 2.0 User's Guide

For additional details about how to use the Storage Monitoring features in Oracle ILOM, see the Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide and the Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide.

For additional details about accessing and managing your server via SNMP or IPMI, see the Oracle Integrated Lights Out Manager (ILOM) 3.0 Management Protocols Reference Guide.

---

Power Management Policies

This release of Oracle ILOM 3.0 software provides new Power Management policies that are supported on the Sun Fire X4470 Server.

For more information about the latest Oracle ILOM 3.0 Power Management policies, see the Oracle Integrated Lights Out Manager (ILOM 3.0) Feature Updates and Release Notes.

This section includes the following topics:

• Host Power Throttling and Recovery
• Service Processor Power-On Policy
• Light Load Efficiency Mode
• Low Line AC Override Mode Policy
• Configure SP Power Management Policies Using the Web Interface
• Configure SP Power Management Policies Using the CLI

Host Power Throttling and Recovery

The Sun Fire X4470 Server supports a simple mechanism to automatically apply hardware throttles to the CPUs and memory controllers when power exceeds the rated capacity of the available power supplies. This can occur when a redundant power supply has failed or has been removed from the system.

When the server’s hardware (power CPLD) determines that power demand has exceeded the system’s available power, it automatically throttles the host processor to reduce its power consumption. The service processor (SP) removes this hardware throttle after it has been applied for 5 seconds. Host power throttling and recovery continues until such action is no longer needed.

Service Processor Power-On Policy

The service processor (SP) power-on policy determines the power state of the server when a cold boot is performed on the server. A server cold boot occurs only when AC power is applied to the server.

Service processor power-on policies are mutually exclusive, meaning that if one policy is enabled, the other policy is disabled by default. If both policies are disabled, then the server SP will not apply main power to the server at boot time. A brief description of the SP power-on policies and default settings follows:

• Auto Power-On Host On Boot - When this option is enabled, the SP automatically applies main power to the server. When disabled (default), main power is not applied to the server.
• Set Host Power to Last Power State On Boot - When this option is enabled, the SP automatically applies main power to the server based on the last power state of the server. The SP automatically tracks the last power state and restores the server to its last remembered power state following a power state change of at least 10 seconds. When disabled (default), the last power state is not applied to the server.

You can configure SP power-on policies using the Oracle ILOM web interface or the Oracle ILOM command-line interface (CLI). For instructions, see the following sections:

• Configure SP Power Management Policies Using the Web Interface
• Configure SP Power Management Policies Using the CLI

Light Load Efficiency Mode

Light Load Efficiency Mode (LLEM) increases system power efficiency by placing power supply unit 1 (PSU1) in warm-standby mode when the system is lightly loaded. LLEM is disabled by default on the Sun Fire X4470 Server.

When PSU1 is in warm-standby mode, PSU0 carries the entire power load. If PSU0 loses AC power or is extracted for replacement, PSU1 takes over the load automatically.

Disabling LLEM forces the PSUs to share the power load at all times, causing reduced efficiency during light power loads.

You can configure LLEM using the Oracle ILOM web interface or the Oracle ILOM command-line interface (CLI). For instructions, see the following sections:

• Configure SP Power Management Policies Using the Web Interface
• Configure SP Power Management Policies Using the CLI

Low Line AC Override Mode Policy

The Low Line AC Override Mode policy setting is provided to enable special test scenarios of a 4-CPU system using low-line (110 volt) power. Low-line voltage is normally supported only in 2-CPU system configurations. The capacity of each power supply unit (PSU) is roughly 1000 watts at low line. Since the power of a 4-CPU system can exceed 1000 watts by a large amount, enabling this setting results in a loss of PSU redundancy. This setting is disabled by default on the Sun Fire X4470 Server.

You can configure Low Line AC Override policy setting using the Oracle ILOM web interface or the Oracle ILOM command-line interface (CLI). For instructions, see the following sections:

• Configure SP Power Management Policies Using the Web Interface
• Configure SP Power Management Policies Using the CLI

1. Log in to Oracle ILOM using the web interface.

2. Select Configuration --> Policy.

The Policy Configuration page appears.

3. Depending on the SP policy you want to configure, do the following:

• To configure Auto power-on host on boot, select its radio button, then click the Actions drop-down menu and select Enable or Disable.
• To configure Set host power to last power state on boot, select its radio button, then click the Actions drop-down menu and select Enable or Disable.
• To configure Set Light Load Efficiency Mode Policy, select its radio button, then click the Actions drop-down menu and select Enable or Disable.
• To configure Set Low Line AC Override Mode Policy, select its radio button, then click the Actions drop-down menu and select Enable or Disable.

4. Click OK to enable or disable the SP policy.

1. Log in to Oracle ILOM using the CLI.

2. To show the current power policy settings, type:

-> show /SP/policy

The SP policy properties appear. For example:

 /SP/policy
    Targets:
 
    Properties:
    HOST_AUTO_POWER_ON = disabled
    HOST_LAST_POWER_STATE = disabled
    LIGHT_LOAD_EFFICIENCY_MODE = enabled
    LOW_LINE_AC_OVERRIDE_MODE = disabled
 
    Commands:
    cd
    set
    show
->

In the above output, Host Auto Power On is disabled, Host Last Power State is disabled, Light Load Efficiency Mode is enabled, and Low Line AC Override Mode is disabled.

3. Depending on the SP policy you want to configure, do the following:

• To enable or disable Host Auto Power On, type:

-> set /SP/policy/ HOST_AUTO_POWER_ON=[enabled|disabled]

• To enable or disable Host Last Power State, type:

-> set /SP/policy/ HOST_LAST_POWER_STATE=[enabled|disabled]

• To enable or disable Light Load Efficiency Mode, type:

-> set /SP/policy/ LIGHT_LOAD_EFFICIENCY_MODE=[enabled|disabled]

• To enable or disable Low Line AC Override Mode, type:

-> set /SP/policy/ LOW_LINE_AC_OVERRIDE_MODE=[enabled|disabled]

---

Oracle ILOM Sideband Management

By default, you connect to the server’s service processor (SP) using the out-of-band network management port (NET MGT). The Oracle ILOM sideband management feature enables you to select either the NET MGT port or one of the server’s Gigabit Ethernet ports (NET 0, 1, 2, 3), which are in-band ports, to send and receive Oracle ILOM commands to and from the server SP. In-band ports are also called sideband ports.

The advantage of using a sideband management port to manage the server’s SP is that one fewer cable connection and one fewer network switch port is needed. In configurations where numerous servers are being managed, such as data centers, sideband management can represent a significant savings in hardware and network utilization.

You can configure sideband management using either the web interface, the command-line interface (CLI), the BIOS, or IPMI. For special considerations and configuration instructions, see the following sections:

• Special Considerations for Sideband Management
• Configure Sideband Management Using the Web Interface
• Configure Sideband Management Using the CLI
• Configure Sideband Management Using the Host BIOS Setup Utility

Special Considerations for Sideband Management

When sideband management is enabled in Oracle ILOM, the following conditions might occur:

• Connectivity to the server SP might be lost when the SP management port configuration is changed while you are connected to the SP using a network connection, such as SSH, web, or Oracle ILOM Remote Console.
• In-chip connectivity between the SP and the host operating system might not be supported by the on-board host Gigabit Ethernet controller. If this condition occurs, use a different port or route to transmit traffic between the source and destination targets instead of using L2 bridging/switching.
• Server host power cycles might cause a brief interruption of network connectivity for server Gigabit Ethernet ports (NET 0, 1, 2, 3) that are configured for sideband management. If this condition occurs, configure the adjacent switch/bridge ports as host ports.

1. Log in to Oracle ILOM using the web interface.

2. Select Configuration --> Network.

The Network Settings page appears.

3. In the Network Settings page, do the following:

a. Configure a static IP address or select the appropriate options to acquire an IP address automatically.

b. To select a sideband management port, click the Management Port drop-down list and select the desired management port.

The drop-down list enables you to change to any one of the four Gigabit Ethernet ports, /SYS/MB/NETn, where n is 0 to 3. The SP NET MGT port, /SYS/SP/NET0, is the default.

c. Click Save for the changes to take effect.

1. Log in to Oracle ILOM using the CLI.

2. If you logged in using the serial port, you can assign a static IP address.

For instructions, see the information about assigning an IP address in the Sun Fire X4470 Server Installation Guide.

3. To show the current port settings, type:

-> show /SP/network

The network properties appear. For example:

/SP/network
    Targets:
    Properties:
        commitpending = (Cannot show property)
        dhcp_server_ip = none
        ipaddress = xx.xx.xx.xx
        ipdiscovery = static
        ipgateway = xx.xx.xx.xx
        ipnetmask = xx.xx.xx.xx
        macaddress = 11.11.11.11.11.86
        managementport = /SYS/SP/NET0
        outofbandmacaddress = 11.11.11.11.11.86
        pendingipaddress = xx.xx.xx.xx
        pendingipdiscovery = static
        pendingipgateway =  xx.xx.xx.xx
        pendingipnetmask =  xx.xx.xx.xx
        pendingmanagementport = /SYS/SP/NET0
        sidebandmacaddress = 11.11.11.11.11.87 
        state = enabled

In the above output the current active macaddress is the same as the SP’s outofbandmacaddress and the current active managementport is set to the default (/SYS/SP/NET0).

4. To set the SP management port to a sideband port, type the following commands:

-> set /SP/network pendingmanagementport=/SYS/MB/NETn

Where n equals 0, 1, 2, or 3.

-> set commitpending=true

5. To view the change, type:

-> show /SP/network

The network properties appear and show that the change has taken effect. For example:

/SP/network
    Targets:
    Properties:
        commitpending = (Cannot show property)
        dhcp_server_ip = none
        ipaddress = xx.xx.xx.xx
        ipdiscovery = static
        ipgateway = xx.xx.xx.xx
        ipnetmask = xx.xx.xx.xx
        macaddress = 11.11.11.11.11.87
        managementport = /SYS/MB/NETn
        outofbandmacaddress = 11.11.11.11.11.86
        pendingipaddress = xx.xx.xx.xx
        pendingipdiscovery = static
        pendingipgateway =  xx.xx.xx.xx
        pendingipnetmask =  xx.xx.xx.xx
        pendingmanagementport = /SYS/MB/NETn
        sidebandmacaddress = 11.11.11.11.11.87
        state = enabled

In the above output the macaddress matches the sidebandmacaddress, and the managementport matches the pendingmanagementport.

You can access the BIOS Setup Utility screens from the following interfaces:

• Use a USB keyboard, mouse, and VGA monitor connected directly to the server.
• Use a terminal (or terminal emulator connected to a computer) through the serial port on the back panel of the server.
• Connect to the server using the Oracle ILOM Remote Console. To use this interface, you must know the IP address of the server. For instructions on viewing the server IP address, see the Sun Fire X4470 Server Installation Guide.

To configure sideband management using the host BIOS Setup Utility, perform the following steps:

1. Power on or power cycle the server.

2. To enter the BIOS Setup Utility, press the F2 key while the system is performing the power-on self-test (POST).

When BIOS is started, the main BIOS Setup Utility top-level screen appears. This screen provides seven menu options across the top of the screen.

3. In the main screen, select Advanced --> IPMI 2.0 Configuration.

The IPMI 2.0 Configuration screen appears.

4. In the IPMI 2.0 Configuration screen, select the Set LAN Configuration option.

The LAN Configuration screen appears.

5. In the LAN Configuration screen, do the following:

a. Use the left and right arrow keys to select the IP Assignment option and set it to DHCP to acquire the IP address automatically, or set it to Static if manually specifying the IP address.

b. Use the left and right arrow keys to select the Active Management Port option and set the port to a sideband management port (NET0, NET1, NET2, NET3).

The NET MGT port is the default.

c. Select Commit for the change to take effect.

---

Switch Serial Port Output Between SP and Host Console

You can switch the serial port output of the Sun Fire X4470 Server between the SP console (SER MGT) and the host console (COM1). By default, the SP console is connected to the system serial port. This feature is beneficial for Windows kernel debugging, as it enables you to view non-ASCII character traffic from the host console.

You can switch serial port output using either the Oracle ILOM web interface or the Oracle ILOM command-line interface (CLI). For instructions, see the following sections:

• Switch Serial Port Output Using the Web Interface
• Switch Serial Port Output Using the CLI

Caution - You should set up the network on the SP before attempting to switch the serial port owner to the host server. If a network is not set up, and you switch the serial port owner to the host server, you will be unable to connect using the CLI or web interface to change the serial port owner back to the SP. To change the serial port owner back to the SP, you must use the Oracle ILOM Preboot Menu to restore access to the serial port over the network. For more information, see the Oracle ILOM Preboot Menu information in the Sun Fire X4470 Server Service Manual.

1. Log in to Oracle ILOM using the web interface.

2. Select Configuration --> Serial Port.

The Serial Port Settings page appears.

3. To select a serial port owner, click the Owner drop-down list and select the desired serial port owner.

The drop-down list enables you to select either Service Processor or Host Server.

By default, Service Processor is selected.

4. Click Save for your change to take effect.

1. Log in to Oracle ILOM using the CLI.

2. To set the serial port owner, type:

-> set /SP/serial/portsharing/ owner=host

By default, owner=SP.

---

Server Chassis Intrusion Sensor

The /SYS/INTSW sensor is asserted when the server’s top cover is removed while power is being applied to the server. This is an improper service action so this sensor serves to alert you to any unauthorized and inadvertent removal of the server’s cover. Thus, this sensor enables system administrators to have confidence that the physical integrity of the server has not been violated. This is particularly beneficial when the server is in a remote or uncontrolled location.

How the /SYS/INTSW Sensor Works

The /SYS/INTSW sensor is asserted when the chassis intrusion switch trips while the server is powered-on. If the AC power cords are connected to the server, power is being applied to the server. Even when you shut down the server’s host, power is still being applied to the server. The only way to remove power from the server completely is to disconnect the server’s AC power cords.

The chassis intrusion switch will trip if the server’s cover is removed, the switch itself is misaligned, or the cover is not properly seated. This sensor is deasserted when the integrity of the server’s chassis is restored, that is, when the removed cover is properly reinstalled, returning the chassis intrusion switch to its closed state.

Caution - Removing the server’s top cover while the power cord is connected to the system is not an authorized service action. Proper service action requires that host and SP shutdown operations be observed and that the power cords be disconnected from the system before the cover is opened. If proper service actions are taken, you should not see the /SYS/INTSWsensor asserted unless there are other issues, such as a misaligned chassis intrusion switch.

---

Fault Management

When a server component fails, error telemetry is either captured via the BIOS or is monitored by the Oracle ILOM SP. Oracle ILOM consumes error telemetry from both sources and provides diagnosis in the form of a fault event. The fault event is stored in the Oracle ILOM event log as a fault message. You can use either the Oracle ILOM web interface or the command-line interface (CLI) to manually clear faults.

This section includes the following topics. The first four topics describe how to examine and clear faults, while the last topic provides reference information for sensors and indicators.

• Determining Faults
• Clearing Faults
• Components With No Fault Diagnosis
• Viewing Sensors Using IPMItool

Determining Faults

When a system fault occurs, you can view system indicators and use the Oracle ILOM CLI or web interface to determine the fault:

• LEDs - The Service Required LED will always be illuminated, and the component or subsystem-specific Service LED will be illuminated when applicable.
• Oracle ILOM CLI - Examine fault messages in the Oracle ILOM event log or see a fault summary.

For example:

• To view the Oracle ILOM event log, log in to the Oracle ILOM CLI and type:
  show /SP/logs/event/list
• To view a fault summary, log in to the Oracle ILOM CLI and type:
  show /SP/faultmgmt

• Oracle ILOM web interface - Examine fault messages in the Oracle ILOM event log or see a fault summary.

For example:

• To view the Oracle ILOM event log, log in to the Oracle ILOM web interface and select:
  System Monitoring --> Event Logs
• To view a fault summary, log in to the Oracle ILOM web interface and select:
  System Information --> Fault Management

Clearing Faults

The procedure for clearing a fault differs depending on the type of component.

1. Customer-replaceable units (CRUs) that are hot-swappable and are monitored by the SP will have their faults cleared automatically when the failed component is replaced and the updated status is reported as deasserted.

2. CRUs and field-replaceable units (FRUs) that have a FRUID container with identity information will have their faults cleared automatically when the failed component is replaced, as the SP is able to determine when a component is no longer present in the system.

3. CRUs and FRUs that are not hot-swappable or lack a FRUID container with identity information will not have their faults cleared automatically.

You can use the Oracle ILOM web interface or the command-line interface (CLI) to manually clear faults. For information on how to use the Oracle ILOM web interface or the CLI to clear server faults, see the Oracle ILOM 3.0 Documentation Collection at:

http://www.oracle.com/pls/topic/lookup?ctx=E19860-01&id=homepage

The following types of faults are diagnosed by the Oracle ILOM SP:

• Environmental events - Fan modules, power supplies, ambient temperature, AC power loss, and chassis intrusion switch
• Memory Reference Code (MRC) errors and warnings - Memory initialization and population
• I/O Hub (IOH) uncorrectable error events - Motherboard
• Memory ECC uncorrectable and correctable events - Memory DIMMs
• CPU uncorrectable error events - Processor
• Boot progress events - Power-on, power-off, IPMI, MRC, QPI, BIOS, setup, and boot retries
• Service Processor error events - Oracle ILOM

TABLE 2-3 lists the server component faults that are persistent after a system cold boot and the action to clear the fault.

In addition to the above faults, the following fault does not require replacement of a faulty part; however, user action is needed to clear it:

fault.security.integrity-compromised@/sys/sp

This fault is generated when the server’s top cover is removed while the AC power cords are still connected to the power supply, that is, power is not completely removed from the server. To clear this fault, replace the server’s top cover and either reboot the server’s SP or remove the AC power cords, and then reconnect the power cords.

Components With No Fault Diagnosis

Certain Sun Fire X4470 Server components do not provide a mechanism to diagnose faults. These include:

• Disk backplane
• DVD player
• Disk drive
• Power supply backplane
• Lithium battery for host and SP real-time clocks

Viewing Sensors Using IPMItool

Sun Fire X4470 Server sensors can be viewed using IPMItool. For information and instructions for viewing sensors using IPMItool, see the Oracle Integrated Lights Out Manager (Oracle ILOM) 3.0 Management Protocols Reference Guide.

---

Sensors and Indicators Reference Information

The server includes several sensors and indicators that report on hardware conditions. Many of the sensor readings are used to adjust the fan speeds and perform other actions, such as illuminating LEDs and powering off the server.

This section describes the sensors and indicators that Oracle ILOM monitors for the Sun Fire X4470 Server.

The following types of sensors are described:

• System Components
• System Indicators
• Temperature Sensors
• Power Supply Fault Sensors
• Fan Speed, and Physical Security Sensors
• Power Supply Unit Current, Voltage, and Power Sensors
• Entity Presence Sensors

System Components

TABLE 2-4 describes the system components.

System Indicators

TABLE 2-5 describes the system indicators.

Temperature Sensors

TABLE 2-6 describes the environmental sensors.

Power Supply Fault Sensors

TABLE 2-7 describes the power supply fault sensors. In the table, n designates the numbers 0-1.

Fan Speed, and Physical Security Sensors

TABLE 2-8 describes the fan and security sensors. In the table, n designates numbers 0, 1, 2, etc.

Power Supply Unit Current, Voltage, and Power Sensors

TABLE 2-9 describes the power supply unit current, voltage, and power sensors. In the table, n designates numbers 0-1.

Entity Presence Sensors

TABLE 2-10 describes the entity presence sensors. In the table, n designates numbers
0, 1, 2, etc.

---

SNMP and PET Message Reference Information

This section describes Simple Network Management Protocol (SNMP) and Platform Event Trap (PET) messages that are generated by devices being monitored by Oracle ILOM.

• SNMP Traps
• PET Event Messages

SNMP Traps

SNMP Traps are generated by the SNMP agents that are installed on the SNMP devices being managed by Oracle ILOM. Oracle ILOM receives the SNMP Traps and converts them into SNMP event messages that appear in the event log. For more information about the SNMP event messages that might be generated on your system, see TABLE 2-11.

PET Event Messages

PET event messages are generated by systems with Alert Standard Format (ASF) or an IPMI baseboard management controller. The PET events provide advance warning of possible system failures. For more information about the PET event messages that might occur on your system, see TABLE 2-12.

Oracle Integrated Lights Out Manager (ILOM) 3.0 Supplement for Sun Fire X4470 Server

E21741-02

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