A floating license scheme is typically used if there are more potential users than purchased licenses.
A floating license scheme is more flexible than a node locked license but it requires more
A floating license-managed installation of an ARM product consists of the following
These are computers that have your ARM development software installed on them.
There can be more clients than purchased licenses. If all of the license seats are
used, no additional users can use the product until one of the current users stops
using the product.
This is the computer that has the license and floating license server utilities
installed on it. A floating license server can also be a client, but this is not the
typical mode of operation.
The floating license server controls the number of copies of the licensed product component
in use at any one time, up to the maximum number of licenses purchased.
The license extract in the following figure shows part of a typical floating license. In
this example the fully qualified
SERVER name is
cumulus.mycompany.com, the host ID is
785f2170 and port
8224 is being used.
This license enables up to ten concurrent users of the specified ARM application, and each
user obtains permission to run the application from the floating license server. Because of
the flexible way the individual parts of the tools are license managed, this floating
license enables up to ten users to use the
armar feature, while a different
ten users use the
fromelf feature. Some product licenses might restrict
concurrent feature use, so check your tools documentation for details.
- Typical single-server floating license extract
SERVER cumulus.mycompany.com 785f2170 8224
INCREMENT fromelf armlmd 5.0201105 permanent 10 7E338B2771EA DUP_GROUP=NONE \
ISSUER="ARM Limited" NOTICE="For support see \
http://www.arm.com/support/" SN=ABCDE-98765-ZYXWV SIGN="8674 \
FEE3 5830 D004 2F8D 8C07 E75C 84AA 14EB 37A0 9AD7 4D73 D34A F83A \
EE22 B1F1 3579 54C8 54BA D9D7 5B87 E024 632C B7E0 1DF2 8526 2312 \
27F2 DD78 C020 ABB9" SIGN2="1E17 F524 7987 9CD4 3BC2 FB34 E2FB \
04AA 2C79 4B4C 776D 0FC3 9797 7653 2FBA 044B 2854 608B D8B9 \
6F8A 7B69 3BFA 4AE4 2234 B9A0 0ACA 3E21 1CF8 0F58 54FE"
INCREMENT armar armlmd 5.0201105 permanent 10 8EE2C29A2DB3 DUP_GROUP=UHD \
ISSUER="ARM Limited" NOTICE="For support see \
http://www.arm.com/support/" SN=ABCDE-98765-ZYXWV SIGN="2B77 \
780F 37C5 CAD3 ED05 AECA 0424 0876 6E3D 2EAC 64EB C78E 7015 6E99 \
2119 08ED 4889 AF20 CD05 9E76 EA75 72FE 0154 CC8F CD78 AA01 \
1824 C650 A7B5 0696" SIGN2="20EA 4015 0356 5FF8 2DE5 083A 2C9F \
5645 B14E 220C 00E1 8970 F32E B873 AC7E 182A 20EF 27EA 7BB8 \
B25E 08DB 70D3 AB8B 7847 DB87 B88A 5700 A079 BEB7 E3D2"…
Windows and Unix/Linux floating license servers and clients can be mixed in any
installation. Client machines must be able to access the server machines over the
Local Area Network (LAN).
ARM does not support the use of floating licenses across Wide Area Networks
(WANs). For performance reasons, you are strongly advised to have your floating license
servers and clients on the same LAN.
ARM software licenses support single-server and three-server floating license
installations. You can only use the ARM License Manager to set up single-server floating
licenses. A multiple server floating license configuration must be set up manually.
The license file is locked to the host ID of a single server that is used for controlling
the licensing process. A single-server floating license model requires that the server
machine is running at all times and that the client machines can access this server machine
over the local area network.
If the network or single server fails, the licensed tools cannot be used until the server
The following figure illustrates the single-server model. On the server, a license file
with the corresponding server details is loaded by the floating license server processes.
The client must be configured so that it references the floating license server and the port
through which the license is issued. The recommended method for doing this is setting the
ARMLMD_LICENSE_FILE environment variable on the client to
port@server. For the single-server model example in the figure, the
environment variable must be set to
Figure 1-1 Single-server model
The license file is locked to the host ID of three separate floating license servers. This
permits more reliable licensing of the product so that the failure of one server does not
stop users from checking out licenses. A three-server floating license model requires
All three servers must be available when the floating license server starts. One of
the servers can be stopped after the initial start up.
A minimum of two server machines are running at all times.
All the servers can access each other over the LAN.
The client machines can also access these server machines over the LAN.
The three-server model has the following limitations:
It is more complicated to set up than a single-server system.
Three servers are required.
Two servers must be operational at all times.
Because of the additional complexity of the three-server model, it is more suitable for
managing ten or more total seats, where many users rely on the servers being
The following figure shows the three-server model. On each of the servers, an identical
license file with details of all three servers is loaded by the floating license server
processes. The client must be configured so that it references all the floating license
servers in addition to the ports through which the license is issued. The recommended method
for doing this is setting the
ARMLMD_LICENSE_FILE environment variable.
Figure 1-2 Three-server model
For the three-server model example in the figure, on Windows, the environment variable must
be set to
8224@Server_A;8224@Server_B;8224@Server_C. The first server in
the list, Server_A, is the master server, and must be started before the other two
Depending on your operating system, the separators for the values in the environment
variable might be different. On Unix or Linux, the separator is a colon “
rather than a semicolon “
;” as on Windows.