Server Management - Systems Insight Manager
cancel
Showing results for 
Search instead for 
Did you mean: 

HPSIM 6.2 and WBEM

HPSIM 6.2 and WBEM

I receive correctly SNMP alerts from a Windows 2008 R2 SP1 client and I want to change the protocol from SNMP to WBEM.

I set disk threshold using HPSMH on the client. I chose datasource: WBEM. I did an identification.
On client Product Description I still have HTTP:, SNMP:1.0, SMH:2.0 in Managements Protocol

HPSIM is hosted on a Windows 2008 R2 SP1 server.
HPSIM build ver: C.06.02.00.00

I did try to subscribe adding 2 accounts in the credentials. One is domain admin and the other one is domain user.

I don't have any alert when disk threshold is reached.

Thanks for your help
13 REPLIES
David Claypool
Honored Contributor

Re: HPSIM 6.2 and WBEM

Use 'Manage Communications'

Re: HPSIM 6.2 and WBEM

In manage communications here is what I have:
in advise and repair:
identification: System(s) have been successfully identified
Events: 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 user
All 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 Managem
ent Homepage 2.0 or later.

Successfully restarted necessary management applications to ensure that all succ
essful changes will be effective.
Configure WBEM / WMI user (START) ...
Configure WBEM / WMI user ...... ................................... [SUCCESS]

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

WBEM protocol settings are not valid/enabled for this system in HP SIM. Check yo
ur HP SIM settings for identification via WBEM.
Subscribe to WBEM / WMI Indications ................................. [FAILED]

Send test WBEM/ WMI indication from the system ...................... [FAILED]
CMS has to be subscribed for WBEM / WMI indications before it can receive a test
indication.

Checking whether the HP SIM CMS can login to the SMH URL " https://load-6.zp.loc
al:2381/ "
Login to the SMH using certificate.............................. [SUCCESS]

Re: HPSIM 6.2 and WBEM

I then go to "Global Protocol Settings"
Enabled WBEM is checked (def con timeout=10)
I go to "System Protocol Settings" (target=myclient) but the only protocols I have are Ping (ICMP) and SNMP.
I go to "system credentials" and find that:
myclient SNMP MWSNMP Discovery (System Automatic Discovery): SNMP
myclient Single Sign-On Certificate HP Systems Insight Manager
I click on "View all credentials" and I have this:
System NameAccess TypeCredentialSourceOK to Try OthersSystem Name Access Type Credential Source OK to Try Others

myclient wbem mydomain\srv_wmi System No
myclient sign-in mydomain\srv_monitor System No
myclient snmp MWSNMP Discovery (System Automatic Discovery) No
myclient snmp public Discovery (System Automatic Discovery) No
myclient sign-in mydomain\srv_monitor Discovery (System Automatic Discovery) No
myclient sign-in mydomain\srv_wmi Discovery (System Automatic Discovery) No
myclient snmp MWSNMP Global Yes
myclient snmp public Global Yes
myclient sign-in mydomain\srv_monitor Global Yes
myclient sign-in mydomain\srv_wmi Global Yes

Re: HPSIM 6.2 and WBEM

In WBEM / WMI System Credentials:
Port is empty
user is mydomain\srv_wmi
The 2 following boxes are unchecked:
"If these system credentials fail"
"Push a WBEM cert... (only valid for HPUX)"

Re: HPSIM 6.2 and WBEM

Any idea?

Re: HPSIM 6.2 and WBEM

On Windows side:
server and client firewalls have been disabled
mydomain\srv_wmi is a member of "Distributed COM Users" local group

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

In HP Version Control Agent:
HP Insight Management WBEM Providers for Windows Server 2003/2008 x64 Editions v2.7.0.0

Re: HPSIM 6.2 and WBEM

I have updated HP Insight Management WBEM Providers for Windows Server 2003/2008 x64 Editions from v2.7.0.0 to v2.8.0.0 and I have launched the config/repair agent for WBEM but it is still the same
shocko
Honored Contributor

Re: HPSIM 6.2 and WBEM

Sounds like SIM is pointing at the wrong WMI mapper. What server is hosting the Pegasus WMI mapper? have you checked that SIM is pointing at it?

Remeber SIM uses WBEM and windows uses WMI
If my post was helpful please award me Kudos! or Points :)

Re: HPSIM 6.2 and WBEM

Pegasus WMI Mapper and HPSIM are installed on the same server.
The 2 Pegasus Services are in Auto startup mode.
In HPSIM (Protocol settings/wmi mapper proxy) here is the settings:
Host: HPSIM server computer name
IP: HPSIM server IP addr
Port: 5989 (N.B: Win FW is disabled)
shocko
Honored Contributor

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
If my post was helpful please award me Kudos! or Points :)