Re: Trap receivers, table_data.conf

Hello again,

My registration table using table_data works fine. Now I'm trying to map 
values from this table to an internal  table in my mib called the 
hosttable :

   table_entry = (regnms_entry *)
                              netsnmp_tdata_extract_entry(request);

 //mapping registered managers to snmphosttable
    hosttable->ipadd = table_entry->ip;
    hosttable->trap_port = table_entry->udp;
    hosttable->type = 1;
    hosttable->community = "public";

the problem is i'm not sure /where/  to place this snippet of code. My 
compiler isn't very happy when i try to put this in the handler. As 
using data_table.conf the data structure is managed by the agent, what's 
the best way of extracting data?

As I understand it, the difference between table_data and iterator.conf 
is where the data structure is stored. In my case where i need to use 
the data structure in my internal MIB would using iterator be better?

As always, any input is greatly appreciated.

Syikin

*be kind, i'm just an intern*




Wes Hardaker wrote:
>>>>>> On Fri, 20 Aug 2010 10:02:57 +0200, Norasyikin MD Ali <[email protected]> said:
>>>>>>             
>
> NMA> Currently I'm trying to create a dynamic registration table so that
> NMA> an NMS can register and de-register to via snmpset. Is that
> NMA> feasible using table_data.conf? And will it's handler take care of
> NMA> creating and deleting rows as well as all the process of setting
> NMA> (createAndGo etc.)?
>
> If you just want the table to work without much "extra restructions"
> such as rules for something like "if the manager sets this column to 1,
> then this other column can't be 2", then yes it should be the best
> choice [or even if you do need such restrictions, it'll still work, but
> will require more on your part].
>
> NMA> I read in another post 
> NMA> (http://www.mail-archive.com/[email protected]/msg24101.html) 
> NMA> that i need to implement a notification receiver and SNMP-TARGET-MIB 
> NMA> (it's all way over my head, it was actually making me cry a little 
> NMA> inside) because we actually have an internal traphost table in the MIB 
> NMA> thatregisters trap managers in snmpd.conf (currently done via CLI).
>
> The SNMP-NOTIFICATION-MIB and the SNMP-TARGET-MIB are the standard way
> for configuring notification destinations and targets and thus most
> managers understand them.  Doing something similar in your own MIB means
> all the other "standards-based" managers won't know how to configure
> your device.
>
>
>

------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d

_______________________________________________
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