Are you running ESX or ESXi?
I would assume ESXi these days.
ESXi uses WBEM as the protocol for monitoring where ESX uses SNMP.
For ESXi you will need to uses HP's ESXi image or install the WBEM providers is using ESX's image. The providers are specific to HP hardware.
When discovering the host assign credentials to access the WBEM infrastructure. This can either be a sing-in credential or WBEM/WMI. I would assign these credentials at the time of discovery.
The user root works by default but any user in the root group will work. Sometimes I will add a user for the WBEM authentication and configure its shell to bin/false so no Getty will be spawned.
Below is an identify from a ESXI server running SIM 7.2
I have highlighted the lines you should be looking for
********* Significant issues and overall target discovery/identification
status:
Normal: The system has valid hardware data (model, serial number, and
unique identifier) and has been identified properly for SIM to
manage.
Normal: System(s) have been successfully identified.
********* Additional results (listed for information only):
* Starting identification process...
* Checking for known running web servers...
* Checking for SNMP protocol support on system...
Normal: The system did not respond to SNMP. Verify security settings and
community strings in Options->Security->Credentials->System
Credentials
* Checking for SNMPv3 protocol support on system...
Normal: The system did not respond to SNMPv3. Verify security settings and
v3 credentials in Options->Security->Credentials->System
Credentials
* Running HP ProLiant management agent identification...
Normal: The system does not support SNMP.
* Running SNMP base cluster identification using common cluster
MIB...
Normal: SNMP is not supported or globally disabled, skipping SNMP cluster
identification.
* Checking for WBEM protocol support on system...
Normal: This system has WBEM protocol support.
Normal: The system support SLP.
Normal: This system has at least one SMI-S CIMOM installed to serve as the
storage proxy to discover storage systems.
Normal: This system has a server CIMOM installed.
* Running WBEM rules based identification...
Normal: Got the system information from the WBEM / WMI providers and it has
a valid WBEM credential.
* Running Virtual Machine (VM) Host (non HP Integrity VM Host)
Identification...
Normal: The system is a Virtual Machine (VM) Host (non HP Integrity VM
Host) and has (17) guests running on it.
* Running Storage identification...
* This system has some storage related information and additional
storage systems may be added.
* This system has some storage related information and additional
storage systems may be added.
* This system has some storage related information and additional
storage systems may be added.
* This system has some storage related information and additional
storage systems may be added.
* Storage identification completed.
* Running HP NetServer identification...
Normal: The system does not support SNMP.
* Running HP-UX SNMP identification...
Normal: The system does not support SNMP.
* Running OA Identifier which will discover systems in an enclosure
if the automatic enclosure discovery option for OA is enabled...
Normal: A non-embedded operating system is detected so skipping the OA
identification.
* Running XMLReply Identifier which will discover systems in a
rack/enclosure if the automatic discovery option for the container
node is enabled...
Normal: A non-embedded operating system is detected so skipping the
Management processor identification.
* Running iLO Identifier which will discover the server if the
automatic server discovery option for iLO is enabled...
Normal: A non-embedded operating system is detected so skipping the ILO
identification.
* Running p-Class Identifier...
Normal: The system is not a p-Class so skipping p-Class identification.
* Running IPMI protocol identification...
Normal: Skipping IPMI discovery in favor of WBEM/SNMP discovery.
* Running SSH Protocol identification...
Normal: This system has SSH protocol support.
* Running SSH Identification...
Minor: The system cannot be logged in using SSH protocol; check
credentials or check the settings in the SSH configuration file
* Running WS-Man identification...
Normal: A non-embedded operating system is detected so skipping the WS-MAN
identification.
* Running Monarch OA Identification...
Normal: The system is not a monarch OA so skipping monarch OA
identification.
* Checking for System Management Homepage and other HP web agents...
Normal: The System Management Homepage is not installed on this system. It
may not be supported.
* Running HP Serviceguard Identification...
Normal: The system is not part of HP Serviceguard cluster.
* Running SNMP System Type manager ...
Normal: The system does not support SNMP.
* Running SNMP subtypes identification...
* Resolving DNS names...
Normal: The fully qualified domain name was successfully resolved for the
system.
* Checking if the Node is a Virtual Center...
Normal: Skipping MxVirtualCenter Identifier.
* Checking if this system is supported by Insight Control power
management...
* Insight Control power management is not supported.
* Running Virtual Machine Management (VMM) Plug-in Identification...
* Automatic discovery for VM Guest(s) is enabled at global level.
* Building system relationships...
Minor: The Secure Shell key-based access authentication is not configured
on the system(s).
Minor: System Management Homepage (SMH) is not installed or is not
responding on the system(s).
* Running system Manage Communication diagnosis...
* This system is not licensed
* System identification finished on system.
Once the system has been successfully discovered you then need to subscribe to WBEM events. Select the node nodes in SIM then go to options>events>subscribe to WBEM events.
You can verify the subscription using the command mxwbemsub -l –n nodename
C:\Users\simadmin>mxwbemsub -l -n dgdl785sim
Filter instances of Subscriptions for:
dgdl785sim
Filter Name: HPSIM_TYPE_1_c2619sim_0
Query: select * from CIM_AlertIndication
Destination: https://15.31.136.54:50004/dgdl785sim.msr.hp.com?wbemip=15.47.81.90
Filter Name: HPSIM_TYPE_1_c2619sim_0
Query: select * from CIM_AlertIndication
Destination: https://15.31.136.54:50004/dgdl785sim.msr.hp.com?wbemip=15.47.81.90
There is no “easy” way to do end to end testing.
If you are using HP's remote support product either IRS or RSA the monitored systems guide will have some helpful instructions. Even though the documents are written for remote support tools the same principal applies to SIM.
Hope this helps