Cc: net-snmp-users@lists.sourceforge.net
Subject: Re: GETNEXT looping problem
On Fri, 13 May 2005 18:35:20 +0530 Kurapati wrote:
KMG> We are observing following misbehaviors.
KMG>
KMG> 1. GETNEXT on the last scalar object:
KMG> NET-SNMP Library calls the table handlers in the fo
On Fri, 13 May 2005 18:35:20 +0530 Kurapati wrote:
KMG> We are observing following misbehaviors.
KMG>
KMG> 1. GETNEXT on the last scalar object:
KMG> NET-SNMP Library calls the table handlers in the following order.
Are any of the tables sub-agents? Are any of them sharing the same handle
On Fri, 2005-05-13 at 14:05, Kurapati M-G19456 wrote:
> 1. GETNEXT on the last scalar object:
> NET-SNMP Library calls the table handlers in the following order.
>
> a. getnext on table-one
> b. getnext on table-two
> c. getnext on table-three
> d. getnext on table-two
Yes
Title: Message
We are using
NET-SNMP 5. 1. 1.
Our test mib
contains the following MIB objects.
1. Scalars Group
(contains five objects) =>registered with NET-SNMP Library using
scalar_group (netsnmp_register_scalar_group())helper
2. TableOne (three
columns, bu
