WBEM Management Protocol not recognised on Windows Servers

[B Hardy]

Hello

I can’t seem to get HP SIM to detect WBEM as a management protocol in any of our Windows servers, even though I have installed a WBEM provider in the servers to be monitored. The WBEM provider generates test events fine, but when I run an “Identify” in HPSIM it responds as follows:

Starting identification process...
.
.
.
Checking for WBEM support on system.
This system does not have any SMI-S CIMOM installed
This system doesn't have a server CIMOM installed locally, or cannot connect to
it using all credentials specified
Running WBEM rules based identification.
Cannot get ComputerSystem WBEM/WMI data from the system
.
.
.
Running Storage identification.
Did not detect WBEM support on this system. Will not attempt storage identificat
ion. If this is a storage host, check WBEM credentials and make sure the provide
rs and CIMOM are operational on the host.
Storage identification completed.
.
.
.
System identification done with this system.

I have turned off the firewall on both the monitored and management servers, and have the domain and local admin accounts entered in the Global Sign-in Credentials. WBEM is enabled in the Global Protocol Settings.

The Management Protocols reported for all Windows servers are : HTTP:, SMH:2.0, SNMP:1.0

Environment:
Windows Servers - Version Server 2003 SP2, Server 2008 SP1
HPSIM Version 5.3 with SP1 (Build version C.05.03.01.00)

WBEM is recognised as a management protocol on our VMware ESX hosts.

Appreciate any help in enabling WBEM as a management protocol on our Windows Servers.

[Dzmitryj Jakavuk]

If CMS and manged servers are located in different subnets with a firewall between them - try to install Pegasus WMI proxy and make shure the network traffic from CMS to Managed servers port 5989 is allowed

[B Hardy]

Thanks. The CMS and the managed servers are in the same subnet, and the firewalls on both are currently turned off. Ports 5988 and 5989 are both unblocked and listening on the CMS but the executable they are associated with is JavaWrapper.exe. Not sure if this is correct, and is there a way of changing the ports used?

[Alexander A]

I think the WBEM agent publish it's information to WMI (Microsofts implementation of WBEM) that uses RPC to set up communication. RPC listens on port 135 and then assign a new port for the connection. The range of port it uses can be configured if needed (when using firewalls other than Windows firewall).

You need to make sure that the user has permission to access DCOM remotely and that all ports are open (unless you change the DCOM RPC port range). By default, members of the group "Distributed DCOM users" have this permission.

DCOM settings are managed using the MMC snapin "Component Services".

[B Hardy]

Problem solved. Turns out that as we are running both HP-SIM and Command View for our EVA4400 SAN on the same server there was a conflict on port 5989 between the JavaWrapper.exe that is used in Command View and the WMIServer.exe used by HP-SIM for WBEM.

============================================

Solution as follows:

Open the file "C:\Program Files (x86)\Hewlett-Packard\SMI-S\CXWSCimom\config\cxws.properties"
Change the ports to 6988 and 6989 (be sure to check these ports aren't in use).

Open the file "C:\Program Files (x86)\HP\Systems Insight Manager\config\identification\wbemportlist.xml"
Change the ports to 6988 and 6989

Stop the Hewlett Packard storage works CIMOM service

Restart the Pegasus WMI Mapper service.

Start the Hewlett Packard storage works CIMOM service

To verify SMI-S can communicate with the storage on the new port, open a command prompt and change directories to where SIM is installed. (Path: C:\Program Files (x86)\HP\Systems Insight Manager\)

Type wbemdisco
Specify the new port number 6989.

============================================

Once I did the steps above and did a re-identify, the WBEM protocol was detected correctly.

Thanks to those who responded.

[B Hardy]

Solution detailed above.