#10 Many templates share "sysdesc" in specs

[canne]

I found out that the following templates share the same "sysdesc" line in the file "specs":
linux-netsnmp
compaq-server
dell-perc

This ends up in having the wrong template for Linux servers.
I got no warnings in the log for this.

[Buchan Milne]

Which is the correct template in your case?

(device identification based solely on sysDescr is wrong, but it is quite some work to get to a better solution).

For now, you should specify the template you want with the model option in bb-hosts, or edit the sysdesc values of the templates you don't use ...

[Buchan Milne]

To be more specific, even if devmon used something other than sysDescr to identify devices, such as by sysObjectID, dell-perc is for a older Dell server running Linux that has a:

pass .1.3.6.1.4.1.3582 /usr/sbin/percmain
statement in snmpd.conf, without overriding sysObjectID:
SNMPv2-MIB::sysObjectID.0 NET-SNMP-MIB::netSnmpAgentOIDs.10
or extending the sysOR table.

compaq-server works for HP/Compaq ProLiant servers running Windows or Linux with HP's HPSIM/HPASM stuff, on Linux, this is net-snmp with:
dlmod cmaX /usr/lib64/libcmaX64.so
and some processes started by the hpasm service. Again, without overriding sysObjectID, or extending sysOR table:

SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10

Contrast this to (e.g.) cisco devices

SNMPv2-MIB::sysObjectID.0 = OID: CISCO-PRODUCTS-MIB::cisco2821
or
SNMPv2-MIB::sysObjectID.0 = OID: CISCO-PRODUCTS-MIB::cisco7304
or
SNMPv2-MIB::sysObjectID.0 = OID: CISCO-PRODUCTS-MIB::ciscoWSC6513