[Pacemaker] cman heartbeat / interconnect configuration

[Dvorak Andreas]

Hi Michael,

now I got it, thank you very much.

What I did:
Put ips of interfaces in /etc/hosts
ccs -f /etc/cluster/cluster.conf --addnode sv2827-p1
ccs -f /etc/cluster/cluster.conf --addnode sv2828-p1
ccs -f /etc/cluster/cluster.conf --addfencedev pcmk agent=fence_pcmk
ccs -f /etc/cluster/cluster.conf --addmethod pcmk-redirect sv2827-p1
ccs -f /etc/cluster/cluster.conf --addmethod pcmk-redirect sv2828-p1
ccs -f /etc/cluster/cluster.conf --addfenceinst pcmk sv2827-p1 pcmk-redirect port=sv2827
ccs -f /etc/cluster/cluster.conf --addfenceinst pcmk sv2828-p1 pcmk-redirect port=sv2828
add a seond ip or name as interconnect
ccs -f /etc/cluster/cluster.conf --addalt sv2827-p1 sv2827-p2
ccs -f /etc/cluster/cluster.conf --addalt sv2828-p1 sv2828-p2

Best regards
Andreas

-----Ursprüngliche Nachricht-----
Von: Michael Schwartzkopff [mailto:ms at sys4.de] 
Gesendet: Freitag, 13. Dezember 2013 13:46
An: The Pacemaker cluster resource manager
Betreff: Re: [Pacemaker] cman heartbeat / interconnect configuration

Am Freitag, 13. Dezember 2013, 13:34:24 schrieb Dvorak Andreas:
> Dear all,
> 
> after a little break I am coming back to my problem to configure 
> heartbeat / interconnect with cman. Meanwhile I know that cman is the 
> recommended stack on RHEL6.
> I have a pacemaker cluster with cman that is working, but now a would 
> like to configure special interfaces for the direct node communication 
> (heartbeat / interconnect /keep alive).
> 
> Unfortunately I do not understand how configure the interfaces. Can 
> you please give me an advice? Currently the cluster uses

(...)

hi,

cman gets its config from /etc/cluster/cluster.conf.

in the clusternode tag you have the name attribute. cman get the IP address from that name and uses this interface as interface for the cluster configuration.

You have name="sv2827". This names resolves to 10.15.28.27 and thus corosync uses bond0 for the communication in the cluster.

If you want more interfaces you have to use the altname attribute (tag?) in cluster.conf. Configure a alternative name of the node that resolves into an other IP address. You can do this by adding the new IP / name to the /etc/hosts.

If you do not want to use your productive interfaces, just configure a different name in the clusternode tag. Be sure to have a bond device or two single interfaces for redundant communication.

--
Mit freundlichen Grüßen,

Michael Schwartzkopff

--
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044 Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein