2008/5/23 Ron Rader <[EMAIL PROTECTED]>:
> but linkUpDownNotifications is just a macro defined
> as a set of more atomic configuration actions. My link traps were
> similar to yours while I used that macro.
OK - then it looks as if there's a bug in the implementation.
The initialisation of the Event MIB module include the
definition of standard sets of objects for particular
events, including:
/* ifIndex */
_init_default_mteObject( "_linkUpDown", ".1.3.6.1.2.1.2.2.1.1", 1, 1);
/* ifAdminStatus */
_init_default_mteObject( "_linkUpDown", ".1.3.6.1.2.1.2.2.1.7", 2, 1);
/* ifOperStatus */
_init_default_mteObject( "_linkUpDown", ".1.3.6.1.2.1.2.2.1.8", 3, 1);
(See _init_default_mteObject_lists() in disman/event/mteObjects.c)
It shouldn't be necessary to define an equivalent configuration
manually:
> notificationEvent linkUpTrap linkUp ifIndex ifAdminStatus ifOperStatus
> notificationEvent linkDownTrap linkDown ifIndex ifAdminStatus ifOperStatus
> monitor -r 5 -e linkUpTrap "Generate linkUp" ifOperStatus != 2
> monitor -r 5 -e linkDownTrap "Generate linkDown" ifOperStatus == 2
That should all be handled by the internal definitions.
I need to investigate why this isn't working.
Dave
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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
