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

Discovery Wintel : Critical: HP SIM cannot communicate with the SNMP service on the system(s).

 
SOLVED
Go to solution
Mrpink200
Occasional Advisor

Discovery Wintel : Critical: HP SIM cannot communicate with the SNMP service on the system(s).

Hello to all

 

I got troubles discoverying Wintel servers for a couple of weeks.

When i access the server and apply SNMP configuration manualy, it works

When i try to setup it while discovering with the Configure and Repair tool... i got the following message

Im surprise / afraid by the UUID message, witch i do not understand

Something wrong with mibs ?

 

 

HP SIM 6.3

All Patchs have been applied

MIB upgraded to 8.70

 

Log : for a PROLIANT BL460C... but same things happen with other Proliant Wintel servers

********* 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 XXXXXX.
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.
Critical: HP SIM cannot communicate with the SNMP service on the system(s).

********* 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 did not respond to SNMP. Verify security settings and
community strings in Options->Security->Credentials->System
Credentials
* Running SNMP System Type manager ...
Normal: The system does not support SNMP.
* 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 system does not support SNMP.
* Running HP NetServer identification...
Normal: The system does not support SNMP.
* Running HP-UX SNMP identification...
Normal: The system does not support SNMP.
* 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...
* 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 Enclosure Manager Identifier which will discover systems in
an enclosure if the automatic enclosure discovery option for
Enclosure Manager is enabled...
Normal: The system is not an Enclosure Manager, 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...
* 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.

 

4 REPLIES
shocko
Honored Contributor

Re: Discovery Wintel : Critical: HP SIM cannot communicate with the SNMP service on the system(s).

What version of the agents on the target  server?

If my post was helpful please award me Kudos! or Points :)
shocko
Honored Contributor

Re: Discovery Wintel : Critical: HP SIM cannot communicate with the SNMP service on the system(s).

Also seems like you need ot check your DNS settings and ensure the CMS can be fully resolved for both A & PTR record
If my post was helpful please award me Kudos! or Points :)
pz7rx8
Advisor

Re: Discovery Wintel : Critical: HP SIM cannot communicate with the SNMP service on the system(s).

I have had that same problem several times. Everytime the problem was the SNMP string entered in SIM had a blank space at the end so it did not match the snmp string on the server.

Mrpink200
Occasional Advisor
Solution

Re: Discovery Wintel : Critical: HP SIM cannot communicate with the SNMP service on the system(s).

I found the pb. the sim server snmp service had its ip changed. fixing it solved the pb ....