Network License

Transcript

Network License Quick Start Setup Guide April 2009 ii |   Autodesk Network License Quick Start Setup Guide © 2009 Autodesk, Inc., All rights reserved. Autodesk, the Autodesk logo, and AutoCAD are trademarks of Autodesk, Inc. registered in the U.S. and other countries. Autodesk, Inc. Under the copyright laws, this manual may not be copied, in whole or in part, without the express written consent of Autodesk. Your rights to the software are governed by the accompanying software license agreement. Worldwide Headquarters Autodesk, Inc. 111 McInnis Parkway San Rafael, CA 94903 USA Autodesk San Francisco The Landmark @ One Market, Suite 200 San Francisco, CA 94105 USA Autodesk, AutoCAD, Autodesk Inventor, DWF, Revit, and 3ds Max are either registered trademarks or trademarks of Autodesk, Inc., in the USA and/or other countries. mental ray is a registered trademark of mental images GbmH & Co. KG licensed for use by Autodesk, Inc. All other brand names, product names, or trademarks belong to their respective holders. Autodesk reserves the right to alter product offerings and specifications at any time without notice, and is not responsible for typographical or graphical errors that may appear in this document. TABLE OF CONTENTS  | iii Table of Contents Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Basic Setup Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Installing the Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Create the Server Directories. . . . . . . . . . . . . . . . . . . . . . . . 3 Create the Debug and License Files. . . . . . . . . . . . . . . . . . . . . 4 Installing the License File. . . . . . . . . . . . . . . . . . . . . . . . . 4 Create the License Option File. . . . . . . . . . . . . . . . . . . . . . . 7 Configure the Service. . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Configure the Windows Firewall. . . . . . . . . . . . . . . . . . . . . . 10 Starting and Stopping the Server Service . . . . . . . . . . . . . . . . . . 11 Verifying the Service Status. . . . . . . . . . . . . . . . . . . . . . . . 12 Verifying the License Status . . . . . . . . . . . . . . . . . . . . . . . . 13 Additional Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . 14 This page intentionally left blank.   | Q uick Start Guide This quick guide is intended to get a network license environment up and running as quickly as possible. It contains instructions to install and configure a complete FLEXnet license server. Overview The following methods and options are examples of a typical installation for a standalone or distributed server. You are encouraged to read the Network Administrators Guide provided with the network license capable Autodesk software. This guide is not intended to be a detailed reference manual nor will it cover the concepts behind network licensing. Side Notes Throughout this text, you will find notes like this one, that gives important details about options and other points of interest. This guide will walk you through setting up the server environment, installing the software, configuring the server options, and installing a network license file. In the end, you should have an operational network license server. Basic Setup Overview Network licensing is composed of three components: the server process which listens for license requests, the vendor process which provides the license for matching products, and the client software which makes the request. Using this document you will ♦♦ Install the server software ♦♦ Configure the server ♦♦ Start and stop the server ♦♦ Verify the server operation Styles, Files, and Code As you read theough this document, you will notice certain words or names are in a different typeface. This designates a file name, menu, or an entry you must make. Filenames: AFile.txt Entries: Your Entry Here Menu Items: Control Panel 1 2 |  Installing the Server 32-bit versus 64-bit Beginning with FLEXnet 2.0, there are two versions of the license server software: 32-bit and 64-bit. These bit depths only affect the bit depth of the application that is run on the server host. It has no bearing on the capability of the license server to deliver licenses to both 32-bit and 64-bit platforms. In general, if you have a 64-bit operating system, install the 64-bit version. If you are running a 32-bit operating system, you must install the 32-bit version. Installing the Server To begin, download the server software from the support portal or locate the server software found on any Autodesk product DVD that supports network licensing. Once located, run the installer from the Tools splash screen or select the appropriate installation package entitled NLM.msi. The Network License Manager (NLM) wizard will open. Follow the prompts to install the server software. This guide assumes you accept the default paths and variables. 2010 Autodesk Network License Manager setup wizard If the Network License Manager is already installed, this dialog will appear Create the Server Directories  | Create the Server Directories Open the directory where you installed the NLM software and create two new directories: License and Logs. The licenses are the files obtained from Autodesk that the server will use to authorize clients. The logs pertain to the error logs and the usage report logs you will configure later on. Directory Permissions Do not confuse the error and report logs with the deployment logs created when the software is installed. The users need no permissions to these directories. They are used exclusively by the server process. 3 4 |  Create the Debug and License Files Create the Debug and License Files Why Extensions Matter The NLM tools use the extensions to filter the files we can select in the tools later on. If we fail to create files with the correct extensions, we won’t be able to select them and complete the configuration later. Before continuing, make sure you can see the extensions of the files you are working on. By default, Windows hides the extension of a file when it already knows the type. If you add the extension ‘.log’ to the name, you will see ‘foo.log’, but in fact, the file may be ‘foo. log.txt’. Make sure you can see the file extensions at all times by choosing Control Panel -> Folder Options, then clicking on the View tab and un-checking ‘Hide extensions for known file types’. Create a Debug file Now that your structure is setup, create a blank debug log file that we will reference later. To do so, open the log folder, right click, and choose ‘New -> Text Document’. Rename the new file to adskdebug.log. About the License File License files are bundles of feature codes (product specific identifiers) that contain information relative to a specific machine. The file sent to you may contain entries for multiple feature codes and machines. These entries must be separated for the system they are intended for or the licenses will not work. Installing the License File If the license file was sent to you in a Word document (DOC) format, you must convert it to text before it can be used. To do so, simply open the Word document, copy the entire text, and paste it into a new Notepad document. Next choose ‘File -> Save As...’ and save the file with a name such as adsk_.lic. For example: adsk_nova.lic Installing the License File  | Now that we have a text version of the file, we need to make sure the file is in the proper format. Usually, when the file is generated for multiple products, the contents are simply appended together; however, this is not a legal format for the server. To prevent problems, we want to remove those redundant elements. Here’s an example of a typical file with redundant and extraneous entries: To be legitimate, there should only be one SERVER, USE_SERVER, and VENDOR entry. Make sure they are defined at the top of the file. If you have a servername: at the top of the file (as shown) either comment it out ‘#’ or remove it. 5 6 |  Create the License Option File Using the previous example, you should end up with a clean license file similar to this: Multiple PLIST entries The only entry that may be duplicated is the PLIST entry; however, only one is required. In general, use the PLIST entry from the most current license provided by Autodesk. The PLIST is updated often and affects all products that support cascading licenses. The license count is always 1. Once your file is cleaned up and converted to text, move it to the License folder created earlier. Create the License Option File  | Create the License Option File The option file contains preference settings for the license server. It can be used to configure every facet of the license server. To use an option file, we must create a file and link it to the license we wish to control. To begin, create a new text document in the License folder and rename the file to ‘adskflex.opt’. Open the option file with Notepad and make the following entries: Many Options The options possible for configuring the server are numerous. Refer to the Server Administrators Guide for a full listing of all possible commands. In short you can control borrow limites, timeout valies, IP ranges, and more. # Timeout options # ======================= # Time out all licenses after 1 hour idle # ======================= TIMEOUTALL 3600 # Report Log # ======================= REPORTLOG +”C:\Program Files\Autodesk Network License Manager\Logs\adskflex.rl” Save the option file, close it, and then open the license file with Notepad. We need to tell the server to use the new option file for the Autodesk vendor’s license daemon configuration. The daemon is configured by the unique vendor code found in each license file. In the license file near the top look for the following line: VENDOR adskflex port=2080 Change this line so that the daemon for autodesk (adskflex) references the option file. VENDOR adskflex port=2080 options=”\.opt” For example: VENDOR adskflex port=2080 options=”C:\Program Files\Autodesk Network License Manager\License\adskflex.opt” Save and close the license file. Copying Commands If you copy the commands from this document, make sure that the quotation marks are single quotations. Sometimes they are translated into left and right quotations which are recognized differently. 7 8 |  Configure the Service Configure the Service FLEXnet Server Types FLEXnet can be configured to use a license file for a vendor or a Service. FLEXnet also runs under multiple operating systems. Autodesk products support only services running under a Windows operating system. Now that the needed files are created and the software is installed, it’s time to put it all together. To do so, we need to define the vendor daemon and install the process as a service within the operating system. While FLEXnet supports two methods of running a vendor daemon, Autodesk only supports the service-based mechanism. To begin, find the new icon on your desktop called LMTOOLS that appeared after you installed the server software and launch it. The License Manager tool opens, and you are greeting with the following: Check off the only checkbox on the screen entitled, “LMTOOLS ignored license file path environment variables”. Next, click on the Config Services tab, the second tab from the right. Configure the Service  | When you first install the server and select the Config Services tab, the default Service Name listed will be either Borrow or something like FLEXnet Service 1. The name entered here will become the name of the Windows service visible in the Microsoft Management Services Console so you should use something clearly descriptive. In the example, the name is Autodesk NLM 11.5. Next, you need to enter the full path to the program that runs as the daemon process, LMGRD.EXE. Click the Browse button next to that field and find the program inside the folder where you installed the software. The program should default to that location. Do the same for the license file and the debug log file you created earlier. Check the options to Start Services at Power Up and Use Services. This will set the service to be Automatic in the services console and will create the service in Windows respectively. Service Names You can use spaces and periods in a service name but in general stick with aA..zZ..0-9 and _ or -. Do not use extended characters. You should also enter a description for the Windows service so other administrators know what the service is for. To do so, open a command prompt and enter the following command: sc description “” “” For example: sc description “Autodesk NLM 11.5” “Provides network licensing services for Autodesk products” 9 10 |  Configure the Windows Firewall Configure the Windows Firewall If you are running a firewall, you must open two ports for the communication to pass through to the server. One port is for the Server listener that accepts the initial request from the client. The second is for the handoff to the appropriate vendor daemon which manages the license for the product. Firewall Ports The default server listening port for FLEXnet is 27000. This port is can be configured on the SERVER line in the license file by adding the desired port number after the MAC address. The vendor port is listed already on the Vendor daemon line using the syntax PORT=2080. If you are using a 3rd party firewall, you will need to follow its instructions to add the port exceptions. If you are not using a firewall or it is turned off, you can ignore this configuration step. You will need to create two exceptions. To do so, open the Windows Firewall, select the Exceptions tab, and click Add Port... Enter a description, such as Autodesk License Manager Server, using port number 27000 and the TCP protocol. Add another port exception with a description of Autodesk License Manager Daemon using port 2080 and the TCP protocol. Close the Windows Firewall tool. Starting and Stopping the Server Service  | 11 Starting and Stopping the Server Service At this point, we have configured the server and are ready to start it up. To do so, select the Start/Stop/Reread tab and click the Start Server button. To stop the server, check the Force Server Shutdown box and click Stop Server. You will not receive a confirmation that the server is stopped, but the LMGRD process will disappear from the task list when it terminates, and the service will appear stopped in the Services Management Console. If you are allowing license borrowing (a default capability), you must select the option to force the server to shutdown, or the server will not shutdown. When you change the license file to point to a new or revised option file, or to add new feature increments, you must re-read the license file in order to activate the changes. To make the changes active, you can simply click the ReRead License File button. However, it is usually best to stop the server and start it up again. When bouncing the service, be sure to Force the shutdown and to wait 15 seconds before starting up the server again. Always use LMTOOLS Even through the service appears in the Services Management Console, do not use the console to stop the service. Always use LMTOOLS to start and stop the service. If you allow borrowed licenses, you must use LMTOOLS to shutdown the server or you risk corrupting the client licenses. Always be sure to stop the service with LMTOOLS before rebooting the server. 12 |  Verifying the Service Status Do NOT Stop the Service! Even through the service appears in the Services Management Console, do not use the console to stop the service. That is akin to killing the service and it will cause a corruption of borrowed licenses. Always use LMTOOLS or the command line tools to stop the service. Take extra care that your server does not automatically reboot after applyig Windows patches, too. If necessary, turn off that option in Automatic updates. Verifying the Service Status With the server configured and started, you need to confirm that it is running. To do so, check the Windows Service Management Console. Here you will make sure the service itself is configured properly and is actually running. To verify the license service, start up the Windows Service Managment Console via Administrative Tools -> Services. Look for the line with the name you defined in the Service Name field. The service should show as Started with the description you defined and set to an Automatic Startup Type. Verify the Logs Now would also be a good time to look inside of your adskdebug.log file for any errors or warnings. Check to make sure that the options file is being read properly. If you see a ‘file not found’ error, check your path in the license file ‘Vendor...options=’ line. Also, verify that your report log is being generated by looking for a report log file with the name given in the options file; adskflex.rl in this case. Verifying the License Status  | 13 Verifying the License Status With the service itself up and running and verified, the last step is to verify the configuration. To do that, go back to LMTOOLS and select the Server Status tab. Click the button Perform Status Enquiry and look in the field below for output. The text in the field should not contain any errors or warnings, and it should contain an entry for each feature code as in the following example: -------Status -------Flexible License Manager status on Mon 4/27/2009 12:06 [Detecting lmgrd processes...] License server status: 27000@nova License file(s) on nova: C:\Program Files\Autodesk Network License... nova: license server UP (MASTER) v11.5 Vendor daemon status (on nova): adskflex: UP v11.5 Feature usage info: Users of 64300ACD_F: (Total of 4 licenses issued; Total of 0 licenses in use) 14 |  Additional Resources Additional Resources While this outlines a typical FLEXnet installation, there are many other options and possibilities. Each Autodesk product that supports network licensing includes software to install the server, manage the processes, and perform reporting on the license use. Full documentation is included. In particular, look for the following documents found on the installation DVD by clicking on the Read the Documentation link at the initial autostart splash screen. FLEXnet Manuals ♦♦ Network Administrators Guide ♦♦ Network Licensing Guide If you have any other questions, concerns, or problems, contact your reseller or go to the Autodesk website for additional support. About the Author Gregg Lagnese is an subject matter expert working for Autodesk technical services within the Government division. He has an extensive background in enterprise distribution and licensing. This page intentionally left blank. Version 1.0, April, 2009, www.autodesk.com