Problem with two servers in SIM 7.2

[online1]

Hi,

I have a problem with two of my HP servers in SIM 7.2.

Server1:

Not able to get all info from the server, e.g.. I'm missing network info. It's a bl460c gen8 and have ESXi 5.0 installed.

When I run discovery I get this minor errors, maybe that's the cause? But how to fix that?

Minor:    System Management Homepage (SMH) is not installed or is not
          responding on the system(s).

Minor:    The system(s) do not have Secure Shell (SSH) installed or it is not
          running on the managed system(s).

Have two servers with the exact same setup and hardware and from them I get all the info.

Server2:

It's getting some major errors. seems like I'm not getting any WBEM. dl360G7 server with 2008R2. I have several other servers that shows up in SIM without any problem. any ideas?

********* 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 returns TCMSQLSRV5.
          However, the forward DNS lookup was not successful because HP SIM
          could not get the fully qualified domain name for the system being
          discovered. In HP SIM, the fully qualified domain name for the
          system will be empty. Verify that the system name is in the forward
          lookup table in the DNS server configuration, or that the fully
          qualified domain name and its IP address are in the host file.
Major:    The system cannot be identified properly for HP SIM to manage;
          unable to get one or more of the following: model, serial number or
          unique identifier (UUID). For management processors, verify the
          system is running the latest firmware. For Linux based operating
          systems, you must have dmidecode installed, enable the
          PermitRootLogin and PasswordAuthentication in sshd, and use root
          sign-in credential. For HP-UX, verify the sign-in credential. For
          Windows, check if WMIMapper is configured correctly on the CMS and
          verify the sign-in credential.

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.
Critical: There are no valid WBEM / WMI credentials for the system(s).
        * 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...

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.
Minor:    If the http communication from CMS to target is working, but if it
          is found to be slow then try increasing the Default connection
          timeout parameter for http in global protocol settings.

Minor:    The system did not respond to WS-Management (WS-Man) request.
        * Running Monarch OA Identification...

Minor:    System Management Homepage (SMH) is not installed or is not
          responding on the system(s).

Thanks.

[LGentile · Accepted solution]

Well since you have two very different issues:

1.  There is no SMH for ESXi - health status and events are forwarded via WBEM to SIM from the 'CIM Providers' if you are using the HP embedded ESXi install (no agents either) so that first message is normal.  You'll want to use credentials (by default, root) for sign-in creds during discovery.  After that, subscribe to WBEM events to be able to accept traps security from ESXi/CIM providers.

2.  If you want to use WBEM on Windows, you need to make sure the WBEM Providers are installed (from the Support Pack) so the proper agent is there, otherwise you will need to use SNMP.

On Windows you basically have two methods: SNMP or WBEM.  You can run "both" but this is not recommended.  Choose or or the other (SNMP works by default with the standard agents, WBEM requires the WBEM provider specifically).  If you use WBEM it will become the default data source for the SMH as well (if you install it, which you should on Windows) even if you are using SNMP to talk to the server.   I am not 100% sure that running both causes any issues, in the past our HP contacts have basically told us to stick to one protocol.  WBEM becomes the default communication channel with both, regardless.

Here's the official SIM document on WBEM on Windows:

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01509052/c01509052.pdf

You especially want to read that if you are about to deploy Gen8 on Windows.  We are currently evaluating WBEM/agentless monitoring (which I don't think we're going to do right now since we use IRSA).

Lance

Here's a feature enhancement for HP:

Upon discovery, they should re-order the discovery communication to look for all open protocols first and get machine information, that way things like SMH can be skipped if the server is ESXi and there would not be a need to throw a 'Minor' error.  A lot of the discovery text will throw errors (even major ones) that really do not fully affect how the server communicates with SIM.   Some "minor' errors are completely normal depending on what you are discovering..  many are "normal" ("This server is ESXi, no SMH = "Normal"), for example.

[online1]

Thanks!

My dl360g7 is now in SIM! I installed used the Support Pack and some drivers where old or missing.

But I still have problem with my ESXi host. It's in SIM but do not show all info, if I compare with another gen8 that have the same setup some info is missing.

Server1.jpg = the server that have missing info
Server2.jpg = server without missing info and showing some "errors"

I tried with the subscribe wbem events but I did just say successfully.

Any ideas?

[Paul Kurtz]

Are you using the HP ISO for esxi 5.0?

If so ssh is not enabled for access by default and wbem is provided by using root.  I would just double check credentials are working.

[online1]

Yes, when I installed the server I did use HP ISO ESXi 5.0.

OK, but it's working on the other two servers that are in the same cluster with same setup. no diff.

double check credentials in SIM you mean? when discover the server?

[LGentile]

Sorry, was out for a week..

Yes, just double check the sign-in credentials.  If you update them it will force an identify task to run and you can see the status of that task.

[online1]

I have double checked the sign-in and it's right.
I did click on the host > Tools and Link > System credentials and did type in the root pw again. After that did I run Discovery on that machine and got these minor errors:

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: xxx.xxx.xxx.xxx 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.

* 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).

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.

[online1]

I solved this myself. last server was missing offline bundle. but the strange thing is that non of the other servers had that installed seperatly...