Any way to recover iLO access remotely if its IP stops responding?

If you can get into Windows, check for HPE’s iLO configuration utility, commonly HPONCFG. Depending on the server generation and installed tools, it can report or change iLO settings from the host OS. Check the current configuration before changing anything, especially the network interface and address.

A host reboot does not necessarily reset the separate iLO management controller. The exact options and utility version vary by hardware, so confirm compatibility for that server model.

First see whether the OS is reachable by another route, such as RDP or a remote management tool from a machine on the same network. If you can get a session, you may be able to restore the services you need without iLO.

Also check the switch port and the configured iLO address against the network records. If the address is static and there is no corresponding MAC activity, that points toward a link, cabling, port configuration, or controller issue rather than a DHCP lease problem.

Worth checking whether iLO uses a dedicated management port or shares a network interface with the server. With shared networking, trying to reach the management address from the host itself may not work as expected. Test from another machine on the relevant network, and verify the cabling and switch port if you can inspect them remotely.

Do a careful address check before assuming the controller is dead. Look at the switch’s MAC table for the iLO port and scan only the appropriate subnet from a permitted machine. That can reveal a changed or unexpected address, but don’t assign a new address blindly if the iLO configuration is static.

If there is no link or MAC activity and the in-OS utility cannot reach the controller, remote options may be limited. At that point, someone onsite may need to check the physical connection or controller.