Hp Ilo

May the source be with you, but remember the KISS principle ;-)
HomeSwitchboardUnix AdministrationRed HatTCP/IP NetworksNeoliberalismToxic Managers
(slightly skeptical) Educational society promoting 'Back to basics' movement against IT overcomplexity and bastardization of classic Unix

HPE iLO Advanced gives you access to Hewlett Packard Enterprise patented Jitter Smoothing technology for significant performance improvements, real savings, and a more intelligent server environment. Workload Performance Advisor, providing you an easy method to get maximum performance from your server by providing recommendations on the right BIOS parameter settings. The HP iLO subsystem is a standard component of selected HP ProLiant servers that simplifies initial server setup, server health monitoring, power and thermal optimization, and remote server administration. The HP iLO subsystem includes an intelligent microprocessor, secure memory, and a dedicated network interface.

NewsHP iLO 4Recommended LinksHow do I reset the HP iLO
IP address and password		ILO3 TCP ports IPMI
Using virtual CDROMHumorEtc

HP iLo command line interface use so called SMASH CLP command language.

SMASH CLP is the DMTF suite of specifications that deliver industry-standard protocols and profiles to unify the management of the data center. The SMASH CLP specification enables simple and intuitive management of heterogeneous servers in a data center. SMASH CLP provides a standardized set of commands for configuration and control of management processors (called Management Access Points) and host systems. On iLO, access SMASH CLP through the SSH port.

The latter provides a standardized set of commands for configuration and control of management processors (called Management Access Points) and host systems. On iLO 3 command line interface can be accessed via SSH or serial port.

Up to five network connections can be active simultaneously.

Note: in case of serial port connection CLI is enabled by hitting ESC. The SSH session starts after authentication.

Command line session had a prompt that is displayed after each command (or if you exit VSP):

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

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

There are several keyboard sequences for frequent commands:

iLO key sequence commands Key sequence Description
<ESC>Q Exits the iLO command line interface
<ESC>R<ESC>r<ESC>R Resets the server
<ESC>^ Powers on the server

The general syntax of a CLP command is:

• Verbs—The supported verbs are:
◦ cd
◦ create
◦ delete
◦ help
◦ load
◦ reset
◦ set
◦ show
◦ start
◦ stop
◦ exit
◦ version

Target—The default target is the /. Change the target using the cd command, or by specifying a target on
the command line.
• Options—The valid options are:
◦ -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, f, 1, and 0.

Escape commands

The escape key commands are shortcuts to popular tasks.

ESC R ESC r ESC R
Resets the system.
ESC ^
Powers on the system.
ESC ESC
Erases the current line.
There is a one second timeout for entering any of the escape sequence characters.

Base commands

Following are the base commands for use on the command line:

  1. help -- Displays context-sensitive help and all supported commands
  2. command help/? -- Displays the help message specific to that command
  3. exit -- Terminates the CLP session
  4. cd -- The command sets the current default target. The context works like a directory path. The root context for the server is a forward slash (/) and is the starting point for a CLP system. Shorten commands by changing the context.

    For example, to find the current iLO firmware version, enter the following command:

The command displays values of a property or contents of a collection target. For example:

See more:

IPMI

The IPMI specification is a standard that defines a set of common interfaces to a computer system. System administrators can use IPMI to monitor system health and manage the system. IPMI 2.0 defines a mandatory system interface, and an optional LAN interface. The iLO processor supports both interfaces.

The IPMI specification defines a standardized interface for platform management. The IPMI specification defines the following types of platform management:

  • Monitors the status of system information, such as fans, temperatures, and power supplies
  • Recovery capabilities, such as system resets and power on/off operations
  • Logging capabilities for abnormal events, such as over-temperature readings or fan failures
  • Inventory capabilities, such as identifying failed hardware components
  • IPMI commands are sent to iLO using a third-party or open source utility, such as IPMITOOL, IPMIUTIL,
    OpenIPMI or FreeIPMI.

You must be familiar with IPMI specifications when issuing raw commands. For additional information, see the IPMI specification on the Intel website at

http://www.intel.com/content/www/us/en/servers/ipmi/ipmi-v2-rev1-1-spec-errata-6-markup.html?wapkw=ipmi.

NEWS CONTENTS

  • 20150319 : Setting HP iLo IP address from the command line ( 03/03/2011 , Alex Who )
  • 20120921 : Reconfigure iLo network settings using HPONCFG by rodvars ( May 25, 2012 , My Knowledge Base )
  • 20120102 : Access HP iLO via SSH UNIX Note by andy ( Access HP iLO via SSH UNIX Note, Jan 02, 2012 )
  • 20120102 : Connecting to HP iLO using the command line by Emerson Takahashi ( July 17, 2010 , setaOffice )

Old News ;-)

Top Visited
Switchboard
Latest
Past week
Past month

[Mar 19, 2015] Setting HP iLo IP address from the command line

03/03/2011 | Alex Who
As is typically the case, I've spent the past hour trying to figure out this poorly documented task. So here goes; somewhere on the net where you can easily find how to set a friggin iLo's IP address using the builtin (crappy) CLI.

I was given a couple of blades that had statically assigned IPs. The c7000 onboard administrator has a handy tool, Enclosure Bay IP Addressing, which lets us set the IPs of all of the management interfaces for blades, i.e. the iLo, and any interconnects that may be attached. What doesn't it do? Well, it doesn't change statically assigned IP addresses.

WTF, seriously? This hunk of junk is 1000 miles away so I can't go to the console and reboot it.

So here we go…

  1. SSH into the OA, I'm not going to say 'or telnet'…why would you do that?
  2. Connect to the blades iLo that you are trying to configure:

    connect server 7 where 7 is the slot number of the blade

  3. You should now be at the iLo command prompt
  4. Now we could get fancy and set the IP from here…but I'm tired, don't feel well, and just wanted to get it over with, so I set it to DHCP:

    set /map1/dhcpendpt1 EnabledState=yes

After the iLo resets it will come up and look for a DHCP server, if you have a DHCP server you're good to go. If you're like me and have no DHCP server, but you were smart enough to think that the EBIPA was gonna do the trick you will notice that the IP address you entered in EBIPA is now assigned to the iLo.

Here's a guide on the CLI: http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00294268/c00294268.pdf

Rjnoll | 09/28/2012 at 05:52 AM

This is correct if you want DHCP for ILO. If you don't you need to type this set /map1/enetport1/lanendpt1/ipendpt1 IPv4Address=XXX.XXX.XXX.XXX subnet=XXX.XXX.XXX.XXX

NOTE!! If you enabled DHCP, you will need to disable it first by typing set /map1/dhcpendpt1 EnabledState=no

JBTN | 10/25/2012 at 05:55 AM

Thanks you very much..

By the way 'connect server XX' can fail too (Unable to establish connection to server.). In this case I don't know what to do.

reset for For Linux:

connect to the enclosure:

$ ssh ixencloxyz -l Administrator

connect to the blade slot (use GUI to find out; I dont have the CLI command right now)
IXENCLOXYZ> connect server X

hpiLO-> cd /map1
status=0
status_tag=COMMAND COMPLETED

hpiLO-> reset
status=0
status_tag=COMMAND COMPLETED
Resetting iLO.

CLI session stopped

[Sep 21, 2012 ] Reconfigure iLo network settings using HPONCFG by rodvars

May 25, 2012 | My Knowledge Base

To proceed with this we will use HPONCFG utility.To write the current iLo configuration simply open a cmd prompt and execute the following command:

To change settings you need to create an XML file containing the parameters you want to change, formatted using the RIBCL language.

RIBCL allows you to write XML scripts to configure and manage iLO config settings.

To modify the network settings create a xml file with this information:

And then run the script like so:

Hope that this information can be useful

[Jan 02, 2012]Access HP iLO via SSH UNIX Note byandy

... Here are the steps to gain access to HP iLO thru Command Line Interface (CLI) via SSH

roo@solaris# ssh Administrator@linux-mgmt
Administrator@linux-mgmt's password:
User:Administrator logged-in to linux-mgmt.corp.ads(142.178.232.97)
iLO 2 Standard Blade Edition 2.00 at 11:16:29 Jun 21 2010
Server Name: linux
Server Power: On

hpiLO-> VSP

Starting virtual serial port.
Press 'ESC (' to return to the CLI Session. <-– TAKE NOTE OF THE Escape Sequence

hpiLO-> Virtual Serial Port active: IO=0x03F8 INT=4

You have new mail in /var/spool/mail/root
linux#

hpiLO-> exit
status=0
status_tag=COMMAND COMPLETED

CLI session stopped
Received disconnect from 142.178.232.97: 11: Client Disconnect
roo@solaris#

[Jan 02, 2012]Connecting to HP iLO using the command line by Emerson Takahashi

July 17, 2010 | setaOffice

Just ssh to the IP that you configured the iLO

emerson@shellcore:~ $ ssh emerson@192.168.50.118
emerson@192.168.50.118′s password:
User:Emerson Takahashi logged-in to ILO_TESTLABHP.(192.168.50.118)
iLO 2 Advanced Evaluation 1.81 at 11:05:47 Jan 15 2010
Server Name: proliant_g5
Server Power: On

hpiLO->

Since I will access through a text terminal, Linux is configured to use the serial port (configured through the file /boot/grub/grub.conf)

hpiLO-> help
status=0
status_tag=COMMAND COMPLETED

DMTF SMASH CLP Commands:

help : Used to get context sensitive help.
show : Used to show values of a property or contents of a collection target.
create : Used to create new user account in the name space of the MAP.
Example: create /map1/accounts1 username= password=
name=
group=

delete : Used to delete user account in the name space of the MAP.
Example: delete /map1/accounts1/

load : Used to move a binary image from an URL to the MAP. The URL is
limited to 80 characters
Example : load -source http://192.168.1.1/images/fw/iLO2_130.bin

reset : Used to cause a target to cycle from enabled to disabled and back to enabled.

set : Used to set a property or set of properties to a specific value.
start : Used to cause a target to change state to a higher run level.
stop : Used to cause a target to change state to a lower run level.
cd : Used to set the current default target.
Example: cd targetname

exit : Used to terminate the CLP session.
version : Used to query the version of the CLP implementation or other CLP
elements.

oemhp_ping : Used to determine if an IP address is reachable from this iLO 2.
Example : oemhp_ping 192.168.1.1 , where 192.168.1.1 is the IP address that you wish
to ping

oemhp_loadSSHKey : Used to authorize a SSH Key File from an URL The URL is
limited to 80 characters
Example : oemhp_loadSSHKey -source http://UserName:password@192.168.1.1/images/SSHkey1.ppk

HP CLI Commands:

POWER : Control server power.
UID : Control Unit-ID light.
NMI : Generate an NMI.
VM : Virtual media commands.
VSP : Invoke virtual serial port.

Type VSP and you're in. To login as root you need to include the serial port (in this case ttyS1) on your /etc/securetty file or you will be given the error message that your user or password is wrong.

hpiLO-> VSP

Starting virtual serial port.
Press 'ESC (' to return to the CLI Session.

hpiLO-> Virtual Serial Port active: IO=0x02F8 INT=3

login as:

Recommended Links

Google matched content

Softpanorama Recommended

Top articles

Sites

Reference

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 and SSH connections.

The privilege level of the logged in user is verified 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 verifying 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, and y, n, t, 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:

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. 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.

Using the command line 29

Escape commands

Hp Ilo Virtual Media

The escape key commands are short-cuts to popular tasks.

  • ESC ( invokes the serial CLI connection. This is not necessary for SSH sessions because they

    automatically start a CLI session after a successful login.

  • ESC Q – Stops the CLI session and terminates the SSH connection.
  • ESC R ESC r ESC R– Resets the system.
  • ESC ^– Powers on the system.
  • ESC ESC– Erases the current line.

There is a one second timeout for entering any of the escape sequence characters.

Base commands

< />The help command displays context-sensitive help.

Entering help displays all supported commands.

Entering <command help/?> displays the help message specific to that command.

  • The exit command terminates the CLP session.
    • The cd command sets the current default target. The context works like a directory path. The

    root context for the server is '/' and is the starting point for a CLP system. By changing the

    context, you can shorten commands.

    For example, to find the current iLO 3 firmware version, enter the show /map1/firmware1

    version command.

    However, if you enter the cd /map1/firmware1 command, then enter show version,

    this displays the information as well.

    The show command displays values of a property or contents of a collection target. For

    example:

    hpiLO-> show

    status=0

    status_tag=COMMAND COMPLETED

    /

    Targets

    system1

    map1

    Properties

    Verbs

    cd version exit show

    The first line of information returned by the show command is the current context. In the

    example, / is the current context. Following the context is a list of subtargets (Targets) and

    properties (Properties) applicable to the current context. The verbs (Verbs) section shows which

    Hp Ilo

    Ilo

    commands are applicable to this context.

    You can also specify the show command with an explicit or implicit context as well as a

    specific property. For example, an explicit context is /map1/firmware1 and is not dependent

    on the current context, while an implicit context assumes that the context specified is a child

    of the current context. If the current context is /map1 then a show firmware command

    displays the /map1/firmware1 data.

    If you do not specify a property, then all properties are shown. In the case of the /map1/

    firmware1 context, two properties are available: version, and date. If you execute show

    /map1/firmware1 date, only the date is shown.

    The create command creates a new instance of the MAP in the name space.

    30 SMASH CLP Scripting Language

  • The delete command removes instances of the MAP in the name space.
  • The load command moves a binary image from a URL to the MAP.
  • The reset command causes a target to cycle from enabled to disabled, and back to enabled.
    • The set command sets a property or set of properties to a specific value, and resets iLO 3

    to implement the changes.

  • The start command causes a target to change the state to a higher run level.
  • The stop command causes a target to change the state to a lower run level.
    • The version command queries the version of the CLP implementation or other CLP elements.

    For example:

    hpiLO-> version

    status=0

    status_tag=COMMAND COMPLETED

    SM-CLP Version 1.0

    The oemhp_ping command determines if an IP address is reachable from the current iLO 3.

    For example:

    oemhp_ping 192.168.1.1

    Where 192.168.1.1 is the IP address you are testing.

    Specific commands

    The following sections cover iLO 3 specific commands available when using the command line,

    including:

  • User commands ('User commands' (page 31))
  • Network commands ('Network commands' (page 33))
  • iLO 3 settings
  • iLO 3 embedded health settings ('iLO 3 embedded health settings' (page 37))
  • SNMP settings ('SNMP settings' (page 38))
  • License commands ('License commands' (page 39))
  • Directory commands ('Directory commands' (page 39))
  • Virtual media commands ('Virtual media commands' (page 40))
  • Start and reset commands
  • Firmware update
  • Eventlog commands ('Eventlog commands' (page 44))
  • Blade commands ('Blade commands' (page 44))
  • Boot commands ('Boot commands' (page 45))
  • LED commands
  • System targets and properties
    • Other commands ('Other commands' (page 48))

    User commands

    User commands enable you to view and modify user settings. User settings are located at

    /map1/accounts1.

    Targets

    Specific commands 31

    All local users are valid targets. For example, if three local users have the login names Administrator,

    admin, and test, then valid targets are:

  • Administrator
  • admin
    • test

    Properties

    Property Access Description

    username read/write Corresponds to the iLO 3 login name.

    password read/write Corresponds to the password for the current user.

    Displays the name of the user. If a name is not specified, the parameter

    uses the same value as the login name (username). This value corresponds

    to the iLO 3 user name property.

    name read/write

    group read/write Specifies the privilege level. The valid values are as follows:

  • admin
  • config
  • oemhp_power
  • oemhp_rc
    • oemhp_vm

    If a group is not specified, no privileges are assigned to the user.

    Examples

    The current path is /map1/accounts1.

    create username=lname1 password=password

    In the example, username corresponds to the login name.

    set lname1 username=lname2 password=password1 name=name2

    group=admin,configure,oemhp_power,oemhp_vm,oemhp_rc

    In the example, lname1 is the login name of the user.

    HP SIM SSO settings

    HP SIM SSO settings commands are accessed using /map1/oemhp_ssocfg1. You must have

    the Configure iLO 3 Settings privilege to change these properties. SSO is only supported for browser

    access from trusted HP SIM servers. SSO is a licensed feature. For more information, see the HP

    ProLiant Integrated Lights-Out 3 User Guide.

    Targets

    None

    Properties

    Hp Ilo Configuration

    Property Access Description

    The Single Sign-On required trust level. Valid values are

    disabled, all, name, and certificate.

    oemhp_ssotrust Read/write

    The privileges associated with the user role. Valid values

    are login, oemhp_rc, oemhp_power, oemhp_vm,

    config, admin.

    oemhp_ssouser Read/write

    32 SMASH CLP Scripting Language

    Property Access Description

    The privileges associated with the operator role. Valid

    values are login, oemhp_rc, oemhp_power,

    oemhp_vm, config, admin.

    oemhp_ssooperator Read/write

    The privileges associated with the administrator role. Valid

    values are login, oemhp_rc, oemhp_power,

    oemhp_vm, config, admin.

    oemhp_ssoadministrator Read/write

    Contains 0 or more HP SIM Trusted Server records. Each

    record can contain a server name or a server certificate.

    oemhp_ssoserver Read

    Examples

    To set the SSO trust level to trust by certificate:

    set oemhp_ssocfg/ oemhp_ssotrust = certificate

    To assign user roles the login privilege:

    set oemhp_ssocfg/ oemhp_ssouser = login

    To assign the operator role login, remote console, virtual power control, and virtual media

    privileges:

    set oemhp_ssocfg/ oemhp_ssooperator = login,oemhp_rc,

    oemhp_power,oemhp_vm

    To Add an HP SIM Trusted Server name record:

    cd map1/oemhp_ssocfg

    </map1/oemhp_ssocfg>hpiLO-> create = hpsim1.corp.net

    Hp Ilo Firmware

    To dynamically import a certificate from the specified server (hpsim2.corp.net):

    </map1/oemhp_ssocfg>hpiLO-> load = hpsim2.corp.net

    To delete oemhp_ssoserver with index 5:

    </map1/oemhp_ssocfg>hpiLO-> delete = 5

    To display the complete iLO 3 SSO configuration:

    cd map1/oemhp_ssocfg

    </map1/oemhp_ssocfg>hpiLO->show

    Network commands

    The network subsystems are located at:

    • /map1/enetport1
    • /map1/dhcpendpt1
    • /map1/dnsendpt1
    • /map1/gateway1
    • /map1/dnsserver1
    • /map1/dnsserver2
    • /map1/dnsserver3
    • /map1/dhcpserver1
    • /map1/settings1
    • /map1/vlan1

      Specific commands 33

      Properties, Targets, and Verbs:

    dhcpendpt1

    Properties

    ◦ EnabledState

    ◦ OtherTypeDescription

    dnsendpt1

    Properties

    ◦ EnabledState

    ◦ HostName

    ◦ DomainName

    ◦ OtherTypeDescription

    • gateway1

      Properties

      ◦ AccessInfo

      ◦ AccessContext

    • dnsserver1

      Properties

      ◦ AccessInfo

      ◦ AccessContext

      Verbs

      ◦ cd

      ◦ version

      ◦ exit

      ◦ show

      ◦ set

    • dnsserver2

      Properties

      ◦ AccessInfo

      ◦ AccessContext

    • dnsserver3

      Properties

      ◦ AccessInfo

      ◦ AccessContext

    • dhcpserver1

      Properties

      ◦ AccessInfo

      ◦ AccessContext

      34 SMASH CLP Scripting Language

    • settings1

      Targets

      DNSSettings1

      ◦

      Properties

      – DNSServerAddress

      – RegisterThisConnection

      – DomainName

      – DHCPOptionToUse

      WINSSettingData1

      Properties

      – WINSServerAddress

      – RegisterThisConnection

      – DHCPOptionToUse

      ◦ Verbs

      – cd

      – version

      – exit

      – show

    • StaticIPSettings1

      Properties

      ◦ oemhp_SRoute1Address

      ◦ oemhp_Mask1Address

      ◦ oemhp_Gateway1Address

      ◦ oemhp_SRoute2Address

      ◦ oemhp_Mask2Address

      ◦ oemhp_Gateway2Address

      ◦ oemhp_SRoute3Address

      ◦ oemhp_Mask3Address

      ◦ oemhp_Gateway3Address

      ◦ DHCPOptionToUse

      Examples

      set /map1/enetport1 speed=100

      set /map1/enetport1/lanendpt1 ipv4address=192.168.0.13

      subnetmask=255.255.252

      You can specify one or more properties on the command line. If multiple properties are on the

      same command line, they must to be separated by a space.

      iLO 3 is reset after network settings have been applied.

      iLO 3 settings

      The iLO 3 settings commands enable you to view or modify iLO 3 settings. iLO 3 settings are

      located at /map1/config1.

      Specific commands 35

      Targets

      No targets

      Properties

      Property Access Description

      Enables or disables the iLO 3. Boolean

      values are accepted.

      oemhp_mapenable Read/Write

      Sets session timeout in minutes. Valid

      values are 15, 30, 60, and 120.

      oemhp_timeout Read/Write

      Enables or disables RBSU prompt

      during POST. Boolean values are

      accepted.

      oemhp_rbsuenable Read/Write

      Enables or disables login requirement

      for accessing RBSU. Boolean values are

      accepted.

      oemhp_rbsulogin Read/Write

      Enables or disables iLO 3 IP address

      display during POST. Boolean values

      are accepted.

      oemhp_rbsushowip Read/Write

      Sets the Remote Console configuration.

      Valid values are enabled, disabled, or

      automatic.

      oemhp_rcconfig Read/Write

      oemhp_httpport Read/Write Sets the HTTP port value.

      oemhp_sslport Read/Write Sets the SSL port value.

      oemhp_rcport Read/Write Sets remote console port value.

      oemhp_vmport Read/Write Sets virtual media port value.

      oemhp_sshport Read/Write Sets the SSH port value.

      Enables or disables SSH. Boolean

      values are accepted.

      oemhp_sshstatus Read/Write

      Enables or disables CLP session through

      serial port. Boolean values are

      accepted.

      oemhp_serialclistatus Read/Write

      Enables or disables authorization

      requirement for CLP session through

      oemhp_serialcliauth Read/Write

      serial port. Boolean values are

      accepted.

      Sets the serial port speed for the CLP

      session. The valid values are 9600,

      19200, 38400, 57600, and 115200.

      oemhp_serialclispeed Read/Write

      Sets the minimum password length

      requirement.

      oemhp_minpwdlen Read/Write

      Sets the logging criteria for failed

      authentications.

      oemhp_authfailurelogging Read/Write

      Enables or disables remote console

      acquire operations.

      oemhp_rc_aquire Read/Write

      (not supported in iLO 3 v1.00)

      36 SMASH CLP Scripting Language

      Property Access Description

      Enables or disables the Remote Console

      Computer Lock.

      oemhp_computer_lock Read/Write

      Enable or disable enforcing AES/3DES

      encryption

      oemhp_enforce_aes Read/Write

      Examples

      set /map1/config1 oemhp_mapenable=yes oemhp_timeout=30

      You can specify one or more properties in the command line. If multiple properties are on the same

      command line, they must be separated by a space.

      oemhp_computer_lock

      command examples:

      set /map1/config1 oemhp_computer_lock = windows

      set /map1/config1 oemhp_computer_lock = custom,l_gui,l

      set /map1/config1 oemhp_computer_lock = disabled

      For a complete list of oemhp_computer_lock custom keys, see the HP ProLiant Integrated

      Lights-Out 3 User Guide. Keys with a space must have the space replaced with an underscore.

      For example:

      set /map1/config1 oemhp_computer_lock = custom,SYS_RQ

      iLO 3 embedded health settings

      iLO 3 embedded health commands enable you to display system embedded health information

      for fans, temperature sensors, voltage sensors, and the power supply.

      iLO 3 embedded health CLP settings are located here:

    • /system1/fan*
    • /system1/sensor*
    • /system1/powersupply*

      Targets

    • Fan
    • Sensor
    • Power supply

      Properties

      Property Access Description

      Displays fan, sensor, or power supply

      label number

      DeviceID Read

      Displays fan, sensor, or power supply

      location

      ElementName Read

      Displays fan, sensor, or power supply

      operational status

      OperationalStatus Read

      Displays if fan is operating at variable

      speed

      VariableSpeed Read

      DesiredSpeed Read Displays the current fan speed

      Displays the health status of the fan,

      sensor, or power supply

      HealthState Read

      Specific commands 37

      Property Access Description

      Displays the reading units for

      temperature and voltage sensors

      RateUnits Read

      CurrentReading Read Displays the current reading of sensor

      SensorType Read Displays the sensor type

      Displays temperature sensor caution

      value

      Oemhp_CautionValue Read

      Displays temperature sensor critical

      value

      Oemhp_CriticalValue Read

      Examples

      The command show system1/fan1 displays the system fan1 properties. For example:

      /system1/fan1

      Targets

      Properties

      DeviceID=Fan 1

      ElementName=I/O Board

      OperationalStatus=Ok

      VariableSpeed=Yes

      DesiredSpeed=40

      HealthState=Ok

      VRM power supplies are usually mapped to the sensor targets. The command show system1/

      sensor1 displays the VRM 1 properties. For example:

      /system1/sensor1

      Targets

      Properties

      DeviceID=VRM 1

      ElementName=CPU 1

      OperationalStatus=Ok

      RateUnits=Volts

      CurrentReading=0

      SensorType=Voltage

      HealthState=Ok

      oemhp_CautionValue=0

      oemhp_CriticalValue=0

      Other sensor targets show system temperatures. The command show system1/sensor3 displays

      one of the temperature zone properties. For example:

      /system1/sensor3

      Targets

      Properties

      DeviceID=Temp 1

      ElementName=I/O Board Zone

      OperationalStatus=Ok

      RateUnits=Celsius

      CurrentReading=32SensorType=Temperature

      HealthState=Ok

      oemhp_CautionValue=68

      oemhp_CriticalValue=73

      SNMP settings

      SNMP settings commands enable you to view and modify SNMP settings. SNMP settings are

      available at /map1/snmp1.

      38 SMASH CLP Scripting Language

      Targets

      None

      Properties

      Property Access Description

      Sets the first SNMP trap destination

      address.

      accessinfo1 Read/Write

      Sets the second SNMP trap destination

      address.

      accessinfo2 Read/Write

      Sets the third SNMP trap destination

      address.

      accessinfo3 Read/Write

      Enables or disables iLO 3 SNMP alerts.

      Boolean values accepted.

      oemhp_iloalert Read/Write

      Enables or disables host agent SNMP

      alerts. Boolean values accepted.

      oemhp_agentalert Read/Write

      Enables or disables iLO 3 SNMP

      pass-through. Boolean values accepted.

      oemhp_snmppassthru Read/Write

      oemhp_imagenturl Read/Write Sets the Insight Manager Agent URL.

      Determines if the LOM device responds

      to anonymous XML queries. Valid

      oemhp_imdatalevel Read/Write

      selections can be enabled and

      disabled.

      Examples

      set /map1/snmp1 accessinfo1=192.168.0.50 oemhp_imdatalevel=Enabled

      You can specify one or more properties on the command line. If multiple properties are on the

      same command line, they must be separated by a space.

      License commands

      License commands enable you to display and modify the iLO 3 license. License commands are

      available at /map1/.

      Targets

      None

      Commands

      Command Description

      cd Changes the current directory

      show Displays license information

      set Changes the current license

      Examples

    • set /map1 license=1234500000678910000000001
    • show /map1 license

      Directory commands

      Directory commands enable you to view and modify directory settings. Directory settings are

      available at: /map1/oemhp_dircfg1

      Specific commands 39

      Targets

      None

      Properties

      Property Access Description

      Enables or disables directory authentication. Valid settings are as

      follows:

      oemhp_dirauth Read/Write

    • extended_schema – Uses HP extended schema
    • default_schema – Uses schema-free directories
    • disabled – Directory-based authentication is disabled

      Enables or disables local account authentication. This property can

      be disabled only if directory authentication is enabled. Boolean

      values accepted.

      oemhp_localacct Read/Write

      Sets the directory server IP address or DNS name. The schema-free

      directory configuration requires a DNS name.

      oemhp_dirsrvaddr Read/Write

      oemhp_ldapport Read/Write Sets the directory server port.

      Displays the LOM object distinguished name. This field is ignored

      when the schema-free directory configuration is used.

      oemhp_dirdn Read/Write

      Displays the directory user login search context. This field is not

      necessary when the schema-free directory configuration is used.

      oemhp_usercntxt1, 2 ... Read/Write

      (up to 15)

      Displays security group distinguished name. Used within the

      schema-free directory configuration only.

      oemhp_group(n)_name Read/Write

      where n = 1..6

    • The privileges associated with a group. Valid values are login,

      oemhp_rc, oemhp_power, oemhp_vm, config, admin.

      oemhp_group(n)_priv Read/Write

      where n = 1..6

      Examples

    • set /map1/oemhp_dircfg1
    • set /map1/oemhp_dircfg1 oemhp_dirauth=default_schema oemhp_dirsrvaddr=adserv.demo.com

      You can define additional groups using additional set commands.

      You can specify one or more properties on the command line. If multiple properties are on the

      same command line, they must be separated by a space.

      Virtual media commands

      Access to the iLO 3 virtual media is supported through the CLP. The virtual media subsystem is

      located at /map1/oemhp_vm1. See the user guide for more information.

      Targets

      You can access the following sub-components of the virtual media.

      Target Description

      /map1/oemhp_vm1/floppydr1 Virtual floppy or key drive device

      /map1/oemhp_vm1/cddr1 Virtual CD-ROM device

      40 SMASH CLP Scripting Language

      Properties

      Property Access Description

      The image path and name for virtual media access. The value is a URL

      with a maximum length of 80 characters.

      oemhp_image Read/Write

      Displays if a virtual media device is already connected through the CLP

      or scriptable virtual media.

      oemhp_connect Read

      oemhp_boot Read/Write Sets the boot flag. The valid values are:

      • Never – Do not boot from the device. The value appears as No_Boot.
      • Once – Boot from the device only once. The value appears as Once.
      • Always – Boot from the device each time the server is rebooted. The value is displayed as Always.
      • Connect – Connect the virtual media device. Sets oemhp_connect to Yes and oemhp_boot to Always.
      • Disconnect – Disconnects the virtual media device and sets the oemhp_boot to No_Boot.

      oemhp_wp Read/

    Etc

    Society

    Groupthink :Two Party System as Polyarchy : Corruption of Regulators :Bureaucracies :Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia :Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience :Who Rules America :Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy

    Quotes

    War and Peace: Skeptical Finance : John Kenneth Galbraith :Talleyrand :Oscar Wilde :Otto Von Bismarck :Keynes :George Carlin :Skeptics :Propaganda : SE quotes : Language Design and Programming Quotes :Random IT-related quotes : Somerset Maugham :Marcus Aurelius :Kurt Vonnegut :Eric Hoffer :Winston Churchill :Napoleon Bonaparte :Ambrose Bierce : Bernard Shaw : Mark Twain Quotes

    Bulletin:

    Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis :Political Skeptic Bulletin, 2013 :Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments :Slightly Skeptical Euromaydan Chronicles, June 2014 :Greenspan legacy bulletin, 2008 :Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) :Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 :Inequality Bulletin, 2009 :Financial Humor Bulletin, 2008 :Copyleft Problems Bulletin, 2004 :Financial Humor Bulletin, 2011 :Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult :Political Skeptic Bulletin, 2011 :Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

    History:

    Fifty glorious years (1950-2000): the triumph of the US computer engineering :Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds :Larry Wall :John K. Ousterhout : CTSS : Multix OSUnix History : Unix shell history :VI editor :History of pipes concept :Solaris : MS DOS : Programming Languages History :PL/1 : Simula 67 :C :History of GCC development : Scripting Languages :Perl history :OS History : Mail :DNS : SSH : CPU Instruction Sets :SPARC systems 1987-2006 :Norton Commander :Norton Utilities :Norton Ghost :Frontpage history :Malware Defense History :GNU Screen : OSS early history

    Classic books:

    The Peter Principle : Parkinson Law : 1984 :The Mythical Man-Month : How to Solve It by George Polya :The Art of Computer Programming :The Elements of Programming Style :The Unix Hater’s Handbook :The Jargon file :The True Believer :Programming Pearls :The Good Soldier Svejk : The Power Elite

    Most popular humor pages:

    Manifest of the Softpanorama IT Slacker Society :Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story :The Cuckoo's Egg :IT Slang : C++ Humor : ARE YOU A BBS ADDICT? :The Perl Purity Test :Object oriented programmers of all nations : Financial Humor :Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor :Goldman Sachs related humor :Greenspan humor : C Humor :Scripting Humor :Real Programmers Humor :Web Humor : GPL-related Humor : OFM Humor :Politically Incorrect Humor :IDS Humor : 'Linux Sucks' Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor :Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor :Networking Humor :Shell Humor :Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 :Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor :Education Humor : IBM Humor : Assembler-related Humor :VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

    The Last but not LeastTechnology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

    Copyright © 1996-2020 by Softpanorama Society. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

    FAIR USE NOTICEThis site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

    This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

    You can use PayPal to to buy a cup of coffee for authors of this site

    Disclaimer:

    The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society.We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

    Last modified: July, 28, 2019

    -->

    Important

    This version of Orchestrator has reached the end of support, we recommend you to upgrade to Orchestrator 2019.

    The Integration Pack for HP iLO and OA is an add-on for System Center - Orchestrator that enables you to automate HP iLO and OA commands.

    Microsoft is committed to protecting your privacy, while delivering software that brings you the performance, power, and convenience you want. For more information, see the System Center Orchestrator Privacy Statement.

    System Requirements

    The Integration Pack for HP iLO and OA requires the following software to be installed and configured prior to implementing the integration. For more information about installing and configuring Orchestrator and HP iLO and OA, refer to the respective product documentation.

    • System Center 2016 integration packs require System Center 2016 - Orchestrator
    • System Center 2019 integration packs require System Center 2019 - Orchestrator
    • HP iLO 2
    • HP iLO 3
    • HP OA firmware 3.31

    Downloading the Integration Pack

    • To download this integration pack for Orchestrator 2016, see HP iLO and OA Integration Pack for System Center 2016 - Orchestrator..

    • To download this integration pack for Orchestrator 2019, see HP iLO and OA Integration Pack for System Center 2019 - Orchestrator..

    Registering and Deploying the Integration Pack

    After you download the integration pack file, you must register it with the Orchestrator management server and then deploy it to Runbook servers and Runbook Designers. For the procedures on installing integration packs, see How To Install an Integration Pack.

    Default Credentials

    Default credentials are used to store a common set of credentials that can be selected when configuring a HP iLO and OA connection.

    To set up default credentials

    1. In the Runbook Designer, click the Options menu, and select HP iLO and OA. The HP iLO and OA dialog box appears.
    2. On the Connections tab, click Default credentials to begin the setup. The Default credentials dialog box appears.
    3. In the User name box, enter a default user name.
    4. In the Password box, enter a default password.
    5. In the Key box, enter a default key Or click the ellipsis (...) button to browse and select a Key.
    6. Click OK to close the default credentials dialog box.

    Configuring the HP iLO and OA Connections

    Hp Ilo Application

    A connection establishes a reusable link between Orchestrator and a HP iLO and OA system. You can create as many connections as you require to specify links to multiple systems running HP iLO and OA. You can also create multiple connections to the same system to allow for differences in security permissions for different user accounts.

    To set up a HP iLO and OA connection

    1. In the Runbook Designer, click Options, and then click HP iLO and OA. The HP iLO and OA dialog box appears.
    2. On the Connections tab, click Add to begin the connection setup. The Connection dialog box appears.
    3. In the Name box, enter a name for the connection. This could be the name of the HP iLO and OA system or a descriptive name to distinguish the type of connection.
    4. In the Address box, type the name or IP address of the HP iLO and OA system. If you are using the computer name, you can type the NetBIOS name or the fully qualified domain name (FQDN).
    5. In the Port box, type the number of the HP iLO and OA system.
    6. Select Use default credentials to apply the default credentials to this connection. If you do this, then you can skip the next two steps.
    7. In the Username and Password boxes, type the credentials that Orchestrator will use to connect to the HP iLO and OA system.
    8. In the Private Key box, optionally specify the SSH key used to connect to the HP iLO and OA system.
    9. In the Attempts box, enter the number or times a command will attempt before failing.
    10. In the Time between attempts box, enter the number in seconds between each attempt.
    11. Click OK to close the configuration dialog box.
    12. Select the connection and click the Test button. Test connection succeeded will appear when the connection is valid. Click Finish.

    Exporting and Importing Connections

    Connections can be exported and imported into the connections list.

    To export a connection

    1. In the Runbook Designer, click the Options menu, and select HP iLO and OA. The HP iLO and OA dialog box appears.
    2. On the Connections tab, click Export to begin the export. The Save As dialog box appears.
    3. In the File name box, enter a name for the export file.
    4. Click Save to export.
    5. Click OK to close the configuration dialog box and then click Finish.

    To import a connection

    1. In the Runbook Designer, click the Options menu, and select HP iLO and OA. The HP iLO and OA dialog box appears.
    2. On the Connections tab, click Import to begin the import. The Open dialog box appears.
    3. In the File name box, enter a name for the import file.
    4. Click Open to import.
    5. Click OK to close the configuration dialog box and then click Finish.

    Configuring the HP iLO and OA Groups

    A group establishes a reusable list of connections between Orchestrator and a HP iLO and OA systems. You can create as many groups as you require to specify lists to multiple systems running HP iLO and OA.

    To set up a HP iLO and OA group

    1. In the Runbook Designer, click the Options menu, and select HP iLO and OA. The HP iLO and OA dialog box appears.
    2. On the Groups tab, click Add to begin the group setup. The Managed group dialog box appears.
    3. In the Group name box, enter a name for the group. This could be a descriptive name to distinguish the type of group.
    4. In the Available list, press the Ctrl button while clicking on the connections to select multiple connections. Press the >> button to move the connections to the Selected list.
    5. Click OK to close the configuration dialog box, and then click Finish.

    To batch update credentials on a group

    1. In the Runbook Designer, click the Options menu, and select HP iLO and OA. The HP iLO and OA dialog box appears.
    2. On the Groups tab, select a group and click Batch credential update.
    3. In the User name box, enter a new user name or leave blank to keep original.
    4. In the Password box, enter a new password or leave blank to keep original.
    5. In the Key box, enter a new key or leave blank to keep original.
    6. In the Port box, enter a new port or leave blank to keep original.
    7. Click OK to close the configuration dialog box, and then click Finish.