Arctera License Management Service Help
- Introduction
- Pre-installation
- Installing and configuring
- About installing License Management Service
- About configuring License Management Service on Linux and Windows
- Getting started
- About LAS access
- Registering the License Management Service product key
- Adding Lightweight Directory Access Protocol or Active Directory-based authentication in License Management Service
- Adding a user group
- About using reports
- Registering
- Managing license usage
- Managing hosts
- Managing software upgrades
- Managing user administration
- Managing backup, restore, and uninstall
- Known issues
Installing License Management Service along with Operations Manager in a high availability environment
You can configure the high availability (HA) feature in InfoScale Operations Manager to improve the availability of the Management Server. In the same HA environment, you can install License Management Service on the same two nodes.
The InfoScale Operations Manager installation with HA feature typically consists of:
InfoScale Operations Manager
Two nodes (Node1 and Node2) in the same datacenter.
Storage Foundation Enterprise version for cluster and storage software or Storage Foundation 8.0 or later versions.
Prerequisites:
Install Operations Manager Patch 8.0.2.540 or higher on both the nodes.
HA configuration must be complete. Refer to the InfoScale Operations Manager documentation for details.
In the event of a failure or a planned maintenance, InfoScale Operations Manager in HA can fail over from Node1 to Node2. Both the nodes are in the same datacenter and are part of the same cluster. When License Management Service is installed and configured on both the nodes, the License Management Service console is also accessible from the active node, with minimum downtime.
To configure License Management Service along with Management Server in a HA environment:
- Configure License Management Service on the active node (Node1) using one of the following:
Virtual host name (VHN) and Virtual IP (VIP)
Local host name and local IP
- Fail over to the other node (Node2). Ensure that it is the active node.
- Configure License Management Service on the other node (Node2) which is now active.
If VHP and VIP are used on Node1, then ensure the same is used on Node2. In case of local host name and local IP the values on both nodes are different.
- Product registration, entitlement, and license meter file updates should be completed separately on each node.
- Local user and local user group configurations must be completed on both the nodes separately.
Configuration of user and user groups that is done on Node 1 is not accessible on Node 2.
Restricted operations:
Any host-related operations such as adding, removing is restricted on both the nodes. Similarly all software upgrade operations are also restricted.
Uninstalling:
Uninstalling License Management Service operation must be done on both the nodes. The process is the same as uninstallation of standalone License Management Service. To uninstall, the node can be active or passive.