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

SIM 6.3 Identification problem

Frederic Crespo
Occasional Advisor

SIM 6.3 Identification problem

Hello,

I am running into an identification problem.

Instead of using the discovery process for addind devices into SIM I import them from my CMDB using a custom script that leverages the mxnode command line utility.

Essentially for all devices in the CMDB I run the following command:
mxnode -a "nodename" -w

This effectively registers all the devices into HP SIM. However most often than not the device is not identified properly. All characteristics are recognized (name, serial number, protocols, ip address, os, etc) but the device is registered as unmanageable.

If I run more identification tasks on these systems the are not identified correctly. However if I delete them and add them through mxnode or discovery again most of the time they are identified correctly.

Hence the problem is that altough SIM has all info.config needed to identifiy the system it misses correct identification and cannot solve this trough Daily system identifications.

Any help will be greatly appreciated.
2 REPLIES
shocko
Honored Contributor

Re: SIM 6.3 Identification problem

Can we see the indentification logs?
If my post was helpful please award me Kudos! or Points :)
Frederic Crespo
Occasional Advisor

Re: SIM 6.3 Identification problem

Here is the identification task:
--------------------------------

System Name: 101-0004515
Status: Completed with major errors

Exit code: N/A
Stdout:

********* 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.
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 System Management Homepage and other HP web agents...
Normal: The System Management Homepage is not installed on this system. It
may not be supported.
* 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: Skipping IPMI discovery. System is logical device.
* Checking for WBEM protocol support on system...
Normal: The system is not a server so skipping WBEM identification.
* 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)
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...
Normal: This system has SSH protocol support.
* Running SSH Identification...
Normal: The system can be logged in using SSH protocol; has a valid SSH
credential.
* 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...
Normal: The system is not part of HP Serviceguard cluster.
* 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...
Normal: The bare-metal server will be added because the automatic server
discovery option for iLO is enabled.
* 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.
* Checking if this system is supported by Insight Control power
management...
* Insight Control power management is not supported.
* 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...
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.