You need to check in dot3StatsTable_interface.c
There is no element for id = 12 you need to clean the code to go from 11 to 13.
/*
dot3StatsCarrierSenseErrors(11)/COUNTER/ASN_COUNTER/u_long(u_long)//l/A/w/e/r/d/h
*/
case COLUMN_DOT3STATSCARRIERSENSEERRORS:
var->val_len = sizeof(u_long);
var->type = ASN_COUNTER;
rc = dot3StatsCarrierSenseErrors_get(rowreq_ctx, (u_long *)var->val.string );
break;
/*
dot3StatsFrameTooLongs(13)/COUNTER/ASN_COUNTER/u_long(u_long)//l/A/w/e/r/d/h */
case COLUMN_DOT3STATSFRAMETOOLONGS:
var->val_len = sizeof(u_long);
var->type = ASN_COUNTER;
rc = dot3StatsFrameTooLongs_get(rowreq_ctx, (u_long *)var->val.string );
break;
--- On Tue, 4/17/12, Robert Story <[email protected]> wrote:
> From: Robert Story <[email protected]>
> Subject: Re: Error OID not increasing...
> To: "Jes" <[email protected]>
> Cc: [email protected]
> Received: Tuesday, April 17, 2012, 11:50 AM
> On Mon, 16 Apr 2012 17:31:28 -0500
> Jes wrote:
> J> I am developing support for the EtherLike-MIB and
> another custom MIB
> J> with Ethernet statistics.
> J>
> J> For both MIBS I have a problem in my handler (when I
> receive a
> J> MODE_GETNEXT), that I get the column number for the
> first column ok(via
> J> netsnmp_extract_table_info) and the appropriate oid, I
> lookup my value and
> J> return it via snmp_set_var_value .. but my snmpwalk
> J> command gets the value but then says "Error: OID not
> increasing: ..."
>
> Ok, when you send a snmpgetnext request, the agent may (or
> may not) translate
> that to a snmpget request before passing it to your handler.
> So, if your
> handler gets a snmpget request, you return the exact OID
> requested. If you are
> getting a snmpgetnext request, you need to return the OID
> after the requested
> OID. Most handlers do the work for you, and only pass
> in get requests.
>
> J> 2.) Regarding the OID not increasing .. should I
> manually increment that
> J> oid in my handler..
> J>
> J> I did a mib2c -c mib2c.create-dataset.conf dot3 to get
> a skeleton ...
>
> No, the dataset helper should have already handled the OID
> for a get-next. Are
> you sure that your dataset storage doesn't have a duplicate
> index in it? I
> can't remember if that handler checks for duplicate entries,
> and that would
> certainly explain a non-increasing OID.
>
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes
> to
> monitoring Big Data applications. Try Boundary one-second
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> _______________________________________________
> Net-snmp-coders mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
>
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
