ILO 5 - after firmware upgrade to 3.06 cant connect from outside of network

[Axl_1971]

My system details

ProLiant ML350 Gen10

iLO 5 - Firmware Version 3.06 Jul 10 2024

I upgraded the ILO 5 firmware from 3.01 to 3.06 and now I cannot connect via web browser or PING the ILO port when outside of the network.

However when I am on the same subnet as the ILO, I can connect via web browser and PING the ILO port. But when outside of the subnet I am unable to do so.

Just to clarify this was working perfectly on firmware 3.01 - since upgrading the firmware this issue has occured.

I did notice in the ILO log this after firmware upgrade

Duplicate IP address 10.9 detected on network. 

The 10.9 is the subnet of the ILO.

The IP address has not changed and from a network perspective no issues. I have checked networking side on the switch (Cisco 2960x) and can see the port connected and MAC address of the ILO is mapped correctly to the switch port where the ILO is connected.

This is very odd, is there some issue with 3.06 firmware.

[thutchings]

Hello,

Are you using the Shared Network Port (SNP) in your environment? There is an issue currently under investigation at the development team related to communication issues from different network segments when running iLO firmware 3.05 or 3.06. This is most commonly observed with the SNP. There is another similar, but different, issue with the dedicated port that could result in a similar behavior, but the cause is different.

The message about the duplicate IP is unrelated and does not seem to have any ill effects. This is also under investigation.

Regards

[support_s]

System recommended content:

1. HPE iLO 5 3.06 User Guide | iLO network connection options

2. HPE iLO 5 3.06 User Guide | iLO access settings options

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[Axl_1971]

I am using a dedicated port. 

Should I downgrade the firmware to 3.01

[thutchings]

Hello,

Yes, I would recommend downgrading the firmware to, at least, version 3.04. A new iLO firmware version is in the works. I believe the new version will contain the fix for this, but it's not clear yet what the timeline is for that. FYI...when I was talking about SNP I meant Shared Network Port (SNP), not Simple Network Time Protocol (SNTP).

Regards

[Axl_1971]

I am not using SNP, but have a dedicated network port for the ILO

I will downgrade to the version it was on before 3.01

[Amjad_kasem]

The issue you're experiencing after upgrading the iLO 5 firmware to version 3.06 likely involves network configuration changes or new features in the update. Here are steps to troubleshoot and resolve the connectivity issue:

1. Check for Duplicate IP Addresses:
- The log entry "Duplicate IP address 10.9 detected on network" suggests an IP conflict. Verify no other devices use the same IP as the iLO interface.

2. Verify iLO Network Settings:
- Ensure the iLO network settings (IP address, subnet mask, gateway) are correctly configured. Check for changes or resets during the firmware update.
- If using DHCP, confirm the DHCP server provides the correct IP configuration.

3. Update Network Configuration:
- Verify network configuration on the iLO and switch, including VLAN settings if applicable.
- Ensure the port settings on the Cisco 2960x switch (VLAN assignment, speed, duplex settings) are correct and unchanged.

4. Check Firewall and Security Settings:
- Ensure no firewall rules or security settings block iLO access from outside the subnet.
- Verify if Access Control Lists (ACLs) or network security groups restrict access.

5. Review iLO Network Services:
- Confirm all necessary network services on the iLO are enabled (e.g., HTTP/HTTPS for web access, ICMP for ping responses).
- Ensure the iLO's network interfaces are correctly configured and any bonded interfaces function properly.

6. Rollback Firmware:
- If the issue persists, consider rolling back to the previous firmware version (3.01) to determine if the problem is specific to version 3.06.

[Axl_1971]

No changes done to the network infrastructure, and I was able to connect from outside of the subnet, once I upgraded the firmware the issue occured.

Taking the above statement into account, and the only vartiable that has changed is the ILO version therefore, one can assume 3.06 has some known issue with accessing from a different subnet.

I plan to roll back later on and will feedback on this issue.

[Axl_1971 · Accepted solution]

I have reverted the firmware to 3.01 and the issue is resolved and I can access from remote site.

I plan to apply firmware 3.04 next week and see if the issue occurs again.

[Sunitha_Mod]

Hello @Axl_1971,

Perfect! 

We are glad to know the issue has been resolved. 

[marciocosta]

Same issue here, reverted from 3.06 to 30.3

It's unbelievable that this hasn't been fixed yet.

[Mr_Techie]

@marciocosta 

Good Day! you should refer thutchings reply here: 

"Hello,

Yes, I would recommend downgrading the firmware to, at least, version 3.04. A new iLO firmware version is in the works. I believe the new version will contain the fix for this, but it's not clear yet what the timeline is for that. FYI...when I was talking about SNP I meant Shared Network Port (SNP), not Simple Network Time Protocol (SNTP).

Regards"

[ClemmondBest]

Our network engineer found the issue after extensive diagnostics. The firmware upgrade to 3.06 appears to ignore the IP default gateway after the initial iLO reboot. Resetting the iLO once more solved the routing issue and we could access it from another subnet.