philippe wrote: > Hi, > > I added an interface eth0 to the OS tab of a Linux server. > > When the system polls, I get the following message in the events tab: > Error reading value for "eth0" on XXXXX (oid .1.3.6.1.2.1.2.2.1.17.0 is bad). > Also the graphs for the interface don't appear. > > I get this for all the OIDs for which interface data is collected. > > Now, if I snmpwalk or snmpget my system, using exactly the same OIDs as above > MINUS the trailing zero, it works but of course if I use the trailing zeroes > above it fails. Also, if I go into the relevant template, the OIDs there are > set fine, no trailing zeroes and if I do "test against the device", it works > just fine. > > Is this mysterious trailing zero responsible for the lack of data collection > ? Any idea what causes this ? > > Thanks in advance for any help you can provide. > > Philippe.
More than likely...eth0 isn't .0 in your if index. For example, if I snmpwalk my localhost: > [EMAIL PROTECTED]:~# snmpwalk -v2c -c public localhost 1.3.6.1.2.1.2.2.1 > IF-MIB::ifIndex.1 = INTEGER: 1 > IF-MIB::ifIndex.2 = INTEGER: 2 > IF-MIB::ifIndex.3 = INTEGER: 3 > IF-MIB::ifDescr.1 = STRING: lo > IF-MIB::ifDescr.2 = STRING: eth1 > IF-MIB::ifDescr.3 = STRING: eth0 > IF-MIB::ifType.1 = INTEGER: softwareLoopback(24) > IF-MIB::ifType.2 = INTEGER: ethernetCsmacd(6) > IF-MIB::ifType.3 = INTEGER: ethernetCsmacd(6) > IF-MIB::ifMtu.1 = INTEGER: 16436 > IF-MIB::ifMtu.2 = INTEGER: 1500 > IF-MIB::ifMtu.3 = INTEGER: 1500 > IF-MIB::ifSpeed.1 = Gauge32: 10000000 > IF-MIB::ifSpeed.2 = Gauge32: 10000000 > IF-MIB::ifSpeed.3 = Gauge32: 10000000 > IF-MIB::ifPhysAddress.1 = STRING: > IF-MIB::ifPhysAddress.2 = STRING: 0:50:4:d3:6d:f3 > IF-MIB::ifPhysAddress.3 = STRING: 0:1:3:33:62:80 > IF-MIB::ifAdminStatus.1 = INTEGER: up(1) > IF-MIB::ifAdminStatus.2 = INTEGER: up(1) > IF-MIB::ifAdminStatus.3 = INTEGER: up(1) > IF-MIB::ifOperStatus.1 = INTEGER: up(1) > IF-MIB::ifOperStatus.2 = INTEGER: up(1) > IF-MIB::ifOperStatus.3 = INTEGER: up(1) > IF-MIB::ifLastChange.1 = Timeticks: (0) 0:00:00.00 > IF-MIB::ifLastChange.2 = Timeticks: (0) 0:00:00.00 > IF-MIB::ifLastChange.3 = Timeticks: (0) 0:00:00.00 > IF-MIB::ifInOctets.1 = Counter32: 4730624 > IF-MIB::ifInOctets.2 = Counter32: 443262134 > IF-MIB::ifInOctets.3 = Counter32: 499608857 > IF-MIB::ifInUcastPkts.1 = Counter32: 56891 > IF-MIB::ifInUcastPkts.2 = Counter32: 607549 > IF-MIB::ifInUcastPkts.3 = Counter32: 4520588 > IF-MIB::ifInNUcastPkts.1 = Counter32: 0 > IF-MIB::ifInNUcastPkts.2 = Counter32: 0 > IF-MIB::ifInNUcastPkts.3 = Counter32: 0 > IF-MIB::ifInDiscards.1 = Counter32: 0 > IF-MIB::ifInDiscards.2 = Counter32: 0 > IF-MIB::ifInDiscards.3 = Counter32: 0 > IF-MIB::ifInErrors.1 = Counter32: 0 > IF-MIB::ifInErrors.2 = Counter32: 0 > IF-MIB::ifInErrors.3 = Counter32: 0 > IF-MIB::ifInUnknownProtos.1 = Counter32: 0 > IF-MIB::ifInUnknownProtos.2 = Counter32: 0 > IF-MIB::ifInUnknownProtos.3 = Counter32: 0 > IF-MIB::ifOutOctets.1 = Counter32: 4730624 > IF-MIB::ifOutOctets.2 = Counter32: 515224503 > IF-MIB::ifOutOctets.3 = Counter32: 29798825 > IF-MIB::ifOutUcastPkts.1 = Counter32: 56891 > IF-MIB::ifOutUcastPkts.2 = Counter32: 596707 > IF-MIB::ifOutUcastPkts.3 = Counter32: 201536 > IF-MIB::ifOutNUcastPkts.1 = Counter32: 0 > IF-MIB::ifOutNUcastPkts.2 = Counter32: 0 > IF-MIB::ifOutNUcastPkts.3 = Counter32: 0 > IF-MIB::ifOutDiscards.1 = Counter32: 0 > IF-MIB::ifOutDiscards.2 = Counter32: 0 > IF-MIB::ifOutDiscards.3 = Counter32: 0 > IF-MIB::ifOutErrors.1 = Counter32: 0 > IF-MIB::ifOutErrors.2 = Counter32: 0 > IF-MIB::ifOutErrors.3 = Counter32: 0 > IF-MIB::ifOutQLen.1 = Gauge32: 0 > IF-MIB::ifOutQLen.2 = Gauge32: 0 > IF-MIB::ifOutQLen.3 = Gauge32: 0 > IF-MIB::ifSpecific.1 = OID: SNMPv2-SMI::zeroDotZero > IF-MIB::ifSpecific.2 = OID: SNMPv2-SMI::zeroDotZero > IF-MIB::ifSpecific.3 = OID: SNMPv2-SMI::zeroDotZero look at ifDescr....eth0 has a .3 on the end. It should be the same index (.3) for all the oid's that collect info on eth0. It's not a .0 necessarily. You shouldn't really need to add any interfaces to zenoss. The modeling process should pick it up automatically. You can manually run a model as described here: http://www.zenoss.com/community/docs/zenoss-guide/2.3.0/ch10s11.html#d0e3149 Just be sure you don't assign a ethernetCsmacd directly to a server. The modeling process will automatically graph the ethernetCsmacd template that's bound to the class and populate the ethernet devices for you. If that's not working...be sure you can do an snmpwalk to that device from within the zengui first. It should be available if you go to the device and click the top left drop down. -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=27724#27724 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
