11.07.2015 Views

License Administration Guide - norsar

License Administration Guide - norsar

License Administration Guide - norsar

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 15: Managing Virtualized <strong>License</strong> Servers for File-Based LicensingSetting Up a Virtual <strong>License</strong> Server on Microsoft Hyper-VTask:To bind the license server to the Ethernet address of the physical system1. Identify the virtual machine on which the license server will be run.2. Identify the physical machine--either the Microsoft Hyper-V hypervisor hosting this virtual machine or a remotephysical machine; and download the platform-specific lmhostid utility from the Flexera Software website tothis physical system.Note • If you download lmbind to the Hyper-V hypervisor, see Installing lmbind for Microsoft Hyper-V foradditional details.3. Do either:• If lmbind is installed on the Microsoft Hyper-V hypervisor, log in to the Windows Console OS (COS), andrun the following from the command line of the COS:lmhostid -ptype LMB -ether• If lmbind is installed on a remote physical machine, log on to this physical machine, and enter the samecommand.4. Send the output of this command to the software publisher. The software publisher sends back a licensecertificate in which the license server is bound to the Ethernet address of the host machine.5. Modify the license certificate to configure server parameters (like TCP port number, options file, and otherparameters).6. From where lmbind is installed, enter the following command to launch the binding agent at port 27010:lmbind -port 27010 -l lmbind.log7. On the virtual machine that hosts the license server, configure the environment variable LM_BINDING_AGENT@, where• is the TCP port number at which the binding agent is listening (27010 in the above example)• is the fully qualified host name or IP address of the physical system on which lmbind is running8. Launch the license server on the virtual machine by pointing to the license certificate.Note • If the license server has to be moved to another physical machine, make a re-host request to thesoftware publisher. However, if the license server has to be moved to another virtual machine on the samephysical host, you do not need to contact the software publisher. The license server can simply be run on adifferent instance of the virtual machine hosted on the same physical host, after shutting down the licenseserver running on the first virtual machine.180 FNP-11111-LAG01 <strong>License</strong> <strong>Administration</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!