Re: arserverd binding to 0.0.0.0

2014-02-21 Thread Narayanan, Radhika
@ARSLIST.ORG] On Behalf Of Axton Sent: 20 February 2014 21:39 To: arslist@ARSLIST.ORG Subject: Re: arserverd binding to 0.0.0.0 ** If done properly, the rpc port mapper could work on all interfaces for all 3 servers. I say could because it's probably not been proven/done, but in theory it should

Re: arserverd binding to 0.0.0.0

2014-02-21 Thread Theo Fondse
:39 *To:* arslist@ARSLIST.ORG *Subject:* Re: arserverd binding to 0.0.0.0 ** If done properly, the rpc port mapper could work on all interfaces for all 3 servers. I say could because it's probably not been proven/done, but in theory it should work. Axton Grams On Thu, Feb 20, 2014

Re: arserverd binding to 0.0.0.0

2014-02-21 Thread Narayanan, Radhika
in the Load balancer name in /etc/arsystem ! Thanks Radhika +44 20718 25880 From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Theo Fondse Sent: 21 February 2014 15:12 To: arslist@ARSLIST.ORG Subject: Re: arserverd binding to 0.0.0.0 ** Hi Radhika

Re: arserverd binding to 0.0.0.0

2014-02-21 Thread Theo Fondse
System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *Theo Fondse *Sent:* 21 February 2014 15:12 *To:* arslist@ARSLIST.ORG *Subject:* Re: arserverd binding to 0.0.0.0 ** Hi Radhika! The only way you will be able to do this is to fool Remedy into thinking each

Re: arserverd binding to 0.0.0.0

2014-02-20 Thread Narayanan, Radhika
Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W Sent: 19 February 2014 19:42 To: arslist@ARSLIST.ORG Subject: Re: arserverd binding to 0.0.0.0 So you have 1 physical server box with 3 IPs. You could run 3 virtual Red Hat instances (each with 1 IP

Re: arserverd binding to 0.0.0.0

2014-02-20 Thread Grooms, Frederick W
, Radhika Sent: Thursday, February 20, 2014 8:20 AM To: arslist@ARSLIST.ORG Subject: Re: arserverd binding to 0.0.0.0 Hi Fred, Yes, you're so right. Only, in our case, the client is not willing to create 3 virtual RHEL instances from the physical server. They give a reason that their vendor support

Re: arserverd binding to 0.0.0.0

2014-02-20 Thread Narayanan, Radhika
Subject: Re: arserverd binding to 0.0.0.0 Then the only way to have multiple ARS system running on the same machine is to put them on different TCP ports (and only 1 of them can use portmapper) Fred -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist

Re: arserverd binding to 0.0.0.0

2014-02-20 Thread LJ LongWing
@ARSLIST.ORG] On Behalf Of Narayanan, Radhika Sent: Thursday, February 20, 2014 8:20 AM To: arslist@ARSLIST.ORG Subject: Re: arserverd binding to 0.0.0.0 Hi Fred, Yes, you're so right. Only, in our case, the client is not willing to create 3 virtual RHEL instances from the physical server. They give

Re: arserverd binding to 0.0.0.0

2014-02-20 Thread Axton
should raise an RFE. Thanks again, Radhika +44 20718 25880 *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *Axton *Sent:* 19 February 2014 03:57 *To:* arslist@ARSLIST.ORG *Subject:* Re: arserverd binding to 0.0.0.0

Re: arserverd binding to 0.0.0.0

2014-02-20 Thread Axton
again, Radhika +44 20718 25880 *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *Axton *Sent:* 19 February 2014 03:57 *To:* arslist@ARSLIST.ORG *Subject:* Re: arserverd binding to 0.0.0.0 ** Network daemons bind to address/protocol

Re: arserverd binding to 0.0.0.0

2014-02-19 Thread Grooms, Frederick W
@ARSLIST.ORG Subject: Re: arserverd binding to 0.0.0.0 ** Thank you so much, Axton, Fred and others. Our client gave us one physical server with 3 virtual IP Addresses. And asked us to install AR Server on each of the virtual IP Addresses, all on same port. I guess I’m not able to use iptables

Re: arserverd binding to 0.0.0.0

2014-02-19 Thread Theo Fondse (Gmail)
To: arslist@ARSLIST.ORG Subject: Re: arserverd binding to 0.0.0.0 ** I don't know if 'bind' is the proper term, but Remedy DOES get the MAC address of the first ethernet, and if it can't find that ethernet, I have experienced issues in the past with Remedy starting because it can't tell what the host ID

Re: arserverd binding to 0.0.0.0

2014-02-18 Thread patrick zandi
it apparently does not think it has a nic, or have a default address. Need to ensure that the address is up and operational and functioning prior to install. On Tue, Feb 18, 2014 at 8:13 AM, Narayanan, Radhika radhika.naraya...@cgi.com wrote: ** Hi List, How can I make the arserverd

Re: arserverd binding to 0.0.0.0

2014-02-18 Thread Grooms, Frederick W
As far as I know the ARS binaries do not bind to an IP. They will bind to a TCP port if one is specified (and/or use portmapper if that is set). If you are not connecting to the AR Server one item to check is the /etc/hosts file. See if the name you used for your AR Server is listed as a

Re: arserverd binding to 0.0.0.0

2014-02-18 Thread LJ LongWing
I don't know if 'bind' is the proper term, but Remedy DOES get the MAC address of the first ethernet, and if it can't find that ethernet, I have experienced issues in the past with Remedy starting because it can't tell what the host ID should be. On Tue, Feb 18, 2014 at 10:21 AM, Grooms,

Re: arserverd binding to 0.0.0.0

2014-02-18 Thread Axton
Network daemons bind to address/protocol/port. 0.0.0.0 means all addresses. I looked through all the ar.conf parameters and flags supported by arserverd and it does not look like there is a way to tell arserverd to listed on a specific IP. You could use iptables to restrict access on those

Re: arserverd binding to 0.0.0.0

2014-02-18 Thread Axton
Bind is a common term in Linux/Unix circles for this. It is the name of the function in the network stack that does just this (as defined in POSIX.1-2001). http://man7.org/linux/man-pages/man2/bind.2.html Axton Grams On Tue, Feb 18, 2014 at 11:34 AM, LJ LongWing lj.longw...@gmail.com wrote:

Re: arserverd binding to 0.0.0.0

2014-02-18 Thread Narayanan, Radhika
] On Behalf Of Axton Sent: 19 February 2014 03:57 To: arslist@ARSLIST.ORG Subject: Re: arserverd binding to 0.0.0.0 ** Network daemons bind to address/protocol/port. 0.0.0.0 means all addresses. I looked through all the ar.conf parameters and flags supported by arserverd and it does not look like