[SIM6.1] Cannot identify EVA4400 Management Module

[Danilo B]

Hi all,

my SIM 6.1 is unable to identify the EVA4400 Management Module during discovery. Management Module respond to ping from SIM server, and network traffic between them is all allowed (ANY-ANY firewall rule). I am able to identify EVA from the CommandView Windows Server.
XCS version is 09522000, mmp-0001.3000-CR03D8

Please also note I have the problem described here:

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=ca&taskId=110&prodSeriesId=3664768&prodTypeId=12169&objectID=c02030082

but I don't know if thi is the password SIM is using to connect to management module.

Here is the identification log:

********* 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.
Critical: The Central Management Server (CMS) cannot communicate with 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: 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: 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 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.
* Resolving DNS names...
Normal: The DNS 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...
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.

[Rob Buxton]

SIM discovers the EVAs via the Management Server.
It uses any account that is in the local Storage Admins group on the CV Server.
The account and credentials for that account should be listed under the server specific settings for the CV Server in HPSIM.
Click on the server name, under Tools see the Edit Credentials section and add them there.

[Danilo B]

Thank you Rob for your answer. As I said I can correctly identify EVA from the management server. The problem is that the EVA managament module (the one I can access at https://[IP]:2372 and https://[IP]:2373 fot WOCP) is present in my HP SIM inventory but cannot be identified directly pointing to its IP address nor using the management server. Is SIM able to identify this module?

Regards, Danilo