On May 6, 2015, at 12:48 , Andy A <[email protected]> wrote:
> My question was just around syncing files to the passive node.
> Wouldn't the passive node have different IP address configuration?
> In which case, how would you maintain the interface configuration in pf.conf
> to be different?
What we do most of the time (when possible) is that we configure pacemaker to
add a VIP to the active server.
When the cluster needs to switch to the other node pacemaker can be configured
to delete that ip from the other server and add it to the new active node.
The same logic can apply to any interface, including the registration and
isolation vlan.
If you can’t share an IP between servers you could always rewrite the pf.conf
file after syncronisation using sed or perl for simple cases.
It’s just a text file, so the choice of methods for that is wide open.
Regards,
--
Louis Munro
[email protected] :: www.inverse.ca
+1.514.447.4918 x125 :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
(www.packetfence.org)
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
