[Pacemaker] IPaddr2 between eth1 e bond1

[Michael Schwartzkopff]

Am Freitag, 4. Oktober 2013, 21:04:13 schrieb Charles Mean:
> Hello guys,
> 
> I have a cluster with 2 nginx sharing one VIP:
> 
> primitive VIP_AD_SRV ocf:heartbeat:IPaddr2 params ip="X.Y.Z.W"
> cidr_netmask="30" nic="eth1" op monitor interval="1s"
> 
> 
> The problem is that I have replaced on of those two server and the new one
> can't connect over eth1 just over bond1, so, when I move the resource to
> this new server it creates a virtual interface at eth1 and I never reach it.
> Is there a way to solve this situation ?
> 
> Thank you

hi,

yes, it is possbile to solve that problem. But it is a little bit tricky and 
you need to play with the XML config file. No shell (pcs, crm) I would know of 
supports that feature.

For details see:

http://clusterlabs.org/doc/en-US/Pacemaker/1.1-
crmsh/html/Pacemaker_Explained/_using_rules_to_control_resource_options.html

The example given uses different ports on the cluster nodes, but it also works 
for different interface names on the nodes.

ON the other hand, you could the resource figure out the interface by itself 
via the routing lookup. If the nodes have a dedicated IP address in the net of 
the VIP it should work automagically.

Greetings,
-- 
Dr. Michael Schwartzkopff
Guardinistr. 63
81375 München

Tel: (0163) 172 50 98
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20131005/fc23f60d/attachment-0003.html>