how can I implement my esxi 4.1 into HP SIM 6.3?

[autsch1986]

Hello everybody I am trying to implement my esxi host into my sim server, but when i try to discover it, I always get the message:

the system(s) can not be identified by wbem, snmp or ssh? I hvae downloaded the esxi from the hp page.

the complete log here:
Stdout:
********* Significant issues and overall target discovery/identification
status:
Major: The system cannot be identified properly for HP SIM to manage;
unable to get one or more of the following: model, serial number or
unique identifier (UUID). For management processors, verify the
system is running the latest firmware. For Linux based operating
systems, you must have dmidecode installed, enable the
PermitRootLogin and PasswordAuthentication in sshd, and use root
sign-in credential. For HP-UX, verify the sign-in credential. For
Windows, check if WMIMapper is configured correctly on the CMS and
verify the sign-in credential.
Critical: The system(s) can not be identified by WBEM, SNMP or SSH

********* Additional results (listed for information only):

* Starting identification process...
* Checking for known running web servers...
* 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.
* 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
* Running SNMP System Type manager ...
Normal: The system does not support SNMP.
* Running SNMP base cluster identification using common cluster
MIB...
Normal: This system does not have the common cluster MIBs support.
* Running IPMI protocol identification...
Normal: IPMI protocol not detected so skipping IPMI Identification.
* Checking for WBEM protocol support on system...
Minor: This system does not have any SMI-S CIMOMs installed. No storage
systems will be found on this system.
Minor: The Central Management System (CMS) cannot communicate with the
CIMOM locally installed on the managed system using the WBEM
protocol, Identification will try to identify Windows systems using
the WMI Mapper as proxy; for Linux and HP-UX systems, check
credentials by going to Options->Security->Credentials->System
Credentials. For Linux systems also check if the HP WBEM provider
is installed.
Critical: There are no valid WBEM / WMI credentials for the system(s).
* Running WBEM rules based identification...
Minor: Identification cannot get computer system hardware data from the
WBEM / WMI providers.
* Running Virtual Machine (VM) Host (non HP Integrity VM Host)
Identification...
Normal: The system is not a VM Host (non HP Integrity VM Host), or WBEM
credentials may not be specified so skipping VM Identification.
* Running WS-Man identification...
Minor: The system did not respond to WS-Management (WS-Man) request.
* Running HP ProLiant management agent identification...
Normal: The system does not support SNMP.
* Running HP NetServer identification...
Normal: The system does not support SNMP.
* Running HP-UX SNMP identification...
Normal: The system does not support SNMP.
* 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 Storage identification...
* Did not detect the WBEM protocol support on this system. SMI
storage identification will be skipped.
* Storage identification completed.
* Running HP Serviceguard Identification...
* Running SNMP subtypes identification...
* Running RackManager Identifier which will discover systems in a
rack if the automatic rack discovery option for RackManager is
enabled...
Normal: The system is not a Rack Manager, skipping automatic discovery of
systems in the rack.
* Running OA Identifier which will discover systems in an enclosure
if the automatic enclosure discovery option for OA is enabled...
Normal: The system is not an Onboard Administrator, skipping automatic
discovery of systems in the enclosure.
* Running Enclosure Manager Identifier which will discover systems in
an enclosure if the automatic enclosure discovery option for
Enclosure Manager is enabled...
Normal: The system is not an Enclosure Manager, skipping automatic
discovery of systems in the enclosure.
* Running iLO Identifier which will discover the server if the
automatic server discovery option for iLO is enabled...
Minor: The system responds to the HTTP request but cannot get the XML
output. It is normal for servers not to get the XML data.
* Running p-Class Identifier...
Normal: The system is not a p-Class so skipping p-Class identification.
* Running Monarch OA Identification...
Normal: The system is not a monarch OA so skipping monarch OA
identification.
* Resolving DNS names...
Normal: The fully qualified domain name was successfully resolved for the
system.
* Running Virtual Machine Management (VMM) Plug-in Identification...
Normal: Virtual Machine Management (VMM) Integration is not enabled so
skipping VMM VM Identification.
* 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...
* System identification finished on system.
Stderr: None


I have no idea what is the problem.
Hope someone can help me.
Thanks in advance.
best regards
andreas

[BPE · Accepted solution]

Try to login to your ESXi from your SIM server ssh root@your_esxi_server. If it does not work your ESXi settings are still default!!! Go to the ESXi console and enable the ssh login. WBEM should also work. SNMP never works for ESXi because ESXi has no SNMP agent active ( ESX had an SNMP based Agent)
You can try the WBEM credentials with the wbemdisco program in the SIM home directory.
the name space root/cimv2 or vmware/esxv2 should work. Check the wbemportlist.xml file in the ...\System Insight Manager\config\identification directory for the correct spelling of the namespaces. Take care with the password field of wbemdisco if you try different passwords. Go with the cursor to the right in the password field and delete the invisible space characters before you enter a new password.

[dgerol]

You can get SNMP to work in ESXi... You need to install the vSphere CLI (not the PowerCLI)and use the command "vicfg-snmp.pl"

See the attachment for the protocols dicovered on my ESXi 4.0 U2 host

[autsch1986]

hello, thanks for the great information, I didn´t set a password,........
But it is good to know that I can also implement SNMP!

best regards and a nice weekend!!
andreas

[BPE]

Take care SNMP Support is only forwarding traps to a Management system. You can not read the health status or network traffic counters from a ESXi system.

[Rob Buxton]

I'd recommend getting wbem working rather than SNMP.
The beauty of ESXi is that the hypervisor is kept as clean as possible.
I try and avoid adding other stuff to it.

Ensure in the credentials section for the server under wbem that there are credentials added (I use root).
Once that's done you need to subscribe to wbem events.

[MariusGillesen]

Had a similar problem one one of my exi hosts, and discovered that the server was not installed with the HP build of esxi. Could that be the problem for you as well?

[Rodd Masteller]

I am doing the same thing right now, trying to get our new ESXi 4.1 update 1 hosts into SIM 6.3.  I did use our VMA appliance to run commands to set up SNMP and that works on an HP version of ESXi.  (example commands below)  You can sent a test trap and SIM will see it as a "warm start" event.

I need help with wbem setup.  Is there a document you can point me to, or some basic instructions you can provide from experience to a wbem novice?

Thanks

+++++++++++++++++++++++++

From the VMA console (using vCLI commands):

1. vicfg-snmp --server <hostname> --username <name> --password <pw> --show
2. vicfg-snmp --server <hostname> --username <name> --password <pw> -c <communityname> -t <simservername @ 162/<communityname>
3. vicfg-snmp --server <hostname> --username <name> --password <pw> --enable
4. vicfg-snmp --server <hostname> --username <name> --password <pw> --show

From the SIM console

1.  Discover the system you just enabled snmp on.

From the VMA console

1. vicfg-snmp --server <hostname> --username <name> --password <pw> --test

From the SIM console

1.  Check the system for events.

[Rodd Masteller]

Nevermind.  I didn't have the correct credentials in Global Security.  I added the ROOT account and password and WBEM data started coming in after another discovery.