WBEM Communication Issue During Discovery

[ske99ey]

Hello,

I am new with HP SIM and have been fighting with it but have been slowly making progress. Currently trying to get one of our servers fully setup so that we can then use that setup as a basis to setup the others. I have been able to get SNMP set up and working but my problem now arises with WBEM. During discovery I get "Critical: HP SIM cannot communicate with these systems using the WBEM protocol."

The WBEM ports 5988/5989 (WBEM Service) and 50004 (WBEM Event Receiver) are open as needed. The Pegasus WMI mapper is properly installed on the CMS to my understanding. The credentials that are being used have Admin access. WBEM is installed on the target server and is up to date.

Both the CMS and the server are HP ProLiant DL360p G8 servers running Windows Server 2012. The CMS is running a fresh install of SIM 7.3 with the hotfix applied.

I am not sure what else to try so any help would be appreciated.

Here is the full discovery result:

********* 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.
Critical: HP SIM cannot communicate with these systems using the WBEM
          protocol.

********* 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 responded to an SNMP request; it supports SNMP Protocol
          and has a valid read community string.
        * Checking for SNMPv3 protocol support on system...
Minor:    Global SNMPv3 Identification is disabled.
        * Running HP ProLiant management agent identification...
Normal:   Identification can get the system information from the ProLiant
          SNMP Foundation agents for servers.
        * Running SNMP base cluster identification using common cluster
          MIB...
Normal:   This system does not have the common cluster MIBs support.
        * 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 Storage identification...
        * Did not detect the WBEM protocol support on this system. SMI
          storage identification will be skipped.
        * Storage identification completed.
        * 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 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...
Major:    WS-Management(WS-Man) is globally disabled so skipping 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:   System Management Homepage (SMH) is installed or is responding on
          the system(s).
        * Running HP Serviceguard Identification...
Normal:   The system is not part of HP Serviceguard cluster.
        * Running SNMP System Type manager ...
Normal:   No matching SNMP System Type Manager rule for sysObjID was found.
        * Running SNMP subtypes identification...
        * No additional subtype(s) found from SNMP.
        * Resolving DNS names...
Normal:   The fully qualified domain name was successfully resolved for the
          system.
        * Checking if the Node is a Virtual Center...
Normal:   Node is not a Virtual Center Node
        * Running Virtual Machine Management (VMM) Plug-in 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.

[Andrew_Haak]

Hello,

If you lookup your system in SIM go to the second tab tools and links. Here lookup your credentials, i would think that you would only see a trust and SNMP credential set.

If that is the case, go to the option menu and find the menu option credentials and set your WBEM credentials under the credentials bit. If you filled that in reidentify your server. If you take a second look at the server credentials you should see the credentials you just filled in at the general settings. Now every new system will try these credentials for wbem and SSH if you got both protocols turned on.

The whole problem is that you have to set the WBEM credentials in SIM to, not only in the WMI Pegasus tool.

[ske99ey]

Andrew,

I looked in SIM and those credentials are actullay set and they are correct. I am still getting the same result during identification. I looked in the manage communcations section and it says "For Windows System(s), make sure that the WMI service is correctly installed and running on them, and that there is an HP SIM WMI Mapper running either on the managed system(s), or as a proxy on another system."

The CMS itself works via WBEM so I know the WMI Mapper works. I tried to repair the agent but still no changes. Am I missing something?

[Andrew_Haak]

Hello again,

Can you check with one of your servers what is the datasource for the System Management Homepage on the top right? You can switch that undet settings, datasource. The options are SNMP or WBEM. Set it to WBEM and try again.

[J_N_Rhodes]

Why you r worried abt WBEM when SNMP is working fine. Any specific reason?
Dont you see traps coming to CMS?

Whats the health status of discovered server?

[ske99ey]

I checked on the server and the data source is already selected as WBEM in the SMH.

In regards to why using WBEM, we would like to be able to use it for the full functionality with SIM. My understanding is a system just recognized with SNMP doesn't have the capabilities to push out and update firmware? The health status of the CMS is Normal but the server I am trying to get working is Major since it can't be properly identified with WBEM.

[Andrew_Haak]

I have almost all of my servers set on snmp as the datasource and SNMP traps configured. I've done this because of firewall issues with wbem trapping. The SNMP setting works as good as WBEM. HP on the other hand tends to abandon the SNMP prototol on Windows systems. Unix only work with SNMP, devices only support SNMP and ESX  later than 4.1 supports WBEM. I've only seen that system details are more complete on windows and ESX servers if set on WBEM. If you set your servers to WBEM, don't forget to set subscriptions from SIM. If you use SNMP as a datasource don't forget to set your SNMP trap in your SNMP configs on the servers that you want to receive traps from.

I see no real advantage in either options, just go with works for you. Regarding the WBEM  discovery, check if the wbem port is open, or just for test sake disable the firewall temporarly.

[ske99ey]

I appreciate the continued replies but unfortunetly disabling the firewall doesn't change anything. I have tried to do so for testing purposes and I did so again with no change. Not quite sure what else there is to try in order to get WBEM working. Even with firewall in place I can't find any place that it something drops which I guess makes sense because SIM continues to talk to the server for the rest of the discovery just not over WBEM. As you mentioned, system details are more complete over WBEM for a windows server so we would like to get WBEM set up eventually.

[Andrew_Haak]

So the moet likley problem has to be the credentials, you could try the local admin account Administrator or do a repair to set a nonadmin for discovery purposes. It's one of the repair options. Disabeling the firewall was just for tests, you should always keep your (software) firewalls running. Are the systems you try to discover in the same subnet.