mark cormier <firstname.lastname@example.org>
"Perrier,Kent - PLANO" <Kent.Perrier@Oneco.net>
Matthew Stier <Matthew.Stier@tddny.fujitsu.com>
who suggested I look into clustering.
I think I am going to combine that idea with the IP aliasing
I mentioned in my post.....
I can allocate IP addresses on my private network for each SNA
functionality that I want. I can then use Cluster management
scripts to figure out which hosts can really offer those services
(eg, rsh proddg '(cd /opt/SUNWpu21; ./sunop -c dis)' )
Then, my service management script can configure the private
interface of that host to have the virtual IP of that service.
My /hosts file could then remain the same on the whole cluster.
This scheme does not require the SNA-providing server to be a member
of the cluster, since the management can be done remotely.
>>> "Seth Rothenberg" <SROTHENB@montefiore.org> 07/17/00 10:45AM >>>
We use SunLink SNA to communicate with an IBM mainframe.
Currently, the primary Sun server has a direct connection to the IBM,
and I configure the application to use "localhost". I would like to
set up two workstations with a direct connection on each, and give
the workstations aliases "sna1" and "sna2".
Then, I would change the application to use the SNA server on host "sna1" or "sna2"
However, I would really like to automate the failover between sna1 and sna2.
I would set up the applicaiton to use "sna" as the name,
and then one workstation or the other could serve that role - which one responds
would be controlled by outside tests.
U BEFORE POSTING please READ the FAQ located at
. and the list POLICY statement located at
A To submit questions/summaries to this list send your email message to:
A To unsubscribe from this list please send an email message to:
E and in the BODY type:
R unsubscribe sun-managers
. unsubscribe sun-managers email@example.com
L To view an archive of this list please visit:
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:12 CDT