title: PCS Cluster with Shared IP on different interface
body: <p>I am creating a Fedora PCS Cluster for HAProxy.  I have it running on VMWare, and am following this guide, and get to this step of adding a IPAddr2 resource: <a href="http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/_adding_a_resource.html" rel="nofollow">http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/_adding_a_resource.html</a></p>
  
  <p>The only difference is that I need my cluster heartbeat/comms on one NIC/subnet, and my shared resource IP on a different NIC/subnet.</p>
  
  <p>My internal comms is Node1=192.160.0.1 and Node2=192.168.0.2, and my resource ip is 10.0.0.1</p>
  
  <p>How do I use this command in this situation:</p>
  
  <pre><code>pcs resource create ClusterIP ocf:heartbeat:IPaddr2 \
      ip=192.168.0.120 cidr_netmask=32 op monitor interval=30s
  </code></pre>
  
  <p>If I add it as above, I get this:</p>
  
  <pre><code>[root@node-01 .pcs]# pcs status
  Cluster name: mycluster
  Last updated: Tue Oct 28 09:10:13 2014
  Last change: Tue Oct 28 09:00:13 2014 via cibadmin on node-02
  Stack: corosync
  Current DC: node-02 (2) - partition with quorum
  Version: 1.1.11-1.fc20-9d39a6b
  2 Nodes configured
  1 Resources configured
  
  
  Online: [ node-01 node-02 ]
  
  Full list of resources:
  
   ClusterIP      (ocf::heartbeat:IPaddr2):       Stopped
  
  Failed actions:
      ClusterIP_start_0 on node-01 'unknown error' (1): call=7, status=complete, last-rc-change='Tue Oct 28 09:00:13 2014', queued=0ms, exec=27ms
      ClusterIP_start_0 on node-02 'unknown error' (1): call=6, status=complete, last-rc-change='Tue Oct 28 09:00:13 2014', queued=0ms, exec=27ms
  </code></pre>