Since I didn't get a response to either of my previous questions about multiple ucast directive and hangman, I'll try to explain what we're trying to do. Basically, a potentially showstopping constraint is geographic redundancy. This makes running a serial cable between the two rather difficult.
Each server has two NICs. Each NIC will be connected to a different router, so there will be multiple paths between the nodes. We're concerned about a "hangman" situation where communication between both nodes goes down and the services we're monitoring with Heartbeat come up on both nodes. Is there an easy way to configure 2.0.x without CRM so that in a state of confusion, only the primary node stays up? I mean, the haresources already require I specify the preferred primary node. So, is there a way to key off of this? Or, will we have to write our own ipfail script? Thanks for any tips. -- Jiann-Ming Su "I have to decide between two equally frightening options. If I wanted to do that, I'd vote." --Duckman "The system's broke, Hank. The election baby has peed in the bath water. You got to throw 'em both out." --Dale Gribble _______________________________________________________ Linux-HA-Dev: [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
