HI,
The below is not accurate in describing the "standard" way
for configuring SNMP notification originators as specified
by the objects defined in RFC 3413.
First, implementations are not required to objects in RFC 3413,
and I personally believe that they were not well designed.
However, if you want to use them, there are 5 interrelated
tables that are used to specify where to send notifications,
the attributes of the notifications, and filtering of the
notifications.
Here they are:
1)snmpNotifyTable - targets to send notifications to and
notification type (trap or inform)
2) snmpNotifyFilterProfileTable - a notification filtering
profile associated with a target
3) snmpNotifyFilterTable - notification filter rules
for each notification filtering profile
4) snmpTargetAddrTable - address of a notify target
5) snmpTargetParamsTable - protocol type and security type info
for a target
Understanding the interractions of these tables, and
the VACM and USM tables is not easy. And again, I believe
that there are much better approaches for accomplishing
the same results.
<soap>
The above, and the notification log (see RFC 3014) are
overly complex, and broken. I just wish they would be
replaced with usable solutions. However, once they
are implemented, they implementors see the problems,
but do not then rip them out and replace them with
better approaches. This is now becomes the problem
of the users (the management apps) to figure out
how to use the mess. The agent side people just
walk away from owning the problem, and thus,
a true solution is never developed. This is sad.
</soap>
On Thu, 22 Jun 2006, Dave Shield wrote:
> Passera Pablo-APP015 wrote:
>
> >What about the SNMP-NOTIFICATION-MIB? I was taking a look to that mib and it
> >seems to be used for sending notifications to specific NMs.
> >
> Yes - that MIB has been used by the Net-SNMP agent for some time.
> It can be used to configure where notifications should be sent (and what
> version of SNMP to use, the community string or v3 user name, etc).
>
> But this MIB is purely concerned with the issue of "send [all]
> notifications to these destinations using these settings". It does
> *not* handle requirements such as "send these particular
> notifications to these destinations, and these other notifications
> to these (different) destinations".
> That's the significance of notification *filtering*, as Robert
> suggests.
>
>
>
> >The net-snmp page for the notification mib refers to the section 6
> >
> >
> > of the [SNMP-APPL], someone know what is that? Is it a book?
> >
> No - it's actually a dangling reference to RFC 3413, which is the
> document where this MIB is defined. The reference should probably
> have been updated to point to the RFC by number before it was issued,
> but it seems to have slipped through the reviewing process.
>
>
> Dave
Regards,
/david t. perkins
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
