The following list outlines the requirements for setting up a license server in a Microsoft Cluster:
- Before configuring Citrix Licensing for Microsoft clustering, you must have a fully-functional active/passive cluster environment. Citrix Licensing does not support active/active clusters.
- To cluster the license server, you must follow the following cluster requirements in addition to any requirements from Microsoft for hardware and clustering in general.
- You must install licensing on the cluster by starting the licensing setup program using a command line.
- When you install Citrix Licensing on a cluster, you must specify the name of the cluster when prompted for the name of the license server during product installation.
- Citrix recommends that you use identical license server hardware for both nodes in the cluster. In particular, Citrix recommends two network adapters on each node and the servers have one drive configured as a shared drive.
- Each node should have two network adapters—one for connection to the public network and the other for the node-to-node private cluster network. Citrix does not support using one network adapter for both connections.
- The public and the private IP address must be on different subnets because the Cluster Service will recognize only one network interface per subnet.
- A name resolution method, such as DNS, WINS, HOSTS, or LMHOSTS, is necessary to resolve the cluster name.
- Both servers that form the cluster must be in the same domain.
- The hostname of both servers must be ALL UPPERCASE.
- Set static IP addresses for the private network connector.
- When you generate a license file at citrix.com, use the name of the license server cluster when prompted for the host name.
- After you download a license file, you must copy it to the F:\Program Files\Citrix\Licensing\MyFiles folder (where F: is the shared drive for the cluster) on the license server and reread it. Alternatively, use the License Administration Console to download, copy, and reread the file.
Important: Citrix recommends setting static IP addresses for all network adapters in the cluster, both private and public. If IP addresses are obtained by Dynamic Host Configuration Protocol (DHCP), access to cluster nodes could become unavailable if the DHCP server goes down. If you must use DHCP for your public network adapter, use long lease periods to assure that the dynamically assigned lease address remains valid even if the DHCP service is temporarily lost or perform a DHCP reservation.