ILO 5 TCP Socket limitation

[RalphOV]

Hi,
I have an issue where my ILO keeps losing connection randomely, After troubleshooting with HPE the problem came from my enterprise security scanner.
HPE told me the limitation is around 200, more and glitches and disconnection will occur, when that happens we get alerts.

Since the security team won’t budge to help, I'm looking for a workaround.
Is there a way to increase that limit or to force close the open port or better yet, is there a way to schedule a reboot of an ILO?

Thank you,

[support_s]

System recommended content:

1. HPE iLO 5 Troubleshooting Guide | iLO TCP/IP communication fails

2. HPE iLO 6 Troubleshooting Guide | iLO TCP/IP communication fails

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

Thank you for being a HPE valuable community member.

[BunnyPon]

I am sorry, that answer has nothing what so ever to do with his problem.

[Rama2]

Since ILO keeps losing connection randomly. Need to know what limitation you are referring to as '200'. Since it's specific to the environment, we need to conduct extensive analysis. Hence, I recommend you to raise a support ticket with HPE.

[RalphOV]

Hi,
I did open a ticket, that's why I know about the limitation.. ILO 5 have a limitation of 200 tcp socket, passed that threshold random disconect can and will appen.
Since HPE pointed the problem to our security scan they close the case and my security team won't budge, that's why i'm looking for a workaround here.

Thank you,

[BunnyPon]

At this point, to use the technical term, you are screwed.

Choices are, firewall out your security wonks,  everytime something breaks because of them open a trouble ticket until they get so upset at your wasting their time they do something, go over their heads to management and point out they are breaking stuff, considering alternative employment may not be possible.

ILO5 is only this cute toy chip on the M/B, I'm impressed it can cope with 200 at all, especially if it's that redfish rubbish.

What are they doing, port scanning? You might be able to change the ports, or add a static route to make them unable to connect. \\^^// (May not be recommended if management don't love you to bits.)

[Rama2]

The TCP sockets limitation refers to the maximum number of concurrent TCP connections that a system can handle.

The limitation you mentioned about TCP sockets is as per design. ILO seems to have been reached because of security scans in the environment being run against the iLO's.

No possible workaround available from the ILO side. Maybe you can try to slow the scan down so that the number of sockets is not exceeded

[RalphOV]

Not easy to go over the security teams nowadays, they are God likes in our company since it's a financial institute.
That is why I was first looking for a work around here, either a way to increase the limitation or a way to schedule reboot the ILO once a week.

But there are not options for scheduling periodique reboot of an ILO, but maybe someone has a workaround to schedule the reboot.

It would be a practical feature and can't be that hard to implement.