RE: Multiple sets in one pdu

Ok, got it, thanks a lot Dave for your help.

Best,
Yong Chen=20

> -----Original Message-----
> From: Dave Shield [mailto:D.T.Shield@csc.liv.ac.uk]=20
> Sent: Wednesday, December 14, 2005 1:10 AM
> To: Yong Chen (yongche)
> Cc: net-snmp-users@lists.sourceforge.net
> Subject: RE: Multiple sets in one pdu
>=20
> On Wed, 2005-12-14 at 00:35 -0800, Yong Chen (yongche) wrote:
> > Are you saying I can set 'b1' at RESERVE2 (instead of=20
> ACTION), then by=20
> > the time when 'a1' gets to ACTION phase, it can be set=20
> since 'b1' was=20
> > set already in previous pass?
>=20
> Yes.
>=20
> > But this approach seems to be not scalable.
>=20
> Correct.
>=20
> > If I have 'a' depending on
> > 'b', 'b' depending on 'c', 'c' depending on 'd', then I=20
> need to set 'd'
> > in RESERVE2, and 'c' in ACTION, and 'b' in COMMIT, then there's no=20
> > pass left for 'a'.
>=20
> If you've got that many interdependent variables:
>=20
> - processing them each in a separate pass is not a very
> efficient approach.
> - it *might* be possible to save the assignments in R1,
> sort them into the appropriate order in R2, and act
> on them in ACTION. (Or else act on them in R2, and
> report errors in ACTION).
> - you're probably stretching the v4 model further than it
> can sensibly go.
> - you could probably do with reviewing the design of your MIB!
>=20
>=20
>=20
> > (Actually when we return an error, do we really associate the error=20
> > with the offending varbind in response?)
>=20
> Yes.
>=20
>=20
> > Still the same problem, the error will be associated with the last=20
> > varbind, not the real "offending" varbind.
>=20
> Yup.
> Unless you jump through hoops to avoid this (see above).
>=20
>=20
> > Will 5.x handler style solve this problem?
>=20
> Yes.
>=20
> > All my varbinds are in the
> > same table so they can have one handler.
>=20
> And they will *all* be passed to the handler in one go, so=20
> you can whizz through the list as many times as you like.
>=20
>=20
> > Also just curious, in 5.x style, since one handler will=20
> have a list of=20
> > varbinds (in requests) as one of its input parameters, if=20
> some error=20
> > happens during processing, do we know in response pdu which varbind=20
> > caused the problem?
>=20
> Because the error is set for a particular varbind:
>=20
> netsnmp_set_request_error(reqinfo, request, SNMP_ERR_XXX);
> ^^^^^^^
>=20
> (where 'request' is looping through the list of varbinds).
>=20
>=20
> Dave
>=20


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/...net-snmp-users