View source for License Management
From T-VEC Wiki
==Introduction== Access to the T-VEC Toolset is controlled by a license management scheme supported by flexlm. A valid, encrypted license key must be installed for the software to operate. The toolset supports license management in node-locked and floating configurations. In node-locked licensing each machine running the toolset requires a machine-specific key. In a floating configuration, a set of licenses is shared by multiple computers on a network. Floating licenses require the installation of a license manager to control license usage on the network. By default the toolset is installed to operate in a node-locked configuration. To prepare the toolset for operation, a license key must be obtained from T-VEC. To setup a floating license configuration, the license manager software must be installed on a machine designated as the license server, and a set of floating licenses must be obtained for that specific machine. ==License Management== Access to the T-VEC toolset is controlled by license management. A valid license key is required to operate the tools. T-VEC generates and distributes encrypted license keys based on the number of licenses purchased. Licenses can be managed as node-locked or as floating. Node-locked licenses are generated for and used by specific machines, while floating licenses are shared among a group of networked machines. Floating licenses are more flexible as they allow licenses to be shared by multiple users. For example, two licenses may be used to support 5 developers as long as only 2 developers require access to the tools concurrently. ===License Registration=== License keys are distributed by T-VEC support. To obtain licenses, contact Support with the target machine’s identification information. In a node-locked setup, submit the machine identifier for the workstation that will be running the tools. In a floating setup, a license manager controls the license keys. Submit the machine identifier of the machine that runs the license management software. ===Machine Identification=== In order to uniquely identify a machine, the T-VEC license management scheme uses the machine’s ethernet address and hard disk serial number. Thus, machines must be equipped with an ethernet card or adapter in order to execute the tools and/or operate as a license server. This is true regardless of whether license management is setup as nodelocked or floating. Open a command window (DOS window) and execute the command ipconfig /all You should see something like: <table> <pre> Windows IP Configuration Host Name . . . . . . . . . . . . : computer_name Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : Yes DNS Suffix Search List. . . . . . : abc.efg.net Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : abc.efg.net Description . . . . . . . . . . . : Network Connection Physical Address. . . . . . . . . : 00-11-22-AB-DC-33 Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 100.100.100.1 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 100.100.100.2 DHCP Server . . . . . . . . . . . : 100.100.100.2 DNS Servers . . . . . . . . . . . : 100.100.100.2 </pre> </table> The important information is the Physical Address (e.g. 00-11-22-AB-DC-33) ==Problems or Issues== ===Firewalls=== License server issues may require specific ports to be opened when firewalls are in place. Port 27000 is the primary port, but it may be necessary to open ports 27000 and 27007. ===Reference Material=== System administrators may be familiar with the Flexlm license management system, but support information can be found [http://www.macrovision.com/pdfs/flexnet_licensing_end_user_guide.pdf Flexlm User Guide] or at the [[http://www.macrovision.com/support/by_category/Software_Licensing.shtml Flexlm Support Website]
Retrieved from "
What links here
About T-VEC Wiki