C H A P T E R 2 |
This chapter contains information on ILOM features on the Sun Netra T5440 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. Topics include:
Use the remote control properties to specify how ILOM handles boot.
To Manage the Host’s Boot Mode LDoms Configuration Using the CLI
To Change the Host’s Boot Mode Behavior at Reset Using the CLI
To Change Boot Mode Configuration Settings Using the Web Interface
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.
To Manage the Host’s Boot Mode LDoms Configuration Using the CLI |
-> 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.
-> bootmode config=factory-default |
-> 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.
-> 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.
Note - Note: If you set /HOST/bootmode script="", ILOM sets the script to empty. If you set /HOST/bootmode config="", ILOM sets the config to empty. |
To Change the Host’s Boot Mode Behavior at Reset Using the CLI |
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.
-> 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
Use the system information properties to view system configuration and firmware version information.
To Specify Host Behavior When the Watchdog Timer Expires Using the CLI
To Specify Host Behavior When an Error Is Discovered During Diagnostics Using the CLI
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 Specify Host Behavior When the Watchdog Timer Expires Using the CLI |
Use the /HOST autorestart property to specify how ILOM should handle expiration of the Solaris watchdog timer.
To Specify Host Behavior When an Error Is Discovered During Diagnostics Using the CLI |
Use the /HOST autorunonerror property to specify whether the host should continue to boot after system diagnostics have discovered an error.
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:
Use the /HOST/diag level property to specify the level of diagnostic testing to be executed when diagnostics are enabled.
Use the /HOST/diag mode property to control whether diagnostics are enabled and to specify which diagnostic mode is enabled.
-> set /HOST/diag mode=value |
Use the /HOST/diag trigger property to control the conditions under which POST runs if diagnostics are enabled.
-> set /HOST/diag trigger=value |
where value is one (or a combination, supplied within quote marks) of the following:
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].
The default value is the combination of power-on-reset error-reset.
-> set /HOST/diag trigger=”user-reset power-on-reset” -> show /HOST/diag trigger user-reset power-on-reset |
To Choose the Amount of Verbosity in Diagnostic Output Using the CLI |
Use the /HOST/diag verbosity property to specify the verbosity level of the output from POST diagnostics, if diagnostics are enabled.
-> 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.
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 |
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.
Copyright © 2010, Oracle and/or its affiliates. All rights reserved.