--On Friday, August 05, 2011 03:57:53 PM +0200 Albéric de Pertat <alberic.deper...@adelux.fr> wrote:
> I have two nodes with ips 10.0.9.11/24 and 10.0.9.12/24 routed > via 10.0.9.254. I have declared an IPaddr resource for > 10.0.10.10/24. So far so good. > > primitive ip ocf:heartbeat:IPaddr \ > params ip="10.0.10.10" cidr_netmask="24" nic="eth0" \ > broadcast="10.0.10.255" > > Then I added a Route resource like so : > > primitive gw ocf:heartbeat:Route \ > params destination="0.0.0.0/0" gateway="10.0.10.1" It's not clear from the above what is the role of 10.0.9.254 and if 10.0.10.1 is on your cluster or elsewhere. If 10.0.10.1 is the IP of your normal default gateway and is not part of the cluster, you should be able to get rid of the Route resource and just use the normal non-cluster mechanisms for setting up your default route. > This also works fine. The problems come if I try to move the > resources. If I standby the node where ip is running, the > resources ip and gw will move fine but the first node will be > left without a default gateway as the Route RA simply deletes it > when it stops, whether it's been added by the cluster or not. Routes aren't "stacked", so the fact that the cluster has to remove it when the resource is moved is reasonable. If you had it set up independent of the cluster with the same parameters, then I would consider that a config error. OTOH, if moving the gw resource gets rid of a default route that points to a second gateway, I would consider that a problem with either the cluster software or network stack. Devin _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
