2009/7/3 김은영 <[email protected]>: > disman:event:fire: disman:event:fire: Event fired (snmpd.conf, > rfcNotiFaultCritical) > Event fired (snmpd.conf, rfcNotiFaultCritical) > disman:event:fire: disman:event:fire: No matching event > No matching event > ------- > What does this mean? "No matching event"?
Your monitor command specifies a named event "rfcNotiFaultCritical" to be invoked when the trigger is fired. The agent is looking for a matching "notificationEvent" (or setEvent) entry in the snmpd.conf file. See the snmpd.conf(5) man page for information about notificationEvent. > But there's no response on snmptrapd when I sent a v3 inform like this: > ------- > snmptrap -v3 -u jupiter localhost "" RADFINDER-NOTIFICATION- > MIB::rfcNotiFaultCritical RADFINDER-MIB::rfcPlatformRunningProcessCount.0 i > 2 > ------- If you want to send SNMPv3 notifications, then you'll need to set up the trap receiver to handle them. But your snmpd.conf file specifies a v2 trap, so that is not relevant here. Remember, the "jupiter" SNMPv3 settings are for the internal query used to monitor the value(s) of interest - *not* for the traps that are sent. The trap settings are handled by the trap2sink directive (and similar) Dave ------------------------------------------------------------------------------ _______________________________________________ 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
