Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi all,
I've set a cluster of 3 servers with Proxmox 4.2 and DRBD9; Proxmox
on 2 RAID1 HDD and DBRBD9 on 4 RAID 10 HDD.
DRBD9 use a complete mesh network configuration, with 2 dedicated
Ethernet interfaces for each node, connected with cross patch (no
switch connections).
Here below the drbdctrl.res, manually configurated regarding connections:
------------------
resource .drbdctrl {
net {
cram-hmac-alg sha256;
shared-secret "secretstring";
allow-two-primaries no;
max-buffers 8000;
max-epoch-size 8000;
sndbuf-size 0;
}
volume 0 {
device minor 0;
disk /dev/drbdpool/.drbdctrl_0;
meta-disk internal;
}
volume 1 {
device minor 1;
disk /dev/drbdpool/.drbdctrl_1;
meta-disk internal;
}
on mpve1 {
node-id 0;
}
on mpve2 {
node-id 1;
}
on mpve3 {
node-id 2;
}
# mpve1-2 have crossover links like 192.168.65.x
connection {
host mpve1 address 192.168.65.135:7012;
host mpve2 address 192.168.65.136:7021;
}
# mpve1-3 have crossover links like 192.168.67.x
connection {
host mpve1 address 192.168.67.135:7013;
host mpve3 address 192.168.67.137:7031;
}
# mpve2-3 have crossover links like 192.168.66.x
connection {
host mpve2 address 192.168.66.136:7023;
host mpve3 address 192.168.66.137:7032;
}
}
-----------------
Due to a missed initial communication between the noder mpve1 and
mpve3 adding mpve3 , I have this output from drbdmanage list-nodes:
root at mpve1:~# drbdmanage list-nodes
+------------------------------------------------------------------------------+
| Name | Pool Size | Pool Free | |
State |
|------------------------------------------------------------------------------|
| mpve1 | 7612664 | 7581452 | |
ok |
| mpve2 | 7612664 | 7581452 | |
ok |
| mpve3 | unknown | unknown | | pending actions: adjust
connections |
+------------------------------------------------------------------------------+
The ssh communication between nodes seems to be OK.
Maybe there was a problem creating meta-data in the initial setup?
Is there any way to correct the problem without the need to reinstall the node?
Thanks in advance for help.
Michele