prerequisite for SIM Clients

Scott James Walker — Fri, 24 Sep 2010 14:16:06 GMT

Hi, I have installed HP SIM and are having troble getting the machines I want to look after connect to it. The log keeps saying:

* 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...
Major: In order to access Secure Sockets Layer (SSL) based tools such as
System Management Homepage and Version Control Repository Manager
on remote systems without performing an additional sign-in, you
need to establish trust between the Central Management Server (CMS)
and the managed system(s).
* Running system Manage Communication diagnosis...
* System identification finished on system.

Can anyone help?

Re: prerequisite for SIM Clients

Rob Buxton — Sat, 25 Sep 2010 23:58:55 GMT

SIM can use a couple of ways to identify a server.
Easiest is SNMP. On the SIM side you need a community name set up in the Global Credentials.
On the client side you need SNMP set up to allow the SIM Server access on that community name.
SIM is moving to wbem, typically you just use a domain account / password to access the server.
In order for SIM to connect to the agents seamlessly you want to install the SIM Server's certificate on the client.
Once you have successfully ID'd a server you can replicate those settings to other servers.
You can also configure the agents before you deploy them to contain a number of the items that you change, including the certificate.

Re: prerequisite for SIM Clients

Change_happens — Mon, 04 Oct 2010 13:05:41 GMT

apart from what Rob has explained: SIM also gets all this snmp/wbem data through agents which is called PSP(proliant support pack).
SO PSP needs to be install on all HP servers from which you want to get data in SIM.

topic Re: prerequisite for SIM Clients in Server Management - Systems Insight Manager

prerequisite for SIM Clients

Re: prerequisite for SIM Clients

Re: prerequisite for SIM Clients