Grace Periods Warning

Hello! 

Vers:7.2.48.1.17992.RELEASE (VMware) - Downloaded -1 month ago

and vers. 7.2.49.1.18450.RELEASE(VMware) - Downloaded 3 days ago.

Both have this problem. 

Manual "Update License" - working well, on email I have "Your LoadMaster Serial number  ## has been licensed as Free LoadMaster"

But in "Home"  - pop -up "The call Home grace period is going to end in XX days. To avoid to be blocked, please provide an internet connection"

Also I have  Vers:7.2.45.2.17112.RELEASE (VMware) -Downloaded 1 year ago - NO PROBLEM.

How fix "grace period" bug?

Hi Gianluca Furnarotto

I see your device called home this morning actually.  Can you try and open up a private browser and/or clear your cache, see if there is still an issue?

Everyone please make sure that as of our 7.2.53 release, everything goes to 'licensing.kemp.ax', which resolve too 52.166.52.190.  If you downloaded recently you are on .54 and will be using this FQDN/IP.

I checked a lot of your SNs and call home data the past week, and I see a few days missing but overall it does connect eventually.

Trying to re-license will not affect that error message.  Call home will happen at a random point during the day, if it fails, it will try again the next day.

There are a lot of factors which it could fail within a home network. 

Let me check on a few things and get back to this thread in a day or two for possible troubleshooting steps.

With that being said though, we could use a little more transparency in either the logs or the message as to why it failed or maybe even if it fails on the day, it can try again that day.  I will see if I can get PM/dev to add something in for a future release.

The call home feature is a way to see what our customers are using the product for.  If we put in a new feature, like Kubernetes, we want to see how many are using it.  That is just one example.  More information from the link below.

https://kemptechnologies.com/about-us/policies/call-home/

When a license is updated, it will tell you to reboot.  This is a way to make sure if you ever went from a standard subscription device to something like our Enterprise+ subscription, that the features would be there.

Looks to be broken again for me as of this morning. Will raise a ticket Monday if it persists.

Hi,

Can you try to manually update the license on this VLM;
1) Access LoadMaster Web Interface
2) Navigate to System Configuration>System Administration>Update License
3) Enter your KEMP ID and Password
4) Press Update License

Hi, i have tryed but nothing change.
From SSH - Utilities - Diagnostic - Ping Host i have tryed to ping 8.8.8.8 but it not ping 8.8.8.8.
I have checked the gateway and it is correct.
From other internal VLAN i have ping the ip of Kemp and it respond (to test the use of gateway).
Any idea?
Thanks

Hi,

For connecting to the licensing server you will need to allow connection on port 443 on your firewall/gateway.

Hi all,
Does anyone else have this problem?

Last weekend I have installed my third Free LoadMaster as the old ones always stopped working after 30 days. The initial activation works like a charm, but the day after, the "The Call Home grace period is going to end in XX days. To avoid to be blocked, please provide an internet connection" messages started to appear.

When accessing the Update License page it tells me "To update the license your LoadMaster must be connected to the Internet".

Ping tests from SSH console are successful, DNS resolution is working.
HTTP and HTTPS are allowed from the network containing the LoadMaster.
Firewall log does not contain any blocked connections from LoadMaster IP.

Any ideas?

Yes I have the same problem. I am now considering removing Kemp from my Lab; looking for an alternative load balancer that will not expire in the middle of a Demo to Management.

Same Here !

Hi All,

So that I understand completely what is happening here. The Free LoadMaster does not update its license even if you have HTTPS access to alsi.kemptechnologies.com from the Free LoadMaster? As a result the original license expires?

Hi Derek,
yes exactly. Internet connectivity is working fine, but the license is expiring.

But maybe the issue is fixed in 7.1-28.
I have deployed the new version a few days ago and imported my old config. By now the warning did not occur again!

We are investigating this internally. Will keep you posted.

I have the same issue

Is there any solution?  I have the same problem. im using 7.1.26 vmware

I don't know if I just was lucky or if the problem is solved in the new firmware, but in 7.1-28 (for Hyper-V) it did not happen again.

I've got the same problem with Vers:7.1-26-15(VMware).

Changed to 7.1.-28b  VMWare since yesterday. No license warning until now.  Think it's fixed.

Has anybody had this issue with 7.1-28b?

No licence warnings since I moved on the 19 okt. to version 7.1-28b.  (VMWare).

Hi all,

we had the same issue here. We figured out, that the vmware OVF Archive is version 7.1-26-15 and the vmware VMDK archive is version 7.1-30-75.

Maybe it is possible to update the OVF archive to the same version as VMDK archive.

Or is there a reason for this version differences?

No, there is no specific reason for the version differences. Any downloadable version can be set to free mode, but be aware that the maximum throughput is restricted to 20mbps.

Hi,

same problem with version 7.1-26-15.

New version 7.2.47.0.17592 worked fine.

Thanks

Andreas

Hi,

I would like to say I also have this same problem.  I am currently using 7.2.48.0.17891.RELEASE (VMware)

As others have said I have just gone to the Update License section where a red banner says it cannot connect to the Licensing server.  On that page I have managed to enter my credentials and update the license.  I have rebooted the appliance and yet it still says 6 days left on the grace period.

We are using a number of Kemp appliances with no problems at all, just with the Free version.

Please Kemp can you help?

Hi Nick,

I hadn't thought about DNS.  Good shout.  I checked and I was using a local Name server on my test domain that wouldn't have been able to resolve external entries.

I have added the alsi.kemptechnologies.com - 52.136.251.129 as it only allowed for one entry and rebooted the appliance however I still get a grace warning message.  I can see on our firewall that the traffic has gone out to the above and has not been blocked.

Would you suggest trying the latest build?

Hi @matthew.ridley,

Are you still getting the error?  Also when did you make the change?  Because I do see data for the 19th, but not for any days before that.  So it would APPEAR that the host file entry worked.  I actually think it called home about 30 minutes after you posted this based off of timestamps.  Can you check again please?

Hi Nick,

Yes it does appear to be working ok now thank you.  It looks like it was a timing issue after me making the changes.

Thank you for all your help.

We are experiencing the same issue with Vers:7.2.49.1.18450.RELEASE (VMware).

I logged in this morning to see the grace paeriod warning, Idid dome internal checks and did see that our firewall was blocking DNS requests. We have fixed these issues now and cleared the DNS cache on the Keml LB, the appliance is now resolving the alsi.kemptechnologies.com addesses and I can see this on our firewall logs.

Multiple reboots of the Kemp, re-applied the license credentials but the notification warning persists.

Can you help?