Major Error on discovery -

emabot — Mon, 06 Feb 2017 11:59:36 GMT

Hi All,

what's the meaning of below Major error?

I'm using correct credentials for WBEM/WMI and also SNMP community string.

In the managed target system port 135 and 2381 are open and in Listening status.

The WMI proxy is correctly configured because it's working well with several

systems, similar to those that report this Major Error.

What am I Missing?

Regards

********* 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: 10.175.210.14 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.
Major: The system cannot be identified properly for HPE 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.
Normal: Identification status is only available for servers, workstations,
or desktops, where monitoring is enabled.

********* 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 did not respond to SNMP. Verify security settings and
community strings in Options->Security->Credentials->System
Credentials
* Checking for SNMPv3 protocol support on system...
Normal: The system did not respond to SNMPv3. Verify security settings and
v3 credentials in Options->Security->Credentials->System
Credentials
* Running HPE ProLiant management agent identification...
Normal: The system does not support SNMP.
* Running SNMP base cluster identification using common cluster
MIB...
Normal: SNMP is not supported or globally disabled, skipping SNMP cluster
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 HPE 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 HPE Integrity VM Host)
Identification...
Normal: The system is not a VM Host (non HPE 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 HPE NetServer identification...
Normal: The system does not support SNMP.
* Running HP-UX SNMP identification...
Normal: The system does not support SNMP.
* 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 XMLReply Identifier which will discover systems in a
rack/enclosure if the automatic discovery option for the container
node is enabled...
* 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.
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.
* Running p-Class Identifier...
Normal: The system is not a p-Class so skipping p-Class identification.
* Running IPMI protocol identification...
Normal: IPMI protocol not detected so skipping IPMI Identification.
* 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...
Minor: The system did not respond to WS-Management (WS-Man) request.
* Running Monarch OA Identification...
Normal: The system is not a monarch OA so skipping monarch OA
identification.
* Checking for System Management Homepage and other HPE web agents...
Normal: The system is not a server, storage or desktop. Skipping the check
for System Management Homepage.
* Running HP Serviceguard Identification...
* Running SNMP System Type manager ...
Normal: The system does not support SNMP.
* Running SNMP subtypes identification...
* Resolving DNS names...
* Checking if the Node is a Virtual Center...
Normal: Skipping Virtual Center Identifier.
* Running HPE Synergy identification...
* Running Virtual Machine Management (VMM) Plug-in Identification...
* Building system relationships...
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.

Re: Major Error on discovery -

n0kia — Wed, 08 Feb 2017 00:16:58 GMT

Can you test from the SIM server to the target via cmd line if you get information back with the account.

C:\>wmic /node:IPofTarget /user:"Domain\User" /password:"password" path win32_computersystemproduct get uuid

Re: Major Error on discovery -

Andrew_Haak — Thu, 09 Feb 2017 09:05:05 GMT

from the log you can see that you don't get WBEM or SNMP information. It would be a good idea to explore the WBEM instead of the SNMP. Does your WBEM account have admin rights or at least remote dcom rights ? To exclude a rights issue you can use an admin account as domain admin or a local admin. Is the server(s) you try to discover a Windows server and what generation is it ? If it's a Gen8 or newer you should use AMS/ILO instead of OS discovery

Re: Major Error on discovery -

emabot — Fri, 10 Feb 2017 09:23:12 GMT

Hi,

I get the following error

ERROR:
Description = The RPC server is unavailable.

Re: Major Error on discovery -

emabot — Fri, 10 Feb 2017 09:25:47 GMT

Hi,

with SNMP is working OK.

It's an old ProLiant BL460c G1

Re: Major Error on discovery -

Andrew_Haak — Fri, 10 Feb 2017 11:18:49 GMT

Could be that the firewall is blocking the call.

topic Re: Major Error on discovery - in Server Management - Systems Insight Manager

Major Error on discovery -

Re: Major Error on discovery -

Re: Major Error on discovery -

Re: Major Error on discovery -

Re: Major Error on discovery -

Re: Major Error on discovery -