[Pacemaker] IPaddr2 between eth1 e bond1

Andreas Kurz andreas at hastexo.com
Sun Oct 6 21:27:20 UTC 2013


On 2013-10-05 02:04, Charles Mean wrote:
> 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 ?

Simply don't specify "nic" if you don't have several interfaces in the
same network. The resource agent will find the interface by looking at
interfaces having already an IP in the same network configured ... no
matter whether they are simple/bond/bridges/vlan interfaces.

Regards,
Andreas

-- 
Need help with Pacemaker?
http://www.hastexo.com/now

> 
> Thank you
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
> 




-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 287 bytes
Desc: OpenPGP digital signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20131006/bb2cdab1/attachment-0004.sig>


More information about the Pacemaker mailing list