Integrated Lights Out Manager (ILOM) CLI Quick Reference (Doc ID 1009715.1)

APPLIES TO:

Sun Fire X4500 Server - Version Not Applicable and later
Sun Fire X4140 Server - Version Not Applicable and later
Sun Blade 8000 System - Version Not Applicable and later
Sun Fire X4200 M2 Server - Version Not Applicable and later
Sun Fire X4200 Server - Version Not Applicable and later
All Platforms

GOAL

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - Sun x86 Systems

Description
Most Oracle x86 servers implement the ILOM service processor (Integrated Lights Out Manager).
This is a combination of dedicated hardware and supporting software.

For a list of which servers support ILOM, refer to:

Which systems have ILOM/ALOM4v/ALOM/LOM/ELOM/SP or RSC ? (Doc ID 1012360.1)

NOTE: This guide is intended as a quick reference. It is not an exhaustive list of all possible command options.

The commands below are listed in a perceived order of importance, to help users immediately get 'up and running' with an ILOM-related issue.

Note: The SP web interface can be used as an alternate for most ILOM commands.

https://<ip_address_of_SP>

Documentation:

Integrated Lights Out Manager (ILOM) Administration Guide - For ILOM 1.1.1
Integrated Lights Out Manager (ILOM) Administration Guide - For ILOM 1.0
Integrated Lights Out Manager (ILOM) 2.0
Integrated Lights Out Manager (ILOM) 3.0

SOLUTION

Steps to Follow

Integrated Lights Out Manager (ILOM) CLI Quick Reference:

Introduction

ILOM uses a hierarchical namespace.
It contains a predefined tree /SP namespace manages the ILOM. e.g., to manage users and clock settings. The SP namespace is generic over all platforms using the ILOM. /SYS namespace manages the host

system -- e.g., change the host state, read sensor information, and access other information for managed system hardware. The SYS namespace is unique to each platform.
[For an example of the hierarchy see the Integrated Lights Out Manager Administration Guide].

Command Syntax

Command syntax can be separate or in combination:
Individually:

-> cd /SP/services/http
-> set port=80

Single combined command:

-> set /SP/services/http port=80

Useful ILOM CLI Commands:

Display SP firmware version:

-> version 

Show available CLI commands:

-> show /SP/cli/commands

Display help information about commands and targets

-> help 

For help specific to a command, use help followed by the command of interest, for example:

-> help start

Display status information about the controller board in your server (the command path to the board will vary within the X4000 family):

-> show /SYS/MB/P0

Connect to host serial console (host COM0):

-> start /SP/console 

Power on host:

-> start /SYS

Power off host:

-> stop /SYS

Reset host:

-> reset /SYS

Reset ILOM:

-> reset /SP

Resetting the ILOM and BIOS Passwords: 

Requires changing a hardware jumper within the server enclosure

Exit the ILOM CLI:

 -> exit

Send break to the host:

 Escape + B (press the Escape key and type upper case B)

Start the server console:

 -> start /SP/console

Exit the server console (escape key plus an opening bracket '(' ):

 ->  (

List users with open sessions to the system console (who is using the console?):

 -> show /SP/sessions

Terminate a server console session started by another user:

 -> stop /SP/console

Display SEL (System Event Log)

 -> show /SP/logs/event/list

Clear all System Event logs:

 -> set /SP/logs/event clear=true

Locate LED - a white LED to help find a server.
Enable locate LED:

 -> set /SYS LOCATE=on

Disable locate LED:

 -> set /SYS LOCATE=off

Configuring a Static IP Address
Set the working directory:

 -> cd /SP/network

Specify a static Ethernet configuration:

 -> set pendingipdiscovery=static
 -> set pendingipaddress=xxx.xxx.xx.xx
 -> set pendingipnetmask=yyy.yyy.yyy.y
 -> set pendingipgateway=zzz.zzz.zz.zzz
 -> set commitpending=true

Display the targets in SYS:

 -> show /SYS
/SYS Targets:
INTSW
BIOS
SP
REAR_SVC
TOP_SVC
TEMP_FAULT
POWER
LOCATE
SERVICE
V_+12V
V_+1V2

Display the targets with the /SYS/SASBP ? disk backplane:

 -> show /SYS/SASBP
/SYS/SASBP
Targets:
ID0
ID1
T_AMB
HDD0
HDD1
HDD2
HDD3
Properties:
type = Disk Backplane
Commands:
cd show

Add a local user account:

 -> create /SP/users/username password=password role=[administrator|operator]

Delete a User:

 -> delete /SP/users/username

Displaying Users:

 -> show /SP/users

Change the role of user1 to operator

 -> set /SP/users/user1 role=operator

Display the role of username 'user1' (the role will clearly impact which command functionality is available for a user):

 -> show /SP/users/user1

Change user1's password:

 -> set /SP/users/user1 password
Changing password for user /SP/users/user1/password...
Enter new password:********
Enter new password again:********
New password was successfully set for user /SP/users/user1

ILOM has two serial ports: an internal host port that interfaces directly with the host server using the start /SP/console command, and an external port that is exposed on back of the server.

Display serial port settings (on back of server):

 -> show /SP/serial/external

Display settings for the host serial port (internal):

 -> show /SP/serial/host

Change speed (baud rate) for host serial port:

 -> set /SP/serial/host pendingspeed=57600 commitpending=true

Display network settings:

 -> show /SP/network

Change the IP address of ILOM:

 -> set /SP/network ipaddress=nnn.nn.nn.nn commitpending=true

Change HTTPS settings:

 -> set /SP/services/https port=portnumber servicestate=[enabled|disabled]

Change HTTP settings, such as enabling automatic redirection to HTTPS:

 -> set /SP/services/http port=portnumber secureredirect=[enabled|disabled] servicestate=[enabled|disabled]

Display clock settings:

 -> show /SP/clock

Configure clock to synchronize with NTP server:

 -> set /SP/clients/ntp/server/1 address=nnn.nnn.nn.nn 

To disable use of NTP set the NTP-server IP address to none as show below:

 -> set /SP/clients/ntp/server/1 address=none 

Enable NTP service:

 -> cd /SP/clock
-> set usentpserver=enabled

Check NTP service:

There are no commands from the ILOM itself to confirm that NTP is functioning, however, from a Solaris host you can query the ILOM and confirm that it has connected to a timesource:

$ ntpq -p x123-sp.yourdomain.com
remote   refid  st   t   when   poll  reach  delay  offset  jitter
==================================================================
*domain-rtr-1-v5 nnn.nn.nnn.nnn 3 u 771 1024 377 1.339 1.487 0.244

Upgrade ILOM Firmware:

 -> load -source tftp://archive/newmainimage
Are you sure you want to load the specified file (y/n)? y
File upload is complete.
Firmware image verification is complete.
Do you want to preserve the configuration (y/n)? n **
Updating firmware in flash RAM:
.
Firmware update is complete.
ILOM will not be restarted with the new firmware.

** If you wish to preserve the platform configuration, please enter a 'y' at the appropriate prompt above. Not doing so will reset the system firmware configuration to default.

When preserving the platform configuration, if you experience errors such as 'Unable to successfully parse XML input', this is due to the directory you are in when attempting an ILOM firmware update.

Using the directory: /SP/config causes the issue listed above due to a conflict in the restore location. Other errors may show as a symptom. This happens when a restore config is attempted.

To avoid this conflict, execute the load command from anywhere (/ or /SP or /SYS etc.) except /SP/config.

See Bug: 15702754 : SUNBT7027523 FW UPGRADE AND RESTORE ILOM CONFIG USES LOAD COMMAND WHICH IS MISLEADING.

Display configured alerts:

 -> show /SP/alert/rules 

Display alert configuration rule in detail:

 -> show /SP/alert/rules/N (where N is 1 to 15)

Configure an alert:

 -> set /SP/alert/rules/1 destination=nnn.nnn.nn.nn level=critical

Change an alert level to critical:

 -> set /SP/alert/rules/1 level=critical

Disable an alert:

 -> set /SP/alert/rules/1 level=disable

Send a test alert for all enabled rules:

 -> set /SP/alert/rules testalert=true