Xymon Mailing List Archive search

Getting Xymon client to send from a specific IP address

4 messages in this thread

list Bill Arlofski · Fri, 13 Dec 2013 10:59:38 -0500 ·
Hi everyone.

I have a few servers which have multiple IP addresses bound to the same
ethernet interface. I am not sure how the Xymon client chooses which IP to use
when sending.  In a post from Henrik in a different thread it seems like it
may be the underlying OS that chooses.

My problem is that on a recently built server, the Xymon client reports are
coming from the server's aliased IP rather than the primary IP on the
interface, so this host's reports show up in the ghost client report.

Any way to force it to use an IP.

Thanks for any help

-- 
Bill Arlofski
Reverse Polarity, LLC
http://www.revpol.com/
-- Not responsible for anything below this line --
list Josh Luthman · Fri, 13 Dec 2013 11:06:56 -0500 ·
Could you do it with a route?  That is specify a preferred source to the
destination IP.


Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX
quoted from Bill Arlofski


On Fri, Dec 13, 2013 at 10:59 AM, Bill Arlofski <user-0b8af203a56e@xymon.invalid>wrote:
Hi everyone.

I have a few servers which have multiple IP addresses bound to the same
ethernet interface. I am not sure how the Xymon client chooses which IP to
use
when sending.  In a post from Henrik in a different thread it seems like it
may be the underlying OS that chooses.

My problem is that on a recently built server, the Xymon client reports are
coming from the server's aliased IP rather than the primary IP on the
interface, so this host's reports show up in the ghost client report.

Any way to force it to use an IP.

Thanks for any help

--
Bill Arlofski
Reverse Polarity, LLC
http://www.revpol.com/
-- Not responsible for anything below this line --

list Bill Arlofski · Fri, 13 Dec 2013 13:52:42 -0500 ·
quoted from Josh Luthman
On 12/13/13 11:06, Josh Luthman wrote:
Could you do it with a route?  That is specify a preferred source to the
destination IP.


Josh Luthman
Hi Josh,  Thanks for that... But the IP addresses are in the same subnet.

I think I may have fixed it by adding the    conn=2ndIPAddress    to the
servers's line in the hosts file.

If I have some time, I will remove the line and see if the server shows up
again in the ghost clients page and I'll report back what I find.

Thanks!
quoted from Josh Luthman

-- 
Bill Arlofski
Reverse Polarity, LLC
http://www.revpol.com/
-- Not responsible for anything below this line --
list Bill Arlofski · Wed, 18 Dec 2013 12:20:49 -0500 ·
quoted from Bill Arlofski
On 12/13/13 13:52, Bill Arlofski wrote:
On 12/13/13 11:06, Josh Luthman wrote:
Could you do it with a route?  That is specify a preferred source to the
destination IP.


Josh Luthman
Hi Josh,  Thanks for that... But the IP addresses are in the same subnet.

I think I may have fixed it by adding the    conn=2ndIPAddress    to the
servers's line in the hosts file.

If I have some time, I will remove the line and see if the server shows up
again in the ghost clients page and I'll report back what I find.

Thanks!
OK, just a quick follow-up.

I removed the conn= setting from the host's definition and the ghost client
entry has not shown up after several days.

Can't explain why, perhaps the host just started sending Xymon reports from
its primary IP for an unknown reason.

No idea on this one, but thought I would at least report back to close out
this thread. :)
quoted from Bill Arlofski

-- 
Bill Arlofski
Reverse Polarity, LLC
http://www.revpol.com/
-- Not responsible for anything below this line --