# snmpd.conf (names changed to protect the guilty) # syslocation "There" syscontact "Help desk" sysservices 79 agentSecName foobar1z rouser foobar1z rocommunity sandy trapsink foobar1z sandy trap2sink foobar1z sandy informsink foobar1z sandy trapcommunity sandy
proc mdlogd ################### There's a known problem. The network gods slam the network with a discovery broadcast (to a different community string) every once in awhile, but that used to just generate one or two traps. Now it's dozens, hundred. Primarily, I use SNMP to check network and HOST-RESOURCES-MIB but I've been fiddling around with DISMAN-EVENT-MIB (which I'll discuss some other time). Is the above overkill? This communication is intended for the use of the recipient to which it is addressed, and may contain confidential, personal and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communication received in error, or subsequent reply, should be deleted or destroyed. ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ 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
