ILO5 ver. 3.05 - access via IPv4

[Jiri3]

Hello guys,  

our machine Proliant DL360 Gen10 has a ILO5 version.  3.04 has a Network configured as a Shared LOM.
It is setting IPv4 and IPv6 access via the web and remote console as well.

After upgrading the firmware to version 3.05, access via the IPv4 address stopped working.
Access via IPv6 works normally.

Where is a problem? How to renew IPv4 access?

Thank Jiri

[rabindra11sharm]

Dear  Jiri3

you have to check is there ipv4 IP address configured correctly or not. Please download HPE Lights-Out Online Configuration Utilityand install in to your server, from there you can check or configure iLO with out restarting your server.

If IP address not configured for ipv4, please configured as per your network configuration. if already configured, please restart iLO management controller. and check. there is possibilities after upgradation of iLO firmware it auto matically switched to default iLO port, that is why you are not able to access it.

I could provide you with clear and helpful instructions. If you have any more questions or need further assistance, don't hesitate to ask. we are here to help you!

Have a great day!

[Jiri3]

Dear Rabindra,

thank you for the quick reply. Our server has been running ipv4/ipv6 without problems
for three years, up to version 3.04. The problem occurred only after upgrading to ver. 3.05.  

However, it does not run as a windows server, but linux/debian. is there a mentioned
Configuration Utility and Managemewnt Controller for linux too?

Thank Jiri

[Jiri3]

Dear Rabindra,

I installed the hponcfg binary on our server.  configuration listing of both versions, 3.04 and 3.05 are identical.  I restarted the ILO controller but the result is the same. IPv4 does not work.

Thank Jiri

[rabindra11sharm]

Dear Jiri

you can check your iLO configuration by restart your server prss F10 intelligent Provisioning option. or F9 Setup utility for RBSU menu > System configuration > iLO5 configuration utility >Network option . 

if you want install tools on your linux OS, Please download HPE Lights-Out Online Configuration utility.

[Jiri3]

Dear Rabindra,

thank you for your advice and recommendation. If the server needs to be restarted, I have a few days
wait until the company allows me to interruption.

I tried one thing: downgrade ILO 3.05 to 3.04. Then access via IPv4 works again.
Then I thought, what if we wait for the release of the next version of ILO, for example 3.06.
Just skip version 3.05.

What would be the result?

Jiri

[rabindra11sharm]

Dear Jiri

Do one thing, log in via IPV6 as you earlier mentioned that you are able to login via IPV6.  It's a SLAAC conection for dedicated network port. you can log in to iLO web page, then configure as per your requairment by selecting iLO Shared Network Port.

[Jiri3]

@rabindra11sharm Dear Rabindra,

This is nothing new, we have had our servers and the web ILO interface installed like this for three years:
- IPv6 connection i s SLAAC-DHCPv6-static.routing - it works stable all the time
- IPv4 connection is static.routing - it works up to firmware version 3.04.

So I have no problem configuring anything, but I would need to find out the cause IPv4 failures when upgrading 3.04 -> 3.05. 

Jiri

[rabindra11sharm]

Dear Jiri3

- IPv6 connection i s SLAAC-DHCPv6-static.routing - it works stable all the time, for dedicated iLO network port. but you configure IPV4 for shared network port. 

So please check the configuration page, is it still showing as configured, or it is changed its configuration. If configuration changed., Please reconfigure it.

[Jiri3]

Dear Rabindra,

our configuration page still shoving as configured for shared network port, it is unchanged. On web ILO intrface, and on HPONCFG as well. I think there will be no problem in the configuration, because the same configuration works on version 3.04.

Upgrade ILO firmware to version 3.05 we performed on web page from ilo5_305.bin or on IloRest from ilo5_305.fwpkg as well  lternatively. Checksum verified. Resetting the ILO doesn't change anything. Still IPv4 does not work.

And if we downgrade ILO firmware back from 3.05 to 3.04, access by IPv4 will start again.

Jiri

[Jiri3]

Dear Rabindra,

do you still think there is a configuration error?

**REMOVED** The Release version of iLO 5 v3.05 has exposed a bug, when the host server is installed with NS204i boot controllers. A new iLO 5 version fixing the issue will be released in the next couple of days. This component provides updated iLO firmware that can be installed directly on supported Operating Systems. This component can also be used to obtain the firmware image for updating via iLO user interface, utilities, or through the scripting interface. Additionally, this component can be used with the Smart Update Manager.

Jiri

[tjcolby13]

Yes, 3.05 breaks connectivity for us too.  Also on Gen 11, FW 1.60 breaks them too.  

[tjcolby13]

FYI FW 3.,05 breaks connectivy for us too.  Downgrading back to 3.02 works.  The latest FW is also broken on Gen 11.  1.60 is bac.

[SimeTom]

It looks like a common problem with 3.05 and 3.06.

On a few ML110 Gen10 I've upgraded from 3.04 to 3.05 and I lost access. Even resetting iLO with iLO configuration utility didn't helped.

After downgrading to 3.04 I got the connection again.

Today I tried upgrade to 3.06 and I lost connection again. I had to downgrade it from 3.06 to 3.04.

3.07... to be...

[Jiri3]

Dear Rabindra,

do you still think there is a configuration error?

And  new version 3.06 from yesterday do not work too.!!!!!

**REMOVED** The Release version of iLO 5 v3.05 has exposed a bug, when the host server is installed with NS204i boot controllers. A new iLO 5 version fixing the issue will be released in the next couple of days. This component provides updated iLO firmware that can be installed directly on supported Operating Systems. This component can also be used to obtain the firmware image for updating via iLO user interface, utilities, or through the scripting interface. Additionally, this component can be used with the Smart Update Manager.

Jiri

Jiri

[Jiri3]

Dear Rabindra,

our configuration page still shoving as configured for shared network port, it is unchanged. On web ILO intrface, and on HPONCFG as well. I think there will be no problem in the configuration, because the same configuration works on version 3.04.

Upgrade ILO firmware to version 3.05 we performed on web page from ilo5_305.bin or on IloRest from ilo5_305.fwpkg as well  lternatively. Checksum verified. Resetting the ILO doesn't change anything. Still IPv4 does not work.

And if we downgrade ILO firmware back from 3.05 to 3.04, access by IPv4 will start again.

Jiri

[thutchings]

Hello,

Hello,

When attempting to access the iLO is this being done from a different network or the same network? Has an attempt been made via the local network? If it does work on the local network, then I suspect the iLO is responding to a router advertisement being sent out on the network, so the traffic may be getting to the iLO, but it is sent to the incorrect gateway.

I have upgraded multiple servers to 3.05 (iLO 5) and 1.60 (iLO 6). None of these have had issues with connecting to them in the lab environment I have access to.

Regards

[Jiri3]

Dear Thutchins,

Access the ILO is being done from different (external) network. Access via local network does not work

So we have it set to the same onfiguration from 2020 year and firmware version 2.12. It still works on version 3.04,
but stopped on .05 or 3.06.

Regards

Jiri

[tjcolby13]

We have the same issue., with both 3.06 (gen10)and 1.61 (gen11)  Try these ip addresses in your lab.  I would also be happy to show you what happens via a teams meeting.

Server:  192.168.4.150/23 gw 192.168.4.1

ilo: 192.168.40.150/22 gw 192.168.40.1

Wordstation 192.168.4.10/23 gw 192.168.4.1, 192..168.40.10/22

[thutchings · Accepted solution]

Hello,

@tjcolby13  I see from the original post that @Jiri3 is using the Shared Network Port (SNP) feature with the iLO. Are you also using the SNP? If so, then I think both of you are running into a problem related to a case being worked now with the iLO development team. I would recommend both of you getting a case created with HPE support for this problem.

Regards

[tjcolby13]

I have open cases, for Gen 10 and Gen11.   I'm not getting help. They keep trying to point the finger at other things.  Which is why I posted in the first place.  

[Jiri3]

Hi tjcolby,

please can you your email address private? It will better to write directly

I can to open our case and to wait and share results… Do you have some case open already?

Grus

Jiri

[Jiri3]

Helo Thutchings,

thank you for the quick and clear explanation. I created and registered the case and I believe that your ILO development team the problem will be solved soon.

Regards

Jiri

[FrancWest]

Beware when upgrading from 3.05 to 3.06, we were hit hard by this bug.

https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00141858en_us

HPE doesn't mention this when downloading the 3.06 ILO update.

[tjcolby13]

So far support has not been helpful.  I am very frustated.  I have tickets for both iLo5 on Gen10 and iLo6 Gen11.   They don't seem to belive us.

Gen 10

Starting verision;

[root@tlae300 ~]# hponcfg

HPE Lights-Out Online Configuration utility

Version 6.0.0 Date 10/30/2022 (c) 2005,2022 Hewlett Packard Enterprise Development LP

Firmware Revision = 3.02 Device type = iLO 5 Driver name = hpilo

C:\WINDOWS\system32>ping tlae300-ilo

Pinging tlae300-ilo.exodus1.gk [192.168.40.150] with 32 bytes of data:

Reply from 192.168.40.150: bytes=32 time<1ms TTL=252

Reply from 192.168.40.150: bytes=32 time<1ms TTL=252

Reply from 192.168.40.150: bytes=32 time<1ms TTL=252

Reply from 192.168.40.150: bytes=32 time<1ms TTL=252

Ping statistics for 192.168.40.150:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Upgraded to 3.06            

[root@tlae300 ~]# hponcfg

HPE Lights-Out Online Configuration utility

Version 6.0.0 Date 10/30/2022 (c) 2005,2022 Hewlett Packard Enterprise Development LP

Firmware Revision = 3.06 Device type = iLO 5 Driver name = hpilo

C:\WINDOWS\system32>ping tlae300-ilo

Pinging tlae300-ilo.exodus1.gk [192.168.40.150] with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Ping statistics for 192.168.40.150:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Downgrade back to 3.02

[root@tlae300 firmware-ilo5-3.02-1.1]# ./hpsetup

Flash Engine Version: 2.6.2.0

Name: Online ROM Flash Component for Linux - HPE Integrated Lights-Out 5

New Version: 3.02

Current Version: 3.06 (07/10/2024)

The software is installed, but the installed version is

newer than the version you are attempting to install.

Do you want to downgrade the software to an older version (y/n) ?y

Flash in progress -- Do not interrupt or your system may become unusable.

Working........................................................................................................................................................................................................................................................................................................................................................

The installation procedure completed successfully.

C:\WINDOWS\system32>ping tlae300-ilo

Pinging tlae300-ilo.exodus1.gk [192.168.40.150] with 32 bytes of data:

Reply from 192.168.40.150: bytes=32 time<1ms TTL=252

Reply from 192.168.40.150: bytes=32 time<1ms TTL=252

Reply from 192.168.40.150: bytes=32 time=1ms TTL=252

Reply from 192.168.40.150: bytes=32 time<1ms TTL=252

Ping statistics for 192.168.40.150:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 1ms, Average = 0ms

Gen 11

Starting version 1.57

[root@tlae600 ~]# hponcfg

HPE Lights-Out Online Configuration utility

Version 6.0.0 Date 10/30/2022 (c) 2005,2022 Hewlett Packard Enterprise Development LP

Firmware Revision = 1.57 Device type = iLO 6 Driver name = hpilo

C:\WINDOWS\system32>ping tlae600-ilo

Pinging tlae600-ilo.exodus1.gk [192.168.42.123] with 32 bytes of data:

Reply from 192.168.42.123: bytes=32 time=1ms TTL=252

Reply from 192.168.42.123: bytes=32 time<1ms TTL=252

Reply from 192.168.42.123: bytes=32 time<1ms TTL=252

Reply from 192.168.42.123: bytes=32 time<1ms TTL=252

Ping statistics for 192.168.42.123:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 1ms, Average = 0ms

After upgrade to 1.61

[root@tlae600 ~]# hponcfg

HPE Lights-Out Online Configuration utility

Version 6.0.0 Date 10/30/2022 (c) 2005,2022 Hewlett Packard Enterprise Development LP

Firmware Revision = 1.61 Device type = iLO 6 Driver name = hpilo

C:\WINDOWS\system32>ping tlae600-ilo

Pinging tlae600-ilo.exodus1.gk [192.168.42.123] with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Ping statistics for 192.168.42.123:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Afer Downgrade to 1.59

[root@tlae600 firmware-ilo6-1.59-1.1]# ./hpsetup

Flash Engine Version: 2.6.2.0

Name: Online ROM Flash Component for Linux - HPE Integrated Lights-Out 6

New Version: 1.59

Current Version: 1.61 (07/10/2024)

The software is installed, but the installed version is

newer than the version you are attempting to install.

Do you want to downgrade the software to an older version (y/n) ?y

CAUTION: A Trusted Platform Module (TPM) has been detected in this system.

Failure to perform proper OS encryption procedures will result in loss of

access to your data if recovery key is not available. Recommended procedure

for Microsoft Windows(R) BitLocker(TM) is to "suspend" BitLocker prior to

System ROM or Option ROM firmware flash. If you do not have your recovery key

or have not suspended BitLocker, exit this flash: Failure to follow these

instructions will result in loss of access to your data.

Do you want to continue now? yes

Flash in progress -- Do not interrupt or your system may become unusable.

Working.........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

The installation procedure completed successfully.

C:\WINDOWS\system32>ping tlae600-ilo

Pinging tlae600-ilo.exodus1.gk [192.168.42.123] with 32 bytes of data:

Reply from 192.168.42.123: bytes=32 time=1ms TTL=252

Reply from 192.168.42.123: bytes=32 time<1ms TTL=252

Reply from 192.168.42.123: bytes=32 time<1ms TTL=252

Reply from 192.168.42.123: bytes=32 time<1ms TTL=252

Ping statistics for 192.168.42.123:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 1ms, Average = 0ms