Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
yeruel
Explorer
Jump to solution

API status test failed on Secondary Checkpoint Managment server

I encountered a challenge during the installation of the secondary Check Point management server. The primary server installation was successful. However, after completing the first-time wizard on the secondary server, I checked the API status from the CLISH CLI. The API status test failed, even though the CPM has started and is ready. The issue is that the API is stopped.
I am currently troubleshooting the API status failure on the second management server.
Your suggestions and advice are awaited.

Server Smart-1 600M.

OS GAIA R81.20

0 Kudos
1 Solution

Accepted Solutions
PhoneBoy
Admin
Admin

You cannot make changes via the secondary node unless its primary.
Therefore it makes sense the API server might not be running on the secondary until it is made active.
However, I’m not sure what the expected behavior is here.

View solution in original post

0 Kudos
3 Replies
_Val_
Admin
Admin

Did you sync both management servers yet? Did you manually enable API on the secondary?

0 Kudos
PhoneBoy
Admin
Admin

You cannot make changes via the secondary node unless its primary.
Therefore it makes sense the API server might not be running on the secondary until it is made active.
However, I’m not sure what the expected behavior is here.

0 Kudos
yeruel
Explorer

Thanks, solved!

0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events