Getting Started with BIG-IP Next: Licensing Instances in Central Manager

This article assumes that the license was not applied during the initial instance setup and covers only the GUI process. For the API process or for disconnected mode, please reference the instruction...
Updated Jul 24, 2024
Version 2.0
application delivery
big-ip next
central manager
whisperer's avatar
whisperer
Icon for MVP rankMVP

The licensing process is very opaque. Even with outbound access, and a working default route, I am still unable to license an F5 NEXT instance.

LICENSING-0011: InvalidToken: TokenExpiredOrInvalid

Are there any troubleshooting steps? Logs we can review?

whisperer's avatar
whisperer
Icon for MVP rankMVP
Jul 24, 2024

Ok, so found there is a licensing k8s container running... 

tail -f /var/log/containers/*-llm-*.log

Removing a lot of timestamp gibberish, here is what I get...

Start: verify token...
token verification successful !, returning 200
Start: saving token...
Certificates not available, using token for further processing
failed, err: Post "https://product.apis.f5.com/ee/v1/certificates": dial tcp: lookup product.apis.f5.com on 100.75.0.10:53: server misbehaving, retry count: 1
failed, err: Post "https://product.apis.f5.com/ee/v1/certificates": dial tcp: lookup product.apis.f5.com on 100.75.0.10:53: server misbehaving, retry count: 2
failed, err: Post "https://product.apis.f5.com/ee/v1/certificates": dial tcp: lookup product.apis.f5.com on 100.75.0.10:53: server misbehaving, retry count: 3

Resolves just fine....

root@nextcm:/var/log/containers# ping product.apis.f5.com
PING rgwe1rt100-0-routers.dn.apigee.net (35.199.173.84) 56(84) bytes of data.

Definitely think the article could benefit from some troubleshooting info. CANNOT find this anywhere within any KB :/ I may be blind though.

  • JRahm's avatar
    JRahm
    Icon for Admin rankAdmin
    Jul 25, 2024

    asking internally for additional info. Will keep you posted.