[Linux-cluster] Re: How do I use a cross over cable to set up quorum?

[Lon Hohberger]

On Fri, 2005-09-23 at 13:52 +0200, Andreso wrote:


> On 9/22/05, Lon Hohberger <lhh at redhat.com> wrote:
> >
> > * Set broadcast-primary-only (see man cludb)
> 
> cludb does not have a man page.  broadcast-primary-only does not
> appear in google

Upgrade to the latest package from RHN or wherever you got your
software.  Anyway, as it turns out, the man page is wrong anyway (it
references primary_only instead of broadcast_primary_only).  Oops.


> > * Use the disk based tiebreaker.  DO NOT use the IP tiebreaker.
> I use the ping interval instad of tiebreaker Ip.  I guess that is what you mean.

That's equivalent, yes.


>   Member             Status
>   ------------------ ----------
>   10.0.0.2           Inactive
>   10.0.0.3           Active     <-- You are here
> 
>   Service        Status   Owner (Last)     Last Transition Chk Restarts
>   -------------- -------- ---------------- --------------- --- --------
>   httpd          started  10.0.0.2         13:39:06 Sep 23  30        0
>   mysql          started  10.0.0.2         13:39:06 Sep 23  30        0


>   Member             Status
>   ------------------ ----------
>   10.0.0.2           Active     <-- You are here
>   10.0.0.3           Inactive
> 
>   Service        Status   Owner (Last)     Last Transition Chk Restarts
>   -------------- -------- ---------------- --------------- --- --------
>   httpd          started  10.0.0.2         13:39:06 Sep 23  30        0
>   mysql          started  10.0.0.2         13:39:06 Sep 23  30        0

The disk tiebreaker is working correctly.  Your nodes aren't
communicating over the private network (crossover cable, in your case),
though.

The cluster software doesn't do anything arcane.  You can try
double-checking UDP ping-ability (which is basically what the cluster
does, except it's one way instead of bidirectional) using this:

http://people.redhat.com/udping-1.0.tar.gz

Don't set it up as a cluster service, just start the server on one and
try to use udping to ping the other using the private IP.  Also try
obvious things like normal ping, broadcast ping, and ssh.  If these
don't work, you probably have a bad cable, incorrect routing rules, or
incorrect firewall rules.


Your configuration looks okay.  After you get the cluster working, stop
the cluster on both nodes.  Run this on one of them, and copy the
cluster configuration to the other node:

# cludb -p clumembd%broadcast_primary_only 1

You can also do this from one of the nodes:

# shutil -s /etc/cluster.xml

This will prevent the cluster from using public interfaces for
heartbeats, but is not critical in any way to get the cluster software
working.

-- Lon