I guess I'm a bit confused. I hope you can be patient while I illustrate further in the hopes of having an epiphany.
The 192.168.1.1 ip resource is to provide a failover default gateway for the internal servers, and will have no LVS virtual or real server resources associated with it. The statically assigned ip's (outside of heartbeat control) for the internal interfaces in my example would be 192.168.1.2 and 192.168.1.3
The 10.10.10.1, 10.10.10.4, and 10.10.10.5 ip resources will be Virtualservers configured to use realservers on 192.168.1.xxx (eg: 10.10.10.1 -> 192.168.1.5 & 192.168.1.6). The statically assigned ip's (outside of heartbeat control) for the external interfaces in my example would be 10.10.10.2 and 10.10.10.3.
First, does my clarification above make sense? Second, would I still declare 192.168.1.1 and 10.10.10.1, 10.10.10.4, 10.10.10.5, etc, IP's as you descibe below in haresources?
Chris Malcolm Turnbull wrote:
Chris, You can do it in a number of ways, but I normally configure a fixed IP for both eth0 and eth1 (internal & external) then haresources handles all of the floating/failover ips i.e. firewall.foo.com 10.10.10.1 10.10.10.4 10.10.10.5 192.168.1.1 ldirectord heartbeat figures out which interfaces to use (as you already have the fixed ips in your normal start up scripts).
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
