Hello,
we deployed a new CP 6700 Cluster in HA Mode as have done it a couple of times without any problem like that.
Now we faced the the exact same issue as the User in this CheckMates Post:
https://community.checkpoint.com/t5/Security-Gateways/Virtual-Standby-member-cannot-reach-internal-D...
I used the workaround with the fwkern.conf command "fwha_cluster_hide_active_only = 0" to fix the issue for this cluster.
I would like to explain to my colleagues why this fwkern.conf command is required for this new cluster. We run many HA Clusters and all of them run R80.40 Take 91 without the need for this fwkern.conf command.
Can somebody explain me, why we need this hotfix and how can we change our setup to remove the need the need of this fwkern.conf command. I also would be interested why this problems only occured on this cluster.
Edit: We also noticed hard "laag" with the commands in expert mode: "arp -a" and "tcpdump" the output needed about 1~ Minute to display the results. This issue was also resolved with the fwkern.conf command.
Best regards
