SIM - Eva 4400 discovery problem.

Pavel Slepushkin — Wed, 15 Dec 2010 06:20:28 GMT

Hello.

I'm trying to add EVA 4400 to SIM. I've installed SIM and Command View on same server.
Command view SMI-S is using port 60000.
Wbemdisco works OK (i've attached the output).
The problem is - when I try to discover EVA I got critical error
Critical: There are no valid WBEM / WMI credentials for the system(s).

I've double check the credentials: I've entered WEB/WMI credentials for host, discovery credentials, but nothing helps.

What should I do next?

Re: SIM - Eva 4400 discovery problem.

Pavel Slepushkin — Wed, 15 Dec 2010 13:44:50 GMT

Hello again.
I checked all log files and found errors in PegasusStandart.log (WMI Mapper).
--------------------
WARNING cimserver: Failed to Login. Invalid username or password.
-------------------

I also read that SMI-S doesn't need WBEM/WMI and works throw HTTPS, but discovery process returns error:
Minor: This system does not have any SMI-S CIMOMs installed. No storage
systems will be found on this system.

Re: SIM - Eva 4400 discovery problem.

BPE — Wed, 15 Dec 2010 23:11:55 GMT

Did you add the port 60000 to the wbemportlist xml file in \program files\HP\system insight manager\config\identification\wbemportlist.xml?

See help->troubleshooting for details

Re: SIM - Eva 4400 discovery problem.

ITRC Test-CH — Thu, 16 Dec 2010 06:22:28 GMT

You must enter this port number in the system credentials of your system whit command view on it also.
Easier: If only the Pegasus WMImapper is the reason for a port change for CV, just set the WMI Mapper proxy port to 6989 and modify this in the WMI Mapper settings too.

Regards, Werner

Re: SIM - Eva 4400 discovery problem.

Pavel Slepushkin — Thu, 16 Dec 2010 10:45:56 GMT

Thank you.

I've added 60000 port to wbemportlist.xml and now I can see in log that SIM sees SMI-S agent, but still can not connect to it.
-------------------discovery log-------------

********* 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: There are no valid WBEM / WMI credentials for 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 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...
Normal: This system has at least one SMI-S CIMOM installed to serve as the
storage proxy to discover storage systems.
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.
Critical: There are no valid WBEM / WMI credentials for the system(s).
* 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 ProLiant SNMP Foundation agents for servers are not installed
or are not configured.
* 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...
Normal: This system has SSH protocol support.
* Running SSH Identification...
Minor: The system cannot be logged in using SSH protocol; check
credentials or check the settings in the SSH configuration file
* Running Storage identification...
* This system has some storage related information and additional
storage systems may be added.
* 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...
Minor: The Secure Shell key-based access authentication is not configured
on the system(s).
Normal: The trust between the CMS and the managed system is established.
* Running system Manage Communication diagnosis...
* System identification finished on system.
---------------------------------------

SIM version 6.2
Windows Server 2003 R2 working on virtual machine (vmware ESX)
Any ideas?

topic Re: SIM - Eva 4400 discovery problem. in Server Management - Systems Insight Manager

SIM - Eva 4400 discovery problem.

Re: SIM - Eva 4400 discovery problem.

Re: SIM - Eva 4400 discovery problem.

Re: SIM - Eva 4400 discovery problem.

Re: SIM - Eva 4400 discovery problem.