Seems like the only built-in traps are "linkUp", "linkDown", "coldStart"
and
"authenticationFailure", others you have to add manually which would take _awhile_ to do.
Right. The new SNMP trap machinery provided in Data ONTAP 5.3 is very flexible and extremely powerful. As you have probably seen in the documentation, it actually enables you to set a variety of different types of trap on any supported MIB variable you like. You can monitor variables for crossing administrator defined thresholds in either direction (rising above or falling below). You can monitor variables for staying within administrator defined ranges, or even *outside* of ranges if that makes sense for a particular value. You can keep traps firing when variables stay on the wrong side of "lines" (with a backoff cabability). It's thoroughly wicked.
However, one of the last little things that unfortunately didn't get implemented in time for the 5.3 release was the "spoon feed some nice traps on a silver platter" component. :-) As you have discovered, you currently have to look at the filer MIB(s) yourself, figure out what variables you are interested in monitoring in your environment, and then put the relevant traps on them "by hand". Sophisticated administrators will probably *always* want to go through such a procedure, but it is not unreasonable to want to be supplied some "starter traps" on the kinds of events that are likely to be interesting to the majority. We do supply a small handful (which you note above), but there's obviously more we could do here, such as:
I am interested in things like: failed disks, stopped fans, cluster status etc.
Yep. In fact, we are always actively seeking input on the kinds of default traps our customers would like to have supplied "out of the box". Any input posted either here or to my inbox will be seen by the folk who can turn the requests into reality.
http://now.netapp.com/knowledge/docs/ontap/rel53/html/sag/net2.htm says there should be a "traps.dat" file in "the same directory as the MIB" (=/etc/mib??) but I am unable to locate this file.
I'll see if I can find out what happened to it for you. :-)
Keith