Xymon Mailing List Archive search

SNMP destination (eg. not DevMon)

list Xymon User in Richmond
Fri, 14 Jan 2011 17:11:58 -0500
Message-Id: <user-e004cdb70b44@xymon.invalid>

Way kewl.  Canned version of a WAG definitely beats rolling your own.

On Fri, January 14, 2011 16:56, Ryan Novosielski wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Thanks a bunch! I had sniffed around some and had read an FAQ or two but
only saw DevMon. The relevant link here is:

http://cerebro.victoriacollege.edu/hobbit-trap.html

Have a nice weekend!

On 01/14/2011 04:31 PM, Williams, Doug (Consultant-RIC) wrote:
http://en.wikibooks.org/wiki/System_Monitoring_with_Xymon/Other_Docs/FA
Q #Q._How_do_I_enable_SNMP_monitoring_with_Hobbit_Server.3F


-----Original Message----- From: Xymon User in Richmond
[mailto:user-24d6f8323faa@xymon.invalid] Sent: Friday, January 14, 2011
4:15 PM To: xymon at xymon.com Subject: Re: [xymon] SNMP destination (eg.
not DevMon)

On Fri, January 14, 2011 15:52, Ryan Novosielski wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi all,

Is anyone aware of any direction I might look for supporting
RECEIVING SNMP traps from devices (not querying them via SNMP)? I
have a device that can set an SNMP destination, but I don't believe
has support for being queried by SNMP (if it does, it is a slightly
moot point as it
is
not on a network that can be accessed easily remotely).

Happy to just hear the name of a script or software if you know of
one.
Just a WAG, but I'd try pointing it at an snmptrapd and then monitor
the log.  But maybe someone knows a better way.

- -- - ---- _  _ _  _ ___  _  _  _ |Y#| |  | |\/| |  \ |\ |  | |Ryan
Novosielski - Sr. Systems Programmer |$&| |__| |  | |__/ | \| _|
|user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922) \__/ Univ. of Med. and
Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP
SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG
with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0wxpoACgkQmb+gadEcsb4b3QCgyAf7MQStVNu1wZh7d8DU9Iyq
XSoAoKuv7aM3KCiP7QlFnDlBBjvTfQSa =2CvN -----END PGP SIGNATURE-----