Firewall-1

[FW-1] ClusterXL: - why have multiple synchronisation interfaces?

Subject: [FW-1] ClusterXL: - why have multiple synchronisation interfaces?
From: Dave Aitchison <Dave AT CANBERRADJ DOT COM>
To: FW-1-MAILINGLIST AT AMADEUS.US.CHECKPOINT DOT COM
Date: Mon, 22 Dec 2003 19:15:36 +1100
Hi all,

While testing a Firewall-1 load-balanced cluster today, I played briefly
with a secondary synchronisation network to see what the benefits might
be.  I assumed that having a second network would allow for a failure on
one.  This would be handy in the event that a switch fails.  I've since
discovered that if one synchronisation interface on a module fails, that
module falls out of the cluster.

I've since scoured the ClusterXL documentation, Checkpoint's knowledge
base, and the archives from this mailing list, and I can't find any
reason for having a secondary synchronisation network.  Can anyone give
me an explanation as to why I might do this?  I'm sure there is some
benefit, but I'm having trouble finding it...

Thanks,

David Aitchison.

=================================================
To set vacation, Out-Of-Office, or away messages,
send an email to LISTSERV AT amadeus.us.checkpoint DOT com
in the BODY of the email add:
set fw-1-mailinglist nomail
=================================================
To unsubscribe from this mailing list,
please see the instructions at
http://www.checkpoint.com/services/mailing.html
=================================================
If you have any questions on how to change your
subscription options, email
fw-1-owner AT ts.checkpoint DOT com
=================================================

<Prev in Thread] Current Thread [Next in Thread>
  • [FW-1] ClusterXL: - why have multiple synchronisation interfaces?, Dave Aitchison <=