Hi LJ,
It used to be like that, up to ~v5.x or so, but AFAIK, the issue you mentioned has been fixed. The problem used to be that ARSystem validates the server license against what it deemed the Host ID to be and the Host ID was linked to the MAC of the first NIC. The AR System server would then not start up properly if the first NIC has the wrong MAC. It was changed at some point to search for any NIC with the correct MAC. To answer Radhika's original question: AFAIK: No, you cannot bind ARSystem to a specific interface. It binds to all interfaces (0.0.0.0) by default. This is hardcoded into the arserverd code. You will have to log an RFE with BMC if you want to have this changed. Best Regards, Theo From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of LJ LongWing Sent: 18 February 2014 19:35 To: [email protected] 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 should be. On Tue, Feb 18, 2014 at 10:21 AM, Grooms, Frederick W <[email protected] <mailto:[email protected]> > 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 <http://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:[email protected] <mailto:[email protected]> ] On Behalf Of Narayanan, Radhika Sent: Tuesday, February 18, 2014 7:14 AM To: [email protected] <mailto:[email protected]> 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 <http://www.arslist.org> "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"
