reproduced in any form or by any
means (including electronic storage
and retrieval or translation into a
foreign language) without prior
agreement and written consent from
Keysight Technologies, Inc. as
governed by United States and
international copyright laws.
Manual Part Number
5951-5739
Published By
Keysight Technologies
900 S. Taft
Loveland
Colorado
Edition
Edition 3.2, December, 2020
U.S.A.
Warranty
THE MATERIAL CONTAINED IN THIS
DOCUMENT IS PROVIDED “AS IS,”
AND IS SUBJECT TO BEING
CHANGED, WITHOUT NOTICE, IN
FUTURE EDITIONS. FURTHER, TO
THE MAXIMUM EXTENT PERMITTED
BY APPLICABLE LAW, KEYSIGHT
DISCLAIMS ALL WARRANTIES,
EITHER EXPRESS OR IMPLIED,
WITH REGARD TO THIS MANUAL
AND ANY INFORMATION
CONTAINED HEREIN, INCLUDING
BUT NOT LIMITED TO THE IMPLIED
WARRANTIES OF
MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE.
KEYSIGHT SHALL NOT BE LIABLE
FOR ERRORS OR FOR INCIDENTAL
OR CONSEQUENTIAL DAMAGES IN
CONNECTION WITH THE
FURNISHING, USE, OR
PERFORMANCE OF THIS
DOCUMENT OR OF ANY
INFORMATION CONTAINED
HEREIN. SHOULD KEYSIGHT AND
THE USER HAVE A SEPARATE
WRITTEN AGREEMENT WITH
WARRANTY TERMS COVERING
THE MATERIAL IN THIS DOCUMENT
THAT CONFLICT WITH THESE
TERMS, THE WARRANTY TERMS IN
THE SEPARATE AGREEMENT
SHALL CONTROL.
KEYSIGHT TECHNOLOGIES DOES
NOT WARRANT THIRD-PARTY
SYSTEM-LEVEL (COMBINATION OF
CHASSIS, CONTROLLERS,
MODULES, ETC.) PERFORMANCE,
SAFETY, OR REGULATORY
COMPLIANCE, UNLESS
SPECIFICALLY STATED.
Technology Licenses
The hardware and/or software
described in this document are
furnished under a license and may be
used or copied only in accordance
with the terms of such license.
U.S. Government Rights
The Software is “commercial
computer software,” as defined by
Federal Acquisition Regulation
(“FAR”) 2.101. Pursuant to FAR
12.212 and 27.405-3 and Department
of Defense FAR Supplement
(“DFARS”) 227.7202, the U.S.
government acquires commercial
computer software under the same
terms by which the software is
customarily provided to the public.
Accordingly, Keysight provides the
Software to U.S. government
customers under its standard
commercial license, which is
embodied in its End User License
Agreement (EULA), a copy of which
can be found at
http://www.keysight.com/find/sweula.
The license set forth in the EULA
represents the exclusive authority by
which the U.S. government may use,
modify, distribute, or disclose the
Software. The EULA and the license
set forth therein, does not require or
permit, among other things, that
Keysight: (1) Furnish technical
information related to commercial
computer software or commercial
computer software documentation that
is not customarily provided to the
public; or (2) Relinquish to, or
otherwise provide, the government
rights in excess of these rights
customarily provided to the public to
use, modify, reproduce, release,
perform, display, or disclose
commercial computer software or
commercial computer software
documentation. No additional
government requirements beyond
those set forth in the EULA shall
apply, except to the extent that those
terms, rights, or licenses are explicitly
required from all providers of
commercial computer software
pursuant to the FAR and the DFARS
and are set forth specifically in writing
elsewhere in the EULA. Keysight shall
be under no obligation to update,
revise or otherwise modify the
Software. With respect to any
technical data as defined by FAR
2.101, pursuant to FAR 12.211 and
27.404.2 and DFARS 227.7102, the
U.S. government acquires no greater
than Limited Rights as defined in FAR
27.401 or DFAR 227.7103-5 (c), as
applicable in any technical data.
Safety Notices
A CAUTION notice denotes a hazard.
It calls attention to an operating
procedure, practice, or the like that, if
not correctly performed or adhered to,
could result in damage to the product
or loss of important data. Do not
proceed beyond a CAUTION notice
until the indicated conditions are fully
understood and met.
A WARNING notice denotes a hazard.
It calls attention to an operating
procedure, practice, or the like that, if
not correctly performed or adhered to,
could result in personal injury or
death. Do not proceed beyond a
WARNING notice until the indicated
conditions are fully understood and
met.
iii
Contents
Overview6
What Is Keysight Licensing?7
License Types8
Recognize Your License Type10
Setting Up Licenses14
What License Management Tool Should I Use?15
Setting Up Floating Licenses20
Windows License Server Setup23
Linux License Server Setup27
Setting Up Node-Locked and Transportable Licenses31
Setting Up USB Portable Licenses32
Setting Up Module Licenses34
Advanced Licensing Configuration Options36
Accessing Floating Licenses through a Firewall37
Creating an Options File38
Licensing Environment39
Multiple Server Configurations40
Setting Up Three-Server Redundancy41
Keysight Licensing FAQs44
What Files and Paths are Used By Keysight Licensing?50
How to Troubleshoot Problems52
Floating License Problems59
Flexera Communication Problems66
Port Number Conflicts68
Glossary and Abbreviations70
Appendix: Manual License Setup72
Manual Setup: Node-Locked or Transportable Licenses on Windows73
Manual Setup: USB Portable Licenses on Windows76
Manual Setup: Floating Licenses on Windows80
Manual Setup: Node-Locked or Transportable Licenses on Linux81
Manual Setup: USB Portable Licenses on Linux84
Manual Setup: Floating Licenses on Linux89
Appendix: Migrating from Older Versions of Keysight Licensing94
iv
v
Overview
Overview
https://www.keysight.com/find/licensingdoc.
This document is intended for use by system administrators and end users who
perform advanced configuration tasks as an aid in managing Keysight licensing, which
utilizes the FlexNet licensing solution. For additional information on FlexNet, refer to
the FlexNet Publisher License Administration Guide. This document focuses on
recommendations and information specificto Keysight licensing.
Licensing governs the usage of a Keysight product. Depending on the product, you
may purchase one or more licenses to enable you to run a software application on a
computer or instrument, or to unlock specificfeatures of an application or instrument.
Keysight licensing is based on FlexNet Publisher and supports most of the FlexNet
licenses that have been issued by Keysight for its products over the years. Keysight
Licensing provides tools and processes for floating, USB portable, node-locked, and
transportable licenses.
In this section
What Is Keysight Licensing?
License Types
Recognize Your License Type
Administrator's Guide6
Overview
What Is Keysight Licensing?
Keysight Licensing includes these elements that work together to unlock applications
and features of Keysight products:
License client software, built into your licensed Keysight product, to manage
feature requests
License files, which contain licenses that unlock your licensed Keysight products
License management tools to help you install, view, and manage your licenses
For floating and counted licenses:
The FlexNet license server manager (
The Keysight vendor daemon(s) (
product licenses
Licensed client software:
Requests the use of a license when you try to use a licensed Keysight
application or feature
Lets you know if it cannot acquire a license
License files:
Are identified by the
Contain a unique signature and information that identifies the type and usage of
this license; see Recognize Your License Type
Are obtained from the Keysight Software Manager website, using the certificate
you received when you bought your Keysight product
Are installed on your computer or instrument, or on a floating license server, to
enable the use of your licensed product
License management tools:
Help you to install and view licenses, and to perform various management
operations (such as borrowing)
See What License Management Tool Should I Use? for information on the
specific tool(s) appropriate to your Keysight productsand licenses.
License server manager
Starts and maintains
agilent
Refers license checkouts (requests) to the appropriate vendor daemon
Keysight vendor daemons
Manage Keysight product licenses, mapping feature requests to the appropriate
license
For historical reasons, Keysight licensing uses either or both of the two vendor
daemons
licenses in use.
) listed in the VENDOR lines of the license file used to start
agileesofd
.lic
lmgrd
and
suffix
:
agileesofd
agileesofd
agilent
and any other vendor daemons (such as
and
, depending on the product(s) and type(s) of
agileesofd
agilent
lmgrd
) to manage servers
and/or
:
agilent
) to manage
lmgrd
7Administrator's Guide
Overview
License Types
Keysight Licensing providesthese types of licenses:
node-locked
USB portable
transportable
module
floating
Each license is either perpetual (permanent) or time-based (good for a limited
amount of time).
A node-locked license permits the licensed software to run on only one machine. Each
node-locked license is locked to an instrument or computer: The license is resident on
the hard disk of the system that it's locked to, and that system runs the licensed feature
or product. Trial licenses are node-locked, time-based licenses. Trial licenses are
issued for a particular instrument or computer and are provided free of charge for you
to try out a Keysight product.
A USB portable license is locked to a USB dongle (also called a USB key). Systems
that run the licensed feature or product must have the license file resident on their hard
disks, have a dongle driver installed, and have the dongle attached when they run the
licensed feature or product.
A transportable license is a type of node-locked license that can be unlocked from one
client host and then locked to another client host, via a network-enabled process
performed in conjunction with the Keysight Software Manager website.
Node-locked, transportable, and USB portable licenses may
be counted or uncounted. Counted licenses enable a specified number of a given
capability— for example, a given number of processesin a measurement application.
An uncounted license simply unlocks the licensed feature or application on the system
where it is installed.
A module license is locked to a PXI modular instrument and is used to enable
capabilities of that modular instrument.
Floating licenses (network licenses) reside on a license server (a separate computer)
and are checked out for use by Keysight products (instruments or applications), then
returned (checked in) when no longer needed so that they can be used on another
computer or instrument. Floating licenses are always counted; you purchase the count
of licenses that your users need to be able to use concurrently.
Some floating licenses can also be borrowed for a specified number of days. Once you
have borrowed a license, you can disconnect the licensed instrument or computer from
the license server and continue to use the license offline for the duration of the borrow
period. You can distinguish borrowable licenses by the BORROW keyword in the license
file.
Administrator's Guide8
Overview
See also
Recognize Your License Type
9Administrator's Guide
Overview
Recognize Your License Type
These examples illustrate some of the important differences among license types, and
some of the important properties of Keysight licenses. Your licenses may look similar to
these, or quite different, depending on the licensed product, time of issue, and other
factors.
Example 1: Node-locked license (unserved, permanent)
In the example above, the presence of HOSTID=005056905d85 indicatesthat this license
is tied to the host ID 005056905d85. The presence of a SERVER line indicates that this is a
served
license. To use this node-locked license, you'll need to run a license server
process locally on the machine where you will use the license.
The fourth line of this license, beginning with #Product:, is a comment. All lines
beginning with # are human-readable comment lines; there may be any number of
these in your license.
A USB portable license is tied to a USB key (dongle) rather than to a computer. The
host ID FLEXID=10-0b3bf1c2 identifies the USB key to which thislicense is tied. You can
use this license on any computer by installing the license file and a dongle driver on that
computer and plugging the corresponding USB key in to that computer.
As shown above, the INCREMENT line with no HOSTID indicates that this is a floating
license. It is tied to the license server whose host ID is 005056905d85, and uses port
27009, as indicated in the SERVER line. The BORROW keyword indicates that this license
can be borrowed (taken offline to be used for a limited time). In this case, the license
can be borrowed for up to 8760 hours (365 days).
This is a trial license. Typically, you can use a Keysight trial license for 30 days after you
receive it. It is implemented simply as a node-locked expiring license; in this case, the
expiration date is 22-may-2020.
Administrator's Guide12
13Administrator's Guide
Setting Up Licenses
This section describes how to set up Keysight Licensing, including licensestied to an
instrument or computer (via host ID), to a USB dongle (USB key), or to a PXI modular
instrument, as well as floating licenses (tied to a networked license server). These
setup instructions apply to both permanent and time-limited (including trial) licenses.
No matter what kind of licenses you have, you'll first need to obtain your license file(s)
and install the appropriate tools. Specific tools and additional setup steps vary
depending on what Keysight product(s) you're licensing and on the type of licenses
you'll be using: See What License Management Tool Should I Use?
Setting up licenses manually
In certain cases, you may not be able to install or manage your licenses with a Keysight
licensing tool; see What License Management Tool Should I Use? to determine if this
applies to you. If that is the case, you'll use FlexNet tools and some manual steps. The
manualsetup processes are described in Appendix: Manual License Setup.
Setting Up Licenses
Administrator's Guide14
Setting Up Licenses
What License Management Tool Should I Use?
Refer to your Keysight product documentation to determine which of the following
license management applicationsare appropriate for your product(s). In many cases,
the appropriate license management application is included in the installation of your
Keysight product, or is preinstalled on your Keysight instrument.
You can also use the Flexera license management tools for many licensing tasks.
These tools and the FlexNet Publisher License Administration Guide, which describes
their use, are included in the Keysight License Server download as well as in several of
the license management tool downloads.
License Management Tool Comparison
The vendor Name is found on the FEATURE or INCREMENT line of each license.
Keysight licenses may have either
depending on the licensed product and when the license was issued.
agileesofdoragilent
as the vendor Name,
vendor Name and other particulars of the license. Again, refer to your
Keysight product documentation to ensure you are using the best tool to
manage your licenses.
15Administrator's Guide
Setting Up Licenses
Keysight
PathWave
License Manager
Keysight License
Manager 6
Keysight License
Manager 5
Keysight Floating
License Manager
for EEsof EDA
Products
Nodelocked
licenses
Install
(
agileesofd
only), view
(agileesofd
and
agilent)
counted
nodelocked
(
agileesofd
only:
install,
view,
delete
Install,
view,
delete
(
agilent
only)
Install,
view,
delete
(
agileesofd
only)
Transportable
licenses
View
(agileesofd
and
agilent)
Install,
transport
(
agileesofd
only)
Not
supported
)
Install, view,
delete,
transport
(
agilent
Not
supported
only)
USB
portable
licenses
Install,
view
Install,
view,
delete
not
supported
Install,
view,
delete
Floating
licenses
Install,
view,
borrow;
configure
license
server (v.
2.3 and
later)
Install,
view,
delete,
borrow,
configure
license
server
not
supported
Install,
view,
delete,
configure
license
server
Keysight PathWave License Manager
Administrator's Guide16
Setting Up Licenses
PathWave License Manager is a new license management tool that can install, view,
and manage many of the latest Keysight product licenses. This tool will be installed
with your licensed Keysight software if it is appropriate for managing your licenses.
PathWave License Manager utilizes the
agileesofd
and
agilent
vendor daemons. It is
installed with your Keysight software product, if needed.
Keysight License Manager 6
17Administrator's Guide
Setting Up Licenses
This license management application allows you to manage floating and USB portable
licenses for a variety of software products and instruments.
You can also use the Keysight License Manager 6 to configure remote license servers
for sharing licenses across a network, or to configure a local license server (used with
certain types of node-locked licenses) on the computer or instrument where your
Keysight software is installed.
Keysight License Manager 6 utilizes the
agileesofd
vendor daemon. You can
download Keysight License Manager 6 at https://www.keysight.com/find/KLM6.
Keysight License Manager 5
This license management application allows you to manage node-locked and
transportable licenses for a variety of software products and instruments.
Keysight License Manager 5 utilizes the
agilent
vendor daemon. You can download
Keysight License Manager 5 at https://www.keysight.com/find/KLM5.
Keysight Floating License Manager for EEsof EDA Products
Administrator's Guide18
Setting Up Licenses
This license management application allows you to manage many types of licenses
specifically for EEsof EDA products.
You can also use the Keysight Floating License Manager for EDA to configure remote
license servers for sharing licenses across a network, or to configure a local license
server (used with EEsof EDA node-locked licenses) on the computer or instrument
where your Keysight software is installed.
The Keysight Floating License Manager for EDA utilizes the
agileesofd
vendor
daemon. You can download Keysight Floating License Manager for EDA
at https://www.keysight.com/find/eesof-flexnet-downloads.
This section describes the high-level setup process for floating licenses (tied to a
networked license server). The details depend on your license management tool; see
What License Management Tool Should I Use? These setup instructions apply to both
permanent and time-limited licenses. If you have already set up your license server,
and just need to add a new license, go to Add a Floating License, below.
Floating License Setup: First Time
To set up floating licensing, you'll need to configure the license server and the client
(the instrument or computer running the licensed Keysight product). The first time you
configure a particular license server machine, you'll need to install server software and
configure the license server process on the server machine.
You'll first need to choose a license server machine, install the Keysight License Server
software on that machine, install at least one license, and start the server process. For
details of initial license server setup, see:
Administrator's Guide20
Setting Up Licenses
Windows License Server Setup
LinuxLicense Server Setup
Then, you'll need to go to the client machine (the machine where the licensed Keysight
software will be used), install the licensed software and license management tool, and
configure it to get its licenses from the license server machine you just set up. For
details of client setup, see the Help for your license management tool.
To add a floating license to your license server:
Step 1: Obtain a license file
a. If you have ordered a licensed Keysight product, you'll receive (typically by
email) a license certificate. Note the order number and certificate number.
b. Determine the license server's host ID or the USB dongle ID in one of
these ways:
On the server machine, execute lmutil lmhostidto get the
FlexNet host ID directly.
On the server machine, execute getmac /v /fo list . Your host
ID islisted as the Physical Address of the Network Adapter.
If you want the license tied to a dongle, read the dongle ID directly
from the key or, with the dongle connected to your computer,
execute lmutil lmhostid -flexid.
c. Go to http://www.keysight.com/find/softwaremanager to obtain your
license file. Follow the instructionson screen to enter your order number,
certificate number, and host ID.
account and add the Software Manager capability.
d. Follow additional instructions to request a license file, which will be
emailed to you.
Step 2: Save the license file on the license server machine
If your license management tool supports license server setup (see What License
Management Tool Should I Use?), see your tool's Help for license installation
instructions. Otherwise, do the followin:
a. Ensure that your intended usage conforms to your purchased license
types. Your floating licenses may be single site, single region, or
worldwide licenses; you can find this information in the license files.
b. Make a copy of the license file on your hard disk, either:
to the location where you have installed past license files, or
if you do not have an existing location,
in
C:\ProgramData\Keysight\Licensing\Licenses\Server
(Windows) or
/opt/keysight/licensing/licenses/server
.(Linux).
c. Open or view the license files in the directory to ensure they all specify the
same port value (between 27000 and 27009, inclusive) in their SERVER
statements. If not, edit them to have the same port value. You will
21Administrator's Guide
experience licensing failures if the licenses have conflicting port numbers.
See Port Number Conflicts for more information.
Step 3: Restart the license service
Windows: In the Windows Services app, Restart the license server
service (such as EEsof EDA License Server).
If your license management tool supports license server setup, you can choose to
follow the prompts in your tool or consult the Help in the tool for detailed instructions.
PathWave License Manager (version 2.3 or later) and Keysight License Manager 6
support license server setup. See What License Management Tool Should I Use? for
information on other tools. The following steps describe license server setup using Flex
tools and manual steps.
Ensure that your chosen license server conforms to your purchased license types.
Your floating licenses may be single site, single region, or worldwide licenses; you can
find this information in the license files. For additional help on choosing a license
server, see the FlexNet Publisher License Administration Guide.
Determine your executable and license locations and stop any existing server process
Step 1:
a. Check whether there is already an
license server.
Windows: Run Task Manager. The process may be listed as
VendorDaemon agileesofd.
b. If you find such a process, determine the path to its executable:
i. Right-click the processin Task Manager.
ii. Select Properties.
iii. Make note of the full path, shown in the Location field.
c. Open a command prompt, go to the executable path, and run
d. In the LMTOOLS window, go to the Config Services tab and take note of
the Path to the license file. Thisis where you'll put your new licenses.
e. Close LMTOOLS.
f. Right-click the
Step 2: Install Keysight License Server on the license server machine
Keysight License Server.
a. On your license server machine, open your web browser and navigate to
http://www.keysight.com/find/licenseserver.
b. Download the
c. Extract the files, either:
to the executable location from Step 1 above, or
if you do not have an existing location, to
agileesofd
process in Task Manager and select End task.
agileesofd-<version>-<platform>.zip
agileesofd
process running on your
archive.
C:\Program
Files\Common Files\Keysight\Licensing\Agileesofd
lmtools.exe
.
.
Step 3: Obtain a license file
a. If you have ordered a licensed Keysight product, you'll receive (typically by
email) a license certificate. Note the order number and certificate number.
b. Determine the license server's host ID or the dongle ID in one of these
ways:
23Administrator's Guide
On the server machine, execute lmutil lmhostid to get the
FlexNet host ID directly.
On the server machine, execute getmac /v /fo list. Your host ID
is listed as the Physical Address of the Network Adapter.
If you want the license tied to a dongle, read the dongle ID directly
from the key or, with the dongle connected to your computer,
execute lmutil lmhostid -flexid.
a. Go to http://www.keysight.com/find/softwaremanager to obtain your
license file. Follow the instructionson screen to enter your order number,
certificate number, and host ID.
account and add the Software Manager capability.
b. Follow additional instructions to request a license file, which will be
emailed to you.
Step 4: Save the license file on the license server machine
a. Make a copy of the license file on your hard disk, either:
in the license file directory from Step 1 above, or
if you do not have an existing location, in
C:\ProgramData\Keysight\Licensing\Licenses\Server
b. Open or view the license files in the directory to ensure they all specify the
same port value (between 27000 and 27009, inclusive) in their SERVER
statements. If not, edit them to have the same port value. You will
experience licensing failures if the licenses have conflicting port numbers.
See Port Number Conflicts for more information.
c. If you want the license to be served from multiple servers, put a copy of
the license file on each server machine.
Setting Up Licenses
.
server manager and the vendor daemon.
To start the FlexNet license server manager (
lmgrd
) and vendor daemon (
agileesofd
and automate their restart upon PC reboot, configure a Windows service as follows:
Administrator's Guide24
)
Setting Up Licenses
The service will run under the local system account as the special
Server
user, which does not have special system privileges. This means
Local
you should consider the following:
The log file must be in a location that is writable by all users. If you
specify a log file location that is not writable, the service
will immediately exit, and will not indicate any errors (it returns an
exit code of 0 even though it encountered an error). Since the log
file was not writable, you will have no error message anywhere to
indicate what went wrong, or even that there was a problem.
The license files must be in a location that is readable by all users. If
you specify a location that isn't readable, the log file will contain an
error indicating that the license file couldn't be found.
Keysight recommendsyou put the log file and license files
somewhere under
C:\ProgramData\Keysight
, which will allow them
to inherit the appropriate permissions.
a. Run
lmtools.exe
from
C:\Program Files\Common
Files\Keysight\Licensing\Agileesofd
. The LMTOOLS window is
displayed.
b. In the Service/License File tab, select the Configuration using Services
option.
c. Click the Config Services tab and enter the following details. See the
NOTE above for additional information about paths.
i. Service Name: For compatibility with Keysight EDA products, use
the Name EEsof EDA License Server.
ii. Path to the lmgrd.exe file: Click Browse and specify the path to
If you have multiple license files for multiple Keysight products,
include them all.
Path to the debug log file: ClickBrowse and specify the path to the
debug log file on the license server (for example,
If your license management tool supports license server setup, you can choose to
follow the prompts in your tool or consult the Help in the tool for detailed
instructions. PathWave License Manager (version 2.3 or later) supports license server
setup. See What License Management Tool Should I Use? for information on other
tools. The following steps describe license server setup using Flex tools and manual
steps.
Ensure that your chosen license server conforms to your purchased license types.
Your floating licenses may be single site, single region, or worldwide licenses; you can
find this information in the license files. For additional help on choosing a license
server, see the FlexNet Publisher License Administration Guide.
License server setup...
Repeat the following steps on each license server. (For help on choosing a license
server, see the FlexNet Publisher License Administration Guide.)
Step 1: Determine your executable location and stop any existing server process
a. First, run ps -ef | grep agileesofd to see whether there is already an
agileesofd
b. If you find such a process, determine the path to its executable by
executing readlink -f /proc/<pid>/exe. Make note of this path.
c. Kill the
Step 2: Install Keysight License Server on the license server machine
Keysight License Server.
a. On your license server machine, open your web browser and navigate to
http://www.keysight.com/find/licenseserver.
b. Download the
c. Untar the files, either:
Step 3: Obtain a license file
a. If you have ordered a licensed Keysight product, you'll receive (typically by
email) a license certificate. Note the order number and certificate number.
b. Determine the license server's host ID in one of these ways:
process running on your license server.
agileesofd
process.
agileesofd-<version>-<platform>.tar.gz
to the executable location from Step 1 above, or
if you do not have an existing location, to
/opt/keysight/licensing/agileesofd
On the server machine, execute lmutil lmhostid to get the
FlexNet host ID directly.
.
archive.
you try to run lmutil, then you need to installthe Linux
Standard Base library . Use yum to install redhat-lsb.
On the server machine, execute /sbin/ifconfig -a
Examine the ifconfig results to find your Ethernet interface
27Administrator's Guide
Setting Up Licenses
(often called eth0) and use its hardware address (HWaddr). For
example, in the ifconfig output shown below, the host ID is
c. Go to http://www.keysight.com/find/softwaremanager to obtain your
license file. Follow the instructionson screen to enter your order number,
certificate number, and host ID.
account and add the Software Manager capability.
d. Follow additional instructions to request a license file, which will be
emailed to you.
Step 4: Save the license file
To save the license file for use by Keysight licensing:
a. Make a copy of the license file on your hard disk, either:
to the location where you have installed past license files, or
if you do not have an existing location, in
/var/opt/keysight/licensing/licenses/server
b. Open or cat the license files in the directory to ensure they all specify the
same port value (between 27000 and 27009, inclusive) in their SERVER
statements. If not, edit them to have the same port value. You will
experience licensing failures if the licenses have conflicting port numbers.
See Port Number Conflicts for more information.
c. Set the file permissions so that it can be read by
chmod a+r <fileName.lic>
This example gives all users read access to the license.
Step 5: Start the license server manager
.
lmgrd
. For example:
server.
Start the license server manager (
lmgrd
) and vendor daemon (
agileesofd
) on the
machine to which the license is tied as follows:
a. Change directory to the location of your server files (for example,
To automate the license server manager's startup upon system reboot, add something
similar to the following sample script in the system boot services directory or in
/etc/rc.d/init.d
#!/bin/sh
#
# Sample FlexNet startup script for restarting license server process
#
### BEGIN INIT INFO
# Provides: license server
# Required-Start: $network
# Required-Stop:
# Default-Start: 3 4 5
# Default-Stop:
# Description: Start License Server
### END INIT INFO
/opt/keysight/licensing/agileesofd/lmgrd -c
/var/opt/keysight/licensing/licenses -l
/var/log/keysight/licensing/log/license-server.log
echo "Starting license server process......"
sleep 5
.
Once you implement your version of the FlexNet startup script using the above sample,
follow the steps below to complete the automation:
1. Change to the system boot services directory
2. Create a startup script (for example,
keysight_lmgrd_restart
/etc/rc.d/init.d.
) in the system boot
services directory.
3. Insert your FlexNet startup script (above) into the startup script.