SuSE linux agents not connecting to CMS

[Scott Massari]

After properly setting the snmpd settings, discovered Linux systems are still showing as unknown in the SIM server.
I ran "Identify Systems" and it says snmp failed but all settings on the server are correct, this was the output:


Starting identification process...
Checking for known running web servers.
Checking for System Management Home Page and other HP web agents.
Received a response from the system management homepage, this system supports SMH.
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, or cannot connect to it using all credentials specified
Running WBEM rules based identification.
Cannot get ComputerSystem WBEM/WMI data from the system
Running WS-Man identification.
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.
The system does not have Windows DMI support.
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
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
idPluginStart.IPMCompatible
Running VM identification.
Checking for license data on system.
SMH trust status is false.
Running limited data collection for common attribute.
Done with limited data collection, checking retrieved data.
Building system relationships.
System identification done with this system.

[Rob Buxton]

You might be better off posting the snmpd.conf file.
Also, any firewalls involved?
Note community strings are case sensitive and do need to match on the HPSIM and remote server.

[Scott Massari]

snmpd.conf:

dlmod cmaX /usr/lib/libcmaX.so
rwcommunity public 127.0.0.1
rocommunity public 127.0.0.1
rocommunity public xxx.xxx.xxx.xxx
trapcommunity public
trapsink xxx.xxx.xxx.xxx public
syscontact Sysadmin (root@localhost)
syslocation Server Room

[Scott Massari]

No firewall involved. It seems to be all Linux systems. I have only manually added 3 - I wanted to get those working before I added all of them. The agents and snmp are installed on all of them as well.

[Scott Massari]

Retract my previous statement :)
I just found out there is a firewall between some of the subnets (it's only my third week here).

[Rob Buxton]

Providing the xxx's are the IP address of the HPSIM server that looks okay.

In the global settings is "public" the ro community name you're using?

Also by using the Options->Manage System Types and selecting new you can see if you do get an snmp response.

Unknown indicates HPSIM has contacted the server and found a management protocol, it just cannot use it. If you click on the server name and expand Product Description you'll find out what protocols its actually found. If it has snmp listed it could indicate a community name issue. Note that they are case-sensitive.