I have set up a two-node cluster (active/passive) with Corosync/Pacemaker and nginx as a reverse proxy. OS is RHEL7 and the machine has only one network interface at the moment.

I configured two resources:

  • cluster-vip for the shared virtual IP
  • reverse-proxy for nginx

Here are the declarations of both resources:

pcs resource create cluster-vip ocf:heartbeat:IPaddr2 ip= cidr_netmask=24 op monitor interval=30s

pcs resource create reverse-proxy systemd:nginx op monitor interval=5s meta failure-timeout=60s

pcs constraint colocation add reverse-proxy with cluster-vip INFINITY

pcs constraint order cluster-vip then reverse-proxy

Yesterday, I spotted an unexpected behaviour while doing a network capture. When communicating with the clients, the active node uses the virtual IP address ( When communicating with the web servers located on the internal network, it uses the primary IP address of the interface instead of the vip ( or depending on the active node).

As a result, I am forced to create two different rules on my firewall (one for node1 and one for node2) instead of just allowing the vip to communicate with the web servers. I plan to add other nodes to the cluster, and it would be convenient not to have to allow every single node one by one and just allow the vip once and for all.

Does this behaviour have a logical explanation? Is there a way to tell pacemaker to only use the vip? And is it good practice? I don't want to do anything stupid, so if you think I should not do that, I would gladly hear why.



I don't believe this is a question of instructing pacemaker to only use the virtual IP, but rather telling Nginx to only use the virtual IP.

I am no Nginx expert, but reading through their documentation I found a configuration directive named proxy_bind. I believe this might be what you need to set to get the desired behaviour. From the Nginx documentation here.

If your proxy server has several network interfaces, sometimes you might need to choose a particular source IP address for connecting to a proxied server or an upstream. This may be useful if a proxied server behind NGINX is configured to accept connections from particular IP networks or IP address ranges.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.