- CheckMates
- :
- Products
- :
- General Topics
- :
- License warning massage
- 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
License warning massage
Hi all,
We are facing a problem with our licenses.
The infrastructure consists of a Cluster with two members(FW1 and FW2).
Three VSXs are hooked to each member.
On each VSX (Active and Standby) the license expiration date is correct (2025).
On FW2 the date is correct (2025). While for FW1 it still shows me the old date (31/03/2024).
I ran a cplic print on FW1 and FW2 and on both the date is correct.
I only see the warning on smartconsole.
Is this a cosmetic iussue?
At expiration 31/03/2024 does the date automatically update to 2025?
Thanks for the support.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you send a screenshot? Also, if its central license, make sure fw1 is tied to it from smart update.
Best,
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Andy,
Which screen do you need ?
From the smartupdate I checked and there are several licenses under FW1 , I visualized the contracts and they all expire 2025.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Your best bet is to call in and speak with Account services, they can check, I dont believe they are open on the weekend, but you could always open regular TAC case and if they confirm for sure its not technical issue, they can transfer the case over to License folks.
Best,
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Also, I tried to download the license for FW1 from user center , but when I try to import it to smartupdate it tells me that the license is already there.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Maybe reboot of mgmt will solve it.
Also from Smartupdate you can fetch the license from gateway. Then it will pull the key from the fw
If you like this post please give a thumbs up(kudo)! 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good point, rebooting the mgmt server can be done any time and may help, for sure.
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This fixed for me
https://support.checkpoint.com/results/sk/sk176211
in addition, try this too
https://support.checkpoint.com/results/sk/sk163500
Both sk are similar lol
Please be sure no VS are active on the affected node during sk implementation
