I'm not sure if anyone have seen this, but building AWS vSEC cluster today, I am seeing this:
Nope, it was not defined manually.
Additionally, when failing over from active to standby members, secondary IPs are no longer moving to the new active member:
5 minutes later:
It may be a coincident, but the Check Point SE working on one of my previous cases (Inconsistent behavior of vSEC in AWS ) was able to repeatedly reproduce the issue last week. but can no longer do so today.
If someone can get an update from CP about any changes that may have transpired in the past week, please let me know.
Thu 05 Oct 2023 @ 09:30 AM (IDT)Simplifying & securing your hybrid WAN with Azure Virtual WAN & Check Point