Hi Dave ...
Your assumptions are correct, AI allows for a second/backup sync net should
one fail. However, in the event of an interface (any interface) failing
the cluster will failover, you could configure the sync interfaces on each
member as disconnected, thus ClusterXL won't monitor & failover should one
fail ...
To define an interface as "disconnected":
1. Add the name of the interface to the $FWDIR/conf/discntd.if file on each
member
2. Restart ClusterXL (cphastop; cphastart) on each member
Regards ...
Andrew ...
----------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
----------------------------------------------------------------------------------------
|---------+--------------------------->
| | Dave Aitchison |
| | <Dave |
| | @CANBERRADJ.COM>|
| | Sent by: Mailing|
| | list for |
| | discussion of |
| | Firewall-1 |
| | <FW-1-MAILINGLIS|
| | T |
| | |
| | |
| | 06/01/2004 09:05|
| | Please respond |
| | to Mailing list |
| | for discussion |
| | of Firewall-1 |
| | |
|---------+--------------------------->
>---------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: [FW-1] ClusterXL: - why have multiple synchronisation
interfaces? |
>---------------------------------------------------------------------------------------------------------------|
Hi everybody,
I first send this plea for help on Dec 22rd, but got no reply. The
cluster I'm working on is rolling out this weekend, and I'm still hoping
someone out there has an answer to my question, so here goes again...
> 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 [EMAIL PROTECTED]
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
[EMAIL PROTECTED]
=================================================
=================================================
To set vacation, Out-Of-Office, or away messages,
send an email to [EMAIL PROTECTED]
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
[EMAIL PROTECTED]
=================================================
