Forum Discussion
COMMS-CORE_1795
Nimbostratus
Jan 28, 2016BIG-IQ: how to license a LTM VE device
Hi,
I've set up a License Pool (F5-BIG-VEP1-25M25V13) on my BIG-IQ 4.6 (Centralized Management), to provide LTM licensing to my new machines, which I'm deploying on vCloud.
So, what I'm do...
Customer_Kyle_2
Nimbostratus
Jan 28, 2016What version of BIG-IP are you trying to license? What error messages are shown in the restjavad log of the BIG-IQ and the BIG-IP?
Is the rest framework up to date between the BIG-IQ and the BIG-IP?
COMMS-CORE_1795
Nimbostratus
Jan 28, 2016LTM versión 11.6.0. This is the error:
[WARNING][2019][28 Jan 2016 17:46:26 UTC][RegKeyUpdater][checkedCompleted] Device 10.36.209.17 didn't have a registration key.
[I][2061][28 Jan 2016 17:46:46 UTC][8100/cm/autodeploy/jobs JobsWorker][onPatchCompleted] Job 1afd4c70-dd66-473e-bb2d-ae11a47f313d started by user admin
[I][2063][28 Jan 2016 17:46:46 UTC][LicenseTask][licenseDeviceFromGenericPool] Installing pool license grant to device '/mgmt/shared/resolver/device-groups/cm-autodeploy-group-manager-autodeployment/devices/0ae7e9b2-ef50-4e09-9e00-b34e11636dc5' using 'http://localhost:8100/cm/shared/licensing/pools/b876a3b7-1d6d-43a1-bee2-3b2575be6578/members'
[WARNING][2069][28 Jan 2016 17:46:46 UTC][8100/cm/shared/licensing/pool-activation PoolLicenseActivationWorker][patchFailed] java.lang.IllegalArgumentException: Unparseable license format
at com.f5.rest.workers.em.license.PoolLicenseUtils.makeLicenseBlob(PoolLicenseUtils.java:189)
at com.f5.rest.workers.em.license.PoolLicenseUtils.createDeviceLicense(PoolLicenseUtils.java:129)
at com.f5.rest.workers.em.license.PoolLicenseActivationWorker$7.completed(PoolLicenseActivationWorker.java:311)
at com.f5.rest.workers.em.license.PoolLicenseActivationWorker$7.completed(PoolLicenseActivationWorker.java:300)
at com.f5.rest.common.RestOperation.complete(RestOperation.java:1808)
at com.f5.rest.common.ApacheAsyncRequestSender.handleRequestCompleted(ApacheAsyncRequestSender.java:147)
at com.f5.rest.common.ApacheAsyncRequestSender$1.completed(ApacheAsyncRequestSender.java:91)
at com.f5.rest.common.ApacheAsyncRequestSender$1.completed(ApacheAsyncRequestSender.java:87)
at org.apache.http.concurrent.BasicFuture.completed(BasicFuture.java:119)
at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.responseCompleted(DefaultClientExchangeHandlerImpl.java:177)
at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.processResponse(HttpAsyncRequestExecutor.java:412)
at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.inputReady(HttpAsyncRequestExecutor.java:305)
at org.apache.http.impl.nio.client.InternalRequestExecutor.inputReady(InternalRequestExecutor.java:83)
at org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:267)
at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:81)
at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:39)
at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:123)
at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:164)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:339)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:317)
at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:278)
at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106)
at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:590)
at java.lang.Thread.run(Thread.java:745)
When I discover the LTM device, I check the "update framework" item, so I guess it's up to date.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects