Comments inline. > -----Original Message----- > From: Robert Story (Users) [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 26, 2004 6:55 AM > To: Srini Kode > Cc: net-snmp-users > Subject: Re: new style of mib code > > > On Mon, 25 Oct 2004 17:40:02 -0700 Srini wrote: > SK> 1) If you're writing code for some generic scalars > SK> (by hand use: "mib2c -c mib2c.scalar.conf > ciscoPortChannelMIB") > > SK> Your tables will likely either fall into one of two categories: > SK> 1) tables which monitor or manipulate external data > SK> 2) A API layer wrapped on top of number 1) above that provides > SK> more APIs to fill out, but are much more refined. > > Is the code you sent exactly what mib2c generated, or have > you mixed and matched two files? > I generated the code for scalar objects first and then for the table and Combined the 2 tables.
> SK> 2: portChannelTestString.0 (octet string) porttest > SK> 3: portChannelTestString.1.1.19922944 (integer) 2 > > Are there any other files compiled into the agent? This looks > like a table somewhere has registered an overlapping OID. The > code you sent looked like it was registering the correct OIDs. > Yes. We have lots of mibs in the agent which are using the old ucd-snmp style of Coding. They are working fine. Now I am adding this mib with new style of coding. I know which handler is being called, but there is no reason why it must be called. That mib code has been there for long time and working and is using old style. > If you can turn on debugging, turn on the following debug > tokens : "handler,helper,table,result" and then run > > snmpgetnext -r 0 -c public localhost portChannelTestString.0 > > The debug output should tell you what handlers are being > called, and might help narrow down the problem. > > > On a side note, the iterate_access conf might not be the best > choice for table code for the uninitiated. It is the middle > ground between the iterate conf file and the new mfd in 5.2. > The iterate code is more basic, but has been around longer > and had more testing. The mfd code is by far the most verbose > and simplified of the conf files. > > In short, the iterate_access conf file lacks a champion, and > thus support might not be as forthcoming as with the iterate, > array-user, mfd and scalar conf files. > In our case we are using 5.1, so you suggest we use, scalar, iterate conf files. Thanks Srini > -- > Robert Story; NET-SNMP Junkie <http://www.net-snmp.org/> > <irc://irc.freenode.net/#net-snmp> > Archive: > <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-users> > > You are lost in a twisty maze of little standards, all different. > ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ Net-snmp-coders mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
