Arctera License Management Service Help
- Introduction
- Pre-installation
- Installing and configuring
- About installing License Management Service
- Verifying License Management Service installation on Linux
- Verify License Management Service installation on Windows
- About configuring License Management Service on Linux and Windows
- Installing License Management Service along with Arctera InfoScale Operations Manager 8.0.2
- Installing License Management Service along with Operations Manager in a high availability environment
- Getting started
- About LAS access
- Registering the License Management Service product key
- About License Management Service console
- About the Setup panel
- About the License Management Service dashboard
- Updating the License meter file
- Updating the Entitlements file
- About managing hosts
- Adding Kubernetes clusters
- Adding Lightweight Directory Access Protocol or Active Directory-based authentication in License Management Service
- Adding a user group
- Adding local users
- Configuring SMTP settings for email notifications
- Managing License Management Service site details
- Changing the password
- About using reports
- Managing faults
- Viewing the activity monitor
- Registering
- Managing license usage
- About license usage
- Scheduling auto update for License meter file
- About assigning entitlements
- Scheduling auto update for entitlements file
- Assigning entitlements to hosts
- Reassigning entitlements to hosts
- Unassigning host from an entitlement ID
- Unmanaging a host
- Managing hosts
- Assigning entitlements to Kubernetes nodes
- Reassigning entitlements to Kubernetes nodes
- Unassigning Kubernetes node from an entitlement ID
- Viewing the License cores usage data
- Managing hosts
- Managing software upgrades
- Managing user administration
- Managing backup, restore, and uninstall
- Known issues
About assigning entitlements
Using the License Management Service console you can assign entitlements to hosts and Kubernetes worker nodes that have the Arctera InfoScale product suite installed. You can select a single on-premises or cloud host or a Kubernetes node to assign entitlements or you can choose multiple by using filters and proceed with the task.
While assigning entitlements to hosts or nodes, you need to ensure that certain parameters are taken into consideration. Refer to the table to understand the various combinations that are permitted while assigning entitlements.
Table: New -- Entitlement, product, and platform combinations
Platform type / Location | Entitlement product bundle | Host product bundle |
|---|---|---|
On-premises | InfoScale Enterprise | InfoScale Enterprise InfoScale Availability* InfoScale Storage* |
InfoScale Availability | InfoScale Availability | |
InfoScale Storage | InfoScale Storage | |
InfoScale Foundation | InfoScale Foundation | |
Cloud | InfoScale Enterprise Alta Enterprise | InfoScale Enterprise InfoScale Availability* InfoScale Storage* |
InfoScale Availability Alta Application Resiliency | InfoScale Availability | |
InfoScale Storage Alta Storage | InfoScale Storage | |
InfoScale Enterprise for Kubernetes InfoScale Enterprise for Kubernetes Cloud | InfoScale Enterprise for Kubernetes | |
InfoScale Storage for Kubernetes InfoScale Storage for Kubernetes Cloud | InfoScale Storage for Kubernetes |
[*] A lower-level product bundle can be assigned to a higher-level product bundle, but this is not recommended.
Hosts that are deployed within the cloud should be mapped to cloud entitlements. Depending on the purchase date the entitlement product bundle names can vary.
In addition to the above product and entitlement product bundle mapping, you need to also consider the following criteria:
All selected hosts must have a similar platform type.
All selected hosts must have similar entitlement status such as unassigned or partially expired.
When mapping host to entitlements there may be two types of licenses for each, perpetual and subscription.
Hosts assigned to an entitlement can be easily moved to another entitlement.
Best practice is to match the entitlement product bundle with a similar bundle that is installed on the host (on-premises or cloud).
The following are some examples which explain how the mapping works:
Example 1: An on-premises host has the InfoScale Availability product installed. You have entitlements belonging to InfoScale Enterprise, Availability, and Foundation. Now while assigning entitlements to this particular host, you can choose entitlements from InfoScale Enterprise and Availability only. If you choose entitlements from InfoScale Foundation, then an error message is displayed.
Example 2: For cloud hosts having InfoScale products, the mapping is similar to on-premises hosts. Cloud hosts having InfoScale products should be mapped to Alta or InfoScale for Cloud entitlements.
More Information