[hobbit] big brother replacement

[Tod Hansmann]

I think he's just looking for the alerts.  From what he's indicating, it
doesn't look like he's too concerned about the display (unless he has a
bunch of web pages up at once all the time).

 

Tod Hansmann

Network Engineer

 

  <http://www.directpointe.com/>  

________________________________

From: Josh Luthman [mailto:josh at imaginenetworksllc.com] 
Sent: Thursday, November 01, 2007 5:12 PM
To: hobbit at hswn.dk
Subject: Re: [hobbit] big brother replacement

 

I see what you're saying, but you still have to manually specify which
server you're connecting to.  If the bb1.domain.tld can not be reached
the techs have to manually enter bb2.domain.tld - correct?

I know of several BB ext scripts that work perfectly with Hobbit and
even more then just needed a small weak.  Would you be able to post the
entire ext script?  Hopefully Henrik is willing to answer your $64
question =) 

Josh

On 11/1/07, Sloan <joe at tmsusa.com> wrote:

Tod Hansmann wrote:
> Let me see if I understand.  You have several bb servers at one
> datacenter, each with their twin at the other datacenter, and both
sets
> do the tests.  They report to one central display server, but only one

> set reports at a time, depending on failover state, correct?
>
You have the basic idea, but there is no single central server, just
pairs of bb servers, one to a data center, in each lan which is being 
monitored. For each pair of bb servers, only the server at data center A
does reporting, unless the server in data center B cannot reach the
server in data center A, in which case the server in data center B will 
take over the reporting duties until the bb server in data center A
becomes reachable again. While this could theoretically lead to a split
brain condition, the failover condition has only ever triggered when
there was a wan outage.

> Is this failover automatic?  If so, how is this failover determined?
> What if this failover has a false positive?  If not, what is your
> timeframe to swap over?
>

IIRC It takes one bb cycle to kick in.

We've not seen a false positive, as I mentioned above.

It's just the standard built-in bb failover -

head ~bb/ext/failover follows:

#!/bin/sh

# failover
#
# BIG BROTHER - FAILOVER SCRIPT
# Sean MacGuire
#
# (c) Copyright Quest Software, Inc.  1997-2003  All rights reserved.
#

#
# failover WATCHES BBNET and BBPAGER
#
# IF BBNET OR BBPAGER BECOMES UNAVAILABLE, THEN TAKE OVER UNTIL THEY
RETURN 
#
# To use, just add failover to the BBEXT variable in etc/bbdef.sh
#
# To configure BBPAGER failover:
# define both the primary and failover machines as BBPAGERS in
etc/bb-hosts
# and set bbwarn: FAILOVER in etc/bbwarnsetup.cfg 


Joe



To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe at hswn.dk






-- 
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373

Those who don't understand UNIX are condemned to reinvent it, poorly.
--- Henry Spencer 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20071101/118a0987/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 1744 bytes
Desc: image001.gif
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20071101/118a0987/attachment.gif>