This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
ABOUT CHECKMATES & FAQ
Create a Post
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Are you a member of CheckMates?

×
Sign in with your Check Point UserCenter/PartnerMap account to access more great content and get a chance to win some Apple AirPods! If you don't have an account, create one now for free!
Razotevs
Participant
‎2022-02-15 10:45 AM
Jump to solution

Azure cloudguard VMSS health probes on 8117 and __monitor__restrictive policy

Hello,

I am hitting the following problem with R81.10 management and R81.10 VMSS on Azure. Applying "__Monitor__RestrictivePolicy" out of nowhere.

Cme.log shows "API call failed:set package. Message:: requested object not found" but pushing manually the very same policy is working every time. 

On top of that the image of the security gateways is missing "cloud_balancer_port=8117" in fwkern.conf and newly provisioned instances are not returning the health probes, respectively azure load balancer is not sending traffic because thinks they are unhealthy. Adding it manually works for the minimum count of the VMSS but is not scalable automatic solution.

Autoprov_cfg show all seems correct with the right policy and vSec controller is working fine. API status is ready, CME test is passing as also.

Any idea how to proceed? I've opened SR with Checkpoint TAC, but it's been 10 days and no development.

Thanks

0 Kudos
8 Replies
This widget could not be displayed.

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

View All ≫
UPCOMING CLOUDMATES EVENTS
    Sort by:
    All CloudMates Events