Re: Trap receivers, table_data.conf

>>>>> 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.


-- 
Wes Hardaker
Cobham Analytic Solutions

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
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