Hello all, I have an Active/Passive configuration that I have been trying to get working that is very frustrating. This may have already been answered somewhere, and if so, just point me to the place.
Overview: I have a system (PUBLIC_WEB) with a public viewable IP address (128.249.65.X) that runs a web service. I have a VMware Host on another system with a public viewable address (VMWARE_HOST) (128.249.65.X) that contains a virtual system (VIRT_PUBLIC_WEB) with a private ip (172.30.10.X). I want the virtual system (VIRT_PUBLIC_WEB) with the private IP (172.30.10.X) to provide simple failover for the public system (PUBLIC_WEB). I have this working with another node, but in that case both nodes are on the private ip (172.30.10.X), so I know it is possible for VMware virtual systems to act as failover devices. In all cases the host files are correct, the ha.cf files match as do the haresources files. All systems can ping one another. I am using heartbeat v2, but configured as a v1 (no crm or anything fancy). Questions: First of all, is it possible for a heartbeat node on one net to failover and assume a different nets address. That seems to be the hangup here. If anyone else has done a setup like this I would appreciate some assistance. Second, might it be a routing issue? Each system can ping across its net to the other, but does heartbeat have its own way of doing things that may not include using the standard linux net tools? When the master node (PUBLIC_WEB) is taken down, the virtual system (VIRT_PUBLIC_WEB) detects it and craps out running the resource.d/IPaddr <ip address> start. Any help would be appreciated. Once I have been assured that this configuration is possible, I will post any config files that are needed to help me fix this problem. Many Thank In Advance. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
