License Administration Guide - norsar

Chapter 15: Managing Virtualized License Servers for File-Based LicensingAdditional ConsiderationsAdditional ConsiderationsConsider the following when configuring the binding agent:• 3-server redundancy--When using the license server in a 3-server redundant configuration using hostidtypes that require connection to the binding agent, each license server that is part of the quorum must connectto a unique instance of the lmbind process. The hostids for all three servers must use the same platform type(VM_UUID or PHY_*). It is recommended that only PHY_* hostid types be used for a 3-server redundantconfiguration.• CVD support--If you desire a combined vendor daemon (CVD) to support the virtualization hostid types (suchas VM_UUID or PHY_*), both the primary and all the secondary vendor daemons that constitute the CVD musthave the appropriate vendor keys that support virtualization. If only some of the secondary vendor daemonshave the requisite vendor keys that support virtualization, the behavior of the CVD is unpredictable withrespect to the support for virtualization hostid types.• Hypervisor COS use--Running a license server or a FlexEnabled client application on the COS of thehypervisor is not supported. The license server and FlexEnabled client application must run either on aphysical machine or on a virtual machine.Virtualization SupportThe following picture illustrates how the FlexNet licensing server or a FlexEnabled application operates within avirtualization stack. The table below the picture lists the virtualization stacks that FlexNet Publisher supports.License Administration Guide FNP-11111-LAG01 185