- CheckMates
- :
- Products
- :
- Quantum
- :
- Management
- :
- Re: Secondary SMS Certificate expired error
- 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
Secondary SMS Certificate expired error
Hi Team,
We have deployed two Check Point Smart Management Servers (SMS) and their synchronization appears successful. However, when attempting to log in to the secondary SMS, we encounter a certificate expiration error.
Could you please advise on the cause of this issue and the recommended steps for resolving the certificate expiration on the secondary SMS server?
FYI: The error screenshot is attached here.
Thanks,
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Known issue that happens every time we set up Management HA for the CCSE labs on R81.20 GA. Simply execute cprestart or reboot the Secondary and the problem will go away. This was an issue in prior code releases too, not sure why this can't ever seem to be fixed.
March 27th with sessions for both the EMEA and Americas time zones
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When you are login to Primary, will you get the similar error?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nop The primary is working Ok.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Known issue that happens every time we set up Management HA for the CCSE labs on R81.20 GA. Simply execute cprestart or reboot the Secondary and the problem will go away. This was an issue in prior code releases too, not sure why this can't ever seem to be fixed.
March 27th with sessions for both the EMEA and Americas time zones
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Timothy_Hall is 100% right. I had this happen in the lab 3 times and either cprestart or reboot fixes it, easy peasy.
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Interesting, I had setup few times with Mgmt HA but so far never encountered any of this error message.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What version was it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
mostly R81.10.
Done with R80.10 as well but never encountered such.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I will try replicate it in R81.10
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It seems to be some kind of timing/race condition that depends on the performance of the secondary. In a VMWare environment my CCSE attendees run into it every single time.
March 27th with sessions for both the EMEA and Americas time zones
