HP SIM 7.3.0 and Linux client software

[gnubibi]

Hello,

I am newb in HP SIM, I have tried to read different documentation, but it's still confused.

First, sorry for my bad english, I hope you'll understand :)

Configuration :

HP SIM 7.3.0 on Windows

Linux server are Red-Hat 5/6

HP Tools installed are :

hpacucli-9.10-22.0.x86_64
hp-ams-1.4.1-1089.1.rhel6.x86_64
HP-CNA-FC-hpqlgc-Enablement-Kit-2.0.0.0-4.noarch
hpdiags-9.5.0-938.x86_64
hp-health-9.40-1602.44.rhel6.x86_64
hpmouse-1.2.1-1.noarch
hp-nx_nic-docs-1.0.0-1.noarch
hp-nx_nic-tools-4.0.590.6.1-1.noarch
hp-ocsbbd-1.1.38.0-1.x86_64
hponcfg-4.2.0-0.x86_64
hp-qlgc-docs-1.0.0-1.noarch
hp-qlgc-utils-1.0.0-1.noarch
hpsmh-7.2.2-8.x86_64
hp-smh-templates-9.4.0-1327.37.noarch
hp-snmp-agents-9.40-2506.37.rhel6.x86_64
hpssa-1.50-4.0.x86_64
hpssacli-1.50-4.0.x86_64
hp-tg3sd-1.0.12-1.x86_64
hpvca-7.1.0-2.i386

Discover is working, but I had to give root permission to the hp-sim basic user, to get info during a ssh access.

I have setup a user account with sudo access, but it's not working.

Do we have to use root access the first time, and for the different update HP-SIM will use the user account with sudo ?

Also, snmp is not working, and I do not understant why.

I am able to snmpwalk the linux pc from the windows server.

And snmpd.conf look good :

rocommunity hpsim "IP_HPSIM-SERVER" should work ?
Community is also set in hpsim.

So without snmp, I am not able to retrieve software status, and compare it to the baseline.

But we're able to do software update.

Somebody can help me about this 2 points :

- snmpd communication

- use basic user + sudo than root user

Thanks for your help.

[Andrew_Haak]

Hello,

Could it be that the community is right but the IP of the SIM server was not added ?

The second question is answered where : 

http://h30499.www3.hp.com/t5/ITRC-HP-Systems-Insight-Manager/Linux-and-HPSIM-6-1-root-access/td-p/4780119#.UxYvIWa0vMI

Kind regards,

Andrew

[gnubibi]

Hello,

Thanks for your reply.

Snmpd is well configured and working, we use it for our monitoring.

So the community and ip address were added. It's the same if I use the public community.

I do not understrant why HP-SIM can't communicate with snmp :(

About ssh, when I launch a discovery, if root password has not been set, I won't be able to get information like identification informations (serial number...). dmidecode is used to get this information.

If I let HPSIM using my "normal" account with sudo permission, he won't be able to get these informations :(

And I do not want to set root password for X servers in HP-SIM.

Is there a clear "how to" about configuring Linux servers in HP-SIM ?

Normally we should have :

- HP SIM Server

On client side :

- HP tools

- snmp to retrieve software informations

- ssh with root access to grab information (only used 1 time ?)

- ssh accound with sudo permissions for update ?

I juste wand to see software version installed on client side, compared to a baseline and start and update if needed :)

And I do not want HP SIM using a root account, but a normal account deployed on all my servers with right sudo permission.

++

[gnubibi]

Discovery log :

********* Significant issues and overall target discovery/identification
status:
Major: The system cannot be identified properly for HP SIM to manage;
unable to get one or more of the following: model, serial number or
unique identifier (UUID). For management processors, verify the
system is running the latest firmware. For Linux based operating
systems, you must have dmidecode installed, enable the
PermitRootLogin and PasswordAuthentication in sshd, and use root
sign-in credential. For HP-UX, verify the sign-in credential. For
Windows, check if WMIMapper is configured correctly on the CMS and
verify the sign-in credential.
Normal: MiniCRA has started to run as part of the discovery task, the
situation may remedy itself later. To view the task result for the
MiniCRA task, go to Tasks&Logs -> View Task Results, and click on
the Job Id [74452].
Critical: The system(s) can not be identified by WBEM, SNMP or SSH

********* Additional results (listed for information only):

* Starting identification process...
* Checking for known running web servers...
* 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
* Checking for SNMPv3 protocol support on system...
Minor: Global SNMPv3 Identification is disabled.
* Running HP ProLiant management agent identification...
Normal: The system does not support SNMP.
* Running SNMP base cluster identification using common cluster
MIB...
Normal: SNMP is not supported or globally disabled, skipping SNMP cluster
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 Storage identification...
* Did not detect the WBEM protocol support on this system. SMI
storage identification will be skipped.
* Storage identification completed.
* Running HP NetServer identification...
Normal: The system does not support SNMP.
* Running HP-UX SNMP identification...
Normal: The system does not support SNMP.
* 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 XMLReply Identifier which will discover systems in a
rack/enclosure if the automatic discovery option for the container
node is enabled...
* 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.
Minor: If the http communication from CMS to target is working, but if it
is found to be slow then try increasing the Default connection
timeout parameter for http in global protocol settings.
* Running p-Class Identifier...
Normal: The system is not a p-Class so skipping p-Class identification.
* Running IPMI protocol identification...
Normal: IPMI protocol not detected so skipping IPMI Identification.
* Running SSH Protocol identification...
Normal: This system has SSH protocol support.
* Running SSH Identification...
Normal: The system can be logged in using SSH protocol; has a valid SSH
credential.
Normal: OS Name is identified by the SSH Identification.
* Running WS-Man identification...
Major: WS-Management(WS-Man) is globally disabled so skipping WS-Man
identification.
* Running Monarch OA Identification...
Normal: The system is not a monarch OA so skipping monarch OA
identification.
* Checking for System Management Homepage and other HP web agents...
Normal: The system is not a server, storage or desktop. Skipping the check
for System Management Homepage.
* Running HP Serviceguard Identification...
Normal: The system is not part of HP Serviceguard cluster.
* Running SNMP System Type manager ...
Normal: The system does not support SNMP.
* Running SNMP subtypes identification...
* Resolving DNS names...
Normal: The fully qualified domain name was successfully resolved for the
system.
* Checking if the Node is a Virtual Center...
Normal: Skipping MxVirtualCenter Identifier
* Running Virtual Machine Management (VMM) Plug-in Identification...
* System passed the discovery filter and will be added.
* Building system relationships...
Minor: The Secure Shell key-based access authentication is not configured
on the system(s).
Minor: System Management Homepage (SMH) is not installed or is not
responding on the system(s).
* Running system Manage Communication diagnosis...
* System identification finished on system.

[gnubibi]

snmp, hp-smh, ssh are running and woring well on the linux client.

[sunhero]

Did you try to change your snmpd.conf file premission for tesitng?