Re: Network Failover

Thanks Chris. It's the "reconnect" issue that causes problems. Folks in the company don't understand why this switch can't be invisible to the remote users. I haven't kept up with networking for the last three or so years, probably a world of change...

Kelley

----- Original Message -----
From: "Chris Bipes" <chris.bipes@xxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, March 19, 2008 11:52 AM
Subject: RE: Network Failover

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.


Chris Bipes
Director of Information Services
CrossCheck, Inc.