MSA Storage
cancel
Showing results for 
Search instead for 
Did you mean: 

MSA2012fc not connecting to SIM

 
Clark Ambrose
Occasional Contributor

MSA2012fc not connecting to SIM

We have an MSA2012fc dual-controller connected to an HP DL580 G3 running ESX 3.5. SIM 5.3 is installed on another management server. The DL580 with ESX reports its status properly to SIM, but we cannot get the MSA to report.

SNMP is turned on and set to report all levels on the MSA and we have tried sending a test trap, but SIM never seems to receive any events. We do have it connected through the ethernet interface into the same subnet as the server running SIM.

I have not been able to find any information for this series that we need to load any additional software for SIM to be able to pick up the SAN.
4 REPLIES 4
Clark Ambrose
Occasional Contributor

Re: MSA2012fc not connecting to SIM

This is what I get when I run discovery against the SAN from SIM 5.3. Note that I can connect to the SAN via SSH and http from the same server that SIM is hosted on.

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 system supports SSH protocol
Running SSH Identification.
This system cannot be logged in using ssh; check credentials or use a non-root user
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 SSH is not configured on this system
The system does not have SMH or SSO support.
Running node communication diagnosis
System identification done with this system.


Martin Smoral
Trusted Contributor

Re: MSA2012fc not connecting to SIM

Since the MSA2012 definately supports SNMP, I would verify the SNMP Trap destination and make sure the security settings and community strings match what SIM is looking for.
Clark Ambrose
Occasional Contributor

Re: MSA2012fc not connecting to SIM

SNMP trapping is sending to the correct address and is enabled for informational and up. The public strings match.

I checked the security settings in SIM and they correspond to the user account on the SAN, although this part I'm not 100% confident on. Should it just use the management account that I use to log into the SAN?
Martin Smoral
Trusted Contributor

Re: MSA2012fc not connecting to SIM

Maybe the trap is coming through as unregistered. See if you have SIM set to acccept unregistered events. This is not selected by default. if not then set it and try it again.