Local License Manager¶
A10’s provided the GLM system and ELM system that users can deploy and in their environment as offline license manager and note that Harmony Controller will act as Local License Manager (LLM) in this case.
Users will have to export license from GLM and manually import to Harmony Controller which will act as license manager and from that point Harmony Controller will manage licenses for all devices registered with Harmony Controller.
Harmony Controller initiates the flow and pushes the license to the device. When you register the device, Harmony Controller pushes the license to the device. In case of the device license, Harmony Controller initiates the flow at the registration time or separately after the registration if user wants to manage the license for the device and Harmony Controller will initiate the flow, and pushes the profile and then triggers the device for the licensing request for LLM. In case of Harmony Controller license it would purely be Harmony Controller initiated flow and Harmony Controller takes care of the operation and in case of the device license it is both Harmony Controller and device has a role to play.
An overall workflow is setting up Harmony Controller as LLM and listing of licenses. When the user uses Harmony Controller as LLM for the first time and the user tries to login the user need to go through the set-up or activate it. They can import the licenses and they will be able to see the listing of licenses they have imported in Harmony Controller as license manager.
When user has a license in LLM, provider admin assessing the license to a device is called as activating the device or creating an activation. Revoking activations in a device which is licensed in LLM or removing the license from the device and unrevoking licenses.
In a multi provider view when Harmony Controller starts to act as LLM and primarily user scope is super-admin, particularly the LLM which is using Harmony Controller as a LLM. As LLM within Harmony Controller, the super-admin will be able to activate the service and import the license and perform license life cycle management. Adding a license using the license token and assign their license to their devices which they are managing as their infrastructure and monitor usage of those licenses. This shows the segmentation or distinction the functionality that is used as LLM means and functionality associated with LLM versus providers license management within Harmony Controller. In this case there is no direct connection between GLM and Harmony Controller. Once user has license issued to user in A10 GLM service you will have to use the ELM activation key essentially activating ELM and then exporting your license and manually importing them into Harmony Controller as LLM.
Essentially devices will be licensing themselves from LLM which is running inside the Harmony Controller. The other is license usage which is repeatable at a certain frequency heartbeat communication from device and that communication would be from Harmony Controller.
Harmony Controller is being integrated with GLM Harmony Controller and will be used as LLM and Harmony Controller being the license manager.