Hi Robert,
Thanks for writing.
I have been working on mib2c.iterate_access.conf to generate ifTable iterate_access, because that looks most close to what I want.
The obstacle I met here is in ifTable_access.c line 40,
*my_loop_context = /** XXX */ ;
*my_data_context = /** XXX */ ;
How to set the context for ifTable?
I found a good example in agent/mibgroup/agent/nsTransactionTable.c, the function nsTransactionTable_get_first_data_point() uses agent session list :
extern netsnmp_agent_session *agent_delegated_list;
In my case, I need to declare a list for ifTable. What is the proper type for ifTable here?
Thanks.
--
Emi
Robert Story <[EMAIL PROTECTED]>
03/28/2005 11:11 AM
|
|
On Thu, 24 Mar 2005 09:45:29 -0600 [EMAIL PROTECTED] wrote:
EYC> I sent out an email a week ago which I wish could get some feedback.
EYC> Continuing my research, I found in RFC2741 an Example which is exactly
EYC> what I want to do to avoid conflict of ifTable between master agent and my
EYC> subagent.
[...]
EYC> Would you give me some advise on how this subagent should register or
EYC> allocate a single row of ifTable? Thank you very much.
This is exactly the right idea. Unfortunately, it still might not work. The
problem is that the existing ifTable doesn't use this method of allocating
indexes, so there could potentially be an overlap.
If the system comes up and interfaces don't come and go, then it's likely that
a conflict will never occur, but it is still a possibility.
I've never tried the index allocation stuff, or registering a row, but I think
it has been discussed on the mailing list in the past. Have you tried searching
the archives?
--
Robert Story; NET-SNMP Junkie
Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp>
Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders>
You are lost in a twisty maze of little standards, all different.
<<inline: graycol.gif>>
<<inline: pic01999.gif>>
<<inline: ecblank.gif>>
