Xymon client on private network - proxy solution?
Xymon users & admins,
I have a few servers(LDAP, QNAP/NFS, etc..) that are located on a private network but can be reached via ssh by tunneling through various other servers which are connected to the internet. I need to figure out how to have these private network clients send xymon reports to my xymon server located on the outside. I will try and map out the situation so you guys can have a better visual idea with fictional IPs.
2 Main subnets are controlled by me 120.15.130.x 120.15.131.x
Server A : Main XYMON Server - 120.15.131.1 Server B : Current working Xymon Client - 120.15.131.2 & 192.168.1.2 (2nd NIC connected to a switch which is not connected to any other outside network) Server C : NFS Server - 192.168.1.3 - I need an xymon client installed on here and to be able to communicate(push reports) to the main xymon server by going through Server B(proxy).
As you can see the NFS server is not accessible from the main two subnets (120.15.130/131), only accessible from a server connected to the switch. Connecting the xymon server to the private switch is not an option. Is there anyway I can have Server B proxy the report from Server C to Server A. Server B is already running tinyproxy, can I use this or do I have to use a special xymonproxy extension? I would like to avoid having a 2nd full xymon server, I would just like one of my current xymon clients to act as a proxy or relay server.
Appreciate any help. Thanks,
*Joseph De Nicolo* *Secure Database Administrator*- *Center for Complex Network Research <http://www.barabasilab.com>* *Northeastern University*
I just did this. Install the Xymon server on B, but disable xymond and enable xymonproxy following the instructions in tasks.cfg. You won't be running a full Xymon server. Of course, you will still want the Xymon client running there. In xymonserver.cfg set XYMSERVERIP to the IP of B, but set XYMSRV to the IP of your main server A. Steve
Wherever you go, there you are.
On Feb 6, 2013, at 2:27 PM, Joseph De Nicolo <denicoloj at gmail.com> wrote:
Xymon users & admins,
I have a few servers(LDAP, QNAP/NFS, etc..) that are located on a private network but can be reached via ssh by tunneling through various other servers which are connected to the internet. I need to figure out how to have these private network clients send xymon reports to my xymon server located on the outside. I will try and map out the situation so you guys can have a better visual idea with fictional IPs.
2 Main subnets are controlled by me 120.15.130.x 120.15.131.x
Server A : Main XYMON Server - 120.15.131.1 Server B : Current working Xymon Client - 120.15.131.2 & 192.168.1.2 (2nd NIC connected to a switch which is not connected to any other outside network) Server C : NFS Server - 192.168.1.3 - I need an xymon client installed on here and to be able to communicate(push reports) to the main xymon server by going through Server B(proxy).
As you can see the NFS server is not accessible from the main two subnets (120.15.130/131), only accessible from a server connected to the switch. Connecting the xymon server to the private switch is not an option. Is there anyway I can have Server B proxy the report from Server C to Server A. Server B is already running tinyproxy, can I use this or do I have to use a special xymonproxy extension? I would like to avoid having a 2nd full xymon server, I would just like one of my current xymon clients to act as a proxy or relay server.
Appreciate any help. Thanks, Joseph De Nicolo Secure Database Administrator Center for Complex Network Research Northeastern University
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
If you can get a shell login on server C, you can use this to collect most of the client data you might want - you don't need to install a Xymon client on C:
http://tools.rebel-it.com.au/xymon-rclient/
Alternatively, you could setup server B do to port forwarding to server A.
J
On 7 February 2013 07:00, Steve Holmes <sholmes42 at gmail.com> wrote:
I just did this. Install the Xymon server on B, but disable xymond and enable xymonproxy following the instructions in tasks.cfg. You won't be running a full Xymon server. Of course, you will still want the Xymon client running there. In xymonserver.cfg set XYMSERVERIP to the IP of B, but set XYMSRV to the IP of your main server A. Steve
Wherever you go, there you are.
On Feb 6, 2013, at 2:27 PM, Joseph De Nicolo <denicoloj at gmail.com> wrote:
Xymon users & admins,
I have a few servers(LDAP, QNAP/NFS, etc..) that are located on a private network but can be reached via ssh by tunneling through various other servers which are connected to the internet. I need to figure out how to have these private network clients send xymon reports to my xymon server located on the outside. I will try and map out the situation so you guys can have a better visual idea with fictional IPs.
2 Main subnets are controlled by me 120.15.130.x 120.15.131.x
Server A : Main XYMON Server - 120.15.131.1 Server B : Current working Xymon Client - 120.15.131.2 & 192.168.1.2 (2nd NIC connected to a switch which is not connected to any other outside network) Server C : NFS Server - 192.168.1.3 - I need an xymon client installed on here and to be able to communicate(push reports) to the main xymon server by going through Server B(proxy).
As you can see the NFS server is not accessible from the main two subnets (120.15.130/131), only accessible from a server connected to the switch. Connecting the xymon server to the private switch is not an option. Is there anyway I can have Server B proxy the report from Server C to Server A. Server B is already running tinyproxy, can I use this or do I have to use a special xymonproxy extension? I would like to avoid having a 2nd full xymon server, I would just like one of my current xymon clients to act as a proxy or relay server.
Appreciate any help. Thanks,
*- *Center for Complex Network Research <http://www.barabasilab.com>* *Northeastern University*
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
For the proxy solution provided by Steve. Do I need to enable [msgcache] in the clientlaunch.cfg of SERVER C? The cfg says msgcache is used for passive clients that cannot connect to the xymon server directly.
*Joseph De Nicolo* *Secure Database Administrator*- *Center for Complex Network Research <http://www.barabasilab.com>* *Northeastern University*
On Wed, Feb 6, 2013 at 6:35 PM, Jeremy Laidman <jlaidman at rebel-it.com.au>wrote:
If you can get a shell login on server C, you can use this to collect most of the client data you might want - you don't need to install a Xymon client on C:
http://tools.rebel-it.com.au/xymon-rclient/
Alternatively, you could setup server B do to port forwarding to server A.
J
On 7 February 2013 07:00, Steve Holmes <sholmes42 at gmail.com> wrote:
I just did this. Install the Xymon server on B, but disable xymond and enable xymonproxy following the instructions in tasks.cfg. You won't be running a full Xymon server. Of course, you will still want the Xymon client running there. In xymonserver.cfg set XYMSERVERIP to the IP of B, but set XYMSRV to the IP of your main server A. Steve
Wherever you go, there you are.
On Feb 6, 2013, at 2:27 PM, Joseph De Nicolo <denicoloj at gmail.com> wrote:
Xymon users & admins,
I have a few servers(LDAP, QNAP/NFS, etc..) that are located on a private network but can be reached via ssh by tunneling through various other servers which are connected to the internet. I need to figure out how to have these private network clients send xymon reports to my xymon server located on the outside. I will try and map out the situation so you guys can have a better visual idea with fictional IPs.
2 Main subnets are controlled by me 120.15.130.x 120.15.131.x
Server A : Main XYMON Server - 120.15.131.1 Server B : Current working Xymon Client - 120.15.131.2 & 192.168.1.2 (2nd NIC connected to a switch which is not connected to any other outside network) Server C : NFS Server - 192.168.1.3 - I need an xymon client installed on here and to be able to communicate(push reports) to the main xymon server by going through Server B(proxy).
As you can see the NFS server is not accessible from the main two subnets (120.15.130/131), only accessible from a server connected to the switch. Connecting the xymon server to the private switch is not an option. Is there anyway I can have Server B proxy the report from Server C to Server A. Server B is already running tinyproxy, can I use this or do I have to use a special xymonproxy extension? I would like to avoid having a 2nd full xymon server, I would just like one of my current xymon clients to act as a proxy or relay server.
Appreciate any help. Thanks,
*- *Center for Complex Network Research <http://www.barabasilab.com>* *Northeastern University*
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
participants (3)
-
denicoloj＠gmail.com
-
jlaidman＠rebel-it.com.au
-
sholmes42＠gmail.com