When a LoadMaster is successfully activated by Kemp 360 Central, a log message that looks like the following is added to the audit log:

Activating ASL instance 172.16.188.1 with ASL License VLM-MAX. Current activations is 5

The current activation is per license type and not the total number of all active instances. When a LoadMaster is successfully re-licensed by Kemp 360 Central, two log messages that are similar to the ones below are added to the audit log:

ASL Instance 172.16.188.1 license change. Old license was VLM-MAX and current activations is 4

Activating ASL instance 172.16.188.1 with ASL License VLM-5000G. Current activations is 2

Similarly, the current activation is per license type. The first log message refers to old licenses and the next refers to the new license type. When an activation failure is observed on the LoadMaster ASL Activation page, the reason for the failure can be determined by looking at the debug log on Kemp 360 Central as shown below:

Debug Log Message Description
ASL instance limit already reached. Cannot issue more licenses Kemp 360 Central has already activated the maximum number of LoadMasters permitted. To activate another LoadMaster, you must de-activate a currently activated LoadMaster or contact Kemp to obtain a new license that increases the number of LoadMasters that Kemp 360 Central can activate.
ASL License given by lic_type_id <integrer> does not meet the requirements. An internal error occurred; contact customer support.
No message in debug log and also no message of successful activation in audit log. The activation request was refused because Kemp 360 Central is not configured to provide licenses that match the LoadMaster’s platform type.
Cannot verify ASL instance check. Is the request really coming from a LoadMaster? This occurs if Kemp 360 Central is unable to verify whether the request came from a LoadMaster or something else. The LoadMaster sends specific headers in its requests.