Re: [opennms-discuss] ONMS 1.3.2 Snmp4JStrategy & PIX Error

[Mike C. <mco...@ma...>]

Matt,

Thanks, that update did the trick. Works like a champ now and appears to be
respecting the max-vars-per-pdu setting.

--=20
Mike Coakley
Managed Business
http://www.managedbusiness.com
http://my.managedbusiness.com
Voice - 973-252-0770 x2100
Fax - 973-252-1797





From: Matt Brozowski <br...@op...>
Reply-To: General OpenNMS Discussion <ope...@li...=
>
Date: Thu, 28 Sep 2006 17:41:31 -0400
To: General OpenNMS Discussion <ope...@li...>
Subject: Re: [opennms-discuss] ONMS 1.3.2 Snmp4JStrategy & PIX Error


On Sep 28, 2006, at 3:52 PM, Mike Coakley wrote:

> 00, Retries: 4, MaxVarsPerPdu: 1, Max request size: 1, Version: 1]
> 2006-09-28 15:24:05,789 INFO=A0 [Capsd Rescan Pool-fiber0] JoeSnmpWalker:
> Walking system/ifTable/ifXTable/ipAddrTable for /192.168.0.1 using versio=
n
> SNMPv1

<snip>

> 2006-09-28 15:24:05,791 DEBUG [Capsd Rescan Pool-fiber0] JoeSnmpWalker:
> Sending tracker pdu of size 38

This is clearly not honoring your MaxVarsPerPdu setting....

1. Don't ever set max request size since there is no code in place in the
walker to detect when this size is too large it will probably just kill
collection on that box.=A0 Instead just set maxVarsPerPdu to a size that will
work.=A0 We can't vary the request size in any way EXCEPT to change the numbe=
r
of vars we put in so that is all the size configurations we need.=A0 I will
likely take the maxRequestSize setting out.=A0 Setting it to 1 should work on
any system that you can SNMP walk.

2.=A0 Though the content of you message says Snmp4JStrategy, the about log is
clearly using the JoeSnmpWalker so if you were planning to be using SNMP4J
you were not.
Check your settings.

3.=A0 Given all of that I see that though you set maxVarsPerPdu to 1 is was
trying to send out requests of size 38.=A0 I looked through this code and
found a hard coded setting of 50 with a FIXME associated with it.=A0 I'm not
sure why that was there but I took it out and capsd should now honor your
setting.=A0 I have searched through the code and found a few other places
where the hardcoding setting existed.=A0 It should now work.=A0 The only anomal=
y
is that dataCollection has an ordering of 'which' maxVarsPerPdu setting it
will accept since you can set it separately in datacollection-config.xml=A0 I
think probably a better model would be to take the minimum of the
'maxVarsPerPdu' settings

Please check out the code with the fixes (revision 4615) and see if that
solves your problem.

Matt

=20
___________________________________________________________________________
Matt Brozowski, OpenNMS Maintainer Main: +1 919 812 4984
The OpenNMS Group, Inc. Fax: +1 503 961 7746
Email: br...@op... URL: http://www.opennms.com

=20



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share you=
r
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDEVDEV

_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of thi=
s
page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss