Sending Hobbit data from one server to another

Hi,

In the past I struggled the same. Here is a summary what I did to make it work:

Situation:
 
Before:
 
- Local hobbit listens on 10.15.xxx.xxx port 1984 
- Local clients sends messages to IP 10.15.xxx.xxx port 1984 
 
 
With bbproxy:
 
- Local hobbit listens on 127.0.0.1 port 1984 
- Local bbproxy listens on 10.15.xxx.xxx port 1984 
- Local clients sends messages to IP 10.15.xxx.xxx port 1984 (bbproxy) 
- bbproxy forwards incoming messages to 127.0.0.1 port 1984 AND to remote hobbit (10.170.xxx.xxx) port 1984 
 
 
This is what needs to be changed on the local hobbit sever:
 
- Add a --listen=127.0.0.1 to hobbitd in hobbitlaunch.cfg on local hobbit 

- Enable bbproxy on local hobbit in hobbitlaunch.cfg. Use the option "--bbdisplay=127.0.0.1,10.170.xxx.xxx" to tell bbproxy to forward to both server and add --listen 10.15.xxx.xxx so it will listen on this IP for incoming messages 

- Change the BBSERVERIP setting in hobbitserver.cfg to point at the 127.0.0.1 address. 
This setting is used e.g. by the web CGI's that talk to the "real" hobbit server, so it is best to point this at the real server IP, not the proxy. 

- Because there are also running network tests from the same server, we need to change the CMD setting of [bbnet]  in hobbitlaunch.cfg also.
Instead of calling bbtest-net directly, put it into a shell script wrapper and set BBDISPLAY explicitly to 10.15.xxx.xxx. Otherwise it will pick up the BBSERVERIP setting (127.0.0.1) and send the network test results to 127.0.0.1 - so they won't go through the proxy, and hence you won't see them on the remote server. 

- Restart Hobbit 
 
 
From the hobbitlaunch.cfg on the local hobbit server:
 
[hobbitd]
        HEARTBEAT
        ENVFILE /opt/hobbit/server/etc/hobbitserver.cfg
        CMD hobbitd --pidfile=$BBSERVERLOGS/hobbitd.pid --restart=$BBTMP/hobbitd.chk --checkpoint-file=$BBTMP/hobbitd.chk 
        --checkpoint-interval=600 --log=$BBSERVERLOGS/hobbitd.log --admin-senders=127.0.0.1 --store-clientlogs=!msgs --listen=127.0.0.1


[bbproxy]
        ENVFILE /opt/hobbit/server/etc/hobbitserver.cfg
        CMD $BBHOME/bin/bbproxy --hobbitd --display=127.0.0.1,10.170.xxx.xxx     
  --report=$MACHINE.bbproxy --pidfile=$BBSERVERLOGS/bbproxy.pid 
  --listen=10.15.xxx.xxx --no-daemon
        LOGFILE $BBSERVERLOGS/bbproxy.log
 
[bbnet]
        ENVFILE /opt/hobbit/server/etc/hobbitserver.cfg
        NEEDS hobbitd
        CMD $BBHOME/bin/net-test.sh
        LOGFILE $BBSERVERLOGS/bb-network.log
        INTERVAL 5m
 
 
Wrapper script for bbtest-net:
 
#cat $BBHOME/bin/net-test.sh
 
#!/bin/sh
export BBDISP=10.15.xxx.xxx
$BBHOME/bin/bbtest-net --report --ping -checkresponse
 
All that done  it's working!

Hope this helps...

-Johann

-----Original Message-----
From: Asif Iqbal [mailto:user-6f4b51ac2a40@xymon.invalid]
Sent: Donnerstag, 6. März 2008 22:28
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Sending Hobbit data from one server to another

So I am still struggling with this idea. How would I have bbproxy
server do bbnet test as well?
To run bbrpoxy you have to disable hobbitd, but to do bbnet test
hobbitd needs to be running.

What a catch 22!

Anyone figured that out yet?


On Wed, Mar 5, 2008 at 11:51 AM, Asif Iqbal <user-6f4b51ac2a40@xymon.invalid> wrote:

bbrpoxy works fine but I do not understand the comment for [bbproxy]
 in habbitlaunch.cfg

 # "bbproxy" is the Hobbit proxy server that allows you to forward
 status messages
 # from a protected network to your Hobbit server. It is not enabled by
default,
 # since it would conflict with the hobbitd task.
 # If you need to run this, then disabled hobbitd and the hobbitd-
modules
 # above, then enable this. Make sure you enter the IP-address of your
 # Hobbit server in the command-line, so that the proxy knows where to
forward
 # status messages.
 [bbproxy]
        ENVFILE /home/hobbit/server/etc/hobbitserver.cfg
        CMD $BBHOME/bin/bbproxy --hobbitd
 --bbdisplay=real.hobbit.server.ip --report=$MACHINE.bbproxy
 --no-daemon
               --pidfile=$BBSERVERLOGS/bbproxy.pid
        LOGFILE $BBSERVERLOGS/bbproxy.log

 It says disable hobbitd and hobbit-modules above. I did. So how about
 the hobbitd-modules like [bbdisplay], [bbcombotest],
 [bbnet], [bbretest], [hobbitclient]. All those are below [bbproxy] and
 needs hobbitd to run. So do I disable them?

 If I do then how do I send the connectivity (ping test) report or
 start the hobbitclient without installing a separate client for the
 server?

 So few things needs to be cleared by someone who already using bbproxy
 for same scenario that Gary Bahula, the OP of this email, drew.

 Thanks


 On Mon, Feb 11, 2008 at 11:02 AM, Gary Baluha <user-ae3e15c22de1@xymon.invalid>
wrote:

There's the bbproxy command I was looking at, but I'm not sure from
the man
page if that will accomplish what I want.


On Feb 11, 2008 10:33 AM, Patrick Nixon <user-1f2406f832af@xymon.invalid> wrote:

Can you use the second hobbit server a proxy/relay?

I think hobbit can support that.... bbrelay maybe?


On Feb 11, 2008 10:07 AM, Gary Baluha <user-ae3e15c22de1@xymon.invalid> wrote:

Here's the situation.  I have one Hobbit server that is on our

DMZ

segment,

and another that is on our internal LAN segment.  There are
several
hosts
that are monitored from the DMZ hobbit server, which are
unreachable

(due to

network policy) by the internal hobbit server.  What would be the
best
way
(if any) to merge the status of the DMZ hobbit to the internal
hobbit?

That

is, I would like to create a sub-page on the internal hobbit
server that
shows essentially a mirror of the hobbit status page for the DMZ
server.

 --
 Asif Iqbal
 PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu

--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu