[hobbit] Two BBDisplays, one collaboration
Josh Luthman
josh at imaginenetworksllc.com
Mon Nov 5 19:04:09 CET 2007
Tod,
I've configured it that way and neither of the www pages have any
information (concerning these hosts). I do know that 1984 is "connectable"
from the new Hobbit server (tested with nmap).
Any other ideas out there? From what little I know about this it seems like
this Net option is just an extra step, it doesn't seem required - is this
true? What is the simplest way of getting the list of hosts on both
bbdisplays?
Josh
On 11/5/07, Tod Hansmann <thansmann at directpointe.com> wrote:
>
> So, we have two servers doing tests, and they display their own tests,
> and also send alerts to the main display. So the main display is an
> aggregate of both test servers. This looks to be similar to what you're
> doing, so I hope that helps put the rest of this info in context.
>
>
>
>
>
> This is the testers:
>
> BBDISP="0.0.0.0"
>
> BBDISPLAYS="127.0.0.1 ip.of.main.display"
>
> ------ more stuff -------
>
> BBLOCATION="poller1"
>
>
>
>
>
> The BBLOCATION is important to the setup. I'll point out why in a
> moment. Also, ip.of.main.display is the same in both configs here.
>
>
>
>
>
> This is the main display:
>
> BBSERVERIP="ip.of.main.display"
>
> BBDISP="$BBSERVERIP"
>
> BBDISPLAYS=""
>
> ------ more stuff -------
>
> BBLOCATION="display"
>
>
>
>
>
> Now in the bb-hosts file, I have Net:poller1 with all the hosts poller1
> polls, and Net:poller2 with all the hosts poller2 polls. This may not be
> useful in the setup you're trying to get working, but it can't hurt to
> include. I think your original config is the one to go with, but I might go
> with 127.0.0.1 and no spaces. I'm pretty sure the BBDISPLAYS just has
> bbtest-net send it to everything in that list when it has a status message.
> Also note that port 1984 will have to be opened appropriately on any
> firewalls.
>
>
>
> Way more info than you probably need, but I do hope some of it helps.
>
>
>
> *Tod Hansmann*
>
> Network Engineer
>
>
>
> <http://www.directpointe.com/>
> ------------------------------
>
> *From:* Josh Luthman [mailto:josh at imaginenetworksllc.com]
> *Sent:* Saturday, November 03, 2007 12:58 PM
> *To:* hobbit at hswn.dk
> *Subject:* [hobbit] Two BBDisplays, one collaboration
>
>
>
> What I am trying to do is have two BBDisplay servers. The first one being
> our main one - monitors our network equipment and things - and a second one
> that lives on the customer's network and pings APs, Switches, etc.
>
> I have setup this in bb-hosts on the main one:
>
> page HIXX Holiday Inn X X
> group-compress <H3><I>Access Points</I></H3>
> 1.2.3.4 host.com # noconn
>
> group-compress <H3><I>HIDM Hardware</I></H3>
> 2.3.4.5 host2.com # noconn
>
> Reason for the noconn is that these are all private IPs, accessible only
> by the customer's LAN. These configuration match those of the customer's
> bb-hosts (with the exception of noconn, of course =)
>
> I then went into the customer's server/etc/hobbitserver.cfg and changed it
> as such:
>
> BBDISP=" 0.0.0.0"
> BBDISPLAYS=" 10.59.1.119,MAINSERVERPUBLIC"
>
> I have also tried it without quotes
>
> When I set this neither BBDisplay has anything on the www pages, they're
> completely blank! Once I switch it to
>
> BBDISP="$BBSERVERIP" # IP of a single hobbit/bbd server
> BBDISPLAYS=""
>
> It works perfectly fine on the customer's server, but the main one is
> display blank (obviously =)
>
> Please let me know where I went wrong. Thanks in advance!
>
> Josh
>
> --
> 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
>
>
--
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/20071105/6045aa2e/attachment.html>
More information about the Xymon
mailing list