Connections to Com

[MRyan1]

Greetings

Can you answer a few questions on Com with ILO?

What is the process to form connection to the app with a DL server ?

Does this stay connected or do I need to reestablish a connection after login/logout?

Does a ILO update make changes that require that I re-estab connection?

Any other concerns on a disconnection event?

MattRyan

[Mark-S · Accepted solution]

Hello Matt

Thank you for your question regarding HPE GreenLake for Compute Ops Management and iLO.

As part of the iLO-to-Compute Ops Management communication flow, during the Connect phase from the iLO interface, a wss (WebSocket) connection is established with Compute Ops Management (COM-region specific) that allows for asynchronous communication. So whether you are logged into the application or not, the Server will be connected to COM.

In the event of a network issue that creates a disconnect (WebSocket closed) the iLO interface will retry to establish the WebSocket connection back to Compute Ops Management. Additionally activities like a "Reset" of the iLO interface or a Firmware Update to the iLO would trigger a disconnect but as stated before, the iLO interface will retry once available to establish the connection back.

The only exceptions would be if the user initiates a "Disconnect" from the iLO to the web-based management application or if the user performs a factory reset of the iLO interface. Both of these situations would require user interaction to re-establish a connection back to Compute Ops Management.

Again connections to HPE GreenLake are made with HTTPS and TLS v1.2 and when web-based management is enabled in the HPE iLO a WebSocket using mTLS will be established between HPE iLO and Compute Ops Management. This WebSocket is permanent and would only be permanently disabled if web-based management is disabled.

For more details regarding iLO, Compute Ops Management and security,
visit our Compute Ops Management Security Guide 

Thank you

HPE GreenLake for Compute Ops Management Team

[MRyan1]

Okay it makes sense that is related to opening and closing @ WebSocket allowing information to flow across and update app and pass information back through for status.

thanks for the links.

Matt