- CheckMates
- :
- Products
- :
- CloudMates Products
- :
- Cloud Network Security
- :
- Discussion
- :
- Re: Checkpoint CloudGuard HA clustering VIP issue ...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Checkpoint CloudGuard HA clustering VIP issue in OCI
helo Peeps,
Need some direction and troubleshooting guidance on Cloudguard HA clustering in OCI. we have deployed 2 cloudguard instances in same OCI region in HA cluster. the configs are fine which i got checked from TAC as well as they are are assisting me in this issue. the problem arises when we do the failover to secondary instance and the virtaul IPs dont move to secondary firewall. When primary is active , everything works fine both N-S and E-W traffic. in cloudguard we have to assign secondary IPs to both trust and untrust Vnics of the primary firewall.
Just wondering if anybody else has experienced this same issue in OCI , Azure or AWS ? we have followed the recommended architecture from official checkpoint documents to configure this solution. we have done dynamic grouping for IAM policies as well and went through some Sk articles as well which TAC shared to implment but no luck so far.
Any leads would be highly appreciated. I also have TAC case opened for this.
Regards,
Akshay
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What images are you using?
Seems like some sort of permissions issue on the credentials assigned to the instance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
i am using R81.20 with latest hotfix take 26.
What sort of permissions do you think causing this issue? We created dynamic group and assigned highest level of IAM policy as per documentation for the cluster. Thats all they mentioned. is there something else which we are not aware of?
below is the link:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are the VPC's and instances located in the same compartment ?
also check logs under $FWDIR/log/oracle_had.elg to see the root cause.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Were you able to get this working? Happy to help offline if need be.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
hey Jeff,
thank for reaching out. not yet. we are stuck still at same issue. Happy to have a call or discussion if you are available.
Regards,
Akshay
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Akshay,
Feel free to send me an email at jengel@checkpoint.com
In the meantime, one thing to check real quick is please ensure both cluster members NTP is configured and time is in sync. API calls will not work if system time is not within 5 minutes of actual.
Best Regards!
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are the VPC's and instances located in the same compartment ?
also check logs under $FWDIR/log/oracle_had.elg to see the root cause.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
hi Nir,
We ran this and found out below in the logs. We dont what the last error means
2023-09-21 14:48:46,814 OCI-CP-HA INFO Traceback (most recent call last):
File "/etc/fw/scripts/oracle_had.py", line 258, in main
reconf()
File "/etc/fw/scripts/oracle_had.py", line 72, in reconf
oci_client = oci.OCI()
File "/opt/CPsuite-R81.20/fw1/scripts/oci.py", line 292, in __init__
identity = metadata('identity/')
File "/opt/CPsuite-R81.20/fw1/scripts/oci.py", line 122, in metadata
resp.reason, data)
TypeError: __init__() missing 1 required positional argument: 'body'
does this ring any bell?
regards,