| CPUG | |
| The Check Point User Group | |
| A Resource For The Check Point Community. Fast. Useful. Independent. | |
|
| |||||||
![]() |
| | LinkBack | Thread Tools | Display Modes |
| |||
| I'm sure I'm not alone here. With the recent announcement from EMC Rainfinity that they are no longer selling the RainWall product, we're looking to move from RainWall to clusterXL. Does anybody have experience doing this? Obviously, we want to limit the downtime, but having no experience with ClusterXL, we're a bit over our heads on how to best approach the problem. We currently have a cluster consisting of 2 firewalls running NG (R55) and rainwall. The addressing scheme is such that there are 2 VIP's on each interface (handled by rainwall). For instance, an interface on the 10.10.10.0/24 subnet would use the following schema: 10.10.10.1 - FW1 Physical Interface 10.10.10.2 - FW2 Physical Interface 10.10.10.3 - VIP #1 10.10.10.4 - VIP #2 The use of two vip's was supposed to provide a type of manual load balancing, but whatever the case, they're there, and some hosts use .3 while others use .4 as their gateway. How do I keep the vips alive during the process of uninstalling rainwall and activating ClusterXL? Anybody know what the process should be? CheckPoint support has been less than helpful on this. |
![]() |
| Thread Tools | |
| Display Modes | |
| |