Xymon server reporting to itself and another Xymon server 🔗 link

Hi All, 


I have two new Xymon servers A and B.  All clients will send data to both servers 
excerpt from xymonclient.cfg: 
XYMSRV="0.0.0.0"                        # IP address of the Xymon server 
XYMSERVERS="serverA serverB"                         # IP of multiple Xymon servers. XYMSRV must be "0.0.0.0". 

No problem so far.  
I want serverA to be a client to itself and serverB and vice versa.  Modifying the xymonclient.cfg file on the 
server sends the server (as a client), but also all the client data that reports to it. 
Xymond excerpt: 
Multi-source statuses 
   clientA:conn                    reported by serverB and serverA 
   clientB:conn                    reported by serverB and serverA 
   clientC:conn                    reported by serverB and serverA 
... 


Latest error messages: 
Flapping detected for clientA:conn - 5 changes in 620 seconds 
Flapping detected for clientB:conn - 5 changes in 620 seconds 
Flapping detected for clientB:conn - 5 changes in 620 seconds 


So obviously that's not the way to do it.  Do I have to do anything with xymonproxy? I don't want to change 
all my clients. 


Thanks in advance 
Greg Shea 
EMC Corporation

In <user-4a609205ad0f@xymon.invalid> user-f00ed6e065e8@xymon.invalid writes:

XYMSERVERS="serverA serverB"

What do you have in tasks.cfg as the ENVFILE setting ?

All of the server-tasks should use xymonserver.cfg for the ENVFILE
setting, and in xymonserver.cfg there should only be a XYMSRV="serverA"
(or serverB, depending on what server this is).

Only the client task should point to the xymonclient.cfg file in
ENVFILE.


The "conn" test is reported by the "xymonnet" task. The only way
it can be reported as "multi-source" is if your xymonserver.cfg
is setup with both servers as the target (in XYMSRV / XYMSERVERS).


Regards,
Henrik

Hi Henrik,

Thanks for the reply.

This is a standard install on RH5, all I changed was the xymonclient.cfg file to include both servers
[xymon at yxmprdr01 ~]$ ls
cgi-bin  cgi-secure  client  data  server
[xymon at yxmprdr01 ~]$ grep ENVFILE server/etc/tasks.cfg
        ENVFILE /apps/xymon/server/etc/xymonserver.cfg
...
        ENVFILE /apps/xymon/server/etc/xymonserver.cfg

[xymon at yxmprdr01 ~]$ grep XYMSRV server/etc/xymonserver.cfg
XYMSRV="$XYMONSERVERIP"         # IP of a single Xymon server
XYMSERVERS=""                   # IP of multiple Xymon servers. If used, XYMSRV must be 0.0.0.0
BBDISP="$XYMSRV"

[xymon at yxmprdr01 ~]$ grep XYMONSERVERIP server/etc/xymonserver.cfg
XYMONSERVERIP="10.10.10.69"                    # The IP-address of your server. Use the real one, not 127.0.0.1 .
XYMSRV="$XYMONSERVERIP"         # IP of a single Xymon server
MACHINEADDR="$XYMONSERVERIP"            # This systems IP-address
BBSERVERIP="$XYMONSERVERIP"

[xymon at yxmprdr01 ~]$ more client/etc/xymonclient.cfg
# Environment settings for the Xymon client.

XYMSRV="0.0.0.0"          # IP address of the Xymon server
XYMSERVERS="10.10.10.69 10.10.10.70"                   # IP of multiple Xymon servers. XYMSRV must be "0.0.0.0".
CONFIGCLASS="$SERVEROSTYPE"     # Default configuration class for logfiles

Thanks
Greg Shea
EMC Corporation

In <user-947b442c9ed2@xymon.invalid> user-f00ed6e065e8@xymon.invalid writes:

All of the server-tasks should use xymonserver.cfg for the ENVFILE=20
setting, and in xymonserver.cfg there should only be a XYMSRV=3D"serverA"=

=20

(or serverB, depending on what server this is).=20

Only the client task should point to the xymonclient.cfg file in=20
ENVFILE.=20


The "conn" test is reported by the "xymonnet" task. The only way=20
it can be reported as "multi-source" is if your xymonserver.cfg=20
is setup with both servers as the target (in XYMSRV / XYMSERVERS).=20

So if you run "xymoncmd --env=/apps/xymon/server/etc/xymonserver.cfg"
and then at the shell prompt do an
   echo $XYMSRV
   echo $XYMONSERVERS
the first one reports the IP, and the second is blank ?


Since the "conn" status claims to be flapping, it would be interesting
if you had a look at the historical status logs - especially the
"Status message received from ..." text near the bottom of the status
page. That can tell you if the two reports originated from one
system, or from two different systems (and in that case, which ones).


Regards,
Henrik

I have this set up...

Server A

# cd /export/xymon/server/etc
# egrep "XYMS|RIP" xymonserver.cfg
XYMONSERVERIP="10.235.57.11"            # The IP-address of your server.

Use the real one, not 127.0.0.1 .
XYMSRV="$XYMONSERVERIP"         # IP of a single Xymon server
XYMSERVERS=""                   # IP of multiple Xymon servers. If used,
XYMSRV must be 0.0.0.0

MACHINEADDR="$XYMONSERVERIP"            # This systems IP-address
BBSERVERIP="$XYMONSERVERIP"
BBDISP="$XYMSRV"
BBDISPLAYS="$XYMSERVERS"


Server B
# cd /export/xymon/server/etc
# egrep "XYMS|RIP" xymonserver.cfg
XYMONSERVERIP="10.235.157.56"            # The IP-address of your server.

Use the real one, not 127.0.0.1 .
XYMSRV="$XYMONSERVERIP"         # IP of a single Xymon server
XYMSERVERS=""                   # IP of multiple Xymon servers. If used,
XYMSRV must be 0.0.0.0

MACHINEADDR="$XYMONSERVERIP"            # This systems IP-address
BBSERVERIP="$XYMONSERVERIP"
BBDISP="$XYMSRV"
BBDISPLAYS="$XYMSERVERS"


When I use the CGI to Enable / Disable alerts...  I am only enabling /
disabling on the server I'm viewing.
I'm using http://<server IP>/hobbit-seccgi/enadis.sh

How do I make my single enable / disable action propagate to both servers?

Is it as simple as changing
XYMSRV="0.0.0.0"
XYMSERVERS="10.235.57.11 10.235.157.56"
on both servers
and restarting xymon on both servers?

On 10 November 2012 03:39, Eric Thiele <user-2e962fdfbf92@xymon.invalid> wrote:

No, you probably don't want to do that.  My experience trying to do this
was that each forwarded alerts to the other and back again, so each server
received double status messages for at least some tests.

I solved the problem this way:

http://en.wikibooks.org/wiki/System_Monitoring_with_Xymon/Other_Docs/FAQ#Can_I_enable.2Fdisable_on_only_one_display_server_and_have_it_show_on_both.3F

J

On Fri, 9 Nov 2012 10:39:43 -0600, Eric Thiele <user-2e962fdfbf92@xymon.invalid> wrote:

Server A
Server B

Use the xymond_distribute module on your main server - using it on both is
not recommmended, since you will probably end up with a forwarding loop.


Regards,
Henrik

I was using something similar to what Eric was using.  Nice to know this exists, trying it now, enabled in tasks.cfg.  Perhaps xymond distribute was added in 4.3.10 or an earlier version and I was not paying attention. Nice!  Thanks Henrik.

-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of user-ce4a2c883f75@xymon.invalid
Sent: Wednesday, November 14, 2012 07:23
To: xymon at xymon.com
Subject: Re: [Xymon] Xymon server reporting to itself and another Xymon server

On Fri, 9 Nov 2012 10:39:43 -0600, Eric Thiele <user-2e962fdfbf92@xymon.invalid> wrote:

Use the xymond_distribute module on your main server - using it on both is
not recommmended, since you will probably end up with a forwarding loop.


Regards,
Henrik