Managing the Service Processor

C H A P T E R 3

This chapter describes ILOM properties available on Sun Blade T6340 server modules that augment the properties common to ILOM on other platforms. In particular, this chapter covers properties in the /SP namespace.

Storing Customer Information

ILOM enables you to store information (for purposes such as inventory control or site resource management) on the SP and FRU PROMs. You can change customer FRU data and system identification information using the CLI or the web interface.

To Change Customer FRU Data Using the CLI

Use the /SP customer_frudata property to store information in FRU PROMs.

At the -> prompt, type the following command:

-> set /SP customer_frudata="data"

Note - The data string ("data") must be enclosed in quote marks.

To Change System Identification Information Using the CLI

Use the /SP system_identifier property to store customer identification information.

At the -> prompt, type the following command:

-> set /SP system_identifier="data"

Note - The data string ("data") must be enclosed in quote marks.

To Change Customer Identification Information Using the Web Interface

Screen capture of the ILOM web interface, showing the Identification Information fields.

ILOM enables you to store information on FRUs and the SP.

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

2. Select System Information --> Identification Information.

3. Edit the Customer FRU data field, if desired.

4. Edit the SP Hostname, if desired.

5. Edit the SP System Identifier field, if desired.

6. Click Save.

Changing Service Processor Settings to Factory Defaults

You can reset the service processor setting to factory defaults using the CLI or the web interface. For information about setting the root password back to the factory default, refer to Resetting the Password to the Factory Default.

To Reset the Service Processor Settings to Factory Default Values Using the CLI

Use the set reset_to_defaults command to set all ILOM configuration properties back to their factory default values. The all option sets the ILOM configuration and all user information back to the factory default values.

1. At the -> prompt, type the following command:

-> set /SP reset_to_defaults=value

where value can be one of the following:

none - Make no changes.

all - Reset (clear) all configuration and users.

2. Reset the service processor so that the new property value can take effect.

To Reset the Service Processor Settings to Factory Default Values Using the Web Interface

Screen capture of the ILOM web interface, showing the Configuration Management fields.

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

2. Select Maintenance --> Configuration Management.

3. Select a Reset Defaults value:

None - Make no changes.

All (including users) - Reset (clear) all configurations and users.

4. Click Reset Defaults.

Displaying Console History

This section describes displaying the host server console output buffer.

To Display Console History

The host console buffer can contain up to 1 Mbyte of buffered host console output. The host will send console output when powering on and running the host Power-On Self-Test (POST) diagnostics. The host can also send console output during the OpenBoot and Solaris boot phase; however, this output can also be directed to the Remote Console (remote KVMS). See Chapter 5 for more information about configuring OpenBoot to send boot output to the Remote Console.

If ILOM senses a host server reset, it writes boot information and initialization data into the console buffer until ILOM is notified by the server that the Solaris OS is up and running.

Note - You must have Administrator level user permission to use this command.

At the -> prompt, type the following commands:

-> set /SP/console/history property=option [...] 
-> show /SP/console/history

where property can be one of the following:

line_count - The value for option must fall within the range from 1 to 2048 lines. Specify ““ for an unlimited number of lines, the default.

pause_count - The value for option indicates the number of lines to display before pausing. The value can be either a positive integer or ““ for an infinite number of lines, the default.

start_from - Applies only if the line_count property has also been set. The value for option can be one of these:

end - The most recent (last) line_count lines in the buffer (default).

beginning - The first line_count lines in the buffer.

Note - Timestamps recorded in the log represent the time on the Host Server, as printed by POST or Solaris running on the Host. These times might differ from the time and date on the ILOM SP. Solaris times are printed in the local timezone, while ILOM time is always in UTC (Coordinated Universal Time).

Modifying Console Escape Characters

To Change Console Escape Characters Using the CLI

Use the /SP/console escapechars property to change the escape character sequence to switch from a system console session back to ILOM.

At the -> prompt, type the following command:

-> set /SP/console escapechars=xx

where xx are any printable characters.

The sequence is limited to two characters. The default value is #. (Hash-Period). The sequence can be customized.

Note - Changing the escape character does not take effect in a currently active console session.

Changing Configuration Policy Settings

To Disable or Re-Enable Backup of the User Database Using the CLI

The /SP/policy BACKUP_USER_DATA property specifies whether the local user database on ILOM (that is, user, password, and permission information) should be backed up. When this property is set to enabled, this data is backed up on the removable system configuration card (SCC PROM) on the system.

At the -> prompt, type the following command:

-> set /SP/policy BACKUP_USER_DATA=value

where value can be one of the following:

enabled - Backs up the user database to the SCC.

disabled - No backup.

The default value is enabled.

For example, if you want the local user database on ILOM to be backed up, type the following command:

-> set /SP/policy BACKUP_USER_DATA=enabled

To Disable or Re-Enable Powering On the Host Server Using the CLI

Use the /SP/policy HOST_LAST_POWER_STATE property to control the behavior of the server module after an unexpected power outage. When external power is restored, the ILOM service processor starts to run automatically. Normally, the host power is not turned on until you use ILOM to turn it on.

ILOM records the current power state of the server in non-volatile storage. If the HOST_LAST_POWER_STATE policy is enabled, ILOM can restore the host to the previous power state. This policy is useful in the event of a power failure, or if you physically move the server to a different location.

For example, if the host server is running when power is lost and the /SP/policy HOST_LAST_POWER_STATE property is set to disabled, the host server remains off when power is restored. If the /SP/policy HOST_LAST_POWER_STATE property is set to enabled, the host server restarts when the power is restored.

At the -> prompt, type the following command:

-> set /SP/policy HOST_LAST_POWER_STATE=value

Where value can be one of the following:

enabled - When power is restored, returns the server to the state it was in before the power was removed.

disabled - Keeps the server off when power is applied.

The default value is disabled.

If you enable this property, you should also configure
/SP/policy HOST_POWER_ON_DELAY. For further information, see To Disable or Re-Enable Power-On Delay Using the CLI.

You can use /SP/policy HOST_AUTO_POWER_ON to power on the host automatically when the service processor has been booted. If this policy is set to enabled, the service processor sets HOST_LAST_POWER_STATE to disabled. Refer to To Disable or Re-Enable Automatic Host Power-On Using the CLI for more information.

To Disable or Re-Enable Power-On Delay Using the CLI

Use the /SP/policy HOST_POWER_ON_DELAY property to cause the server module to wait for a short time before powering on automatically. The delay is a random interval of one to five seconds. Delaying the powering on of the server helps minimize current surges on the main power source. This delay of powering on the server is important when multiple servers in racks power on after a power outage.

This property takes effect only if /SP/policy HOST_LAST_POWER_STATE is set to enabled. Refer to To Disable or Re-Enable Powering On the Host Server Using the CLI for more information.

At the -> prompt, type the following command:

-> set /SP/policy HOST_POWER_ON_DELAY=value

where value can be:

enabled

disabled

The default value is disabled.

To Disable or Re-Enable Automatic Host Power-On Using the CLI

Use the /SP/policy HOST_AUTO_POWER_ON property to set whether the server module powers on automatically when power is applied.

At the -> prompt, type the following command:

-> set /SP/policy HOST_AUTO_POWER_ON=value

where value can be:

enabled - The server module powers on automatically when power is applied. If this property is set to enabled, the service processor sets HOST_LAST_POWER_STATE to disabled. Refer to To Disable or Re-Enable Powering On the Host Server Using the CLI for more information.

disabled - You must issue an ILOM or ALOM CMT command to power on the server module.

The default value is disabled.

To Manage Configuration Policy Settings Using the Web Interface

Screen capture of the ILOM web interface, showing the Policy Configuration fields.

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

2. Select Configuration --> Policy.

3. Click the Policy radio button of the policy you want to change.

4. Select an Action value to apply the Action (enable or disable) you have chosen.

Managing Power Usage and Monitoring Power Consumption

This section describes how to use power management interfaces to manage power usage and to monitor power consumption.

Power Management Interfaces

Power management interfaces enable you to configure and display the power management policy of the system. You use power management policies to manage power usage based on user requirements. Power policies enable you to optimize power usage to match system requirements.

Note - An SNMP MIB (PM-ILOM-MIB) is available to support power management software.

Power Management Terminology

TABLE 3-1 defines the terminology used in power management.

TABLE 3-1 Power Management Terms
Term	Definition
Actual power	The input power measured in watts. This is the actual power consumed by all the power supplies in the system.
Permitted power	The maximum power that the server will permit to be used at any time.
Available power	The input power capacity in watts. For server modules, available power is the amount of power available to the server module from the chassis.
Power policy	The setting that governs system power usage at any point in time. Four power policies are supported: Performance, Elastic, Regulated, and Siesta. The characteristics of each policy setting are as follows: Performance: The system is allowed to use all the power that is available. Elastic: The system power usage is adapted to the current utilization level. For example, power up or down just enough system components to keep relative utilization at 70% at all times, even if workload fluctuates. Regulated: N/A Siesta: N/A

To View Power Management Properties (CLI)

At the -> prompt, type the following command:

-> show /SP/powermgmt

For example:

-> show /SP/powermgmt
 
 /SP/powermgmt
    Targets:
 
    Properties:
        actual_power = 131 
        permitted_power = 1000 
        available_power = 1000 
        control = local
        policy = performance
        regulated_budget = (none)
        elastic_budget = (none)
 
    Commands:
        cd
        set
        show

where

actual_power displays the input power (in watts) consumed by all power supplies in the system.

permitted_power displays the maximum power consumption (in watts) expected.

available_power displays the input power capacity (in watts) that is available to system components.

To View the Total Power Consumed by the System (CLI)

The value of /SYS/VPS is equivalent to the value of the following command: show /SP/powermgmt actual_power

The /SP/powermgt actual_power property is the same as /SYS/VPS in that /SYS/VPS is a sensor that has a threshold and actual_power is just the value returned by the sensor.

At the -> prompt, type the following command:

-> show /SYS/VPS

For example:

-> show /SYS/VPS
 
 /SYS/VPS
    Targets:
 
    Properties:
        type = Power Unit
        class = Threshold Sensor
        value = 202 Watts
        upper_nonrecov_threshold = 780.00 Watts
        upper_critical_threshold = 705.00 Watts
        upper_noncritical_threshold = 625.00 Watts
        lower_noncritical_threshold = N/A
        lower_critical_threshold = N/A
        lower_nonrecov_threshold = N/A
 
    Commands:
        cd
        show

To View Total Available Power (CLI)

This interface enables you to view available power.

The system contains one property, available_power. The property supports the show command and returns the value <input available power in watts>.

Type the show command to display the available power.

For example:

-> show /SP/powermgmt available_power

To Monitor Permitted Power Consumption (CLI)

This interface enables you to view permitted power consumption. The permitted power consumption is the maximum input power the server guarantees it will consume at any instant. This value cannot be changed directly, but can change based on the power policy and budget, and chassis available power.

The system contains one property, permitted_power. This property supports the show command and returns the value <maximum permitted power consumption in watts>.

Type the show command to display the permitted power consumption.

For example:

-> show /SP/powermgmt permitted_power

Using the Power Consumption Control Interfaces

The following section describes how to monitor and control available power and set power consumption configuration parameters.

This interface enables you to set and monitor the power policy of the system. The Power Policy setting is saved across reboots.

The system contains one property, policy. This property supports the show and set commands. Two power policies are supported, performance and elastic. (Regulated and Siesta policies are not supported currently.) For a description of each of these values, see the definition of Power Policy in TABLE 3-1.

To Set the Power Policy (CLI)

Type the set command to set the power policy:

For example, set the power policy to performance:

-> set /SP/powermgmt policy=performance

To View the Power Policy (CLI)

Type the show command to display the power policy:

For example:

-> show /SP/powermgmt policy

To View Power Management Properties (Browser Interface)

Screen shot of the ILOM web interface, showing the Power Management fields.

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

2. Select System Monitoring -> Power Management.

3. View the Actual Power consumption.

4. View the Permitted Power consumption.

5. View the Available Power.

6. Select the Power Control.

7. Select the Power Policy.

Note - Elastic and Regulated policy values are not supported currently.

Managing Network Access

To Disable or Re-Enable Network Access to the SP (CLI)

Use the /SP/network state property to enable or disable the service processor’s network interface.

At the -> prompt, type the following command:

-> set /SP/network state=value

where value can be:

enabled (the default)

disabled

To Display the DHCP Server’s IP Address (CLI)

To display the IP address of the DHCP server that provided the dynamic IP address requested by the service processor, view the dhcp_server_ip property. To see the dhcp_server_ip property, use the following procedure.

Type show /SP/network

For example:

-> show /SP/network
 
  /SP/network
     Targets:
 
     Properties:
         commitpending = (Cannot show property)
         dhcp_server_ip = 10.8.31.5
         ipaddress = 10.8.31.188
         ipdiscovery = dhcp
         ipgateway = 10.8.31.248
         ipnetmask = 255.255.252.0
         macaddress = 00:14:4F:7E:83:4F
         pendingipaddress = 10.8.31.188
         pendingipdiscovery = dhcp
         pendingipgateway = 10.8.31.248
         pendingipnetmask = 255.255.252.0
         state = enabled
 
     Commands:
         cd
         set
         show

Managing SSH Server Settings

To Change the Type of SSH Keys Using the CLI

Use the set /SP/services/ssh generate_new_key_type command to change the type of Secure Shell (SSH) host keys generated on your server. After changing the type, you must use the command set /SP/services/ssh generate_new_key_action to generate a new set of keys of the new type.

At the -> prompt, type the following command:

-> set /SP/services/ssh generate_new_key_type=value

where value can be rsa or dsa.

To Generate a New Set of SSH Keys Using the CLI

Use the set /SP/services/ssh generate_new_key_action command to generate a new set of Secure Shell (SSH) host keys.

At the -> prompt, type the following command:

-> set /SP/services/ssh generate_new_key_action=true

To Restart the SSH Server Using the CLI

Use the set /SP/services/ssh restart_sshd_action command to restart the SSH server after you have generated new host keys using the set /SP/services/ssh generate_new_key_action command. This reloads the keys into the server’s dedicated data structure in memory.

At the -> prompt, type the following command:

-> set /SP/services/ssh restart_sshd_action=true

To Enable or Disable the SSH Service Using the CLI

Use the /SP/services/ssh state property with the set command to enable or disable the SSH service. If the SSH service has been disabled, you can re-enable it through the serial management port (SER MGT) using the ILOM web interface.

At the -> prompt, type the following command:

-> set /SP/services/ssh state=value

where value can be:

enabled

disabled

The default value is enabled.

To Manage SSH Server Settings Using the Web Interface

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

2. Select Configuration --> SSH Server Settings.

3. Select an action from the SSH Server pulldown menu:

Enable the SSH server

Disable the SSH server

Restart the SSH server

4. Click Generate RSA Key or click Generate DSA Key to generate a new key type and a new key.

If you have generated a new key, you must restart the SSH server for the new key to take effect.

Note - When the SSH server is restarted or disabled, any CLI sessions running over SSH will be terminated immediately.

Screen capture of the ILOM web interface, showing the SSH Server Settings fields.

Monitoring Active System Faults

To Display Active System Faults

At the ILOM CLI prompt (->), type the show faulty command.

The show faulty command is a shortcut for the following ILOM command string:

-> show -o table -level all /SP/faultmgmt

The shortcut produces the same output as the longer command string, displaying all active faults in the system in a concise, tabular format. Sample output:

-> show faulty 
Target           | Property    | Value
-----------------+-------------+-------------------
/SP/faultmgmt/0  | fru         | /SYS/MB
/SP/faultmgmt/0  | timestamp   | Jan 16 12:53:00
/SP/faultmgmt/0/ | sunw-msg-id | NXGE-8000-0U
faults/0         |             |
/SP/faultmgmt/0/ | uuid        | e19f07a5-580e-4ea0-ed6a-f663aa61
faults/0         |             |
/SP/faultmgmt/0/ | timestamp   | Jan 16 12:53:00
faults/0