Chris, Normally you would just put ldirectord or keepalived in your haresources (crm?) file (assuming you are using a health checking framework for LVS?) Or you can just start them and leave them running all the time on both nodes (as they are pretty much stateless)
2009/3/5 Chris Price <[email protected]>: > > > I am implementing a redundant router-firewall solution with active/passive > failover for a 'floating' ip on BOTH the Internal and External interfaces. > I'm a bit confused at the moment by the documentation, so I'd like to ask > for some clarification/direction on how to best proceed. > > Scenario: > > > External Fail-over Ip: > 10.10.10.1 > / > \ > ----------------------------------------- > ----------------------------------------- | > Firewall 1 | | > Firewall 2 | > | External interface eth0: 10.10.10.2 | | > External interface eth0: 10.10.10.3 | > | Internal interface eth1: 192.168.1.2 | | > Internal Interface eth1: 192.168.1.3 | > ----------------------------------------- > ----------------------------------------- > \ > / > Internal Fail-over IP: > 192.168.1.1 > > > The heartbeat can be accomplished by serial, ucast, bcast or whatever is > best. Again, this is an active/passive setup, with the 'fail-over' IP's only > active on one node at a time. > > Note that the active node in the cluster will also be configured as a LVS > director, providing load balanced services for http/https servers on the > Internal network. I assume that the LVS startup can be handled by linux-ha > as a call to an external script on node failover (my understanding of > linux-ha is running thin here)? > > Any initial direction you can provide is greatly appreciated. > TIA. > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > -- Regards, Malcolm Turnbull. Loadbalancer.org Ltd. Phone: +44 (0)870 443 8779 http://www.loadbalancer.org/ _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
