iLO discovery - populate an iLO IP field on server CI forms

[cyked]

I've read through a few questions posted about avoiding iLO infterface discovery, which in our company should be fine, the networks for iLO (like BUR) are segregated and we exlude those networks from discovery.

My quetion is, does anyone have experience/success with discovery on populating a server CI with a field to house the iLO IP (it wouldn't have to be in the servers Network Adapaters table entries)?  

[sabell2012]

Drew:

At our last client I ended up creating a new table named Remote Adapter and extended from cmdb_ci_hardware to contain the iLO devices.   It really didn't fit in the Network Adapters table.   Btw, I tried MIBs, OIDs, and was not very successful in pulling back information that would uniquely identify the device.   I ended up going off of device name which contained an identifiable reference to iLO (fortunate for all of us that the client had a naming standard).   So.   I know that probably wasn't the answer you wanted to hear, but that is how we ended up resolving that issue.

Steven.

[dedeepyatirugu]

Hi Paul,

We have a similar requirement. Unable to detect iLO ports through discovery process. Could you please post the solution here if it worked for you.

Thanks In advance.

Regards,

Dedeepya

[cyked]

Did not find a solution and abandoned it.   I just don't believe that currently discovery is able to be aware of iLo info as the Server OS is not.

I do not know if discovery patterns could provide a solution either.