Cluster with two subnets on single vlan

[Strongiukas]

Hello,

I'm not sure how I should cope with this problem.

Now we have couple of subnets on the same vlan. Lets say 192.168.1.0/24 and 192.168.2.0/24. I need to create Cluster of two members.

I'm thinking of doing next:

1. Create Allias IPs on that interface (GW1:192.168.1.1 GW1:192.168.2.1 and GW2:192.168.1.2 GW2:192.168.2.2) on web console, 

2. Create new interfaces via smart console with network type: Cluster.

3. Create virtual IPs as 192.168.1.254 and 192.168.2.254

4. Add cluster members as GW1:192.168.1.1 GW2:192.168.1.2 and GW1:192.168.2.1 GW2:192.168.2.2

5. Set topology to Internal and disable Anti-Spoofing.

Will it work or I should do something else?

P.S. I know that is bad to have two or more subnets on same vlan, but I need to stay on same logic as it was before.

[the_rock]

I really hope below will be useful.

Andy

https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_ClusterXL_AdminGuide/Content/Topic...

https://community.checkpoint.com/t5/Security-Gateways/ClusterXL-Different-Subnet-Configuration/td-p/...

https://community.checkpoint.com/t5/General-Topics/Configuring-Cluster-Addresses-on-Different-Subnet...

[Chris_Atkinson]

Use of aliases with ClusterXL is not supported per sk89980 / sk31821

[the_rock]

Thanks for pointing that out Chris 👍

[Strongiukas]

Hi, thanks for pointing out. But maybe you have any suggestions then?

It is not possible to separate  those subnet through vlan's, because of lack of managed switches.

Maybe it is possible to move those aliases to different interfaces and then connect everything to one switch?   

[the_rock]

That might be a bit tricky, since sk clearly states its not supported...maybe you can get an official response from TAC about it.

Andy

[PhoneBoy]

Interface aliases are not supported with clustering.
The only other way to do this is with physical interfaces connected to the same switch.
I haven't heard of any issues with doing this, but that doesn't mean there won't be.