Servers listed as Unknown (X3800 NAS)

[DMorgan]

Hey everyone!

I hope someone can help! We have purchased about 6 of the X3800 NAS Servers and have built them using the System Recovery 1.3 DVD. I have configured the Management Agents, SMH and VCAgent correctly as we normally would and everything is running the latest versions. e.g. 8.6 Management Agents.

Sadly I cant get any of the Servers to register correctly on HP SIM (Version 6.2). If I disable my discovery filter or tick Unknown in System Types then it will be discovered but reported as Unknown system type in SIM.

The report below is from a System Identification task. It seems to be having problems detecting the system type.

Does anyone have any ideas or recommendations???

********* 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: Identification can get the system information from the ProLiant
SNMP Foundation agents for servers.
* 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...
Normal: The trust between the CMS and the managed system is established.
* Running system Manage Communication diagnosis...
* System identification finished on system.

[DMorgan]

Update:

Interestingly I deleted an old X3800 and that now doesnt detect properly either so this is obviously a change caused by the upgrade to 6.2 of SIM. I have created a new System Type called "HP X3800 Network Storage Gateway" with the System Object Identifier as "1.3.6.1.4.1.311.1.1.3.1.2" and assigned as a Server. It detects fine now except the errors below:

********* Significant issues and overall target discovery/identification
status:
Normal: The system has valid hardware data (model, serial number, and
unique identifier) and has been identified properly for SIM to
manage.
Critical: The system(s) can not be identified by either WBEM or SNMP

********* 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: Found matching SNMP System Type Manager rule and the system type
will be added.
* 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: Identification can get the system information from the ProLiant
SNMP Foundation agents for servers.
* 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...
Normal: The trust between the CMS and the managed system is established.
* Running system Manage Communication diagnosis...
* System identification finished on system.

[David Claypool]

Use 'Manage Communications' to diagnose.