Re: Setting multiple table rows in one set operation

I managed to install version 5.3.01 in another machine and tried the same
simple example. I only made the change of the MAX-ACESS to read-create
instead of read-write. Then I execute mib2c with the dataset handler and
created a simple agent.

I tried to execute the same set to create several rows and now everything is
working fine!



Thank you very much for your support.



----- Original Message ----- 

From: "Dave Shield" <[email protected]>
To: "vsaavedra" <[email protected]>
Cc: <[email protected]>
Sent: Thursday, January 17, 2008 3:34 PM
Subject: Re: Setting multiple table rows in one set operation


> On 17/01/2008, vsaavedra <[email protected]> wrote:
> > Am I still making some kind of error in the MIB SMI definition?
>
> Well
>
> > name  OBJECT-TYPE
> >             SYNTAX     OCTET STRING
> >             MAX-ACCESS read-write
> >             STATUS     current
> >             DESCRIPTION
> >                         ""
> >             ::= { newtestEntry 2 }
>
> the MAX-ACCESS should probably be "read-create" if
> you are going to create new rows automatically.   But I
> doubt this is relevant to your current problem.
>
> (And I have to say that your object names aren't particularly
> meaningful, and the descriptions are even worse!)
>
>
>
> > Then, I created a simple agent with mib2c, using  mib2c -c
> > mib2c.create-dataset.conf newtest. I didn't alter one line of the code
> > produced by mib2c.
>
>
> I suspect that this is the underlying reason for your problems.
> I hate to shatter your carefully crafted illusions, but the developers
> of this project are not quite as infallible as you might like to think.
> And the mib2c templates (particularly the less-frequently-used ones)
> may well receive less rigourous scrutiny than the main MIB module
> implementation code.
>
>    So it is not inconceivable that there's a bug in the template code
> produced.    Particularly since I don't think you've ever said which
> version of the mib2c templates you are using.
>
>
> I think you are going to have to debug the MIB module handler
> routine yourself - put in debugging statements as necessary
> so that you can tell exactly what is going on, and see whether
> you can spot why it's not creating things correctly.
>     If you can identify where the problem arises, we can probably
> help with fixing it (and correcting the mib2c template).  But you
> are going to have to do most of the legwork yourself.
>
>    If you do need to come back for more assistance, it's probably
> worth attaching the code of your MIB module, so that we can
> see *exactly* what it looks like, rather than having to guess.
>    But please have a look for the problem yourself first.
>
> Dave
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Net-snmp-users mailing list
> [email protected]
> Please see the following page to unsubscribe or change other options:
> https://lists.sourceforge.net/lists/listinfo/net-snmp-users
>


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users