On Mon, Jun 30, 2008 at 05:35:41PM +0400, rbondar@rich-logic.com wrote:
I've fixed my agent. But scli still thinks the table is empty. Tcp dump follows: 17:32:46.323955 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 420) localhost.52925 > localhost.snmp: [bad udp cksum aaaf!] { SNMPv2c { GetNextRequest(373) R=1804289413 E:20379.2.1.3.2.3.1.2 E:20379.2.1.3.2.3.1.3 E:20379.2.1.3.2.3.1.4 E:20379.2.1.3.2.3.1.5 E:20379.2.1.3.2.3.1.6 E:20379.2.1.3.2.3.1.7 E:20379.2.1.3.2.3.1.8 E:20379.2.1.3.2.3.1.9 E:20379.2.1.3.2.3.1.10 E:20379.2.1.3.2.3.1.11 E:20379.2.1.3.2.3.1.12 E:20379.2.1.3.2.3.1.13 E:20379.2.1.3.2.3.1.14 E:20379.2.1.3.2.3.1.15 E:20379.2.1.3.2.3.1.16 E:20379.2.1.3.2.3.1.17 E:20379.2.1.3.2.3.1.18 } } 17:32:46.325952 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 471) localhost.snmp > localhost.52925: [bad udp cksum 7863!] { SNMPv2c { GetResponse(424) R=1804289413 E:20379.2.1.3.2.3.2.2=1 E:20379.2.1.3.2.3.2.3="proxy1" E:20379.2.1.3.2.3.2.4=192.168.1.2 E:20379.2.1.3.2.3.2.5=1 E:20379.2.1.3.2.3.2.6="gg" E:20379.2.1.3.2.3.2.7="gg" E:20379.2.1.3.2.3.2.8="gg" E:20379.2.1.3.2.3.2.9=1 E:20379.2.1.3.2.3.2.10="ya.ru" E:20379.2.1.3.2.3.2.11=213.24.20.202 E:20379.2.1.3.2.3.2.12="1313" E:20379.2.1.3.2.3.2.13=360 E:20379.2.1.3.2.3.2.14="ldom" E:20379.2.1.3.2.3.2.15="rdom" E:20379.2.1.3.2.3.2.16="1313" E:20379.2.1.3.2.3.2.17=213.24.20.202 E:20379.2.1.3.2.3.2.18=1 } }
Please double check your instance identifiers. Assuming E:20379.2.1.3.2.3.1 is the *Entry node, then the instance identifiers of the table columns should be of the form E:20379.2.1.3.2.3.1.c.x where c is the column number and x is the instance number (in case the table is indexed by a simple integer value).
/js