From: Christy Wu, T.F. (tfwu@TECHNOWORKS.NET)
Date: Thu Aug 15 2002 - 11:48:06 EDT
Thanks for your promptly reply, Theresa. But you see the problem here is:
If node B fails, the Websphere in node A will be activated and will acquire node B's hostname.Meanwhile node A is in fact the production server of application X which has binded to the hostname of node A. So I can simply not be able to change the hostname to either applications (both aplication X and Websphere)
Christy
"Theresa Sarver" <IFMC.tsarver@SDPS.ORG> wrote in message news:sd5b8d9e.078@sdps.org...
> 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?
>
> Best regards,
> Christy
> a
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:16:09 EDT