Known Issues

When installing a different version of Sentinel LDK Run-time Environment (RTE) over an existing version on a Linux platform, the newly-installed hasplmd daemon is typically started automatically. However, in the following instances, the hasplmd daemon is not started automatically:

> When upgrading RTE version 8.13 or earlier to RTE version 8.15 or later

OR

>When downgrading RTE version 8.15 or later to RTE version 8.13 or earlier

Workaround: After installing the desired version of the RTE, do either of the following:

>Install the desired version of the RTE a second time.  After performing the second install, the hasplmd daemon starts automatically.

OR

>Start the hasplmd daemon manually by entering the command: systemctl start hasplmd

Given the following situation:

> When the current state of an SL key is decoded (using SL License Generation API), the status of the container is shown as Secure Storage Id Mismatch in the Key ID column.

> The key contains a Product that is rehostable or detachable OR the Product license type is Executions or Expiration Date.

If the SSID (secure storage ID) of the container changes (for example, the container becomes corrupted or is deleted), the Product will be marked as Cloned and become unusable. In any other situation, the status Secure Storage Id Mismatch has no significance and can be ignored.