Read/Write ILO Details from the Command Line

If you have access to an HP server running Windows but you don't have access to ILO information (such as IP info), you can export it all to an XML file using a tool HP includes in the Proliant Support Pack. The tool is called hponcfg.exe and it's located under C:\Program Files\HP\hponcfg on x86 and x64 systems.

In order to use hponcfg, you'll need to have the ILO driver installed on the system. If you go in Device Manager, you'll see an entry under Multifunction Adapters like this:

If the driver isn't loaded, you'll get an error when you try to run the tool:

HPONCFG RILOE-II/iLO setup and configuration utility
Version 1.4 (c) Hewlett-Packard Company, 2005

ERROR: CPQSMIF.DLL and SM2USER.DLL not found.
ACTION REQUIRED: Please install the latest Proliant support pack.

So, to write out the config to an XML file, you'd do something like this:

hponcfg /w ILOConfig.xml

You'll get a file something like this:


 















 


























 









 


 

There's a few interesting things you can glean from this:

  • The login at the top of the file is bogus, and as long as you're logged in locally as an administrator, you don't need to specify ILO credentials to use the tool
  • Under network settings, because SPEED_AUTOSELECT is "Y" (think auto/auto on the NIC), you can ignore the next two entries for NIC_SPEED and FULL_DUPLEX
  • Towards the bottom under users, it doesn't write out passwords, but it does write out usernames, so, we can see that this ILO has one user with username "admin"

You can use the XML file dumped here as a template that you can customize and import into other ILOs with the same hponcfg tool. To do this, you would run something like this:

hponcfg /f IloConfig.xml

This would import the contents of iloconfig.xml to the local ILO. As noted earlier as long as you're a local admin on the box, you can leave the bogus credentials at the top of the file. The tool is very finicky about the XML so if any of it is invalid, you'll get a confusing error pointing to the XML though rarely in the correct location. In general I'd recommend your remove any sections you're not configuring from your input file as the defaults will be retained.

Posted Wednesday, November 19 2008 3:33 PM by | Comments
Tagged as: ,

Comments