Where to post bug reports for ILO

[tricktracktruck]

Hi.

I already posted a bug report here some time ago but no reaction at all.

What is the best way to report this bug (related to ILO) so that it can be fixed in future releases?

Thanks.

Regards

tricktracktruck

[Jimmy Vance]

For official support by HPE you need to open a support case.  Even though some of us who work for HPE participate here, these forums are community/user supported.

That being said I quickly glanced through your posting history and going by the titles I don't see a post about iLO. What is the issue?

[tricktracktruck]

Hi Jimmy.

Thanks for your fast response.

The reason you don't find it in history is that it has been posted under our HP partner related account.

Description of the issue follows:

When you query ILO health status via RIBCL and are running VSphere ESXi (agentless management service is the component involved here) NIC status changes are not reflected in the response. To get theses changes also via RIBCL script you have to visit the ILO web frontend interactively and click "System Information -> Network". When you do this you first see that the wrong status is also displayed here for a few seconds but then it is updated. After you do that interactively the correct status is also reported via RIBCL script. So to sum it up: to get correct NIC information via RIBCL script an interactive visit of the ILO web fronbtend is necessary which defeats the purpose of scripting at all.

The described behavour also matches for other NIC related properties as well like "PORT_DESCRIPTION". If you reboot the server this filed stays empty via RIBCL script until you visit ILO web fronbtend and click "System Information -> Network" once.

You find all this information under the following XML node within the response:

"RIBCL/GET_EMBEDDED_HEALTH_DATA/NIC_INFORMATION".

The resaon I mentioned agentless management service prior is that these informations are delivered via this service to ILO as ILO management processor cannot query these information directly but it has to be delivered from running OS via this service.

Last thing to mention is that this seems to be a regression bug. From our obersvations It has been introduced by the ILO version where teaming support has been buildt in.

HTH.

Regards

tricktracktruck

[tricktracktruck]

On addition:

The issue has been observed on all DL380/ML350 gen8 + gen9 servers having ILO4.

[Jimmy Vance]

Pleas open a support ticket so this can be tracked and addressed by the iLO team. Have support document all the information yo've provided here

[Dennis Handly]

>that it has been posted under our HP partner related account.

It would helpful if you included a link to that topic.