<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.5726" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=554570010-13022009><FONT face=Arial color=#0000ff
size=2>Presumably when a 171.x.x.x Xymon client wants to talk to the Xymon
server, which has a 2.x.x.x address, the client routes its packets to the
firewall which then routes them back to the server, this is standard packet
routing. You will need to ensure that you have firewall rules in place to allow
this though...</FONT></SPAN></DIV>
<DIV><SPAN class=554570010-13022009><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=554570010-13022009><FONT face=Arial color=#0000ff
size=2>Alternatively if you have a spare interface on your Xymon server you
could configure that with a 171.x.x.x address, connect it into a convenient
switch and have the 171. clients send to that address instead. The clients
will still be referred to by their 171. address in the server's bb-hosts file,
you are simply stopping packets routing to the firewall and back. I do something
similar with my Xymon server and clients.</FONT></SPAN></DIV>
<DIV><SPAN class=554570010-13022009><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=554570010-13022009><FONT face=Arial color=#0000ff
size=2>HTH</FONT></SPAN></DIV>
<DIV><SPAN class=554570010-13022009><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=554570010-13022009><FONT face=Arial color=#0000ff
size=2>|\/|artin</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> David Masterson
(damaster) [mailto:damaster@cisco.com] <BR><B>Sent:</B> 12 February 2009
19:04<BR><B>To:</B> hobbit@hswn.dk<BR><B>Subject:</B> [hobbit] Servers (and
clients) with multiple IPs ?<BR><BR></FONT></DIV>
<DIV><SPAN class=219065418-12022009><FONT face=Arial size=2>In my environment,
we have a lab where all the systems are on the 2.x.x.x subnet. This
subnet is firewalled such that it's not visible to the rest of the
company. However, there are some systems in the lab that have 171.x.x.x
IPs and the firewall translates those IPs to the appropriate 2.x.x.x IP so
that communications can be established out of the lab. Effectively,
these systems have two IP addresses. In fact, I've put Xymon on several
of these systems (including the Xymon server).</FONT></SPAN></DIV>
<DIV><SPAN class=219065418-12022009><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=219065418-12022009><FONT face=Arial size=2>While I was
setting up Xymon clients that were just in the lab, there was no problem as
I'd just identify all the systems by their 2.x.x.x IP. My question,
though, is how to configure things on clients that are outside the lab.
Obviously, when I configure the outside clients, I'll have to identify
the server by it's 171.x.x.x IP. The server, though, is identified by
its 2.x.x.x IP in the bb-hosts file. Will this be a problem? Are there
any gotchas to watch out for?</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV align=left><FONT face="Lucida Calligraphy" size=2>David
Masterson</FONT></DIV>
<DIV> </DIV><BR><BR>
<DIV><SPAN style="FONT-SIZE: 8pt; COLOR: #8c8c8c; FONT-FAMILY: Arial"><A
href="http://www.taglocity.com">Taglocity</A> Tags: Systems, SysMgmt,
SystemMonitor, XYmon</SPAN></DIV></BLOCKQUOTE><FONT SIZE=3><BR>
<BR>
*************************************************************************************<BR>
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. <BR>
<BR>
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 security@colt.net and delete the message and any attachments without retaining any copies. <BR>
<BR>
Internet communications are not secure and COLT does not accept responsibility for this message, its contents nor responsibility for any viruses. <BR>
<BR>
No contracts can be created or varied on behalf of COLT Telecommunications, its subsidiaries or affiliates ("COLT") and any other party by email Communications unless expressly agreed in writing with such other party. <BR>
<BR>
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.<BR>
</FONT>
</BODY></HTML>