Using the command line

After initiating a command line session, the iLO 3 CLI prompt appears. Each time a command is executed (or you exit the Remote Console or VSP) you will be returned to the CLI prompt as shown in the following example.

hpiLO->

Each time a CLI command is executed, the returned output follows this general format:

hpiLO-> {CLI command}

status=0

status_tag=COMMAND COMPLETED

… output returned…

hpiLO->

If an invalid command is entered, then the status and status_tag values reflects the error as shown:

hpiLO-> boguscommand

status=2

status_tag=COMMAND PROCESSING FAILED

error_tag=COMMAND NOT RECOGNIZED

If an invalid parameter is given to a valid command, the response is slightly different:

hpiLO-> show /bad

status=2

status_tag=COMMAND PROCESSING FAILED

error_tag=COMMAND ERROR-UNSPECIFIED

Invalid property.

hpiLO->

The following commands are supported in this release of CLP. The same command set is supported through the serial port, SSH, and telnet connections.

The privilege level of the logged in user is checked against the privilege required for the command. The command is only executed if the privilege levels match. If the serial command line session status is set to Enabled-No Authentication, then all the commands are executed without checking the privilege level.

The general syntax of CLP command is:

<verb> <target> <option> <property>

• Verbs—The supported verbs are:
  • cd
  • create
  • delete
  • help
  • load
  • reset
  • set
  • show
  • start
  • stop
  • exit
  • version
• Target—The default target is the /. The target can be changed by the cd command or by specifying a target on the command line.
• Options—The valid options are:
  • -help/-h
  • -all/-a
• Properties are the attributes of the target that can be modified.
• Output—The output syntax is:
  • status
  • status_tag
  • status_msg

The valid Boolean values for any command are yes, no, true, false, y, n, t, and f.

General notes

If the commands on the CLP command span more than one line, you cannot navigate between different lines.

Operating system-specific notes:

• Windows® 2000 telnet client does not support the Functions keys F1,.., F12, Insert, Home, and End keys. These keys do not work in an iLO 3 command line session.
• The Backspace key in iLO 3 CLP implementation is mapped to the value 0x8. Some client operating systems such as, Novell Linux Desktop and Red Hat Enterprise Linux 4 Desktop map the Backspace key to the value 0x7f, which is used for the Delete key in Windows® telnet client. The Backspace key does not work from a client where it has value of 0x7f. For the Linux clients, using the Home or the End key enables the iLO 3 CLP service to remap the Backspace key to use the value 0x7f, making the key functional.

In the Windows® PuTTy client, the Backspace key can be mapped to a value of 0x8 by changing the setting for Terminal Keyboard to Control-H.