Example of Cluster IP Addresses on Different Subnets

In this example, a one-Security Gateway firewall separating network 172.16.6.0 (Side "A") from network 172.16.4.0 (Side "B") is to be replaced with a ClusterXL. The Cluster Members, however, will use networks 192.168.1.0 for Side "A", 192.168.2.0 for Side "B" and 192.168.3.0 for the synchronization network (all network addresses given in this example are of class "C"). The addresses in italics are the cluster Virtual IP addresses.

In this example, cluster protects two networks, Network A and Network B.

Configuring Static Routes on the Cluster Members

Configure each Cluster Member with these static routes:

• next hop gateway for network 172.16.6.0 is local interface with IP address 192.168.1.x
• next hop gateway for network 172.16.4.0 is local interface with IP address 192.168.2.x

For more on static route configuration, see sk32073.

Configuring Cluster IP Addresses in SmartConsole

1. In SmartConsole, open the cluster object.
2. In the left navigation tree, go to Network Management.
3. Select each cluster interface and click Edit.
4. Configure the settings as follows:

   Interface Properties	Cluster Interface "A" IP address	Cluster Interface "B" IP address
   General section - Virtual IPv4 field	172.16.6.100 / 24	172.16.4.100 / 24
   Member IPs section	192.168.1.1 / 24 192.168.1.2 / 24	192.168.2.1 / 24 192.168.2.2 / 24

5. Click OK.
6. Install the Access Control Policy on this cluster object.