Re: HPSIM 6.2 and WBEM

In manage communications here is what I have:in advise and repair:identification: System(s) have been successfully identifiedEvents: HP SIM has not subscribed to the system(s) to receive WBEM or WS-MAN indications and the Central Management Server is not on the SNMP trap destination list, so no events will be received from the system(s).Then I go to configure and repair agents as it is mentioned.I check "Install WBEM / WMI Provider" and "Force install the agents" then next,I check "Create subscription to WBEM events","Send a sample WBEM / WMI indication", "Configure a non-admin account" with user srv_wmi who is a domain userAll other parameters are unchecked then next,I enter domain/enterprise administrator credentials for HPSIM to remotely access and run whatever is needed.

Re: HPSIM 6.2 and WBEM

Set Trust relationship to "Trust by Certificate"Set Trust relationship to "Trust by Certificate" ................... [SUCCESS] Added this instance of HP SIM to the trusted certificate list for System Management Homepage 2.0 or later.

Set WBEM / WMI user credentials to System protocol settings ........ [SUCCESS]Re-identifying system to get updated information (START) ...Re-identification of system .................................... [SUCCESS]

Re: HPSIM 6.2 and WBEM

Result of client identification:********* 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 System Management Homepage and other HP web agents...Normal: System Management Homepage (SMH) is installed or is responding on the system(s). * Checking for SNMP protocol support on system...Normal: The system responded to an SNMP request; it supports SNMP Protocol and has a valid read community string. * Running SNMP System Type manager ...Normal: No matching SNMP System Type Manager rule for sysObjID was found. * 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. * 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: Identification can get the system information from the ProLiant SNMP Foundation agents for servers. * Running HP NetServer identification...Normal: System supports the NetServer SNMP agent, adding system type. * Running HP-UX SNMP identification...Normal: System does not have the HP-UX SNMP agents installed. * 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 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...Normal: The system is not part of HP Serviceguard cluster. * Running SNMP subtypes identification... * No additional subtype(s) found from SNMP. * 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 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...Normal: The trust between the CMS and the managed system is established. * Running system Manage Communication diagnosis... * System identification finished on system

Re: HPSIM 6.2 and WBEM

try hardcoding in a WBEM credential in the sytem credentials for that system and re-run identification.You may have an issue with WMI namepsace security. Make sure the account you are using is a full admin on the target server just for testing.

Also, possibly check you wbem ports file on the SIM server to see if its seraching on the correct ports. Also, see if you can create a test indication on the target server