Softpanorama

May the source be with you, but remember the KISS principle ;-)
Home Switchboard Unix Administration Red Hat TCP/IP Networks Neoliberalism Toxic Managers
(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and  bastardization of classic Unix

Connecting to HP iLO via SSH

News HP iLO 4 Recommended Links  How do I reset the HP iLO
IP address and password
ILO3 TCP ports IPMI
Using virtual CDROM

iLO 3 -- HP engineering fiasco

Sysadmin Horror Stories

Humor Etc  

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):

hpiLO->

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

hpiLO-> {CLI command} 
status=0 
status_tag=COMMAND COMPLETED
...  command output ...
If an invalid command is entered, then the status and status_tag values reflect the error as shown:
hpiLO-> boguscommand
status=2
status_tag=COMMAND PROCESSING FAILED
error_tag=COMMAND NOT RECOGNIZED

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:

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

show /map1/firmware1
show

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

hpiLO-> show
status=0
status_tag=COMMAND COMPLETED
/
Targets
system1

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:

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 .


Top Visited
Switchboard
Latest
Past week
Past month

NEWS CONTENTS

Old News ;-)

[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

http://www.tricksguide.com/reset-hp-proliant-ilo-2-lights-out-hp-proliant-blade-server.html#comment-39514

[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:

C:\Program Files\HP\hponcfg>hponcfg /w iLoConfig.xml

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:

<RIBCL VERSION="2.0">
 <LOGIN USER_LOGIN="user" PASSWORD="password">
 <RIB_INFO MODE="WRITE" >
 <MOD_NETWORK_SETTINGS>
 <IP_ADDRESS VALUE = "x.x.x.x"/>
 <SUBNET_MASK VALUE = "x.x.x.x"/>
 <GATEWAY_IP_ADDRESS VALUE = "x.x.x.x"/>
 <PRIM_DNS_SERVER value = "x.x.x.x"/>
 <DHCP_ENABLE VALUE = "N"/>
 </MOD_NETWORK_SETTINGS>
 </RIB_INFO>
 </LOGIN>
 </RIBCL>

And then run the script like so:

C:\Program Files\HP\hponcfg>hponcfg /f your_script_name.xml

Hope that this information can be useful

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

... 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 [email protected]
[email protected]′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:[email protected]/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

HP Integrated Lights-Out - Wikipedia, the free encyclopedia

h20565.www2.hpe.com

HP Integrated Lights-Out 3 (iLO 3) - ; Manuals - HP Business Support Center

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>

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

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

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

    Base commands

    Network commands

    The network subsystems are located at:

  • dhcpendpt1

    Properties

    ◦ EnabledState

    ◦ OtherTypeDescription

  • dnsendpt1

    Properties

    ◦ EnabledState

    ◦ HostName

    ◦ DomainName

    ◦ OtherTypeDescription



    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 quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard 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 OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOSProgramming Languages History : PL/1 : Simula 67 : C : History of GCC developmentScripting 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-MonthHow 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 Least Technology 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-2021 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 NOTICE This 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