[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [hobbit] Suitability for bb replacement in large enterprise
- To: hobbit (at) hswn.dk
- Subject: Re: [hobbit] Suitability for bb replacement in large enterprise
- From: J Sloan <joe (at) tmsusa.com>
- Date: Mon, 08 Dec 2008 14:54:39 -0800
- References: <493AEDCE.9060107 (at) tmsusa.com> <493BA976.10803 (at) unil.ch> <493BA976.10803 (at) unil.ch> <200812081608.21732.bgmilne (at) staff.telkomsa.net> <ghk55o$ccr$1 (at) voodoo.hswn.dk>
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.18) Gecko/20081125 Thunderbird/2.0.0.18 Mnenhy/0.7.5.666
Henrik Størner wrote:
> In <200812081608.21732.bgmilne (at) staff.telkomsa.net> Buchan Milne <bgmilne (at) staff.telkomsa.net> writes:
>
>
>> However, it should be relatively easy to make an alerting script to plug into
>> Hobbit to send traps.
>>
>
>
>> The biggest requirement for someone to be able to test such a script
>> compatible with the BB feature would be the MIB file used by BB ...
>>
>
> As far as I recall, BB just sends a trap message using an OID
> that's been configured in the alert-setup config. A trap is really
> just a plain text-string wrapped into an SNMP message.
>
> So there's no MIB involved, other than the "MIB" which has only
> the one OID which is used for the trap.
>
>
>
Yes, it's very simple and straightforward: send out an snmp trap based
on an event, per the bbwarnrules.cfg, just like the email alerts. If
hobbit can be made to do that, one of the two key requirements would be
met, and only the failover behaviour would still need to be resolved.
Joe