Sun Integrated Lights Out Manager 2.0 Supplement for Sun Blade T6320 Server Modules

This chapter describes ILOM features available on Sun Blade T6320 server modules that augment the properties that are common to ILOM on other platforms. In particular, this chapter describes the properties in the /HOST namespace. This chapter consists of:

• Managing Boot Mode
• Viewing Host Information and Setting System Policy Concerning Error Conditions
• Managing Host Diagnostics and POST
• 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 using both ILOM and the ALOM compatibility CLIs, see TABLE B-2.

---

Managing Boot Mode

You can use the remote control properties to specify how ILOM handles boot. Boot mode (bootmode) properties enable you to override the default method the server uses when it boots. This ability is useful to override specific OpenBoot or Logical Domains (LDoms) settings that might be incorrect, to set up OpenBoot variables using a script, and 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 to its factory-default OpenBoot settings.

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

Because bootmode is intended to be used 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.

The properties can be configured using the ILOM command-line interface (CLI) or web interface.

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

  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:

-> set /HOST/bootmode config=ldm-set1

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

For example:

-> set /HOST/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. It does not affect the current /HOST/bootmode setting. The value of value 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, it sets the OpenBoot PROM variable diag-switch? to the user-requested value of true.

The /HOST/bootmode state property controls how OpenBoot nonvolatile, random-access memory (NVRAM) variables are used. Normally, the current settings of these variables are retained. Setting /HOST/bootmode state=reset_nvram changes the OpenBoot NVRAM variables to their default settings at the next reset.

  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 
     Properties: 
         expires = Thu Oct 18 18:24:16 2007 

You can use the ILOM web interface to view or configure the four aspects of boot mode control::

• State
• Expiration Date (not configurable)
• Script
• LDoms Configuration

1. Log in to 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, if desired.

4. View the Expiration Date.

5. Specify a boot script, if desired.

6. Specify an LDoms configuration file, if desired.

7. Click Save.

---

Viewing Host Information and Setting System Policy Concerning Error Conditions

Use the host information properties to view system configuration and firmware version information. You can configure these settings using the CLI or the web

interface.

• To Display the Host MAC Address Using the CLI
• To Display the Host OpenBoot Version Using the CLI
• To Display the Host POST Version Using the CLI
• To Determine Host Behavior When the Watchdog Timer Expires Using the CLI
• To Specify Host Behavior During Diagnostics When an Error Is Discovered During Diagnostics Using the CLI
• To View and Configure Host Control Features 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 removable system configuration card (SCC PROM) and then stored as a property in ILOM..

The /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 Solaris watchdog timer.

  To set this property, type the following command:

-> set /HOST autorestart=value 

where value can be one of the following:

• none - ILOM takes no action other than to issue a warning.
• reset - ILOM attempts to reset the system when the Solaris watchdog timer expires.
• dumpcore - ILOM attempts to force a core dump of the OS when the watchdog timer expires.

The default value is 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 value can be one of the following:

• false - The system stops booting after an error has been discovered.
• true - The system attempts to continue booting after an error has been discovered.

The default value is false.

You can use the web interface 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
• HOST status
• Auto Run On Error
• Auto Restart Policy (watchdog timer)

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, if desired.

7. Select a value for Auto Restart Policy, if desired.

8. Click on Save.

---

Managing Host Diagnostics and POST

Use the diagnostic control properties to specify how ILOM behaves when it encounters an error on the host server. You can configure these settings using the CLI or the web interface.

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 Diagnostic Settings Using the Web Interface

Use the /HOST/diag level property to control 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.
• max - Run the maximum set of diagnostics to fully verify system health.

The default value is max.

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 - Do not run any diagnostics.
• normal - Run diagnostics.
• 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.

The default value is normal.

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 which requires the system to reset itself to recover.
• power-on-reset - Run diagnostics when the system is powered on.
• all-resets - Run diagnostics at any server reset.
• none - Skip diagnostics.

The default value is all-resets.

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

For example:

-> set /HOST/diag trigger=”user-reset power-on-reset”
Set ’trigger’ to ’user-reset power-on-reset’
-> show /HOST/diag trigger
Properties:
       trigger = user-reset power-on-reset
 
   Commands:
       set
       show 

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.
• debug - Diagnostics print extensive debugging output on the system console, including devices being tested and debug output of each test.

The default value is normal.

You can use the ILOM web interface 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, if desired.

4. Select a value for Verbosity, if desired.

5. Select a value for Level, if desired.

6. View the Current Mode.

7. Select a value for Update Mode, if desired.

8. Click Save.

---

Managing System User Interactions

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

• To Enable the System To Send a Break Signal or Force a Core Dump 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 specifying the send_break_action=break brings the server into debug mode. Specify send_break_action=dumpcore to force a core dump.

  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.

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 = Running
 
    Commands:
        show 
->

Sun Integrated Lights Out Manager 2.0 Supplement for Sun Blade T6320 Server Modules

820-2546-11

Copyright © 2008 Sun Microsystems, Inc. All Rights Reserved.