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

Adding EVA 4400 to HP-SIM

UselessUser
Frequent Advisor

Adding EVA 4400 to HP-SIM

Hi,

I am learning this app slowly and have got many bits of kit in, apart from the EVA 4400...

I have tried a basic discovery with its management module IP address but I get this back:

Starting identification process...
Checking for known running web servers.
Checking for System Management Home Page and other HP web agents.
The System Management Homepage is not supported on this system.
Checking for WBEM support on system.
This system does not have any SMI-S CIMOM installed
This system doesn't have a server CIMOM installed locally, or cannot connect to it using all credentials specified
Running WBEM rules based identification.
Cannot get ComputerSystem WBEM/WMI data from the system
Running VM Identification.
The system is not a VM Host, or WBEM credentials may not be specified, skipping VM Identification
Running WS-Man identification.
The system did not respond to WS-Management, verify credentials.
Checking for SNMP support on system.
The system did not respond to SNMP, verify security settings and community strings.
Running SNMP base Cluster identification using common cluster MIB.
This was not a system with the common cluster MIBs supported.
Running HP ProLiant management agent identification
The system does not support SNMP.
Running HP NetServer identification.
The system does not support SNMP.
Running HP-UX SNMP identification.
The system does not support SNMP.
Running SNMP System Type Manager identification.
The system does not support SNMP.
Checking for DMI protocol support.
DMI is globally disabled, skipping DMI identification.
Running DMI System Type Manager identification.
DMI is globally disabled, skipping DMI identification.
Running HP-UX DMI identification.
DMI is globally disabled, skipping DMI identification.
Running HP/Compaq Desktop identification.
DMI is globally disabled, skipping DMI identification.
Running HP DMI Desktop identification.
DMI is globally disabled, skipping DMI identification.
Running Generic DMI identification.
DMI is globally disabled, skipping DMI identification.
Running SSH Protocol identification.
The SSH protocol is not supported on this system
Running SSH Identification.
SSH Protocol is not detected; skipped SSH Identification
Running Storage identification.
Did not detect WBEM support on this system. Will not attempt storage identification. If this is a storage host, check WBEM credentials and make sure the providers and CIMOM are operational on the host.
Storage identification completed.
Running HP Service Guard Identification.
Running SNMP Subtypes identification
Create bare-metal device nodes if OA is discovered with "Automatic Device discovery" option enabled.
Create bare-metal server node if ILO is discovered with "Automatic Server discovery" option enabled.
Running VM identification.
VMM Integration is not enabled, skipping VM Identification
Building system relationships.
Running limited data collection for common attribute.
The system does not have SMH or SSO support.
Running node communication diagnosis
System identification done with this system.

As I have the latest firmware on the EVA the Command View software is now integrated into the management module itself but people keep mentioning some SMI-S module??

Also please note my HP SIM server does not have fibre connectivity to the EVA, just IP...

Any ideas?
3 REPLIES
AdamJ
Frequent Advisor

Re: Adding EVA 4400 to HP-SIM

What version of SIM are you using?

What version of Command View are you running?

Have you established a trust relationship with the SIM server from within Command View?
UselessUser
Frequent Advisor

Re: Adding EVA 4400 to HP-SIM

Hi,

I am using HPSIM 5.3 in a VM.

Command View (running on the EVA now)..

Version: 08.01.00.081213

I saw the option for trust relationship but not sure if I needed to do anything or not?
AdamJ
Frequent Advisor

Re: Adding EVA 4400 to HP-SIM

OK. The way that EVAs are added to SIM is being discovered through the Command View server.

You need to set the trust relationship in Command View by installing the SIM certificate.

Do you have WBEM/WMI credentials configured in SIM for the server that is running command view?

Once this is setup you must run an identify on the Command View server and it should pick up the EVA.