Remote Lights-Out Mgmt (iLO 2, iLO, RILOE II) Forum
Showing results for 
Search instead for 
Do you mean 

Unable to communicate with the RILOE-II/ilo

Advisor

Unable to communicate with the RILOE-II/ilo

Upgrade two DL380 G2 that have RILOE-II cards with latest board driver and firmware (firmware 1.16.) Ran a simple RICBL script to change IP, Gateway, Prim DNS. Both cards indicated they were restarting. Both machines and cards presented this message when we tried to access the card with hponcfg.exe after the script was sent and the card indicated it was restarting.

Unable to communicate with the RILOE-II/ilo.

Any idea what is causing this? Do we have to reboot machines to see card again? Both are in high volume 24/7 trasnactional environments.
7 REPLIES
Honored Contributor

Re: Unable to communicate with the RILOE-II/ilo

The restart might have caused the drivers to lose their connection. However, communication should be restored within a few minutes of reset. You should be able to use them without restarting the host.

You could manually restart the drivers (My Computer/Properties/device mangler or control panel)
You may also be able to do this from the systems management home page.

Can you PING the RILOE boards over the network? This will indicate that the network is up and running and that you should be able to talk to the boards from the host.
Advisor

Re: Unable to communicate with the RILOE-II/ilo

It has been over a day on each machine and neither board has changed their state.

Went to System/Device Manager as suggested. Did not see any method to restart the cards from the driver page, so disabled, then renabled. The message when trying to run hponcfg.exe now is:

ERROR: Couldn't Open the iLo/RILOE-II Driver system file. There is a probem with the ... Drivers installed on this system or ... is disabled ... or device not present.

ACTION REQUIRED: Please Enable iLo/RILOE-II or install ... Drivers.

Cannot ping the board because was trying to access them in HPONCFG to initially set them up with network configuration remotely.

Would like to get them going without a restart.
Trusted Contributor

Re: Unable to communicate with the RILOE-II/ilo

Uninstalling and re-installing the RILOE II drivers might solve the problem.

Try this.
In Device manager, uninstall HP Remote Insight Lights-out II Board driver and HP Remote Insight Lights-out II PCI Device driver. Now scan for hardware changes and wait for the the system to automatically install the drivers. If the drivers are not automatically installed, install the drivers manually.
Trusted Contributor

Re: Unable to communicate with the RILOE-II/ilo

Try this before you try to uninstall and re-install driver.

In Device manager,
* Disable both HP Remote Insight Lights-out II Board and HP Remote Insight Lights-out II PCI Device
* Enable both of the devices.
Now try to run HPONCFG.
Advisor

Re: Unable to communicate with the RILOE-II/ilo

Went ahead and tried disabling both HP Remote Insight Lights-out II Board and HP Remote Insight Lights-out II PCI Device in the Device Manager. No luck. Probably would choose to restart the machines rather than install and uninstall drivers. Definitely a problem here in that two machines experienced the exact same problem.
Advisor

Re: Unable to communicate with the RILOE-II/ilo

BTW, tried disabling and then re-enabling the items. Left this out of the above post.
Advisor

Re: Unable to communicate with the RILOE-II/ilo

Went to Device Manager and uninstalled both items, then scanned for them to be re-installed. This worked. Was then able to communicate with the cards.

(BTW, decided to restart the server in an attempt to restore communication with the cards as a preference to uninstalling the items, and the restart of the machine did not restore service to the cards.)

So everytime hponcfg sends a script that requires the RILOE-II board to be restarted, both items need to be uninstalled and reinstalled. A hard restart of the machine is not sufficient. Defintely a problem here. This occured on both of our identical DL380 G2 with RILOE-II cards. Workable, but a little time consuming.

Thanks for the suggestion that solved the problem.