HP SIM 7.5+ ESXi 5.5 , not receive events

[lzg88]

Hi experts,

I have some ESXI 5.5 blade server. Think through the HP-SIM monitoring hardware .

The ESXI 5.5 server has been found by discover added to the system. Then I remove the server of a hard disk . 

But I didn't see the corresponding event on SIM system .

So I want to ask how to check ???

The attachment is the SIM system on the node information .

The following is the result of the discovery:

\********* Significant issues and overall target discovery/identification
status:
Minor: The name of the system could not be resolved to a fully qualified
domain name. For a Windows CMS, make sure that the domain name of
the managed system is included in the DNS suffixes in the Windows
Advanced TCP/IP Settings page.
Minor: The reverse DNS lookup using the IP address: 10.25.27.148 failed.
It might be that the nslookup timed out or DNS server cannot find
this address, or that the domain does not exist.
Minor: Verify that your name resolution service or the host file
configuration is configured properly so that your system's hostname
can be resolved to the fully qualified domain name.
Minor: The discovered server cannot be associated with its management
processor. For Windows and Linux, verify that the supported HP
Insight Management Agents or WBEM provider is installed on the
server. For HP-UX, verify that the WBEM Services version has the
Management Processor provider. Also, verify that the management
processor has been discovered in HP SIM.
Minor: The discovered blade is not in an enclosure. For c-Class
enclosures, verify that the supported OA firmware version is
installed and verify that the OA has been discovered in HP SIM. For
p-Class enclosures, verify that the iLO firmware and the HP Insight
Management Agents on the server are installed and verify that the
iLO has been discovered in HP SIM.
Normal: The system has valid hardware data (model, serial number, and
unique identifier) and has been identified properly for SIM to
manage.

********* 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: 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...
Minor: The system is a Virtual Machine (VM) Host (non HP Integrity VM
Host), but has no 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...
Minor: The system(s) do not have Secure Shell (SSH) installed or it is not
running on the managed system(s).
* Running SSH Identification...
Normal: SSH Protocol is not enabled so skipping SSH Identification.
* 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...
* Checking if the Node is a Virtual Center...
Normal: Skipping Virtual Center Identifier.
* Running Virtual Machine Management (VMM) Plug-in Identification...
* Building system relationships...
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.

[n0kia]

Did you subscribe to wbem events?

Options > Events > Subscribe to wbem events.

[Andrew_Haak]

Yes that should help and depending on the generation of hardware you can use the ILO4 / AMS setup if you use a Gen8 or newer ! If you use Gen7 or older then the subscription should be enough.

[lzg88]

Of course, I have already subscribed to the WBEM event. SIM can not receive the event, I restart the CIM service can be restored .And  It is back to normal. 

[lzg88]

---

@Andrew_Haak wrote:

Yes that should help and depending on the generation of hardware you can use the ILO4 / AMS setup if you use a Gen8 or newer ! If you use Gen7 or older then the subscription should be enough.

---

I found that this situation mainly occurred on the blade server .