Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
Server Management - Systems Insight Manager
Showing results for 
Search instead for 
Did you mean: 

Unable to Discover a Switch through HP SIM

Occasional Collector

Unable to Discover a Switch through HP SIM


I'm trying to discover a switch in HP SIM server but it always results in the status "Completed with major errors" and the report is

********* Significant issues and overall target discovery/identification
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: 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.
Normal: The system has valid hardware data (model, serial number, and
unique identifier) and has been identified properly for SIM to
Major: 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 SNMP protocol support on system...
Normal: The system did not respond to SNMP. Verify security settings and
community strings in Options->Security->Credentials->System
* 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
* Running HP ProLiant management agent identification...
Normal: The system does not support SNMP.
* Running SNMP base cluster identification using common cluster
Normal: SNMP is not supported or globally disabled, skipping SNMP cluster
* 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...
Normal: The system is not a server so skipping WBEM identification.
* Running Virtual Machine (VM) Host (non HP Integrity VM Host)
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: 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...
Minor: Running an ipmiutil command failed and the IPMI protocol is not
* Running SSH Protocol identification...
Normal: The device is a switch. Skipping check for SSH protocol.
* Running SSH Identification...
Normal: The system can be logged in using SSH protocol; has a valid SSH
Normal: OS Name is identified by the SSH Identification.
* Running WS-Man identification...
Normal: A non-embedded operating system is detected so skipping the WS-MAN
* Running Monarch OA Identification...
Normal: The system is not a monarch OA so skipping monarch OA
* 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...
Normal: The system is not part of HP Serviceguard cluster.
* 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: Node is not a Virtual Center Node
* Checking if this system is supported by Insight Control power
* Insight Control power management is not supported.
* Running Virtual Machine Management (VMM) Plug-in Identification...
* Building system relationships...
Minor: The Secure Shell key-based access authentication is not configured
on the 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.

Can you please help me on getting this resolved?


Valued Contributor

Re: Unable to Discover a Switch through HP SIM

i'm sure there are better people to help, but i would start by setting up SNMP on that switch, and make sure SIM is configured to read that straing i.e. public, then try a rediscovery on that.

Honored Contributor

Re: Unable to Discover a Switch through HP SIM

I agree and see if the switch is supported? If it a HP switch? If it's not see if there is a mib file you can download and import in SIM if needed.

Kind regards,