This can be useful for very, very seldom touched machines. Years after installation, if no-one can remember a login for the host, Ctrl-Alt-Delete will do proper shutdown and then let you use GRUB (or even LiLo!) to supply rw init=/bin/bash to the kernel and thus give you the chance to reset the root password.
The above is also a way that Ctrl-Alt-Delete is ...
The ILO port on the HP server by default asks for an IP via DHCP. So you just need to plug it into a network that has a DHCP server running. It will announce itself with a host name like ILOCZ12345678 which should make it easier to find in your router's DHCP lease table, or in e.g. journalctl/syslog if you run a DHCP server (e.g. isc-dhcp-server) on a system ...
Why do you want to specifically monitor the temperature data of the server?
Are you feeding it to a monitoring solution or NMS like OpenNMS, Zabbix, etc.? Or are you just concerned about the thermal health of the server?
The model of server matters a little, because different ProLiant systems have different temperature thresholds and thermal profiles. ...
Whereas an SSH connection transmits keystrokes, an HP ILO connection transmits key states. Each time you press a key, the server receives separate KeyDown and KeyUp events. The repeated keystrokes result when the KeyUp event is received late.
The two most likely reasons for the KeyUp event to be received late are:
Network congestion/performance issues.
You typically need to update to ILO3 version 1.28 and then move to version 1.50.
As you can can see below, I keep both ILO versions handy on my jump server, just in case I encounter an ILO3 with a <1.20 firmware version.
In the ILO firmware package README file:
PREREQUISITE: iLO 3 v1.20 BUILD DATE: 8/20/2012 EFFECTIVE DATE:
This Python module is likely meant to work with the individual and standalone server ILO interfaces.
It is probably not intended for use with C7000 and C3000 blade enclosure Onboard Administrator modules.
HP had a pretty awful initial set of firmware releases for the ILO3 management interface. See the massive changelog documenting the evolution of the product. I was working for a firm that deployed a large number of ProLiant DL380 G7 servers and had to deal with the pain of managing the buggy feature set.
In your case, you're trying to move from a very old ...
As far as I'm aware there's no standard hardware (or software) solution for this.
You can't Shoot The Other Node In The Head if it's not there.
You can handle this a number of different ways - one that I can suggest is using a Smart PDU - As a last resort when no other STONITH technique works command its power outlets "off" and you don't have to worry ...
If you have access to the operating systems running on the servers (you did not indicate which), you can program the ILO using the hponcfg utility.
The things you can do here are listed in the command's help, with the "-r" flag actually resetting the ILO to default. I would try something less sever first, like "-w" which writes the ILO's configuration to a ...
If you have ILO/IPMI/... It makes absolute sense. The only reason for CTRLALTDEL was a magic trap when nothing else would interrupt. With a control card, you don't need that - you can reset the machine anyway.
Needless to say, if the machine behaves correctly, you can always 'reboot'/'shutdown -r now'/'init 6'/'systemctl reboot' from console or gui.
Another disadvantage (don't know if this applies to all iLO versions and all Proliant models) is that when iLO is on shared port, it cannot communicate with host computer. So server can't even ping its own iLO IP address, although all other devices can - this is because of how this NIC sharing works.
Assuming you're talking about HP servers, out of the box the iLO is configured to get an IP via DHCP and have a hostname based on the serial number of the server. The server has this hostname and the default password written either on a removable tag, a sticker on the top of the server, or a pull-out tag on the front panel.
But if your iLO is actually ...
You could PXEboot or USB boot the systems into a thin linux image and use the hponcfg utility to set the ILO devices via XML config file.
You could ask HP or your vendor to preset the ILOs. I offer that service to clients.
Hire/contract a datacenter technician.
If your systems are co-located, use Smart Hands services.
You could enable DHCP (limit to a list ...
For Ubuntu there is no available firmware installer. Select the one for RedHat. You will get an .scexe file, which you can unpack:
$ chmod 740 CP022551.scexe
$ ./CP022551.scexe --unpack=/tmp/iLO3
$ ls -l /tmp/iLO3
There you have it: a ilo3_180.bin which you can upload with your iLO 3 web interface.
The firmware for that server is located on HP's website.
Here's where to get it.
Don't assume that a system this old has any recent firmware updates.
Here's your BIOS download.
Here's your ILO download.
Here's your RAID controller download.
Try using the the stress utility to generate load in Linux, please. It's very granular and makes more sense than what you're doing.
What I see you doing is generating a single-threaded I/O load on a 4-CPU virtual machine. The CPU graph you pasted-in from the vSphere client shows a 25% load because you're only straining one of the four CPU's assigned to the ...
Trash it :) Buy another for $75 (or less) on eBay.
Why did you clear the NVRAM? Was there a problem with the server after you were able to boot Ubuntu?
The normal approach for this is to leave the system powered off for some time... attempt power-on again.
For the ILO, you may not have an immediate solution.
I'd suggest the "HP ProLiant DL380 ...
Don't do anything. You've entered an ILO license key, so your server and ILO will continue operating with the ILO Advanced functionality. The warranty is just paper support.
To answer your question, though, the main difference between the ILO Advanced and unlicensed ILO is that the Advanced license can use remote console and remote media functions. That ...
iLO 2 supports IPv4 only. (Note that 2.12 was a security and bugfix release only, and added no new features.)
For IPv6 support, you need iLO 3, firmware revision 1.50 or higher, or iLO 4 (any firmware release).
You can prepare a XML file containing the settings and use a script that pushes it out to all nodes you want to update.
An example of how to do this can be found here
On how to prepare the XML (RIBCL) file, see the HP Lights Out Scripting Guide
Yes, the password on the asset tag is the default password for the Administrator account. The user name is "Administrator" (case-sensitive).
I'm curious as to why you're using ipmitool when there are already HP tools for managing the ILO subsystem. Look into the hponcfg tool, which has a specific set of commands for managing the ILO from within the host ...
This feature works perfect under Linux in Firefox and Chrome/Chromium browsers with IcedTee (OpenJDK) or Oracle java plugin installed (both 32- and 64-bit OS versions).
ServerEngines' java applet installs native library libm2-32.so (or libm2-64.so respectivly) which depends on libstdc++5, but modern Linux distros does not contain this library by default. ...
The ILO configuration can always be overwritten and configured using the BIOS utility. If in doubt, just reboot your server and hit F8 when prompted in the BIOS to enter the Lights-Out configuration utility. Double-check your settings there.
If you continue to have problems, consider a firmware update. HP has a bootable Firmware Update DVD that can be used ...
You could set everything in one place from the HP Onboard Administrator.
Through the GUI, the HPOA has password-less access to the individual server ILO interfaces.
Through the CLI, you can HPONCFG ALL HTTP://some.host.ip/iloconfig.xml to take care of all devices using one iloconfig.xml file.
I simplified the script and changed all our iLO passwords with:
for ip in $IPs
echo Starting $ip
sshpass -p 'PWOLD' ssh -o StrictHostKeyChecking=no -l Administrator $ip "set /map1/accounts1/Administrator password=PWNEW"
Works like a charm! Many thanx for the inspiring example! (Typo with IPs is corrected!)
The HP recommended way is to install the Proliant Support Pack for your operating system (regardless) with the HPONCFG and iLO Management Interface Driver.
Then run the %Program files%\HP\hponcfg\hponcfg /a /w C:\ilo-config-output.txt command to dump the complete ILO configuration to C:\ilo-config-output.txt. Then Python away.
Google for "HP iLO 3 ...