We have two NIC's to two switches in the same subnet and a Virtual IP in
the same subnet. Users only connect to the Virtual IP. If either link
fails, the IP users stay connected. As for your remote users, if your
backup link kicks in and the users are going to the same IP, they should
only have to reconnect if their session gets dropped. The network part
should take care of the routing change. Now if they are failing over to
a different machine with a different IP, you will have to change the
clients to the new system. DNS queries may not pick up a new IP if it
is cached. Best bet is to have alternate IP routing and a backup
machine start up the same Virtual IP as the primary machine, AFTER you
END the virtual IP on the Primary machine.
Director of Information Services
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Kelley
Sent: Wednesday, March 19, 2008 9:36 AM
To: Midrange Systems Technical Discussion
Subject: Network Failover
Has anyone done much with Series i in regards to network failover? I
have a number of client machines at a remote location (the other side of
town) connected via VPN. On occasion the link goes down. We have a
secondary link that is in standby mode just in case of failures.
However, the client machines (which run Windows CE and emulator
software) do not "automatically"
switch over as management would like. I explained this would be a manual
operation. Has anyone done any automatic switch overs with Series i
What equipment did you use?
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact