On 1 April 2010 14:00, PEOPLES, MICHAEL P (ATTSI) <[email protected]> wrote: > If that is not available, consider using the agent “Arbitrary Extension > Commands” > function. I have never used them for traps, so it may not be appropriate.
Not really, no. These mechanisms are designed to respond to GET* (or SET) requests - i.e. they are triggered by an incoming SNMP packet. The thing about notifications is that they are *not* related to an incoming SNMP request. Traps are typically triggered by some external event, and detecting this is often the hardest part of the problem. Hence the advice I gave Harendra yesterday. > If you can detect the hardware fault with a script I.e. if you can do the hardest bit! > (you could have it poll every couple of seconds), > then you can have that script execute an snmptrap command Exactly. > with a “fake” OID that your management system will recognize. Please don't think in terms of "fake" OIDs. What you are talking about is an enterprise-specific notification OID. There's nothing "fake" about this. If you have an enterprise number of your own, then you can define MIBs within this tree, including trap objects. Otherwise, you are more than welcome to use the nsPlayPen subtree to define suitable MIB objects. (As long as this is going to be a private definition, and will never be released publically!) Dave ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ 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
