From: Holger.VanKoll@SWISSCOM.COM
Date: Thu Aug 15 2002 - 12:15:00 EDT
I still dont understand what is meant by binding to a hostname.
You can only bind to a combination of ip-address, port and protocol (tcp,udp).
Some apps use the hostname to determine an ip-address to bind to instead of using 0.0.0.0 for all interfaces.
So does App. X and websphere try to use the same combination?
> -----Original Message-----
> From: Green, Simon [mailto:SGreen@KRAFTEUROPE.COM]
> Sent: Donnerstag, 15. August 2002 17:58
> To: aix-l@Princeton.EDU
> Subject: Re: WebSphere and HACMP
>
>
> I think the problem is that there are two applications, each of which
> requires a different hostname. Normally, one runs on each of
> the two nodes
> in the cluster. But if a node fails you'd end up with both
> applications on
> the same server, but needing different hostnames.
>
> I don't see how this can be done.
>
> Simon Green
> Philip Morris ITSC Europe
>
> AIX-L Archive at http://marc.theaimsgroup.com/?l=aix-l&r=1&w=2
> AIX FAQ at http://www.faqs.org/faqs/aix-faq/
>
> N.B. Unsolicited email from vendors will seldom be appreciated.
>
> > -----Original Message-----
> > From: Theresa Sarver [mailto:IFMC.tsarver@SDPS.ORG]
> > Sent: 15 August 2002 16:17
> > To: aix-l@Princeton.EDU
> > Subject: Re: WebSphere and HACMP
> >
> >
> > For apps that require an exaxt hostname match before they
> > start add the following lines to the script you use to start
> > the app servers:
> >
> > ____________________
> > mkdev -t inet
> > chdev -l inet0 -a hostname=nnn
> >
> > Where nnn is the hostname of the machine the fallover node is
> > masquerading as.
> > _____________________
> >
> > Taken from HACMP Troubleshooting Guide.
> >
> > Hope that helps;
> > Theresa
> >
> >
> > >>> tfwu@TECHNOWORKS.NET 08/15/02 09:48AM >>>
> > Dear all,
> >
> > I have a 2-node HACMP cluster running a specific application
> > X. The HA cluster is configured to hot standby mode and takes
> > care of this specific application X which requires to bind to
> > the hostname. Instead of installing Websphere to node A which
> > is currently the production server, I'm required to install
> > Websphere to node B for proction (as reuested by customer for
> > certain restraints in his environment). Since Websphere by
> > itself supports HA feature, I suppose if node B fails,
> > Websphere in node A will somehow aware and take care of such
> > failure. My concern here is that Websphere requires to bind
> > to the hostname as well. How to resolve the hostname binding
> > issure from both applications (Websphere and Application X),
> > in fact it is a situration similar to mutual take over but
> > only form application level of view. Are there any scripts or
> > tricks to work around this solution?
>
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:16:09 EDT