Physical Server iLO Network Interface Failure

Question

Physical Server iLO Network Interface Failure

Liam Wilson 40

The server’s iLO (Integrated Lights-Out) management interface stops responding to both ping and HTTPS/Web UI access, while the host OS and production workloads remain fully operational. The issue appears isolated to the iLO management processor, and a physical power cycle is not desirable because the server is running critical workloads.

What is the recommended way to safely reset or restart the iLO management processor from the host OS using CLI tools, without rebooting or interrupting the operating system?

0 comments

1 answer

Your answer

Answer 1

Hello @Liam Wilson

Welcome to Microsoft Q&A!

Thank you for your patience and for detailing your concern.

Recommended Resolution

On HPE ProLiant servers, the iLO management processor can be restarted without rebooting the host OS or interrupting workloads.

Methods from the Host OS

1. Use the HPE iLO command line utility (hponcfg)

Included with the ProLiant Support Pack or available separately.

Run from an elevated prompt:

powershell

hponcfg /reset

This restarts the iLO processor only.

2. Use RIBCL or RESTful API scripts (if accessible)

Example RIBCL snippet:

xml

<RIBCL VERSION="2.0">
  <LOGIN USER_LOGIN="admin" PASSWORD="password">
    <RIB_INFO MODE="write">
      <RESET_RIB/>
    </RIB_INFO>
  </LOGIN>
</RIBCL>

Execute with:

powershell

hponcfg /f filename.xml

3. Use HPE utilities (Linux)

Tools like hpasmcli provide: Code
```
  reset ilo
```

Note:

The reset affects only the iLO management processor.
Host OS and workloads remain fully operational.
Active iLO sessions (Web UI/SSH) will drop but reconnect once iLO restarts.
Keep iLO firmware updated to minimize hangs.

I hope this clarifies the safe way to reset iLO without impacting production workloads.

If this information was helpful, please click Accept Answer.

Thank you for choosing Microsoft Q&A.