On Sat, Jul 18, 2009 at 4:53 PM, Tom Potwin<[email protected]> wrote: > Hi > > I've searched all over, and just gotten more confused. I need to set up a > auto failover for my primary server. I have the same system backed up on to > my second server in real time already. Both servers have two NIC's; one for > the network connection to my firewall/router, and the other is just for the > replication. I have a few sites that use SSL certificates, so I'm using > separate public IP's on my router, matched to separate private IP's on the > server. The addresses look like this: > 192.168.31.202 - This is the main server address, also used for the common > web sites that have no SSL's > 192.168.31.203 - SSL site 1 > 192.168.31.204 - SSL site 2 > 192.168.31.205 - SSL site 3 > The secondary server uses 192.168.31.212 as the main server IP. > > What's confusing me is how do I make a setup that will detect the primary is > down, switch to the secondary, then change the secondary IP's to be like the > primary's.
It can't and shouldn't do this. The IPs that get moved around need to be additional ones and not owned by the machines themselves. > I've found all kinds of tutorials to set up heartbeat, but I > can't find details on this kind of set up. Am I looking for the wrong thing? > Is heartbeat unable to do this? Do I need another software with it? The only > thing I keep finding is load balancer setup's using a master IP address, but > I don't need a load balancer, and I can't use a single master IP because of > the SSL's. > Please help, I'm getting a headache. > > Thanks, Tom > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
