ilo 2 firmware v2 - certificate FQDN

[dhermans]

nice to hear that this issue has been fixed in the latest firmware.

Has anyone tried it?
I set Domain name to 'Fully Qualified Domain Name' and generated a cert.

it creates the CN without a '.' between hostname and domain name. No biggie, set the network/domain name to .domain.name instead of domain.name and restart

now the CSR looks good, sign it with an OpenSSL CA i use, import it and restart.

upon restart it's back to the original default cert. Try to import the cert again - also fails as the private key is no longer in memory.

Anyone tried this and got it to work?
Surely it was tested so must be something I'm doing!!!!

[dhermans]

anyone from HP monitor these forums?
anyone read these forums?

[R9Y]

Yes, I've tried and have the same issue with the first . missing at the start of the domain name and the amusing fact it doesnt seem to actually import the certificate.

Oh well.. 2.1 please...

[Oscar A. Perez]

The new certificate does get imported but because of the missing DOT in the FQDN, the new certificate is marked as invalid and replaced by the default one when iLO2 reboots.

This issue is going to be fixed in iLO2 2.10

[dhermans]

Any timeframe when firmware 2.10 will be out?

Logged a call on this, after 9 days of inactivity it was just closed!

Seriously terrible support

[Gerrit Heinen - T-ICT B]

anybody from HP who can give a timeline?

*kick*

[Chris Paalman_1]

"Surely it was tested", very interesting observation.

If one of the bullet points about iLO firmware v2 is the ability to use FQDN, one would hope at least a single Q/A person would have tested this and found the problem.

I'm embarrassed for ever convincing the boss to dump our KVM solution for iLO.

[dhermans]

if anyone wants a laugh or is wondering how efficient HP support is actually logged a call on this issue. here is what i have experienced:

12-july - logged

9 days no updates
21-july - comment "Incident was misrouted to HpSw Ovsc."

3 days no updates
24-july - a 'we're working on this with a high priority' comment

6 days and counting with no updates

[Oscar A. Perez]

iLO2 2.01 with the fix for this FQDN bug is being tested right now.
I will post an update here as soon as 2.01 gets signed off.

[Oscar A. Perez]

iLO2 Firmware version 2.01 has been released.

Windows Online Component:
ftp://ftp.hp.com/pub/softlib2/software1/sc-windows-fw-ilo/p1443420321/v63248

Linux Online Component:
ftp://ftp.hp.com/pub/softlib2/software1/sc-linux-fw-ilo/p1285463034/v63249

[DTriplett]

I've been able to get this to work using FW 2.01 and the iLO2 GUI. However, there doesn't seem to be any documentation on setting the domain name entry in the SSL Certificate screen to "Fully Qualified Domain Name" from "Short Name" via script. I need to be able to set this before issuing the Certificate Signing Request (also via script).

Has anyone been able to figure this one out yet?

David

[Anonymous]

I'm Also Looking for documentation on how to set the SSL Certificate to FQDN from shorthost via RIBCL..

Having been working on this for several months now it is growing increasingly frustrating :)

[Oscar A. Perez]

Please try

[DTriplett]

Thanks, Oscar! That worked great!

[Jiri Konecny]

Is there a way to generate CSR for FQDN and short iLO hostname at the same time?