Setting up a Xymon proxy server 🔗 link

Hi all,

I am unable to find any documentation on the configuration of the hosts files when using xymonproxy, can you help?

I have a number of clients client that have the Xymon proxy server configured as their Xymon server in the xymonclient.cfg file:
XYMSRV="10.5.1.205"

So they will send their status messages to the proxy server.

The proxy server only has the [xymond], [xymondproxy], [xymonclient] and [combostatus] sections configured (do I need xymonnet and xymonnetagain?), this seems sensible to me.

The proxy server also has the clients configured in its hosts.cfg file since it needs to know who to poll for.

The question is, how do I then configure these clients in the main Xymon server? Do I have them in the hosts.cfg file there as well? If so how do I stop the main Xymon server from pinging them?
Also, given that these clients are in a group, how do I get them displayed as a group in the Xymon web pages?

I have gone through the xymonproxy and hosts.cfg man pages but to no avail, so am turning to you all.

|\/|artin

[Colt Disclaimer]
The message is intended for the named addressee only and may not be disclosed
to or used by anyone else, nor may it be copied in any way. The contents of
this message and its attachments are confidential and may also be subject to
legal privilege. If you are not the named addressee and/or have received this
message in error, please advise us by e-mailing user-51905b889b93@xymon.invalid and delete the
message and any attachments without retaining any copies. Internet
communications are not secure and Colt does not accept responsibility for this
message, its contents nor responsibility for any viruses. No contracts can be
created or varied on behalf of Colt Technology Services, its subsidiaries,
group companies or affiliates ("Colt") and any other party by email
communications unless expressly agreed in writing with such other party.
Please note that incoming emails will be automatically scanned to eliminate
potential viruses and unsolicited promotional emails. For more information
refer to www.colt.net or contact us on +44(0)20 7390 3900

Yes, they need to be in the hosts.cfg file on the main server, otherwise, they would be ghosts.

Put the noconn directive in the  servers hosts.cfg file after the # for the proxied machines.


Paul Root    - Engineer III
Managed Services Systems - CenturyLink

From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Ward, Martin
Sent: Wednesday, January 04, 2012 11:55 AM
To: 'xymon at xymon.com'
Subject: [Xymon] Setting up a Xymon proxy server

Hi all,

I am unable to find any documentation on the configuration of the hosts files when using xymonproxy, can you help?

I have a number of clients client that have the Xymon proxy server configured as their Xymon server in the xymonclient.cfg file:
XYMSRV="10.5.1.205"

So they will send their status messages to the proxy server.

The proxy server only has the [xymond], [xymondproxy], [xymonclient] and [combostatus] sections configured (do I need xymonnet and xymonnetagain?), this seems sensible to me.

The proxy server also has the clients configured in its hosts.cfg file since it needs to know who to poll for.

The question is, how do I then configure these clients in the main Xymon server? Do I have them in the hosts.cfg file there as well? If so how do I stop the main Xymon server from pinging them?
Also, given that these clients are in a group, how do I get them displayed as a group in the Xymon web pages?

I have gone through the xymonproxy and hosts.cfg man pages but to no avail, so am turning to you all.

|\/|artin

[Colt Disclaimer] The message is intended for the named addressee only and may not be disclosed to or used by anyone else, nor may it be copied in any way. The contents of this message and its attachments are confidential and may also be subject to legal privilege. If you are not the named addressee and/or have received this message in error, please advise us by e-mailing user-51905b889b93@xymon.invalid<mailto:user-51905b889b93@xymon.invalid> and delete the message and any attachments without retaining any copies. Internet communications are not secure and Colt does not accept responsibility for this message, its contents nor responsibility for any viruses. No contracts can be created or varied on behalf of Colt Technology Services, its subsidiaries, group companies or affiliates ("Colt") and any other party by email communications unless expressly agreed in writing with such other party. Please note that incoming emails will be automatically scanned to eliminate potential viruses and unsolicited promotional emails. For more information refer to www.colt.net<http://www.colt.net>; or contact us on +44(0)20 7390 3900

This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful. If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.

On Wednesday, 4 January 2012 19:54:57 Ward, Martin wrote:

Well, strictly 'proxy' means to only proxy reports from clients on to the display server, but in many cases the proxy is there to reduce the firewall access required, and typically this means that the proxy must do the network tests as well. If so, then yes, xymonnet and xymonnetagain should be enabled.

Yes.

In any environment with multiple instances of xymonnet, you should set the XYMONNETWORK variable in xymonserver.cfg on each server running xymonnet, and in hosts.cfg use the NET: tag with the value of the XYMONNETWORK variable of the server whose xymonnet task should do network tests for it.

This allows you to use the same hosts.cfg across all your servers (otherwise you are most likely to have diverging hosts.cfg files across your Xymon servers, requiring manual merging and updating of multiple files etc.).

Using the normal page, group, group-compress etc. statements?

(But, IMHO, it is wrong to mix the definition of what to test with how to present the display, it would be better to split them IMHO).

Regards,
Buchan

On Wednesday, 4 January 2012 20:42:06 Root, Paul wrote:

This approach will work, but the NET tag was specifically provided for this 
case, and would mean you aren't forced to have diverging hosts.cfg files 
across your Xymon servers.

Devmon also respects the NET tag.

Regards,
Buchan

Brilliant, my thanks Buchan and Paul for your assistance.

I found that if I wanted to use a single hosts.cfg file as Buchan suggested then I had to create a NET tag for every entry and adjust it for those in the new network. This was easily done by adding "NET:default" on to the .default. entry and setting XYMONNETWORK="default" in the xymonserver.cfg file.

|\/|artin

From: Buchan Milne [mailto:user-9b139aff4dec@xymon.invalid]
Sent: 05 January 2012 09:17
To: xymon at xymon.com
Cc: Root, Paul; Ward, Martin
Subject: Re: [Xymon] Setting up a Xymon proxy server


On Wednesday, 4 January 2012 20:42:06 Root, Paul wrote:

This approach will work, but the NET tag was specifically provided for this case, and would mean you aren't forced to have diverging hosts.cfg files across your Xymon servers.


Devmon also respects the NET tag.


Regards,

Buchan


[Colt Disclaimer]
The message is intended for the named addressee only and may not be disclosed
to or used by anyone else, nor may it be copied in any way. The contents of
this message and its attachments are confidential and may also be subject to
legal privilege. If you are not the named addressee and/or have received this
message in error, please advise us by e-mailing user-51905b889b93@xymon.invalid and delete the
message and any attachments without retaining any copies. Internet
communications are not secure and Colt does not accept responsibility for this
message, its contents nor responsibility for any viruses. No contracts can be
created or varied on behalf of Colt Technology Services, its subsidiaries,
group companies or affiliates ("Colt") and any other party by email
communications unless expressly agreed in writing with such other party.
Please note that incoming emails will be automatically scanned to eliminate
potential viruses and unsolicited promotional emails. For more information
refer to www.colt.net or contact us on +44(0)20 7390 3900