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 ...
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 ...
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.
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.
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.
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 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.
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 ...
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.
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 ...
For convenience, the latest versions of the firmware are being tracked at https://en.wikipedia.org/wiki/HP_Integrated_Lights-Out, and independently by http://pingtool.org/latest-hp-ilo-firmwares/.
At time of writing (Jan 2022), they are:
ILO1 : ilo196.bin (30-Apr-2014) (Search)
ILO2 : ilo2_233.bin (30-Mar-2018) (Search)
ILO3 : ilo3_194.bin (iLO3 v 1.94, 17-...
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 ...
The hp-ilo package doesn't need to exist anymore on modern Linux systems, since the driver is now part of the mainline kernel (since 2.6.33 or thereabouts).
It should not be necessary to do anything with a standard kernel on any mainstream Linux distribution, since they all build the hpilo module and make it available by default.
However, you seem to have ...
The python-hpilo module can only speak to iLO interfaces, either using hponcfg to talk to the local iLO, or via the network. It cannot use the chassis onboard administrator, as it does not expose the same XML interface.
I feel that the chances of accidental reboot via ctrl-alt-delete are much greater than the chances of a server's root password being forgotten, and therefore in production environments it makes sense to disable ctrl-alt-delete. I personally do this on my production systems.
The chances of a hard powercycle on a running linux host causing unrecoverable data ...
You can configure the iLO/IPMI based fencing, and then using for example fence_apc fencing agent with an APC power switch as a secondary fence device. That way, if the server loses power, then the secondary fencing agent is still able to STONITH the server in a way that makes sense to the cluster.
like described here:
A node can have multiple fence ...
Online ROM Flash Component for Windows - HP Integrated Lights-Out 3
(changelog is here)
Download from HP and extract to your PC. You'll see a .bin file in the resulting directory. You can upload that to the ILO firmware page.
You can update all of the system firmware using the HP Service Pack for ProLiant (HP SPP) DVD download. You can update ILO firmware ...
You don't really need to remove the ILO license. Nobody is going to care, and HP isn't interested in auditing the license status of such an old server.
But if you can open an SSH connection to the ILO using username: Administrator, just run:
delete /map1 license
That's all you'll need.
Edit: My mistake. This server is a ProLiant DL160 G5, so it doesn't ...
I'd suggest calling an HP technician to come onsite and look at this. You're working with such scant details, that it's nearly impossible to provide good information to you.
First: Did you look at the front display to check overall health status?
Green is good. Anything else is bad.
The C7000 chassis is controlled by the Onboard Administrator. That's the ...
First of all: the issue is not related to SHA-1.
The issue is that iLO2 doesn't support TLS >1.0, and TLS 1.0 has been disabled in Chrome.
I don't think this one can be solved without intervention from HP.
Assuming your Linux system is functioning, you can install the iLO online configuration utility (hponcfg). You can use it to get the iLO's configuration or reconfigure it. The configuration is in XML format.
You didn't mention which flavor of Linux you're using, but HPE makes hponcfg packages available for numerous distributions in their Software Delivery ...
It doesn't look like you can do it via so called SMASH CLP (ILO4 CLI) as there is no /system1/drives* target, but you can do it via RIBCL XML.
You can download archive with samples of RIBCL scripts from here
You will need to use locfg.pl perl script against Get_Embedded_Health.xml file.
Then execute it against ILO IP address
./locfg.pl -s 192.168.10.10 -f ...
There isn't too much you can do about this.
Please run the normal firmware updates on the host either via Intelligent Provisioning or the HP SPP bootable DVD.
But since Gen8 systems are end-of-life, there isn't much incentive for HPE to deal with this issue. I've seen this in about 5% of Gen8 servers still in the field.
This should not impact the ...
There is actually a procedure described by HP to correct the problem with the embedded NAND Flash.
We had the same problem and the procedure described in the advisory has corrected the error. After the NAND flash format our server needed a power off and a disconnect from the main power supply. After the following boot the iLO Health was o.k.
Place your ILO, IPMI, DRAC and other management devices on their own management VLAN or network. Secure access to that network with VPN or prevent Internet connectivity. Only allow access from trusted networks.
That's an acceptable way of mitigating the (still narrow) risk you outlined.
You can also disable access to the ILO devices until an updated ...