Xymon Mailing List Archive search

SNMP Traps - We are converting to Xymon from BB

list David Baldwin
Thu, 13 Sep 2018 16:17:07 +1000
Message-Id: <user-d8155c0bc04d@xymon.invalid>

I've been using this method for quite a few years.

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

A lot of moving parts and you need to track down the MIBs to start
creating snmptt translation tables, then hand tweak as various unknown
traps appear, but like anything you can get it working how you want if
you persist long enough.

David.
Galen,

I was pretty familiar with deadcat. I'd say you got the lions share of
what was useful.

Devmon itself is kind of barren.  As I mentioned, with devmon, I've
been able to identify SNMP differences between platforms and something
that *looks* like a memory leak. I have to kill devmon periodically
and restart it to eliminate the memory it comes to use.  I haven't
really had time to chase that down though.

Regards,

Bruce Ferrell


On 9/12/18 6:54 PM, Galen Johnson wrote:
Unfortunately, I was only able to rescue some bits of deadcat,  I was
hoping to be able to save more but it didn't pan out and I have no
idea what Dell did with that content. Devmon is likely the best
option for now.  There is a section for Devmon on Xymonton but it is,
sadly, barren.   IIRC, Henrik was looking to add SMTP traps to Xymon
5 but that has not yet surfaced outside of mentions in the mailing
list archives.

=G=

On Wed, Sep 12, 2018 at 9:16 PM Bruce Ferrell <user-24fbf1912cfe@xymon.invalid
<mailto:user-24fbf1912cfe@xymon.invalid>> wrote:

    Jason,

    I'm a long time BB/Xymon user.  The original FOSS BB, had no trap
handler.  I see from poking google, the professional version of BB
did/does have one:

    http://bb.etermar.pt/bb/skins/eng/help/help/Receiving_SNMP_traps.htm

    I'm sure I'll be corrected if I'm wrong but I don't think xymon
has a native one either, but I remembered this is from the days of
the FOSS BB:

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

    And you may or may not already know about xymonton... It seems to
have copies of all the stuff deadcat used to have for BB.

    https://wiki.xymonton.org/doku.php

    I usually have to tweak the stuff from xymonton to get it to work
right, but it's been extremely useful

    And just on the general topic of SNMP: After 30 years messing
with networks, I have discovered that SNMP is NOT always what I
expect.  Different implementations some times
    return
    different results.  Most of my systems are linux with net-snmp. 
I have a few, that I recently have begun to monitor, that are OS X
(various revisions) with net-snmp.  The data
    returned isn't always the same as my linux boxen.  Again, I've
had to fiddle a bit to find the OIDs for what I'm trying to watch.
Same deal for Cisco gear.... And THAT varies
    from
    model to model! Devmon is what I've been using for that.

    Regards,
    Bruce Ferrell

    On 9/12/18 9:45 AM, Greg Hubbard wrote:
    > Hi Jason,
    >
    > I think you need to provide some more information.  What are
you using in BB to catch, decode, and react to the traps? How is it
configured?
    >
    > Greg Hubbard
    >
    > On Tue, Sep 11, 2018 at 10:37 AM Jason Hildreth - NOAA Federal
via Xymon <xymon at xymon.com <mailto:xymon at xymon.com>
<mailto:xymon at xymon.com <mailto:xymon at xymon.com>>> wrote:
    >
    >
    >
    >
    >     ---------- Forwarded message ----------
    >     From: Jason Hildreth - NOAA Federal
<user-5695a1fe1593@xymon.invalid <mailto:user-5695a1fe1593@xymon.invalid>
    >     To: xymon at xymon.com <mailto:xymon at xymon.com>
<mailto:xymon at xymon.com <mailto:xymon at xymon.com>>
    >     Cc:
    >     Bcc:
    >     Date: Tue, 11 Sep 2018 11:30:34 -0400
    >     Subject: SNMP Traps - We are converting to Xymon from BB
    >     Question is more related to Big Brother in our interim
before we move to Xymon....
    >
    >     If anyone can help (since BB has been dead for a while) it
would be appreciated.
    >
    >     We have SNMP traps setup to be received in our Big Brother
environment but instead of sending the trap back to itself for
processing it is sending the data to the IP of the
    >     other Big Brother (now Xymon) system.  We want to keep the
SNMP traps on the Big Brother system until we put the xymon system in
place completely.  Does anyone know why
    it is
    >     sending to a different IP than the IP of the system the
SNMP trap was received on...and where that is set in order to make
this stop...
    >
    >     Thanks
    >
    >     --
    >
    >     Jason Hildreth
    >
    >     Middleware, Programming, Systems Administrator
    >
    >     Infrastructure and Web Services Branch
    >
    >     NCEP Central Operations
    >
    >
    >
    >
    >     ---------- Forwarded message ----------
    >     From: Jason Hildreth - NOAA Federal via Xymon
<xymon at xymon.com <mailto:xymon at xymon.com> <mailto:xymon at xymon.com
<mailto:xymon at xymon.com>>>
    >     To: xymon at xymon.com <mailto:xymon at xymon.com>
<mailto:xymon at xymon.com <mailto:xymon at xymon.com>>
    >     Cc:
    >     Bcc:
    >     Date: Tue, 11 Sep 2018 11:30:34 -0400
    >     Subject: [Xymon] SNMP Traps - We are converting to Xymon
from BB
    >     
    >
    >
    >
    > --
    > Disclaimer:  1) all opinions are my own, 2) I may be completely
wrong, 3) my advice is worth at least as much as what you are paying
for it, or your money cheerfully refunded.
    >
    > 


    
-- 
David Baldwin - Senior Systems Administrator (Datacentres + Networks)
Information and Communication Technology Section
Business Operations Branch, Corporate Division
Australian Sports Commission          http://ausport.gov.au
Tel 02 62147830 Fax 02 62141830       PO Box 176 Belconnen ACT 2616
user-cbbf693f2c89@xymon.invalid          1 Leverrier Street Bruce ACT 2617
Our Values: RESPECT + INTEGRITY + TEAMWORK + EXCELLENCE


Keep up to date with what's happening in Australian sport visit https://www.sportaus.gov.au

This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.