HP SIM Agent Configure on ESXi 4.1

http://communities.vmware.com/message/1590665


There is no HP Agent for ESXi. What you probably installed (at least I hope...) is the CIM offline bundle for HP.

Once you have those installed, you have to configure HP SIM to use WBEM (NOT SNMP) to communicate with the ESXi server. I actually had to do this very recently and documented it. See below:

1) Make sure the HP CIM bundle is installled. To do this, either install ESXi with the HP version of ESXi, or install the offline bundle downloaded from HPs site. To install the offline bundle:

1) Log onto VMWare VC Server
2) Go to Start Menu and Launch the VMWare CLI
3) Cd to the bin directory: c:\program files (x86)\Vmware\VmWAre vSphere CLI\bin

To Verify what patches in the bundle apply to your host:

Vihostupdate.pl --server servername --scan --bundle path to zip bundle

Vihostupdate.pl --server ah-esxi-exch --scan --bundle "C:\ESXi HP\hp-esxi4.1uX-bundle-1.0.zip"

Make

To install:

Vihostupdate.pl --server servername --install --bundle path to zip bundle

Vihostupdate.pl --server ah-esxi-exch --install --bundle "C:\ESXi HP\hp-esxi4.1uX-bundle-1.0.zip"

2) Go to HP SIM, and go to Options -> Discovery.

3) On the discovery screen, create a new discovery task. Add your ESXi hosts to the "Ping inclusion ranges/host names" text box.

4) CLick the blue Credentials button on the bottom (this is important).

5) CLick Show advanced protocol credentials.

6) Click the WBEM/WMI tab.

7) Enter in a valid username and password for your ESXi Host (I use root and the root password).

8) Click OK.

9) Now save the task by clicking Save.

10) Run the task by selecting it's radio button and clicking Run Now.

This should cause it to appear in HP SIM. Now, you need to setup WBEM indications (they replace SNMP traps).

To do this:

1) Log into Insight Manager on AH-Monitor1

2) Go to Options -> Events -> Subscribe to WBEM Events

3) Verify your server is in the Targets list (Click Add Target if necessary).

4) Click Next and finish the wizard to activate these events.

5) Reboot the ESXi Server to have this take effect.