RE: snmpwalk does not walk the table when using dynamic load.

Hi Dave,

Thanks you for the replies.

Regarding your questions:
1) Cannot walk lmPlTable correctly either: it returns " No Such Object available on this agent at this OID".

2) I registered lmPl, very similar code as dlmod is registered in dlmod.c.  (lmPl table is of same structure as dlmod.)

3) When I snmpwalk ... nsModuleName, it returns " No Such Object available on this agent at this OID".  (Same for using either agentX 
or dynamic load.)

I am wondering, what is the difference on query mibs between agentX and dynamic load?  Same code (mib structure, register and etc.) 
works for agentX, not dynamic load.

More notes:
1) During "snmpwalk lmPl", when callback routine (used when the object is queried) is called, 
for dynamic load, the name passed to the function is the lmPl_oid;
for agentX, the name passed to the function is lmPlNumber oid {lmPl_oid 1}.  (1 is the sub-components for lmPlNumber.)
Question: What makes the difference?  Does this matter?

2) In agentX, when snmpwalk lmPl, snmp_agent logged something like,
===============================================
snmp_agent: varbind 1 is inclusive
snmp_agent: inclusive range(s) in getNext
===============================================
While dynamic load does not have these logs.
Question: What is varbind for?  Does this "inclusive set" matter?

3) I assume having "AgentX master support" tuned on does not affect dynamic load functionalities.  Please correct me if I am wrong.

Thanks,
Wei


-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Dave Shield
Sent: Wednesday, March 17, 2010 1:11 AM
To: Wei Zheng
Cc: [email protected]
Subject: Re: snmpwalk does not walk the table when using dynamic load.

On 16 March 2010 19:09, Wei Zheng <[email protected]> wrote:
> When doing snmpgetnext, it returns the top of next table.
>
> # snmpgetnext -c public localhost lmPlNumber.0
> LOCAL-MIB::lmPlStatResetStats.0 = INTEGER: 0
>
> (** It should be:
> LOCAL-MIB::lmPlName."test1" = STRING: test1
> **)


That would explain the behaviour you're seeing, yes.
   (Forget about snmpwalk - that's operating
    correctly. The problem lies in your MIB module)


Can you walk 'lmPlTable' correctly?

How are you registering lmPlNumer and lmPlTable?
What does the code look like?

Try
     snmpwalk ... nsModuleName  | grep {OID}

where {OID} is the (numeric) OID of 'lmPl'
What does that report?

Dave

PS: Please keep *all* responses on the list.
      I will typically delay responding to any queries
      sent privately to me for a minimum of 24 hours.

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
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