[Pacemaker] DRBD resource over it's own crosscable?
Kees
chkoehoorn at live.nl
Tue Dec 29 15:19:44 UTC 2009
Hi all,
I'm testing heartbeat/corosync. I've been able to make a simple
two-node-cluster with drbd. Now i want to build a 3-node cluster.
Two nodes for storage with drbd. The third node as to become a webserver
getting his data via NFS from the master storge-node.
Sounds simple. But i ran into the first problem. I've would like both
storage-nodes to exchange drdb-data over an (faster, 1Gb/s) link
(crosscable).
Do i have to configure a second ring in corosync.conf for the drbd to
work over this crosscable-link, just like many examples show?
My webserver is not on that second ring, when i try to do that i get an
error: status = Marking ringid 1 interface 192.168.0.1 FAULTY -
adminisrtative intervention required.
I seems corosync.conf has to be the same on all nodes, is that true? if
so, is there a way to let the drdb work on is own link?
Greetings
Kees
More information about the Pacemaker
mailing list