I have an xymon client for a NAS but the NAS is connected via another xymon client and is not reachable from the xymon server. How would I set this up in the xymon server configuration - does it need a hosts.cfg entry and if so, what would it look like? On the client, do I give it the address of the xymon client running xymonproxy or the actual server?
Regards,
Nick Pettefar
I had a similar situation at a client a few years ago. I wrote a script that ran on Xymon client foo, which collected info from device/client bar Client foo, then sent xymon status and data messages to the server as if they were coming from client bar. Very easy to do. All you need to do is make sure that the $MACHINE value is set appropriately.
Regards Vernon
On 13 March 2013 19:13, Nick Pettefar <Nick at pettefar.com> wrote:
I have an xymon client for a NAS but the NAS is connected via another xymon client and is not reachable from the xymon server. How would I set this up in the xymon server configuration - does it need a hosts.cfg entry and if so, what would it look like? On the client, do I give it the address of the xymon client running xymonproxy or the actual server?
Regards,
Nick Pettefar
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
-- "Accept the challenges so that you can feel the exhilaration of victory"
- General George Patton
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I too do this for one of my Solaris zones. It doesn't make too much sense to have the alert come from the parent machine as only the one zone is running on the machine (to isolate it from the hardware and a more serious root breach), but the zone cannot read RAID status or the like. The global zone runs the scripts, impersonating the local zone.
On 03/13/2013 07:52 AM, Vernon Everett wrote:
I had a similar situation at a client a few years ago. I wrote a script that ran on Xymon client foo, which collected info from device/client bar Client foo, then sent xymon status and data messages to the server as if they were coming from client bar. Very easy to do. All you need to do is make sure that the $MACHINE value is set appropriately.
Regards Vernon
On 13 March 2013 19:13, Nick Pettefar <Nick at pettefar.com <mailto:Nick at pettefar.com>> wrote:
I have an xymon client for a NAS but the NAS is connected via another xymon client and is not reachable from the xymon server. How would I set this up in the xymon server configuration - does it need a hosts.cfg entry and if so, what would it look like? On the client, do I give it the address of the xymon client running xymonproxy or the actual server?
Regards,
Nick Pettefar _______________________________________________ Xymon mailing list Xymon at xymon.com <mailto:Xymon at xymon.com> http://lists.xymon.com/mailman/listinfo/xymon
-- "Accept the challenges so that you can feel the exhilaration of victory" - General George Patton
- ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |novosirj at umdnj.edu - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/EI-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlFAkTEACgkQmb+gadEcsb4CCQCfTW27NdLGTN5R/AAHm6LJECLO H3kAn2tTGOxMjldZiLDnBqsc2D4bYqWP =wAIF -----END PGP SIGNATURE-----
On Wed, Mar 13, 2013 at 7:13 AM, Nick Pettefar <Nick at pettefar.com> wrote:
I have an xymon client for a NAS but the NAS is connected via another xymon client and is not reachable from the xymon server. How would I set this up in the xymon server configuration - does it need a hosts.cfg entry and if so, what would it look like? On the client, do I give it the address of the xymon client running xymonproxy or the actual server?
Regards,
Nick Pettefar
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
If I understand your situation correctly: turn the server with connection to the main xymon server into a proxy and point the NAS to that proxy. I believe you would have to install the xymon server there (to provide the xymonproxy utility) turn off everything you don't need in tasks.cfg and turn on xymonproxy. The comments are good in the file about how to do this. You may have to use the arg to xymonproxy to tell it to listen to a different ip than the standard one if the server is dual homed and the NAS is on, say, a private network.
I'm not sure if the proxy needs hosts.cfg. On my proxy it already does because it was private network tester before it was a proxy.
HTH Steve Purdue
-- If they give you ruled paper, write the other way. -Juan Ramon Jimenez, poet, Nobel Prize in literature (1881-1958)
I prayed for freedom for twenty years, but received no answer until I prayed with my legs. -Frederick Douglass, Former slave, abolitionist, editor, and orator (1817-1895)
Hi, thanks for that. I understand that but what I am wondering is what to put in the actual server's hosts.cfg file.
Regards,
Nick Pettefar
On 13 March 2013 13:44, Steve Holmes <sholmes42 at mac.com> wrote:
On Wed, Mar 13, 2013 at 7:13 AM, Nick Pettefar <Nick at pettefar.com> wrote:
I have an xymon client for a NAS but the NAS is connected via another xymon client and is not reachable from the xymon server. How would I set this up in the xymon server configuration - does it need a hosts.cfg entry and if so, what would it look like? On the client, do I give it the address of the xymon client running xymonproxy or the actual server?
Regards,
Nick Pettefar
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
If I understand your situation correctly: turn the server with connection to the main xymon server into a proxy and point the NAS to that proxy. I believe you would have to install the xymon server there (to provide the xymonproxy utility) turn off everything you don't need in tasks.cfg and turn on xymonproxy. The comments are good in the file about how to do this. You may have to use the arg to xymonproxy to tell it to listen to a different ip than the standard one if the server is dual homed and the NAS is on, say, a private network.
I'm not sure if the proxy needs hosts.cfg. On my proxy it already does because it was private network tester before it was a proxy.
HTH Steve Purdue
-- If they give you ruled paper, write the other way. -Juan Ramon Jimenez, poet, Nobel Prize in literature (1881-1958)
I prayed for freedom for twenty years, but received no answer until I prayed with my legs. -Frederick Douglass, Former slave, abolitionist, editor, and orator (1817-1895)
On Wed, Mar 13, 2013 at 10:04 AM, Nick Pettefar <Nick at pettefar.com> wrote:
Hi, thanks for that. I understand that but what I am wondering is what to put in the actual server's hosts.cfg file.
Regards,
Nick Pettefar
On 13 March 2013 13:44, Steve Holmes <sholmes42 at mac.com> wrote:
On Wed, Mar 13, 2013 at 7:13 AM, Nick Pettefar <Nick at pettefar.com>
wrote:
I have an xymon client for a NAS but the NAS is connected via another xymon client and is not reachable from the xymon server. How would I set this up in the xymon server configuration - does it need a hosts.cfg entry and if so, what would it look like? On the client, do I give it the address of the xymon client running xymonproxy or the actual server?
Regards,
Nick Pettefar
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon
If I understand your situation correctly: turn the server with connection to the main xymon server into a proxy and point the NAS to that proxy. I believe you would have to install the xymon server there (to provide the xymonproxy utility) turn off everything you don't need in tasks.cfg and turn on xymonproxy. The comments are good in the file about how to do this. You may have to use the arg to xymonproxy to tell it to listen to a different ip than the standard one if the server is dual homed and the NAS is on, say, a private network.
I'm not sure if the proxy needs hosts.cfg. On my proxy it already does because it was private network tester before it was a proxy.
HTH Steve Purdue
Just treat it as if the NAS server were talking directly to the xymon server.
Now, if the network tests can't get to the NAS from your main xymon server then you would need to set up the server that we've been talking about as the proxy to do the network tests. If you have to do this, it would have to be configured to run xymonnet and have a copy of the hosts.cfg file. Set the LOCATION variable in xymonserver.cfg on both servers (main and proxy) and make them different (e.g. main and proxy), then on the host.cfg line for the NAS server add the NET:proxy tag on both servers and in tasks.cfg on the main server add the --test-untagged arg for xymonnet so you don't have to add a NET:main on all of the other hosts.
Note that the xymonserver.cfg file on the proxy has to have the *main server IP* value for the XYMSRV variable (IIR, I'm not working today :-).
Steve Purdue
-- If they give you ruled paper, write the other way. -Juan Ramon Jimenez, poet, Nobel Prize in literature (1881-1958)
I prayed for freedom for twenty years, but received no answer until I prayed with my legs. -Frederick Douglass, Former slave, abolitionist, editor, and orator (1817-1895)
participants (4)
-
everett.vernon＠gmail.com
-
Nick＠Pettefar.com
-
novosirj＠umdnj.edu
-
sholmes42＠mac.com