Oracle Integrated Lights Out Manager (ILOM) 2.0 Supplement for the Sun Netra T5220 Server

This chapter contains information on ILOM features on the Sun Netra T5220 server that augment the array of properties that are common to ILOM on other platforms. In particular, this chapter describes the properties in the /HOST namespace. This chapter consists of:

• Resetting the Host
• Managing Remote Control
• Viewing System Information and Setting System Policy Concerning Error Conditions
• Managing Diagnostics
• Managing System User Interactions

---

Resetting the Host

The reset command generates a graceful or forced hardware reset of the host server. By default, the reset command gracefully resets the host. If a graceful reset is not possible, a forced reset is performed. For a list of available options for the reset command in both the ILOM and ALOM compatibility CLIs, see TABLE B-2.

---

Managing Remote Control

Use the remote control properties to specify how ILOM handles boot.

• To Manage the Host’s Boot Mode Configuration Using the CLI
• To Manage the Host’s Boot Mode Script Using the CLI
• To Change the Host’s Boot Mode Behavior at Reset Using the CLI
• To Display Host’s Boot Mode Expiration Date Using the CLI
• To Change Remote Control Configuration Settings Using the Web Interface

Boot Mode

Boot mode (bootmode) properties enable you to override the default method the server uses when it boots. This ability is useful to override particular OpenBoot or LDoms settings that might be incorrect, to set up OpenBoot variables using a script, or similar tasks.

For example, if the OpenBoot settings have become corrupt, you can set the bootmode state property to reset_nvram, then reset the server with factory default OpenBoot settings.

Service personnel might instruct you to use the bootmode script property for problem resolution. The full extent of script capabilities are not documented and exist primarily for debugging.

Because bootmode is intended to be used for a single boot only, to correct a problem with the OpenBoot or LDoms settings, the bootmode takes effect for a single boot only. Additionally, to prevent an administrator from setting a bootmode state property and forgetting about it, a bootmode state property expires if the host is not reset within 10 minutes of the bootmode state property being set.

  At the -> prompt, type the following command:

-> set /HOST/bootmode config=value

where the config property takes a configname value such as a named logical domain configuration downloaded to the SP using the Logical Domains software.

For example, if you have created a logical domain configuration called ldm-set1:

-> bootmode config=ldm-set1

To return the boot mode config to the factory default configuration, specify
factory-default.

For example:

-> bootmode config=factory-default

  At the -> prompt, type the following command:

-> set /HOST/bootmode script=value

where script controls the host server OpenBoot PROM firmware method of booting.

The script does not affect the current /HOST/bootmode setting. string can be up to 64 bytes in length. You can specify a /HOST/bootmode setting and set the script within the same command.

For example:

-> set /HOST/bootmode state=reset_nvram script="setenv diag-switch? true"

After the server resets and OpenBoot PROM reads the values stored in the script, firmware sets the OpenBoot PROM variable diag-switch? to the user-requested value of true.

The /HOST/bootmode state property prepares the service processor firmware for reset, retaining the current settings of OpenBoot nonvolatile read-only memory (NVRAM) variables. Setting /HOST/bootmode state=reset_nvram changes the OpenBoot NVRAM variables to default settings.

  At the -> prompt, type the following command:

-> set /HOST/bootmode state=value

where value is one of the following:

• normal - At next reset, retains current NVRAM variable settings
• reset_nvram - At next reset, returns OpenBoot variables to default settings

  At the -> prompt, type the following command:

-> show /HOST/bootmode expires

where expires is the date at which the current bootmode state expires.

ILOM provides several ways to configure the server’s firmware environment. There are four aspects to configuring the boot mode:

• State
• Expiration Date
• Script
• LDom Configuration

1. Log into the ILOM web interface as Administrator (root) to open the web interface.

2. Select Remote Control -> Boot Mode Settings.

3. Select the Boot Mode State.

4. View the Expiration Date.

5. Specify a boot script.

6. Specify an LDom configuration file.

7. Click Save.

---

Viewing System Information and Setting System Policy Concerning Error Conditions

Use the system information properties to view system configuration and firmware version information.

• To Display the Host’s MAC Address Using the CLI
• To Display the Host’s OpenBoot Version Using the CLI
• To Display the Host’s POST Version Using the CLI
• To Determine Host Behavior When the Watchdog Timer Expires Using the CLI
• To Specify Whether the Host Halts During Diagnostics When an Error Is Discovered Using the CLI
• To View Host Information Using the Web Interface

The /HOST macaddress property is automatically configured by the system software, so you cannot set it or change it. The value is read and determined from the server’s MAC address and then stored as a property in ILOM.

/HOST macaddress is the MAC address for the net0 port. The MAC addresses for each additional port increments from the /HOST macaddress. For example, net1 is equal to the value of /HOST macaddress plus one (1).

  To view the current setting for this property, type the following command:

-> show /HOST macaddress

The /HOST obp_version property displays information about the version of OpenBoot on the host.

  To view the current setting for this property, type the following command:

-> show /HOST obp_version

The /HOST post_version property displays information about the version of POST on the host.

  To view the current setting for this property, type the following command:

-> show /HOST post_version

Use the /HOST autorestart property to specify how ILOM should handle expiration of the Oracle Solaris watchdog timer.

  To set this property, type the following command:

-> set /HOST autorestart=value

where values can be none, reset, or dumpcore (default value: reset).

Use the /HOST autorunonerror property to specify whether the host should continue to boot after system diagnostics have discovered an error.

  To set this property, type the following command:

-> set /HOST autorunonerror=value

Where values can be true or false. The default value is false.

This procedure describes how to view and configure several kinds of host information.

ILOM provides several ways to view or configure host control features. There are six aspects to host control:

• MAC address
• OpenBoot version
• POST version
• POST status
• Auto Run On Error
• Auto Restart Policy

1. Log into the ILOM web interface as Administrator (root) to open the web interface.

2. Select Remote Control -> Host Control.

3. View the MAC address.

4. View the OpenBoot version.

5. View the POST version.

6. Select a value for Auto Run On Error.

7. Select a value for Auto Restart Policy.

8. Click on Save.

---

Managing Diagnostics

Use the diagnostic control properties to specify how ILOM behaves when it encounters an error on the host server.

ILOM uses the following diagnostic system interface property:

• To Specify the Level of Diagnostics Using the CLI
• To Change the Diagnostics Mode Using the CLI
• To Specify Diagnostic Trigger Conditions Using the CLI
• To Choose the Amount of Verbosity in Diagnostic Output Using the CLI
• To Manage Diagnostics Settings Using the Web Interface

Use the /HOST/diag level property to specify the level of diagnostic testing to be executed when diagnostics are enabled.

  At the -> prompt, type the following command:

-> set /HOST/diag level=value

where value is one of the following:

• min - Run the minimum level of diagnostics to verify the system
  (the default value).
• max - Run the maximum set of diagnostics to fully verify system health.

Use the /HOST/diag mode property to control whether diagnostics are enabled and to specify which diagnostic mode is enabled.

  At the -> prompt, type the following command:

-> set /HOST/diag mode=value

where value is one of the following:

• off - Run no diagnostics.
• normal - Run diagnostics (the default value).
• service - Run service-technician diagnostics, equivalent to using the preset values of /HOST/diag trigger=all-resets, /HOST/diag verbosity, and /HOST/diag level=max. Setting /HOST/diag mode=service has the same effect as issuing the set /SYS keyswitch_state=diag command.

Use the /HOST/diag trigger property to control the conditions under which POST runs if diagnostics are enabled.

  At the -> prompt, type the following command:

-> set /HOST/diag trigger=value

where value is one (or a combination, supplied within quote marks) of the following:

• user-reset - Run diagnostics when the system is reset.
• error-reset - Run diagnostics when the system takes a fatal error that requires the system to reset itself to recover.
• power-on-reset - Run diagnostics when the system is powered on.
• all-resets - Run all of the diagnostics specified by user-reset,
  error-reset, and power-on-reset [the default value].
• none - Skip diagnostics.

The default value is the combination of power-on-reset error-reset.

For example:,

-> set /HOST/diag trigger=”user-reset power-on-reset”
-> show /HOST/diag trigger
user-reset power-on-reset

Use the /HOST/diag verbosity property to specify the verbosity level of the output from POST diagnostics, if diagnostics are enabled.

  At the -> prompt, type the following command:

-> set /HOST/diag verbosity=value

where value is one of the following:

• none - Diagnostics do not print any output on the system console when running, unless a fault is detected.
• min - Diagnostics print a limited amount of output on the system console.
• max - Diagnostics print full output on the system console, including the name and results of each test being run.
• normal - Diagnostics print a moderate amount of output on the system console (the default value).
• debug - Diagnostics print extensive debugging output on the system console, including devices being tested and debug output of each test.

This procedure describes how to view and configure diagnostics settings.

ILOM provides several ways to view or configure diagnostics. There are four aspects to host control:

• Trigger
• Verbosity
• Level
• Mode

1. Log into the ILOM web interface as Administrator (root) to open the web interface.

2. Select Remote Control -> Diagnostics.

3. Select a value for Trigger.

4. Select a value for Verbosity.

5. Select a value for Level.

6. View the Current Mode.

7. Select a value for Update Mode.

---

Managing System User Interactions

The system user properties enable you to customize the way ILOM identifies and interacts with the host server.

• To Choose Host Response Modes to Break Signals Using the CLI
• To Display Host Status Information Using the CLI

Use the set /HOST send_break_action command to bring the server to a menu from which you can choose to go to the OpenBoot PROM prompt (ok). If you have configured the kmdb debugger, then the break command brings the server into debug mode.

  At the -> prompt, type the following command:

-> set /HOST send_break_action=value

where value is one of the following:

• break - Sends a break to the host.
• dumpcore - Forces a panic core dump of the managed system OS (not supported by all OS versions).

Use the show /HOST status command to display information about the host server’s platform ID and status.

  At the -> prompt, type the following command:

-> show /HOST status

The command returns information similar to the following:

-> show /HOST status
    Properties:
        status = OS Running
 
    Commands:
        show ->

Oracle Integrated Lights Out Manager (ILOM) 2.0 Supplement for the Sun Netra T5220 Server

820-3011-13

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