Hi Radhika! The only way you will be able to do this is to fool Remedy into thinking each instance is running on a diferent hostname by: 1) Aliasing the 3 different server names in the host file. 2) Setting the HOSTNAME variable before installing / starting each copy of ARSystem.
This may or may not work, is a bit dangerous and can NOT be recommended for a production environment. Best Regards, Theo On Fri, Feb 21, 2014 at 11:05 AM, Narayanan, Radhika < radhika.naraya...@cgi.com> wrote: > ** > > Hi Axton/Longwing, > > > > My first problem is that the AR Server itself is not starting when I setup > 3 AR Servers in a server group on a single physical server. (ARS 8.1, RHEL > 6.4) > > > > AR Server 1: Server-Name: d1 (Load balancer), Server-Connect-Name: d10 > > AR Server 2: Server-Name: d1, Server-Connect-Name: d11 > > AR Server 3: Server-Name: d1, Server-Connect-Name: d11 > > > > The 3 AR Servers are on one physical server and in a server group. d10, > d11, d12 are 3 different virtual IP Addresses/Names for the physical server. > > > > AR Server service refuses to start. It complains armonitor.conf file > cannot be found. *Each AR Server (arsystem startup script) is looking for > /etc/arsystem/d1/armonitor.conf !!* d1 is the Load balancer = Server-Name > in ar.conf. > > > > I cannot use 1 armonitor.conf for 3 AR Servers. Can I? The > server-connect-name is referred inside the armonitor.conf which is > different for the 3 AR Servers! > > > > I find this architecture/requirement equally weird. It was decided by the > client. They want 3 AR Servers on one physical server in a server group. > I'm trying to squeeze Remedy into it now. > > > > Thanks > > Radhika > > +44 20718 25880 > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@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 work. > > > > Axton Grams > > > > On Thu, Feb 20, 2014 at 9:59 AM, Axton <axton.gr...@gmail.com> wrote: > > You could setup redirection using iptables to achieve what you want. Each > server would effectively be listening on all ip addresses on different > ports, but the redirection would redirect things as desired. > > > > http://www.cyberciti.biz/faq/linux-port-redirection-with-iptables/ > > http://blog.softlayer.com/2011/iptables-tips-and-tricks-port-redirection > > > > On Wed, Feb 19, 2014 at 1:54 AM, Narayanan, Radhika < > radhika.naraya...@cgi.com> wrote: > > ** > > 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 restriction because I want to > use the other IPs too , but for a second and third instance of AR Server. > > I'll write back to them stating that the current version of AR Server > doesn't support this. Perhaps I 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 > > > > ** > > 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 other IP addresses since you are on linux. > > > > Axton Grams > > > > On Tue, Feb 18, 2014 at 11:21 AM, Grooms, Frederick W < > frederick.w.gro...@xo.com> wrote: > > 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 valid name for an IP. If it is then check if your DNS server has it > listed. > > Example: > AR Server = arsdev01 > Physical Server = devserver1 > > /etc/hosts file > # Do not remove the following line, or various programs > # that require network functionality will fail. > 127.0.0.1 localhost.localdomain localhost > ::1 localhost6.localdomain6 localhost6 > 192.168.1.101 devserver1 devserver1.mycorp.com arsdev01 > > DNS has a cname record for arsdev01 pointing to 192.168.1.101 > > > Fred > > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] On Behalf Of Narayanan, Radhika > Sent: Tuesday, February 18, 2014 7:14 AM > To: arslist@ARSLIST.ORG > Subject: arserverd binding to 0.0.0.0 > > ** > Hi List, > > How can I make the arserverd executable listen on a given, specific IP > Address and not on 0.0.0.0? > > By default, arserverd binds to the interface 0.0.0.0. My RHEL 6.4 server > has 5 IP Addresses. I want it to bind only to one of the 5 IP Addresses > that I mention in armonitor.conf. > > armonitor.conf: > /apps/tim/ar/timw0/bin/arserverd.sh -s dc5chw-000 -i /apps/tim/ar/timw0 -l > /etc/arsystem/dc5chw-000 > > In this line, the server name is mentioned as dc5chw-000. I want arserverd > to bind only to this IP Address. How can I achieve this? > > Environment: ARS 8.1 Patch 2 on RHEL 6.4 > > Thanks > Radhika > +44 20718 25880 > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > > > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
