Upon first time setup and configuration I was able to activate the license and get the system up and running.

In the last week we've noticed on the server that the prompt on the CLI interface is once again listing itself as UNLICENSED:User and that we can no longer get a response by pinging our EM1 interface. In our testing and troubleshooting around this issue we've confirmed that:

1.) auto-activation is enabled - this has not made a difference in terms of actually being activated.

2.) Manually activating does not make a difference on the system.

3.) In bash, we are able to ping activate.f5.com and api.f5.com - and ping 8.8.8.8 and other public dns servers.

4.) Creating a new account - therefore obtaining a new phone-home user, regkey, and subsequent license - and attempting to update the instance with these new details has not produced a solution.

5.) We have started from square one, setting "no license", no regkey, and no phone-home in CLI, writing the changes, and then resetting these values using the new details in step 4.

6.) Show licensing detailed produces the following output:

State: License is expired. Bundle upload has not occurred. Status: inactive Inactive reason: License is expired. Bundle upload has not occurred. Expiration: 02/11/2016 14:18:57 Username: n/a Version: 5b UUID: 422E12CE-68CC-B4B0-D90A-262BF0679E50 HTTP Requests Per Min: 180 TCP Connections Per Min: 120 Mb Per Sec: 5 Burst Duration (min): 1 Processes: 1 Phone Home: on Product Mode: Precision Load Balancer

Any ideas or suggestions on what we can do to ensure that our Linerate instance can be activated? Is this activation issue related to the connectivity problems on our em1 interface?

Thanks.

Forum Discussion

LineRate: License is expired - no auto renewal

SSO Login Update Coming to DevCentral

Kevin - June 2026 Featured F5er

Tyler - May 2026 Featured Member