No subject

bit overwhelming, being new to HA clusters.

My goals:
* create 2-node Active/Passive firewall cluster
* Each FW node has an external, and internal interface
* Cluster software presents external, internal VIPs
* VIPs must be co-located on same node
* One node is preferred for VIP locations
* If any interface fails on node currently hosting VIPs, VIPs move to other
node

For simplicity sake, I'll start by creating VIPs, and add firewall plumbing
to the VIPs in the future.

My config:
CentOS-6.3 based distro +
corosync-1.4.1-1
pacemaker-1.1.8-1
pcs-0.9.26-1
resource-agents-3.9.2-12
and all required dependencies

My questions:

This sounds like a common use case, but I could not find an example/HOWTO.
 Did I miss it?

Do I have the correct HA cluster packages, versions to start work?
Do I also need the cman?, ccs packages?

How many interfaces should each cluster node have?
    2 interfaces: internal, external
    or
    3 interfaces: internal, external, monitor

Do I need to configure corosync.conf/totem/interface/bindnetaddr, and if
so, bind to what net?

$1M question:
How to configure cluster to monitor all internal, external cluster
interfaces, and perform
failover?  Here's my estimate:

* create external VIP as IpAddr2 and bind to external interfaces
* create internal VIP as IpAddr2 and bind to internal interfaces
* co-locate both VIPs together
* specify a location constraint for preferred node

Any help would be appreciated,
thanks
Jeff

--001a113375769d560504e6acb1e8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I am looking to create a=A0=A02-node Active/Passive firewa=
ll cluster. =A0I am an experienced Linux user, but new to HA clusters. I ha=
ve scanned &quot;Clusters From Scratch&quot; and &quot;Pacemaker Explained&=
quot;. =A0I found these docs helpful, but a bit overwhelming, being new to =
HA clusters.=A0<div>
<div><br></div><div>My goals:</div><div><div>* create 2-node Active/Passive=
 firewall cluster</div><div>* Each FW node has an external, and internal in=
terface</div><div>* Cluster software presents external, internal VIPs</div>
<div>* VIPs must be co-located on same node</div><div>* One node is preferr=
ed for VIP locations</div><div>* If any interface fails on node currently h=
osting VIPs, VIPs move to other node</div><div><br></div><div>For simplicit=
y sake, I&#39;ll start by creating VIPs, and add firewall plumbing to the V=
IPs in the future.<br>
</div><div><br></div><div>My config:</div><div>CentOS-6.3 based distro +=A0=
</div><div>corosync-1.4.1-1</div><div>pacemaker-1.1.8-1</div><div>pcs-0.9.2=
6-1</div><div>resource-agents-3.9.2-12<br></div><div>and all required depen=
dencies</div>
<div><br></div><div>My questions:</div><div><br></div><div>This sounds like=
 a common use case, but I could not find an example/HOWTO. =A0Did I miss it=
?</div><div><br></div><div>Do I have the correct HA cluster packages, versi=
ons to start work?</div>
<div>Do I also need the cman?, ccs packages?</div><div><br></div><div>How m=
any interfaces should each cluster node have?</div><div>=A0 =A0 2 interface=
s: internal, external</div><div>=A0 =A0 or</div><div>=A0 =A0 3 interfaces: =
internal, external, monitor</div>
<div><br></div><div>Do I need to configure corosync.conf/totem/interface/bi=
ndnetaddr, and if so, bind to what net?</div><div><br></div><div>$1M questi=
on:</div><div>How to configure cluster to monitor all internal, external cl=
uster interfaces, and perform</div>
<div>failover? =A0Here&#39;s my estimate:</div></div><div><br></div><div>* =
create external VIP as IpAddr2 and bind to external interfaces</div><div><d=
iv>* create internal VIP as IpAddr2 and bind to internal interfaces</div>
</div><div>* co-locate both VIPs together</div><div>* specify a location co=
nstraint for preferred node</div><div><br></div><div>Any help would be appr=
eciated,</div><div>thanks</div><div>Jeff</div><div><br></div></div></div>

--001a113375769d560504e6acb1e8--