ENGINEERED EFFICIENCY FlexNET Server Administraon Guide Contact & informaon: CAXperts GmbH Carl-Zeiss-Ring 4 85737 Ismaning Germany P.: +49 89 96 97 72 0 F.: +49 89 96 97 72 11 E.: info@caxperts.com
FlexLM Server Administraon Guide Administraon guide Copyright Copyright 2002 CAXperts GmbH. All Rights Reserved. Including so6ware, file formats, and audiovisual displays; may be used pursuant to applicable so6ware licence agreement; contains confiden;al and proprietary informa;on of CAXperts and/or third par;es which is protected by copyright law, trade secret law, and interna;onal treaty, and may not be provided or otherwise made available without proper authoriza;on. Restricted Rights Legend Rights reserved under the copyright laws of the Federal Republic of Germany. Warranes and Liabilies All warran;es given by CAXperts about equipment or so6ware are set forth in your purchase contract, and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modifica;on or amendment of such warran;es. CAXperts believes the informa;on in this publica;on is accurate as of its publica;on date. The informa;on and the so6ware discussed in this document are subject to change without no;ce and are subject to applicable technical product descrip;ons. CAXperts is not responsible for any error that may appear in this document. The so6ware discussed in this document is furnished under a licence and may be used or copied only in accordance with the terms of this licence. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT. Trademarks CAXperts is a registered trademark of CAXperts GmbH. Intergraph, the Intergraph logo, SmartSketch, FrameWorks, SmartPlant, INtools, MARIAN, PDS, IGDS, RIS and IntelliShip are registered trademarks of Intergraph Corpora;on. IGDS file formats 1987-1994 Intergraph Corpora;on. Microso6 and Windows are registered trademarks of Microso6 Corpora;on. Bentley, the Bentley logo B, and MicroSta;on are registered trademarks of Bentley Systems, Inc. ISOGEN is a registered trademark of Alias Limited. Other brands and product names are trademarks of their respec;ve owners. 2
Introducon Contents 1 Introducon... 4 1.1 General conven;ons... 4 Typefaces... 4 Symbols... 4 2 License server... 5 2.1 Selec;ng a license server machine... 5 License server sockets... 5 License server CPU ;me... 5 License server disk space... 5 License server memory... 5 Network bandwidth for license server... 6 License server locally mounted disks... 6 License server port... 6 2.2 Setup lmadmin license server manager... 6 System requirements for lmadmin... 6 Install lmadmin... 7 Install vendor daemon... 9 Configure ports... 10 2.3 Using lmadmin... 11 Accessing the license server management interface... 11 Obtain host ID... 12 Import license... 13 3 Report log file... 15 3.1 Managing report log output... 15 3.2 Enabling report log output for a vendor daemon... 16 3.3 Redirec;ng report log output for a vendor daemon... 16 4 Debug log file... 16 4.1 Managing debug log output... 16 Capturing debug log output for a license server... 16 Capturing debug log output for a par;cular vendor daemon... 17 Redirec;ng debug log output for a running vendor daemon... 17 Limi;ng debug log output for a vendor daemon... 17 License server diagnos;cs in the debug log... 17 5 Locang licenses... 18 6 Technical support... 18 3
FlexLM Server Administraon Guide Administraon guide 1 Introducon CAXperts so6ware is suppor;ng Flexera FlexNET Server for licence management. This document is describes basic steps how to setup FlexNET server. For details please refer to FlexNet Publisher License Administraon Guide available at www.flexera.com. 1.1 General convenons This document contains many visual cues to help you understand the meaning of certain words or phrases. The use of different fonts for different types of informa;on allows you to scan the document for key concepts or commands. Symbols help abbreviate and iden;fy commonly used words, phrases, or groups of related informa;on Typefaces Italic Bold Normal typewriter Bold typewriter Indicates a system response, which is an explana;on of what the so6ware is doing. For example, The text is placed in the viewing plane. Indicates a command name, parameter name, or dialog box ;tle. Command paths are shown using an arrow between command names. For example, Choose File Open to load a new file. Indicates an actual file or directory name. For example, The ASCII report is stored in the layout.rpt file. Indicates what you literally type in. For example, Key in original.dat to load the ASCII file. Symbols This document uses the following symbols to iden;fy special informa;on: Note important supplemental informa;on. Map or path shows you how to get to a specific command or form. More informa;on indicates there is addi;onal or related informa;on. 4
License server 2 License server The basic components of a CAXperts Licensing system are as illustrated in the following diagram: License server available at www.caxperts.com : - lmadmin - Web based (recommended) - lmgrd - Command line based Vendor daemon caxperts.exe available at www.caxperts.com. If you have already License Server running (lmadmin or lmgrd) you need onlty to install vendor daemon. 2.1 Selecng a license server machine When selec;ng a machine on which to install a license server, select a stable system; do not choose systems that are frequently rebooted or shut down. Normally, it is not required that each system be the same architecture or opera;ng system as other license servers or the client machines on which the CAXperts applica;ons are running. The following sec;ons discuss the resources used by the license server. When you select a machine on which to install a license server, you may need to consider whether it has sufficient resources. For small numbers of licenses (under about 100), most of these system limits are not a problem on any worksta;on. License server sockets When using TCP/IP ports, each CAXperts applica;on connected to a license server uses one or more sockets. The per-process system limit for file descriptors determines the number of sockets available to the license server. The total number of sockets that the license server uses is slightly larger than the total number needed by the CAXperts applica;ons that connect to it. If the number of sockets required by the license server on a single system becomes excessive, then one solu;on is to run mul;ple license servers and split the licenses between them. This reduces the networking traffic to each license servers. License server CPU me For small numbers of clients, the license servers use very lirle CPU ;me. The servers might have consumed only a few seconds of CPU ;me a6er many days. For a large number of clients or for high checkout and checkin ac;vity levels (hundreds per second), the amount of CPU ;me consumed by the server may start to become significant; although, even here, CPU usage is normally not high. In this case, you may need to ensure that the system you select has enough CPU cycles to spare. License server disk space The only output files created by the license servers are the debug and report log files. FlexNet Manager, Flexera So6ware s Web-based so6ware license management system, uses the report log files to generate accurate usage reports. If there is a lot of license ac;vity, these log files grow very large. You need to consider where to put these files and how o6en to rotate and archive them. You have the op;on to suppress log file output if disk space is at a premium. It is recommended that the log files are local files on the server systems to avoid networking dependencies. See Also Report Log File Debug Log File License server memory The license server uses lirle memory. The vendor daemon caxperts.exe use approximately 2 MB, although memory usage increases in the vendor daemon with the number of concurrent licenses, size of the op;ons file, and the number of concurrent users. lmadmin, uses between 7 5
FlexLM Server Administraon Guide Administraon guide and 10 MB of memory during typical usage. Typically, the command-line license server manager, lmgrd, uses approximately 2 MB. Network bandwidth for license server CAXperts applica;on sends rela;vely small amounts of data across the network. Each transac- ;on, such as a checkout or checkin of a license, generally transfers less than 1 KB of data. This means that it can be effec;vely run over slow networks (such as dial-up SLIP lines) for small numbers of clients. For a large number of instances of CAXperts applica;ons (hundreds), the network bandwidth used may become significant. In this case, run the CAXperts applica;on and server on the same local area network, and run mul;ple license servers. When you are using lmadmin, which uses HTTP, you need to consider the clients that connect to the lmadmin user interface. Depending on the number of clients and the frequency of the page refresh, they can impose a significant burden on network traffic. License server locally mounted disks It is recommended that you do not use remote mounted disks when you run the license server. In other words, it is recommended that lmadmin or lmgrd, the vendor daemon, the license file, and the debug and report log files are all on locally mounted disks. If any of these files are on a remote mounted disk, this doubles the points of failure, which could lead to a temporary loss of all of your licenses. When all files are mounted locally, the licenses are available as long as the server is running. When the files are on a different system, licenses may become unavailable if the license server or file server fails. License server port It is recommended that a specific port is designated on the license server machine to be used only by license server components. The benefits of this are that it is: Easy to track processes by the port that they are run on. Easier to configure clients to access the license server. Easier to manage license server components in an environment where a firewall and/ or antivirus software is in use. Useful in preventing port conflicts and the hijacking of the port by other processes. To configure the license server port: Using lmgrd - Specify it in the license file used to start the license server; see Configuring the Port Used by the License Server. Using lmadmin - Configure the license server manager port either: Using the lmadmin user interface. See the online help for information. Using the lmadmin -licport command. For information about the -licport argument, see lmadmin Command- line Arguments. 2.2 Setup lmadmin license server manager System requirements for lmadmin - Microso6 Windows 7, 8 (32, 64-bit) - Windows Server 2008, 2012 (32, 64-bit) - Microso6 Visual C++ 2008 SP1 Redistributable Package (32 bit) (included in setup) 6
License server Install lmadmin 7
FlexLM Server Administraon Guide Administraon guide 8
License server Verify lmadmin service has Startup Type automa;c and runs in Windows Services: Install vendor daemon Copy vendor damon caxperts.cex into applica;on folder of lmadmin (C:\Program Files\FlexNet Publisher License Server Manager) 9
FlexLM Server Administraon Guide Administraon guide Configure ports There are two ports on the machine running FlexNET server (lmgrd, lmadmin): 1. License Server Manager Port, by default 27000. 2. Vendor daemon port (caxperts), by default some random number > 10000. 10
License server It is recommended to use one specific port for vendor daemo, otherwise a6er restart new port number may be assigned for the vendor daemon and firewall/client sevngs must be adjusted. On the machine running FlexNET server VENDOR DAEMON port MUST be ALWAYS open in the firewall. On client machines CAXPERTS_LICENSE_FILE variable MUST contains the VENDOR DAEMON port -> CAXPERTS_LICENSE_FILE=49169@flexnet_server. Administrator can ADDITIONALLY open License Server Manager port (27000) on the machine running FlexNET server. In this case the client machine will AUTOMATICALLY detect the right vendor daemon port. There is no need to define it explicitly in CAXPERTS_LICENSE_FILE variable -> CAXPERTS_LI- CENSE_FILE=@flexnet_server 2.3 Using lmadmin Accessing the license server management interface 1. Make sure that you have started the license server. 2. Open the Web browser and browse to one of the following URL: http://<server>:8090 where <server> is the system name where the license server is running. 11
FlexLM Server Administraon Guide Administraon guide When lmadmin is first installed, the administrator user name and password are both set to admin. Use this informa;on when you first sign in to the interface as an administrator. Viewing the lmadmin Log Files Obtain host ID To create a licence key for your license server, CAXperts needs the host ID of your server. 1. Open the Web browser and browse to one of the following URL: hrp://<server>:8090 2. Switch to Administra;on page 3. On System Informa;on tab Ethernet Address shows the unique host id of license server. 12
License server Import license 4. Open the Web browser and browse to one of the following URL: hrp://<server>:8090 5. Switch to Administra;on page 3.Select Vendor Daemon Configura;on 4.Click on Import License 13
FlexLM Server Administraon Guide Administraon guide 5. Select License File provided by CAXperts and click Import License. The overview for available licenses is available under Dashboard -> Concurrent. 14
Report log file 3 Report log file The license server produces both report-log-files and debug-log-files. The focus of this sec;on is report log files. For informa;on on debug log files see Debug Log File. The report log file contains feature usage informa;on and is generated by the vendor daemon. However, a vendor daemon does not write report logs by default; this ac;on must be enabled. The data in report logs is compressed, authen;cated, and organized into a repository. Use Flexera So6ware s so6ware license administra;on solu;on, FlexNet Manager, to gain excep- ;onal visibility into license usage data and to create insighzul reports on cri;cal informa;on like license availability and usage. FlexNet Manager can be fully automated to run these reports on schedule and can be used to track license servers and usage across a heterogeneous network of server including Windows NT, Linux and UNIX. Contact Flexera So6ware at www.flexeraso6- ware.com for more details on how to obtain an evalua;on copy of FlexNet Manager for your enterprise. 3.1 Managing report log output As a vendor daemon runs for a period of ;me, the volume of report log output increases. If you have a lot of license ac;vity, these log files grow very large. You need to consider where to put these files and how o6en to rotate and archive them. Therefore, it may be necessary to rotate or switch report log output into different files over ;me, each file containing license ac;vity over a par;cular period of ;me. Report log data is collected by the vendor daemon into an internal data buffer area before being flushed to the output file. The daemon s internal buffer is flushed once a minute or whenever it gets full, whichever occurs first. To ensure the freshest data possible in the report log file, flush the buffer on demand with the lmreread command. Use standard file compression tools to reduce the size of a report log file when it is no longer being wriren. 15
FlexLM Server Administraon Guide Administraon guide To avoid corrup;on and for performance, it is suggested that the vendor daemon write its report log to a file on a disk local to the system running the vendor daemon. Each vendor daemon must write to its own report log file. 3.2 Enabling report log output for a vendor daemon There are two ways to enable report logging for a par;cular vendor daemon either before or a6er star;ng the license server. Add the REPORTLOG line to the options file for that vendor daemon. See RE- PORTLOG for more details. Invoke lmswitchr on the vendor daemon. See lmswitchr for more details. 3.3 Redirecng report log output for a vendor daemon The report log output for a par;cular vendor daemon can be moved into separate files, each file represen;ng ac;vity over a different period of ;me. There are three ways in which to do this whether the vendor daemon is running or not: Change the REPORTLOG line in the vendor daemon s options file and reread its options file by invoking lmreread (version 8.0 or later vendor daemon) or restart. Invoke lmswitchr on the vendor daemon. See lmswitchr for more details. Invoke lmnewlog on the vendor daemon. Requires a version 7.1 or later vendor daemon. See lmnewlog for more details. 4 Debug log file The license server produces both debug log files and report log files. For informa;on on report log files, see Report Log File. A debug log file contains status and error messages useful for debugging the license server. The lmgrd debug log displays the server's system date, ;me, and ;me zone at the beginning of a log. A license server always generates debug log output. Some of the debug log output describes events specific to lmadmin or lmgrd and some of the debug log output describes events specific to each vendor daemon. 4.1 Managing debug log output As the license server manager and its vendor daemons run for a period of ;me, the volume of this output increases. As it gets older, the value of the debug log output decreases; therefore, it may be necessary for you to separate old debug log output from current output; either archive or delete the old output. For performance, it is suggested that each debug log file be on a disk that is local to the system that is running the license server manager and its vendor daemons. However, if the debug log file must be on a remotely-mounted disk and you find that the license server is too slow, start lmgrd with the -nfs_log op;on to improve performance. See Debug Log Messages for a descripon of the debug log output format. Capturing debug log output for a license server If you are using lmadmin as your license server manager, separate log files are created for lmadmin and each vendor daemon that it manages. The log files are wriren to the logs directory within the lmadmin install directory; however, you can use the -logdir op;on on the command line to change the loca;on to which lmadmin writes lmadmin.log. See lmadmin Command-line Arguments for details. 16
Debug log file By default, lmgrd and the vendor daemons it manages write debug log output to standard out. To put this debug log output in a file, either redirect the output of the license server to a file or start lmgrd with the -l debug_log_path op;on. See lmgrd Command-Line Syntax for more informa;on. Capturing debug log output for a parcular vendor daemon The debug log output from different vendor daemons controlled by the same license server can be wriren to their own files (version 8.0 and later vendor daemon). There are three ways to do this: If you are using lmadmin as your license server manager, you configure the location and file name from the Vendor Daemon Configuration screen. See online help for information on Vendor Daemon Log. Add the DEBUGLOG line to the options file for each vendor daemon. See DE- BUGLOG for more details. Invoke lmswitch on the vendor daemon. See lmswitch for more details. Note that lmgrd writes its own debug log output to standard out. Redirecng debug log output for a running vendor daemon It is possible to redirect the debug log output for a par;cular vendor daemon to a different file. There are two ways to do this: Change the DEBUGLOG line to the options file for the vendor daemon and reread its options file by invoking lmreread. See DEBUGLOG for more details. Invoke lmswitch on the vendor daemon. See lmswitch for more details. Liming debug log output for a vendor daemon By default, debug log output contains all events. To limit the events that are logged for a par;cular vendor daemon, add a NOLOG line to the op;ons file of that vendor daemon. One of the reasons you may want to limit the events that are logged is to reduce the size of the debug log output. See Also NOLOG License server diagnoscs in the debug log Enhanced license server diagnos;cs will now be emired in the license server debug log. Addi- ;onal diagnos;cs are prefixed by (@lmgrd-slog@) for the lmgrd and (@<vendor>-slog@) for the Vendor Daemon, facilita;ng easy grep-like extrac;on from the debug-log. The Vendor Daemon would emit the addi;onal diagnos;cs when run with lmgrd or lmadmin. These diagnos- ;cs are intended to assist publishers and Flexera diagnose license server issues. These diagnos- ;cs include: For lmgrd: Start timestamp, Version, ProcessID, Network Info (IPv4/IPv6 interface, listening port), command-line options, list of license files, whether the license server is running as a windows service. For Vendor Daemon: Start timestamp, Version, ProcessID, Network info (IPv4/IPv6 interface, listening port, select timeout of vendor daemon), Vendor daemon name, Options file used, Trusted storage accessed (yes/no), Host name, Virtual/physical environment, (limited) hypervisor info if virtual, Lmbind used (yes/no), #Restarts of vendor daemon since lmgrd startup, #Rereads since vendor daemon (re)start, Last 17
FlexLM Server Administraon Guide Administraon guide reread time, Reread initiation type (automatic versus lmreread). Every 4 hours (and at vendor daemon shutdown) the following performance data are logged: Details of the 10 peak client transactions (including client hostname, user, transaction time, concurrent clients at time of transaction, memory usage (Windows only)), Peak concurrent clients served, High watermark memory usage (Windows only), Transaction time for last 10 transactions. 5 Locang licenses Loca;on of the License server should be defined on every client machine running CAXperts applica;on. This ca be done in two different ways. This ca be done in two different ways: In the environment variable CAXPERTS_LICENSE_FILE=@YouServerName In the registry HKEY_CURRENT_USER\Software\FLEXlm License Manager\CAXPERTS_LI- CENSE_FILE=@YouServerName Where YourServerName is Windows computer name of the machine running lmadmin (FlexNET server). Mul;ple servers can be defined separated by semicolon ;. Every computer name must be preceded by the @ symbol. If lmadmin is running on non-default port, the port number should be defined as follow: port@yourservername. Example: CAXPERTS_LICENSE_FILE=@Server1;@Server2;4000@Server3 6 Technical support Need more help? Contact CAXperts support by email, online, or phone: mailto:support@caxperts.com hrp://www.caxperts.com/contact/ 18