C7000 Enclosures not discovered in SIM 5.2

[Jason_Benoit]

I'm rather new to the BladeSystems and hve been tasked with making over 10+ C7000's get discovered in SIM. I've tried many of the other posted solutions without any success. Since we have so many enclosures that aren't being discovered I'm thinking its more SIM related than OA related.

Versions:
Systems Insight Manager 5.2 with SP2 - Windows
HP BladeSystem Integrated Manager 3.4
HP Insight Power Manager 1.40
HP Performance Management Pack 4.7.1
HP Server Migration Pack 2.0.2
HP Virtual Machine Management Pack 2.0.2
Rapid Deployment Pack 3.81

OA 2.25 - 2.32
ILO2 1.50 - 1.70

Here are my questions:

-Is ICE-BL v2.35 a requirement for the discovery to happen?
It didn't show as installed. When I tried to install it, the setup complained that RDP was newer and we might have some incompatibility issues. Of course just choosing the ICE-BL alone was not an option as check boxes were grayed out. Other engineer went through a fair amount of grief getting RDP configured so we're hesitant to uninstall it to get ICE-BL loaded.

-Tested SNMP and reviewed the XML code for special characters which all checked out ok.

Any assistance is certainly appreciated.

Regards,
Jason

[Ken Henault]

I believe this document will have the information you need:
http://h10018.www1.hp.com/wwsolutions/misc/hpsim-helpfiles/hpsim_51_identifying_cClass.pdf

[Jason_Benoit]

Ken, Thanks for your reply. I did see this doc and attempted both discovery scenarios unsucessfully. This particular doc doesn't even touch on troubleshooting. Here is the output of the failed discovery for the enclosure. It would be really nice to know which of these lines are responsible for its failure:

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 VMware ESX 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 responded to a SNMP request, it supports SNMP.
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
System has the SNMP ProLiant desktop agents installed, adding system type.
Running HP NetServer identification.
System supports the NetServer SNMP agent, adding system type
Running HP-UX SNMP identification.
System does not have the HPUX SNMP agents installed.
Running SNMP System Type Manager identification.
No matching SNMP System Type Manager rule was found.
Checking for DMI protocol support.
The Windows CMS cannot communicate with HP-UX or other DMI, skipping.
Running DMI System Type Manager identification.
The system does not have Windows DMI support.
Running HP-UX DMI identification.
The system does not have HP-UX DMI support.
Running HP/Compaq Desktop identification.
The system does not have Windows DMI support.
Running HP DMI Desktop identification.
The system does not have HP DMI Desktop support.
Running Generic DMI identification.
The system does not have Generic DMI support.
Checking for SSH protocol support.
The system supports SSH protocol
The SSH protocol is not supported on this system
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.
The system is not part of HP Service Guard cluster
Checking if this system is supported by Insight Power Manager.
Insight Power Manager is not supported.
Running VM identification.
System did not pass discovery filter, not added.

Any further direction is much appreciated.

Thanks,
Jason

[Ken Henault]

SIM should be able to talk to the OSa through WBEM and SSH. Seeing that it can't, it must not have the propper credentials. Select all youe OAs, then click on Options -> Protocol Settings -> System Protocol Settings..., and enter the user account and password for the OAs in the WBEM and SSH sections.

[Jason_Benoit]

Id had the proper credentials under global protocols settings. The encslosure wasn't discovered thus making it not available for searching under system protocol settings. So I added it manually and then went and confirmed the ssh and OA credentials. The device shows as (Unknown) just as it always did when manually adding.

On the OA the HP SIM integration has Trust "Disabled". Is it likely that I need to import a cert from the SIM to make this thing discover automatically?

Thanks,
Jason

[David Claypool]

"Trust" is necessary only for single-sign-on (i.e. clicking on the OA link in HP SIM and getting to the OA UI without having to log in).

The enclosure is an implied entity in HP SIM. Its construct is derived through discovering the OA via IP address or DNS name. During discovery HP SIM requests the results of http://[OA_IP_OR_DNS_NAME]/xmldata?item=all which will provide an XML response detailing the enclosure and its contents.

One red flag in your identification log is the comment "System has the SNMP ProLiant *desktop* agents installed, adding system type." which shouldn't be happening.

[Jason_Benoit]

-So I ran http://10.127.128.67/xmldata?item=all from a browser on the SIM server then searched down for desktop which didn't pull any hits.

-We have have 10 or 12 of these in our datacenter and none of them are being discovered. I'm just using an IP inclusion range a dicovery task on the one until I can get it to show under "All c-Class Enclosures" in SIM.

-I'm already two days into this with no luck, so I'm open to any plausible suggestions.

Thanks,
Jason

[Siddiqui]

Hi Guys and gals, any update on this? We have quite a few enclsoures which are readable ny HP SIM bit the one I am having issues with is not able to populate the enclsoures details ( All Blades, All interconnect Switches and also All Onboard Administrators)

[gregersenj]

You must set correct credentials, at both ends.

i suppose, HP SIM has successfully pinged the OA.

Log into the OA.

Select enclosure settings.

Select snmp settings.

set snmp community.

add the host(s), that it must accept snmp communication with.

in HP SIM.

Select IP address for the OA(s).

Select the tools and links tab.

Select system credentials.

Set snmp community.

Worked for me yesterday :)

BR

/jag