SIM and Linux Client not detecting hardware

[Oxiel Contreras]

Hello gurus.

Client has RHEL5 x86_64 with latest Support Pack: psp-8.11.rhel5.x86_64.en.tar.gz

/etc/snmp/snmpd.conf contains:
# Following entries were added by HP Insight Management Agents at
# Tue Sep 16 16:41:54 BOT 2008
dlmod cmaX /usr/lib64/libcmaX64.so
rwcommunity eyPatcmLofQS 127.0.0.1
rwcommunity xxxxx 10.1.100.13
rocommunity xxxxx 10.1.100.13
trapcommunity public
trapsink 10.1.100.13 xxxxx
syscontact AAAAAAA 555555 BBBBBBB
syslocation CCCCCCC
# ---------------------- END --------------------
com2sec notConfigUser default public
group notConfigGroup v1 notConfigUser
group notConfigGroup v2c notConfigUser
view systemview included .1.3.6.1.2.1.1
view systemview included .1.3.6.1.2.1.25.1.1
access notConfigGroup "" any noauth exact systemview none none
pass .1.3.6.1.4.1.4413.4.1 /usr/bin/ucd5820stat

Products involved:
HP BladeSystem Integrated Manager 3.2
HP Insight Control Management 2.20
HP Insight Power Manager 1.40
HP Performance Management Pack 4.7

Hardware involved: Proliant BL465c G1 on Blade Enclosure.

SIM is 10.1.100.13 on W2k3, the problem is that no matter what i do, i can not get the Linux server get correctly identified nor associated to its ilo, i mean the "servers collection" shows this:
ns2 Server 10.1.100.12 Linux Server LINUX
sc01srvadpdc
in Encl. C7000-1 Server 10.1.100.20 ProLiant BL465c G5 Microsoft Windows Serv...

So nothing can be done with linux servers, IPM, nor PMP, nothing because they don't show they are Proliant BL465c G1, etc.

What is the procedure to manage Linux Servers with SIM ?

Best regards.

Oxiel

[VRC]

On Linux, SNMP is the only communication protocol (with some little support from SSH). So make sure snmp community string on the linux box is public. Also check with any snmp utility that the linux machine responds to simple snmp request. (use tools like MibWalker / MibBrowser/ snmputil, etc.)

If all these works, then the machine should be identified properly by SIM. Also if iLo is not linked properly, re-identifying iLo should resolve this issue.

For OpenSSH to work, give the credential in Global credentials page or System credential page before discovering or re-identifying the machine.

-VRC