That's probably left over from that little app that used to be on the
system for monitoring disk utilization on the Netview server itself.
The default threshold and rearm traps provided with SNMP Data
Collection and Thresholding are just that: defaults. In actual fact,
you can use any specific trap numbers you like and define your
own, which you may find useful. The numbers 1000-1999 were
always reserved for customer use. You only get to specify the
threshold trap number, and it must be odd, and it will automatically
use the next number (even) as the rearm trap. Be sure to add them
to trapd.conf under the netview enterprise using the gui. And note
that this freedom of choice does NOT apply to threshold monitoring
done with APM. There you must use the MLM threshold traps.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
I don't do snmpCollect but per the appendix in the NetView Admin Guide, 58720257
is obsolete. I take that to mean that it will not be generated.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Under Data Collection & Thresholds: SNMP....
the diskutil has a default trap of 58720263 which is the data collector
threshold event.
After looking through all the traps, I noticed that 58720257 is a disk space
percentage used threshold.
It would seem that the second trap would be a better one for the trapgend
daemon to generate....
So the question is what generates the 58720257 trap and when?
Steven
P.S. Thanks everyone for all the help with the Netscape MIB and SMUX, all
that works now.
:)
|