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

HP SIM 6.2 Discovery - completed with major errors

Techwiz
Occasional Advisor

HP SIM 6.2 Discovery - completed with major errors

Hi Everyone,

 

I am trying to add few HP servers in to hpsim for hardware monitoring.my success ratio seems to be 3:1 and the servers which are failing to get added are returning with major errors and not getting added to hpsim.the steps i had followed so far are

 

1) Check for proper snmp community string on the server to be added.

2) Check if CMS ip is added to the list of ips to communnicate on the client snmp setting.

3) perfomed a wmi query from the hpsim server to the client and it is indeed returning results , so permissions should n't be a problem.

4) on few servers , in hpsmh the datasource was empty , installed wbem and hpsmh seems to work fine but the server is not getting added to HPSIM.

 

Guys ,please guide me with any additional troubleshooting or tips to add the servers in to HPSIM.

 

BR

 

Shiv

8 REPLIES
Andrew_Haak
Honored Contributor

Re: HP SIM 6.2 Discovery - completed with major errors

Hello Shiv,

Could you please attach a discovery log to this post. Then we can see what went wrong.

Kind regards,

Andrew
Kind regards,

Andrew
Techwiz
Occasional Advisor

Re: HP SIM 6.2 Discovery - completed with major errors

Thank you for the response Andrew , please find the Discovery logs from CMS.

 

 

********* Significant issues and overall target discovery/identification
status:
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.


********* 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: The ProLiant SNMP Foundation agents for servers are not installed
or are not configured.
* 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...
* 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...
Major: In order to access Secure Sockets Layer (SSL) based tools such as
System Management Homepage and Version Control Repository Manager
on remote systems without performing an additional sign-in, you
need to establish trust between the Central Management Server (CMS)
and the managed system(s).
* Running system Manage Communication diagnosis...
* System identification finished on system.

 

Andrew_Haak
Honored Contributor

Re: HP SIM 6.2 Discovery - completed with major errors

Hello again,

 

When we look at the log we see that you do have snmp and SMH installed but the snmp sub agents either are not installed or are not all running. You should logon to the SMH of the server you tried to discover and see if this page looks complete. If it does'nt please look if all subagent services are running. Then your server is a Windows 2008 or higher version you could try the wbem agent and set that as the datasource if you haven't done so already.

 

Then the SMH looks a lot better, but when we look at the log you don't have a account setup to read this wbem/wmi . The use you have to co configure needs to be able to read the wbem/wmi information. A local admin rights account is more that enough. Less can also work but just start with an account that has lokal admin rights on the server you want to discover.

 

If you don't know how to setup these credentials just let me know.

 

Kind regards,

 

Andrew

 

 

Kind regards,

Andrew
Techwiz
Occasional Advisor

Re: HP SIM 6.2 Discovery - completed with major errors

Thanks again Andrew,

 

I did install wbem on one of the server and smh is showing up all components after the installation , but its not getting discovered.please share the documents to setup the local admin account for wbem/wmi , i hope it should have been configured , anyways i wil check on it.i wonder why it is not working for other 2003 when few are working . All let me know how the configure or repair agents would work in this scenario.

Techwiz
Occasional Advisor

Re: HP SIM 6.2 Discovery - completed with major errors

Even now , i was adding up few servers and few failed to get added with the message completed with major failures. just restarted the snmp service and ran a discovery and the same servers now show up minor error and got addes in to HP sim :)

Andrew_Haak
Honored Contributor

Re: HP SIM 6.2 Discovery - completed with major errors

Hello again,

You can always use SNMP but Wbem is the new standard for anything above windows 2003 and ESX 5.x.

Just add an domain account with local admin rights to your discovery settings. Don't use your own account because when you change your password the discovery will stop working and your account will lockout. Create an account with the above mentioned rights and use that for discovery.

Please read other replies i made in this forum. If you can't findthem let me know i will make a document and attach it to this post. Posts like these

http://h30499.www3.hp.com/t5/ITRC-HP-Systems-Insight-Manager/No-valid-working-Sign-in-credentials-Error/m-p/6295509#M57765

Kind regards,

Andrew

Kind regards,

Andrew
GDeepak
Occasional Visitor

Re: HP SIM 6.2 Discovery - completed with major errors

Hi Andrew , I am getting error , but the sever is not getting added to SIM , Plase help

Status: Some Minor Errors
Start time: 6/20/16 1:55 AM
Task name: UCC servers End time: 6/20/16 1:57 AM
Tool: System Automatic Discovery Duration: 1 min, 14 sec
Owner: abbvienet\a-kumargx20 Target: 15.91.67.221
Run by: abbvienet\a-kumargx20
Command: N/A

--------------------------------------------------------------------------------
System Name: 15.91.67.221
Status: Completed with minor errors

Exit code: N/A
Stdout:

********* 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: 15.91.67.221 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 blade is not in an enclosure. For c-Class
enclosures, verify that the supported OA firmware version is
installed and verify that the OA has been discovered in HP SIM. For
p-Class enclosures, verify that the iLO firmware and the HP Insight
Management Agents on the server are installed and verify that the
iLO has been discovered in HP SIM.
Normal: The system has valid hardware data (model, serial number, and
unique identifier) and has been identified properly for SIM to
manage.

********* 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...
Normal: The system did not respond to SNMPv3. Verify security settings and
v3 credentials in Options->Security->Credentials->System
Credentials
* Running HP ProLiant management agent identification...
* 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...
Minor: Running an ipmiutil command failed and the IPMI protocol is not
supported.
* 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...
Normal: A non-embedded operating system is detected so skipping the 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: 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: 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...
* 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...
Major: In order to access Secure Sockets Layer (SSL) based tools such as
System Management Homepage and Version Control Repository Manager
on remote systems without performing an additional sign-in, you
need to establish trust between the Central Management Server (CMS)
and the managed system(s).
* Running system Manage Communication diagnosis...
* System identification finished on system.

Stderr: None

Andrew_Haak
Honored Contributor

Re: HP SIM 6.2 Discovery - completed with major errors

What is the OS and hardware type you want to discover ? 

Kind regards,

Andrew