I am sure you know that "agentless" monitoring is a Gen8+ feature only.
So, just a few things need to be done to make this work:
- Install the "HP Agentless Management Service" (aka AMS) on the server. This service passes OS information and adds a few additional features that the iLO can't do without.
- Set the iLO configuration to "Agentless" and not Pass-Through in the Management section
- Set your SNMP community names and trap destination pointing to your SIM server in the same location
If this is done correctly, you should see an association on the iLO after discovery finishes of the machine's host name, with IP address and OS information (vendor, version). You do not need to discover the host name separately. There is a support matrix out there that explains the difference between full agents, AMS + iLO, and no AMS with iLO only.
All communication from this point forward should be via the iLO using SNMP. It does NOT use RIBCL (I only mention this in case you want to use Insight Remote Support, which likes to use RIBCL). You do not need to configure or set up SNMP on the hosts, or install the full HP Management Agents.
So far, this has worked nicely for me and I have RedHat, ESXi, and Windows machines (Gen8s) discovered this way.
The software status is for the VCA component and you can't use that without the full agents on the OS. It basicaly lets you do version control/compliancy for drivers, agents, etc.. and is matched against a baseline to turn it green/orange/red. I don't think this has any valid status for iLO/agentless.
So, I think you are almost there - just drop the AMS on there and delete/re-discover your hosts. I used HP SUM to painfully update my Windows machines and VMware can be easily updated using Update Manager once you set up a baseline to include the AMS pieces.