flexlm 11.9 manual
LINK 1 ENTER SITE >>> Download PDF
LINK 2 ENTER SITE >>> Download PDF
File Name:flexlm 11.9 manual.pdf
Size: 2745 KB
Type: PDF, ePub, eBook
Category: Book
Uploaded: 2 May 2019, 17:21 PM
Rating: 4.6/5 from 759 votes.
Status: AVAILABLE
Last checked: 9 Minutes ago!
In order to read or download flexlm 11.9 manual ebook, you need to create a FREE account.
eBook includes PDF, ePub and Kindle version
✔ Register a free 1 month Trial Account.
✔ Download as many books as you like (Personal use)
✔ Cancel the membership at any time if not satisfied.
✔ Join Over 80000 Happy Readers
flexlm 11.9 manualThe process of licensing is different than our previous activation key method. Then install the license according to the installation instructions for your specific product as published in the BASIS online help. With the appropriate hostid information, you can install and register licenses remotely. In many cases, BASIS can also automatically register updates or upgrades after the initial registration process is complete. A good tutorial for troubleshooting. All rights reserved. By clicking OK, you consent to the use of cookies. Click Here to learn more about how we use cookies.Flexera Software no longer provides support for Flexlm but as a courtesy we have left this document for any remaining Flexlm users. Please read Flexera Software's end of life policy. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service. The latest versions are always backwards compatible. It's a good way to see if you are up-to-date, or to download the x64 version if your server is 64-bit. It's also beneficial if you are running with separate vendors that each come with a different version. If you don't have the DOCS folder with the user guide, you can also find the manual here: And of course, my favorite thread of FlexLM error codes can be found here: This thread is for information purposes only. Enjoy!Thank you! ? It's a good way to see if you are up-to-date, or to download the x64 version if your server is 64-bit. It's also beneficial if you are running with separate vendors that each come with a different version.http://favourtec.com/attachment/featherweight-repair-manual.xml
- Tags:
- flexlm 11.9 manual, flexlm 11.9 manually, flexlm 11.9 manual.
If you don't have the DOCS folder with the user guide, you can also find the manual here: And of course, my favorite thread of FlexLM error codes can be found here: This thread is for information purposes only. Enjoy! The newest link is: Best regards, Henrik Goldman --- Flexlm license management to reduce your costs - Our blog on software license management - Protect your software with LM-X License Manager - I guess the updated version of this post would be found here: Thank you! ? Ask the community or share your knowledge. We recommend upgrading your browser.Technical documentation is available as a PDF Download.You must have JavaScript enabled in your browser to utilize the functionality of this website.Doing this will break the encryption in the file and result in licensing failure. Installing your floating license file is covered in more detail in the FAQ: 'How do I install my floating license?' See the FAQ: ' How do I move my license to another machine? ' for more information and a link to the online rehost forms. The way to achieve this is dependent upon the version of the license server software you are using.For example, if you have a mixed RVDS v3.1 and v3.0 license, and request a v1.2 compiler license, by invoking the ADS v1.2 compiler, the v3.1 compiler license will be issued first. The nnn value can range from 001 to 255. The lower the value, the higher the sorting priority. The default SORT value of 100 is used when SORT is not defined. You might find that using an options file helps to control license increment use order. For more information please see the FAQ: ' Can I reserve floating licenses for specific users? ' You can also prevent certain users or computers from being issued with a license of a particular type. This is particularly useful if you have a license that enables more than one version of the Arm development tools and you want to control what users have access to what versions.http://hizirferforje.com/admin/fckeditor/editor/images/featherlite-xt25-plus-manual.xml Writing your options file You can create an options file in any text editor. We recommend that your options file has an.opt extension. When complete, copy the options file to each of your Arm license servers. In this example, it is assumed that the license file contains both RVDS 4.0 and ADS 1.2 seats. There are two defined project groups with defined users, and a set of build computers. The administrator wants to limit the number of seats of a given feature on a group basis, and also wants to reserve RVDS 4.0 compiler seats for particular users and clients. A specific user is not to be granted an RVDS 4.0 compiler license. You can specify an exact version of the feature (e.g., 4.0) if required. The MAX option puts a limit on the number of seats of a given feature. The EXCLUDE option prevents a user or group from being granted a license. This overrides any settings to include the user. The example below shows how you would do this at the top of your license file. This must be done on each of your Arm license servers. Check your server log, as it should report something like this: Reservations are made in the options file. The server must be restarted for options file changes to take effect.When setting up your licensing system, you should ensure that client machines have access to local license servers (i.e., across your site's local area network (LAN)). In many cases builds may actually fail if the time delays caused are too great. The high license traffic caused will also greatly increase the traffic on your WAN, which could lead to more general problems on your network. As a rule you should use the license server software provided with the latest version of the Arm development tools that you have. At the command prompt, type: Users of other tools must use the command prompt method above. See the FAQ entry: ' How do I install my floating license? ' If you are adding additional seats to your license file, see the FAQ entry: ' How do I merge my license files?http://dev.pb-adcon.de/node/19350 'If you have instead upgraded your license to support a new version of the tools, you must delete your old license file before installing the new one. You may wish to copy over all the new license utilities, including lmutil. The request will then be dealt with when a seat becomes available. On the client you will see the following message: If your license server hosts a mix of ADS and RVDS licenses, this may prevent license queuing from working. This is the typical error message seen on the client. This is probably because the license is older than the application. The sort option is described in the article: Can I define the order in which different version licenses are issued? The default sort value is 100, so here are some example sort values you could use for the RVDS licenses: Use of the old FLEXnet license key in that situation is not authorized by Arm or its licensors. Quotations for new seats are available upon request from Arm or your local Arm authorized reseller. Typically this would be a USB or PCMCIA Ethernet device. Supported platforms for FLEXnet can be found in the FLEXnet Licensing End User Guide. Also, the many different techniques that Arm compilation tools use to optimize for smaller code size and higher performance can increase build times as well. This article considers various ways of decreasing the time your code takes to build. When you invoke the compiler, three steps are carried out: If a floating license is used, this will depend on network traffic and whether a license is free for checkout on the server. Note that whereas compilation tools in ADS 1.2 will fail if no license is available, RVCT and Arm Compiler will in most circumstances wait for a license to become available. With a node-locked license, the compiler simply has to parse the file to check that there is a valid license. When this is received, it then needs to check whether it has been granted a license. Then, after the compile has completed the license has to be returned back to the server. If speed is your priority, then you should consider obtaining node-locked licenses for your build machines, or some node-locked licenses locked to USB network cards which can be moved between machines as required. However, this must be used with caution, as it may cause an increase in network traffic. Compiling a small number of larger files may be quicker than compiling a large number of smaller files.To do this, instead of having a build script like: It does have some limitations: The much older ADS compiler will attempt to compile all subsequent files. You should try to keep the number of include paths to a minimum. If you have a lot of include paths, make sure the files you need to include the most often exist in directories near the start of the include search path. You can guard against including headers multiple times. For example, if you have a header file 'foo.h', then add: Testing will have been carried out on all of the supported platforms for that product.For example: Each of the tool invocations will involve network communication between the client (build) machine and the license server. This can lead to build failures as below: Each attempt will be recorded in the license server debug log as below: The following environment variables allow command line options to the tools to be added to all invocations of the tool, without the need to change build infrastructures. Therefore, we highly recommend reading the Troubleshooting floating licensing issues article before using the license retry mechanism. Development tools and boards typically come with a time limited support entitlement, we may ask you for your serial number to check that your entitlement is valid. For example we will need: Company Name, Product, and Purchase date. Again there is a current and older format: To do this, open a command prompt and enter: The code that follows this is your serial number. We would normally suggest providing all the unique serial numbers. For RVT units the stick is normally not visible while it is connected to a RVI. The MAC address is a 12 digit code. This is also printed on a sticker, normally found on the rear of the unit. The MAC address is a 12 digit code, again printed on a sticker. The location of the serial number sticker will vary depending on the type of Versatile Express board. See picture below. Be careful not to confuse the serial number and the MAC address. The MAC address is a 12 digit code, again printed on a sticker. The following instructions explain how to read the EEPROM: If the host ID provided at the time the license is generated is wrong, then the license does not enable the tools. Node-locked licenses are normally locked to the physical address, also known as MAC address, of the computer network card. If you change your network card, you must apply to Arm for a new license. So in the example above, the host ID is 001124642313. Arm recommends that you use ifconfig for these version of Linux. See the FAQ entry, 'How do I obtain my license file,' for more information.On a Windows machine, any Physical Address can be used - as long as it is visible when running the tools. Beware of using wireless adapters because they might be disabled when not in use to save power. Step 1 can also be skipped provided that you are using the same version of the server utilities provided with the latest Arm development tools. This directory should be on your PATH. For more information, see the FAQ: ' Which version of the license server daemons should I run?' We recommend that you put the license file in the same directory as your license utilities. You may need to make some changes to the license file's SERVER line(s):Typically this will be 8224 for Arm licenses. On the Configure Services dialog, add paths for the lmgrd daemon, license file, and log file. Click on the Save Service button.All three servers must have been configured and started before you can use the license. Note that the third server in this example has no port number defined as this server is using a default port in the range between 27000 and 27009. This is discussed in the documentation links above. Save the license file as license.dat and place it into C:\Program Files\ARM (or wherever you have chosen to install the tools). For details on how to use the Arm License Manager, refer to chapter 3.1 of the Arm DS-5 License Management Guide. To merge license files, copy all of the INCREMENT lines from your separate license files into a new single license file. Then you can search for licenses for a particular host ID. All licenses with that particular host ID will be returned, allowing you to select which ones you would like to merge, before clicking the Merge button. Therefore a new license will only be required if the host ID of the license server(s) changes. The link below will take you to the Arm web licensing portal. Click the 'Rehost' link in the left-hand-side menu and accept the Rehost License Request (Disclaimer). Then enter either your tools serial number or host ID of your client machine. This will be of the form similar to LMxxxxx-xxxxx-xxxxxxxxxx (where 'x' represents an alphanumeric character) and can normally be found on a sticker on the product box and on a card inside the product (the number of characters immediately after LM may be different). Products purchased between March 2005 and July 2008 will have a serial number of the form xxxxx-xxxxx-xxxxx and evaluation serial numbers during this period are of the form WTxxx-xxxxxxxxx (the number of characters immediately after WT may be different). Before March 2005 serial numbers were of the form xxxxx-xxxxx-xxxxx-xxxxx. For more details please see the FAQ entry: How do I find my host ID? If you are using a Windows platform and a newer version of the Arm development tools (RVDS 2.2 and later) you can use the Arm License Wizard to access the Arm web licensing portal. Only the single individual, company or other legal entity to whom ARM is supplying this Licence may use the Software and Licence Keys.Please therefore raise a support case in the link below and list each serial number associated with the transfer, together with all other relevant details. The diagnostics will collect as much relevant information as possible about your Arm tools and license configuration. While Flexera, who provides FlexNet Licensing, documents these supported platforms, Arm has not tested and validated development tools like DS-5 running on these platforms. Therefore Arm might not be able to support users running the Arm Compiler or DS-5 on virtual platforms, if they encounter compatibility issues. There are a number of ways of configuring a client machine to check out a floating license from a license server and it is worth ensuring that your system is configured in such a way that the time taken for these checkout requests is minimized. Note that this variable can also be used to specify multiple locations (using a list separated by semi-colons on Windows, or colons on Unix) and each location will be checked in turn until a valid license is found. You should ensure that there are no spurious entries here which may cause such a delay. If this is the case the FLEXlm tools will wait until a request to this server has timed out.For example, you may have a three server license and have commented out two of the three server lines. The only parts of the license that you are allowed to modify are the host name (not host ID) and the port number. For instance you can define a port number for the armlmd vendor daemon, or a path to armlmd, in your license file. The guide is intended to help you identify an error, and navigate the product documentation and Knowledge Article database to solve it. For Linux installs, you will need to source the configuration script generated by the installer (e.g. RVDS40Env.posh ). To do this, run two quick tests: The output will look something like this: All Rights Reserved.All Rights Reserved.On the server, open a command prompt and enter: Based on the results of the two tests you have an indication on where the problems lies: The output will look something like this: The license server manager (lmgrd) has not been started yet,Feature: compiler. Server name: 10.1.72.146. FLEXnet Licensing error:-15,10. For further information, refer to the FLEXnet Licensing End User Guide,For now it is the FLEXnet Licensing error (-XXX,XXX) and the License path lines which are of most interest. The error message from the tools will only give the first error. So once you have resolved this issue, you should re-run the command to check for further errors! It may be that this check-out succeeds, but the check-out for other tools fail. If this is the case for you, run the tool that is failing and see what error code it reports. The codes are common across Arm development tools. You should confirm, using Task Manager on Windows or the ps command on Linux. Usually you will have to manually kill these stale processes before attempting to re-start the server software. BEWARE - it is possible to run multiple lmgrd servers (but not armlmd ) on the same physical machine - refer to here. The command is as follows. The -z flag causes the server to print all log and diagnostic information to the console. This is not usually desirable, but useful for troubleshooting. Alternatively, you can replace -z with -l, which directs the messages to a file. Use Macrovision'sFLEXnet ManagerAll Rights Reserved.If this also succeeds, then monitor the server as the problem may come during operation rather than start up. How far through the start up sequence it got before the error gives an indication of where the issue lies. Below are common messages to see in the output: If all the seats are in use, further requests will not be satisfied. Normally, the server will queue a request until a seat becomes available - so that the client does not see a failure. On the client you would see something like this. Waiting for license. This is covered in more detail in the following FAQ: ' Why am I getting a FLEXlm -12,122 license error? ' However, the tools were unable to open a connection to a FLEX license server on the specified port. Possible causes include: It is possible that something is blocking communication, typically a firewall. This is covered in more detail in the following FAQ: ' Why am I getting a FLEXlm -15 license error, even though my license server is running? ' However, the server does not host the feature that the client was trying to check-out. This can happen for a number of reasons. For example, RVDS is sold as Professional and Standard editions. The Professional edition includes additional features. If you were to try using the Professional edition with a Standard license, you could see this error. For example, one server for Arm licenses and another third party licenses. In which case this could indicate that you are specifying the wrong server on the search path.The server hosts the feature that was requested - but not the correct version. This usually indicates that you are trying to use an older license with a more recent tool. For example, using the RVDS 4.0 tools with an RVDS 3.1 license. This is due how the server operates internally when it hosts a mix of licenses, and can be ignored. For further information please see FAQ: ' Why am I getting DENIED messages in my server log? ' This is done using an options file. For more information on option files, please see the following FAQ: ' Can I reserve floating licenses for specific users? ' Attempting to user borrow will result in this error. For further information, please see the following FAQ: Do Arm's development tools support BORROW licenses? It shows that the OS failed to translate the hostname into an IP address. Check that the correct name is being specified, and that your network's name resolution is working correctly.Check on the server which port is being used by the daemon and that it is open on the server's firewall. It is assigned by the host operating system at server start. If the server has a firewall it is advisable to set the port manually. In the license file change: This usually indicates that armlmd has crashed. Check the server's debug log, you should see a message indicating that lmgrd lost its connection to armlmd. Shut down lmgrd, and check that there are no stale lmgrd or armlmd processes. Then re-start lmgrd. For example, trying to issue an ADS license to RVDS. Normally this will not happen, however there are cases where it can.This is due how the server operates internally when it hosts a mix of licenses, and can be ignored. For further information please see the FAQ: ' Why am I getting DENIED messages in my server log? ' This could be because it has been edited, or accidentally commented out. Try re-downloading the license file from Arm's website. Alternatively, you may be passing a node-locked license file, which can not be hosted in this way. It has tried to launch the Arm vendor daemon ( armlmd ), but was unable to locate the executable.Check the location of armlmd ( armlmd.exe on Windows) and ensure that it is on the search path. Alternatively you can specify the location in the license file. The file from Arm will have this line: This is usually caused by having a lmgrd process already running, for example a stale process. You will need to rehost the license to use this machine. Only a few sections of the license file can be edited, editing any other section will result in this error. Re-download the license file from the Arm web licensing portal. If all the features in the license file have expired the server will fail to start. You can run multiple FLEXnet license servers on the same machine - if they are for different vendors' licenses. However, only one instance of armlmd (the Arm vendor daemon) can be running on the machine. If armlmd is already running when the server software starts it fail with this error: You be trying to run two instances of the license server on the same machine - both hosting Arm licenses. This is not supported. You will need to merge the license files, and host them from a single instance of the server software. Merging license file is covered here. You should check for stale instances of armlmd, and terminate them. On Windows you can use Task Manager. It is usually caused when the server is passed a node-locked license. This configuration is not supported, and leads to this error message. The message is only seen at the point a client attempts to use the license, not when the license it initially parsed. If a node-locked license is present on the server, the lmstat output will include one or more lines similar to this: The armlmd daemon requires libraries from Microsoft Visual Studio, if they are not present this error is seen. The SERVER line in a license file should be near the top of the file, and the format is: Check the command used to start the server, and verify the file path. This is not supported, only license files containing floating licenses should be passed to lmgrd. To do this open a command prompt window and execute the command armcc --vsn or armclang --vsn. Depending upon the version, the output of this command should look something like this: Error code: -10. Feature has expired. type of error. Feature: compiler5. Expire date: 31-oct-2015. License path: C:\license.dat path to license file(s). FlexNet Licensing error:-10,32 error code. Component: ARM Compiler 5.06 update 1 (build 61)Between them these two fields give the type of failure. Another useful field is the License path, as this tells you where the tools are looking for a license file. In this case you need to record the error message next time you see it. The hostid of this system does not match the hostid specified in the license file.Run it on your machine and include its output with your e-mail. This is normally because you have not yet installed a license file, or the license file has been moved since installation. To rectify, follow the instructions in this FAQ: ' How do I install my node locked license? ' Typically this will be caused by: In which case you should download a fresh copy of the license from your account on the Arm website ( ). This could be accidental, or because you have tried to edit the license file. You can not not edit any other part of the file without it becoming invalid. To fix, download a fresh copy of the license file from your account on the Arm web licensing portal and then follow the instructions in: ' How do I install my node locked license? ' The hostid of this system does not match the hostid specified in the license file. This error message occurs when the host ID the license has been locked does not match that of the system. For node-locked licenses the hostid can be the disk serial number of the C drive, or the MAC address of an Ethernet adapter. The hostid in the license file must be visible on on your system at all times, otherwise the tools will not work. How to do this is covered in the following FAQ: ' How do I move my license to another machine? ' You can do this manually, or by using the License Wizard. See the following FAQ for more information: ' How do I install my node locked license? '. For example, trying to run the RVCT 3.0 compiler with a RVCT 2.1 license. Navigate to this file, and check whether it is the correct file for the version of the tools you are using. If it is the incorrect file, run through the instructions in the following FAQ to install the newer license: ' How do I install my node locked license? ' For information please see: Why am I getting FLEXnet -89 error message? ' For more information see the following FAQ: ' Why am I getting a FLEXlm -103,122 license error? ' The RVDKs require both a valid license file and also the supplied RVI-ME unit to be plugged in before they will operate. This error message shows that a license file was found, but that the RVI-ME is either not plugged in or is not installed correctly. If it is, you may need to re-install the driver. GUI tools, i.e. AXD Debugger, or RealView Debugger. Once you have launched one of these applications using its GUI, your tools will become unlocked and the 45 day counter will begin. This license file is installed by default into the ADS installation directory and is called license.dat. Because the ADS license file is also called license.dat, the CodeWarrior license file is sometimes moved or deleted by the user in error (for example when installing the ADS license file). A make program can be invoked using the -j flag, for example: The above command would invoke a parallel build, running four jobs in parallel. Each job requests one seat, so in this case the client would attempt to check out four seats. If there are sufficient seats available, the client should observe optimal build times. If the license server only has one seat available, the additional requests will be queued and the client would not benefit from using the -j option. If the operating system is capable of scheduling different jobs to different CPUs, then it is possible to run separate jobs on each core. So for a quad-core machine to operate at its optimum performance, when running a parallel build, it will require at least four seats, otherwise the build might be delayed. For example, if the client machine is a quad-core machine and runs a parallel build using a single seat license, it will request four seats and will check out one seat. The remaining requests will be queued until the seat is returned to the license pool. Whilst the license seat is checked-out, the remaining requests are likely to result in the following message: For example, a build farm might be used for an overnight build. Build farms typically support parallel jobs (mentioned above), and also remote access to allow cross-platform development. Server farms typically run more than one build in parallel using multiple cores, which can lead to a very high frequency of attempts to checkout a license. Conversely, the tools require a license of the same version number or higher to operate. Also, it is recommend to use an options file to prevent older versions of the Arm Compiler consuming licenses that enable newer versions of the Arm Compiler. For more information, please see the FAQ: Can I reserve floating licenses for specific users? It is also very important when upgrading your client machine specifications, that your server(s) are of a suitable specification to handle the clients' demands. Utilities are provided for running a license server on the platforms supported by the tools. License server software consists of two parts: A list of supported platforms can be found in the product documentation, and also in the following FAQs: The latest Arm supported versions can also be downloaded from the Arm website: You can see this happening in the example from a server log: It is just reporting the sequence of events as they happen. VENDOR armlmdTherefore, node-locked licenses do not work under Windows Remote Desktop or Terminal Services. These particular problems are specific to the FLEXlm version 7.2 as used by ADS v1.2x and RVCT v1.2 and do not affect any other Arm tools. The problem lies within FLEXlm client code incorporated into the Arm tools mentioned above.