Setting Up Licenses for Windows Installation

This chapter provides license setup information for ADS on a Windows PC. (Alternatively, see Setting Up Licenses for UNIX and Linux Installation.) After you install ADS using the steps described in Installing Advanced Design System, you will need to set up the FLEXnet license manager and your ADS license file (license.lic) before you can run ADS.

License Installation Overview

Note
The Agilent License Information Tool is available to check your environment variable settings, display your license.lic file, and show your license and server status. Refer to Using the Agilent License Information Tool.

About FLEXnet

ADS uses Macrovision Corporation's Flexible License Manager (FLEXnet) software for all software security configurations. When you run the ADS Setup program, the FLEXnet software is installed at <installation folder>\licenses\bin where <installation folder> is the destination folder you specified when you ran Setup. For more information, see Using lmtools for FLEXnet.

ADS 2008 uses the utility lmtools with the FLEXnet software. This utility does not replace the steps in this chapter for license installation, but can help in the installation and use of FLEXnet licenses.

The utility can be found in the \ADS2008\licenses\bin folder and is named lmtools.exe. Using lmtools, you can:

For details on using FLEXnet and lmtools, refer to the Macrovision website at:

http://www.macrovision.com/

Choose Products > FLEXnet

Before Installing Your Licenses

ADS needs to be installed before licenses are installed. For details on installing ADS on a PC running Windows, please refer to Before You Begin Windows Installation and Installing Advanced Design System.

You must request and install new license codewords for ADS 2008. To learn how to request codewords, see Get Codewords for ADS 2008.

Installing Your Licenses

Use the steps in the following sections to install your ADS licenses.

The FLEXnet licensing system can use different methods to identify your PC and associate it with a license. The "hostid" (that is, the identifier by which FLEXnet recognizes your PC) can be in the form of a FLEXid hardware key attached to a port on the PC; it can also be the Ethernet address (also known as the "physical address") of the PC's LAN card. Before installing ADS licenses on your PC, you will need to do one of the following:

Installing a Hardware Key

One way to run the FLEXnet licensing system on your PC is to install the FLEXid hardware key (also called a dongle) on a parallel or USB port of your computer. In a node-locked environment, it is installed on the local machine. In a floating license environment, it is only required on the server machine.

Note
Before you install the key, make a note of the hardware key ID number on the key. If you have not already received your security codewords from Agilent EEsof, you will need to provide this number for your Codeword Request Form, as explained in the section, Determining License Type.

Installing the FLEXid Driver

Complete the following steps to install the latest FLEXid driver needed to license ADS. You need to do this only if you wish to lock your licenses to a hardware key. Be aware that this procedure requires system administrator privileges. Macrovision recommends that you install the FLEXid System Driver with their installer, which is included on the ADS PC Setup disk.

The installation program will attempt to load the FLEXid driver automatically; however, it may not be able to do so if your system has a FLEXid driver. In that case you will need to load it using the following steps.

To install the Macrovision FLEXid Driver:

  1. Place the ADS PC Setup disk in your DVD drive.
  2. If you wish to remove any existing FLEXid drivers, do the following using a command window:
    1. Change to the DVD drive.
    2. Locate the FLEXId_Dongle_Driver_Installer.exe file.
    3. Type FLEXid_Dongle_Driver_Installer/remove
      This starts the Macrovision FLEXid Cleanup Utility program.
    4. Click the Next button.
    5. When the process is complete, click Finish to close the utility.
  3. Select Start > Run (or use your Windows Explorer and skip the next step).
  4. In the Run box, click Browse.
  5. Change to the DVD drive.
  6. Locate and double-click the FLEXId_Dongle_Driver_Installer.exe file. This starts the Macrovision FLEXid Drivers installation program. For additional information, see the FLEXid_README.pdf file also located on the disk.
  7. Click the Next button.
  8. Select the features you want to install, then click the Next button.
  9. Click the Install button.
  10. When the process is complete, a dialog box with a message to restart your system is displayed.
  11. Click Finish.
  12. Restart your computer. The driver will not become active until your PC is rebooted.

Using the the Ethernet Address of the PC's LAN Card

Another way to run the FLEXnet licensing system on your PC is to read your LAN card's Ethernet address and have Agilent EEsof Business Support tie this identifier to your ADS codewords. To use this method, do the following:

  1. Make sure that you have TCP/IP and IPX/SPX network protocols loaded on your PC. The IPX/SPX protocol is required by FLEXnet. To get help on network protocols, refer to your Windows Help for Network Protocols:
    • Choose Start > Help.
    • Select the Index tab.
    • Enter network protocols.
    • Click the Display button.
    • Select To install a network protocol.
    • Click the Display button.
    • Follow the help instructions, which will ask you to click in the help dialog box to continue.
    • If you already have TCP/IP and IPX/SPX network protocols loaded, these items will be displayed. If you don't have both, choose the Add button and select the needed protocols from the list that appears. For example, select NWLink IPX/SPX Compatible Transport to add the IPX/SPX network protocol.
  2. Verify that you can read your LAN card's Ethernet address (also known as the "physical address"). For all versions of Windows, run the following FLEXnet command from the MS DOS Command Prompt:

    cd \ADS2008\licenses\bin
    lmutil lmhostid
    If lmutil lmhostid does not return the expected address, make sure you have the IPX/SPX (NWLink IPX/SPX Compatible Transport) protocol loaded.

    To obtain the address before you have ADS installed:

    Type ipconfig /all

Note
Before you can use your LAN card's Ethernet address, you will have to let Agilent EEsof Business Support tie this ID to your ADS codewords. If you have not already received your security codewords from Agilent EEsof, you will need to provide this number on your Codeword Request Form, as explained in the section, Determining License Type.

Determining License Type

Look at the INCREMENT lines in your license.lic file to determine the type of licenses you have. If the INCREMENT lines contain the strings HOSTID= and uncounted, then your licenses are node-locked. Otherwise, your licenses are floating. For example:

Node-locked License

INCREMENT ads_datadisplay agileesofd 2.7 08-nov-2007 uncounted \
                VENDOR_STRING="0000FF0FF00F : DXNLFPQ WZBCLQ2 AUJXJ2E IEKCKLI \
                WFYQNVM DNJU1YM LHYKAQC OM" HOSTID=0000ff0ff00f \
                START=11-nov-2007 SIGN="02D6 1B9C F5B8 0399 E483 2FF2 2BDD \
                7EBF 48B2 435E 2101 D7B6 3128 A42A 9D92 EA18 8CB5 C253 F6BB \
                0CD2 F189"

For Node-locked licenses, refer to, Installing Node-Locked Licenses.

Floating License

INCREMENT ads_datadisplay agileesofd 2.7 08-nov-2007 1 \
                VENDOR_STRING="8-5E7012345678 : DXNLFPQ WZBCLQ2 AUJXJ2E \
                IEKCKLI WFYQNVM DNJU1YM LHYKAQC OM" START=11-nov-2007 \
                SIGN="028C 541A A8DE F4CD 9796 2D38 BC5A 7588 F431 7E62 0601 \
                95CE F386 0A87 0B26 7EE7 7FEB 9DE4 60E9 6DDE 0340"

For Floating licenses, refer to, Installing Floating Licenses on a PC Server

Installing Node-Locked Licenses

The license.lic file with the node-locked codewords must be installed on each local machine. The default install path is: <installation folder>\licenses (for example, C:\ADS2008\licenses). Copy the license.lic file that you received via e-mail to the <installation folder>\licenses folder.

Note
Do not execute FLEXnet's lmgrd command for node-locked licenses. If you have started this program, stop it using the Task Manager or re-boot your PC.

Changing the License File Location

If you use the default license file location, your environment variables are set automatically. To use the license.lic file from a different location, you need to set the AGILEESOFD_LICENSE_FILE environment variable to point to the location.

To define the environment variable:

Your environment variable can be entered either as a user variable or as a system variable. The user variable affects only the currently logged-in user; the system variable affects all users. For a node-locked license, be sure you add the AGILEESOFD_LICENSE_FILE variable to the System variables, not the User variables.

If you are running multiple versions of ADS, do not include the HPEESOF_DIR variable in the System variables or User variables list boxes (and remove them have you have them).

Important
The AGILEESOFD_LICENSE_FILE environment variable overrides any LM_LICENSE_FILE settings you might have set up. The LM_LICENSE_FILE variable is used only when the AGILEESOFD_LICENSE_FILE is not set. As a result, using the AGILEESOFD_LICENSE_FILE variable will isolate your ADS license configurations from other applications that use the LM_LICENSE_FILE variable.

Installing Floating Licenses on a PC Server

Use the following sections to install your ADS floating licenses. You should have installed ADS before you complete these steps. For details on installing ADS on a PC running Windows, please refer to Installing Advanced Design System.

Important
Be sure to use the following information to update all existing license servers with the latest version of the FLEXnet software (e.g., lmgrd and lmutil). The software is installed with ADS 2008. Using older versions may cause license-encryption errors, invalid hostid results, and unsupported feature errors.

Verify that all multiple and redundant servers are updated including any license administration scripts in use. Run lmutil directly from the ADS 2008 installation location ($HPEESOF_DIR\licenses\bin) for information to help modify the scripts.

You will need to stop, then restart, the license server to make these updates.

Installing the License File

The license.lic file that implements FLEXnet security must be installed to run ADS. The default install path is: <installation folder>\licenses (for example, C:\ADS2008\licenses). Copy the license.lic file that you received via e-mail to the <installation folder>\licenses folder.

If your licenses will be served by a central server, have your system administrator install the license.lic file on the license server machine.

Entering the Hostname

Change the default hostname setting in your license file to the actual hostname of your license server. The license server is the machine that will serve the licenses on the network, and whose Ethernet address or FLEXID hardware key number, appears on the SERVER line.

For example, assuming that a machine with FLEXID hardware key number 8-5E700059B957 has a hostname of joshua. The SERVER line should read:

SERVER joshua FLEXID=8-5E700059B957

Starting with ADS 2002, all license.lic files are generated with SERVER lines with the following format:

SERVER <hostname> <hostid>

where:

<hostname> is set to unknown by default
<hostid> is the FLEXID hardware key number or Ethernet address of the license server.

You can also specify a specific TCP port number for license requests as follows:

SERVER <hostname> <hostid> <tcp_port>

To run ADS and check out a license from this license server, you will need to set the LM_LICENSE_FILE or AGILEESOFD_LICENSE_FILE as follows.

LM_LICENSE_FILE=2100@joshua
AGILEESOFD_LICENSE_FILE=2100@joshua

The AGILEESOFD_LICENSE_FILE environment variable overrides any LM_LICENSE_FILE settings you might have set up. The LM_LICENSE_FILE variable is used only when the AGILEESOFD_LICENSE_FILE is not set. As a result, using the AGILEESOFD_LICENSE_FILE variable will isolate your ADS license configurations from other applications that use the LM_LICENSE_FILE variable.

If you do not specify a TCP port number on the SERVER line, the license server will use the first available TCP port number in the range 27000 to 27009. In this case you will need to set the LM_LICENSE_FILE or AGILEESOFD_LICENSE_FILE as follows.

LM_LICENSE_FILE=@joshua
AGILEESOFD_LICENSE_FILE=@joshua

Note
Enter a specific port address on the SERVER line for improved license check-out performance. You may enter a port address outside the range of 27000 to 27009, as long as the address is not used elsewhere. Then set the environment variable AGILEESOFD_LICENSE_FILE or LM_LICENSE_FILE.

Setting the Vendor Daemon Path

By default, no path is specified for the agileesofd vendor daemon executable. This is acceptable as long as lmgrd and agileesofd are in the same folder when you start FLEXnet.

In the typical license configuration, lmgrd and agileesofd are both located in the \ads2008\licenses\bin folder. When lmgrd is started from the \ads2008\licenses\bin folder, it looks for agileesofd in the same folder. If agileesofd is not in the same folder as lmgrd, you must specify a path to it using the following syntax

VENDOR agileesofd c:\ads2008\licenses\vendors\agileesofd

Connecting to a License Server through a Firewall

If client systems connect to a license server through an Internet firewall set up on a Windows PC, you must also specify the port number the vendor daemon uses. You can specify the port number on the license file's VENDOR line. If the port is not specified, the default is chosen by the operating system at run time. If this port number is specified, there may be a delay restarting the vendor daemon until all clients have closed their connections to the daemon. Here is an example of a properly configured VENDOR line including the daemon path and port number:

VENDOR agileesofd c:\ads2008\licenses\vendors\agileesofd 27000

Some clients may timeout before they can connect to a license server through a firewall. The default timeout period is 0.1 second. If you need a longer timeout period, you can set the environment variable FLEXLM_TIMEOUT to a new value. Enter the value using microseconds. Agilent EEsof recommends trying one second. For example:

FLEXLM_TIMEOUT=1000000

Depending on your network, you may need to adjust the period so it is long enough to allow connections without slowing down simulations excessively.

Starting FLEXnet

FLEXnet can be started either manually or automatically. You must start the FLEXnet license manager daemon (lmgrd) on the license server(s) first. Once the license server(s) is running lmgrd and has started the vendor daemon(s), you can configure the other machines (clients) and user login accounts that need to access ADS.

To start FLEXnet you need the following.

If you have a three-server redundant configuration, you must start FLEXnet on all three servers before the licenses will be available on the network. Once you have FLEXnet running, you can configure the other machines (clients) and user login accounts that need to access ADS by setting the LM_LICENSE_FILE or AGILEESOFD_LICENSE_FILE.

Starting FLEXnet Manually

While starting FLEXnet manually is a good way to verify that FLEXnet starts correctly, it is generally not recommend for a server machine, because it requires a dedicated MS-DOS Command Prompt to be open at all times and it requires re-starting after rebooting the license server. Use the following steps to start the FLEXnet executable file, lmgrd.exe:

  1. From a MS-DOS Command Prompt, change to
    <installation_directory>\licenses\bin, where <installation_directory> is the folder where you installed ADS.
  2. Type the following command specifying the full path and location of the license file.
    lmgrd -app -c <installation_directory>\licenses\license.lic -l <inst_dir>\licenses\flex.log

To shut down the license manager, enter the following at a command prompt, from the <installation_directory>\licenses\bin folder:

lmutil lmdown -c <installation_directory>\licenses\license.lic

Starting FLEXnet Automatically

Ideally you should configure FLEXnet to start up automatically each time your system is booted by installing the license manager as a Control Panel service.

To start the license manager automatically:

  1. From a MS-DOS Command Prompt, change to
    <installation_directory>\licenses\bin, where <installation_directory> is the folder where you installed ADS.
  2. Enter the full path and filename of both the license executable file and the license.lic file. The default location for the executable file is installation_directory\licenses\bin\lmgrd.exe. (The flex.log file is useful for troubleshooting.)
    installs -e <path to lmgrd> -c <path to license file> -l <path to flex.log>
    For example: 
    installs -e d:\ADS2008\licenses\bin\lmgrd.exe -c d:\ADS2008\licenses\license.lic -l d:\ADS2008\licenses\flex.log

    If you don't specify a flex.log file using the "-l" option when you run installs.exe, FLEXnet creates a default log file in the system32 folder. While this default log file does not contain as much information, it can still be useful. This file is typically located in c:\winnt\system32\ and is named lmgrd.log or lmgrd.xxxx where "xxxx" is the process ID number of lmgrd.

  3. Activate the license server by starting the FLEXnet service using the Control Panel or by rebooting the system:

Start > Control Panel (in classic view) > Administrative Tools > Services

To remove the license manager from the service list and cancel the automatic FLEXnet startup:

From a system prompt, change to the license folder and enter: installs -r

To change the path to your license file, first remove the existing FLEXnet service using the installs -r command, reinstall FLEXnet using the new location, and then reboot your system.

Ensuring Access to the License File

You need to configure each client machine to access the license server and to check out a license. You can do this by using one of two methods:

Typically it is best to use the port@hos t syntax to set the AGILEESOFD_LICENSE_FILE to point to the license server.

set AGILEESOFD_LICENSE_FILE=27000@joshua

Where 27000 is the TCP port on the SERVER line in the license.lic file and joshua is the host name of the license server.

If your license server is set up to search for an available port, use the @host syntax to set the AGILEESOFD_LICENSE_FILE to point to the license server.

set AGILEESOFD_LICENSE_FILE=@joshua

You can also set the AGILEESOFD_LICENSE_FILE to point to the full path and filename of the license.lic file used by the license server.

Note
The AGILEESOFD_LICENSE_FILE environment variable will override any LM_LICENSE_FILE settings you might have set up. If AGILEESOFD_LICENSE_FILE is not set, LM_LICENSE_FILE will be used.

Accessing Licenses From a UNIX or Linux License Server

You can access licenses from a UNIX or Linux license server by doing the following:

  1. Set up the UNIX/Linux license server(s) to use FLEXnet version 11.4.1 or higher lmgrd and agileesofd daemons.
  2. Set up the PC to access the UNIX/Linux license server's license.lic file.

Setting Up the UNIX or Linux License Server

You must use version 11.4.1 or higher of the FLEXnet daemons lmgrd and agileesofd. Use the following commands to check the version of lmgrd and agileesofd on your UNIX/Linux license server:

cd $HPEESOF_DIR/licenses/bin
. / lmgrd -version 

 cd $HPEESOF_DIR/licenses/vendors
. / agileesofd -v

Use the following steps to update current FLEXnet daemons on your license server(s):

  1. Stop the current FLEXnet daemons on the license server: 
    cd $HPEESOF_DIR/licenses/bin
.  /lmutil lmdown -c ../license.lic
  2. Replace the following files with the supported FLEXnet version files: 
    $HPEESOF_DIR/licenses/bin/lmgrd
$HPEESOF_DIR/licenses/bin/lmutil
$HPEESOF_DIR/licenses/bin/agileesofd

    If you have more than one license server, make sure you do this on all of them.

  3. Restart the license daemons on the UNIX/Linux license server(s): 
    cd $HPEESOF_DIR/licenses/bin
. / lmgrd -c ../license.lic -l ../flex.log

Setting Up the Client(s)

Your PC can access the UNIX/Linux license server's license.lic file in either of two ways:

To set an AGILEESOFD_LICENSE_FILE system environment variable that points to the license.lic file, use the steps outlined in Changing the License File Location.

Selecting a License Bundle

This step is necessary only if you are using license bundles.

If you have been using license packages in previous versions, you should be aware that packages were replaced by license bundles in ADS 2003A. Bundles are an improvement over packages by giving you more control over which license bundles are used during an ADS session.

You must select a bundle when starting ADS to ensure a license bundle is being used. The Agilent License Preference Tool is available to help you make a selection. To learn how to select bundles using the preference tool, see Using the Agilent License Preference Tool.

Special Licensing Needs

Be sure to use the lmtools utility to install an ADS license on a server that is already running FLEXnet. For details on using FLEXnet, refer to the Macrovision website at:

http://www.macrovision.com/

Choose Products > FLEXnet

Using FLEXnet Options

An options file enables the license administrator to control the security parameters of FLEXnet. Specifically the license administrator can:

Creating an Options File

Use the desired options listed to create the options file using any text editor. Ideally, you should keep the options file in the same directory as your license.lic file. Also, add the pathname to the options file in the license.lic file as the fourth field on the VENDOR line for agileesofd as shown in the following example. (Remember to use the backslash ('\') character if the file contains wrapped lines.)

VENDOR agileesofd c:\ads2008\licenses\vendors\agileesofd \
c:\ads2008\licenses\agileesofd.opt

You can include comments in your options file by starting each comment with a pound sign '#'. Everything in the options file is case-sensitive. Be sure that user names and feature names, for example, are entered correctly. The available options are:

Use the following steps to create and use an options file. Details about each step located in previous sections:

  1. Create an options file with your required options.
  2. Modify your license.lic file so that the VENDOR or DAEMON line points to this option file as shown in this example: 
    VENDOR agileesofd c:\ads2008\licenses\vendors\agileesofd \
c:\ads2008\licenses\agileesofd.opt
  3. Start up your license server (lmgrd) that is pointing to your license file. You must stop it first if it is running. It's important that a message is displayed or recorded in the FLEXnet log verifying the license manager is using the options file. The following example shows that the license manager is using the agileesofd.opt file containing the TIMEOUTALL option set to 900 seconds: 
    17:35:14 (agileesofd) Using options file: "c:\ads2008\licenses\agileesofd.opt" 
17:35:15 (agileesofd) ALL FEATURES: INACTIVITY TIMEOUT set to 900 seconds
  4. Set AGILEESOFD_LICENSE_FILE to point to your license server.
  5. Run ADS.

Specifying the TIMEOUT Option

You can set a custom time-out period for simulator and library licenses using the TIMEOUT or TIMEOUTALL options. If you do not specify a time-out value in your options file or do not have an options file, a default two-hour limit is used. These time-out options apply to those application features that have explicitly implemented time-out via the heartbeat function. This includes licenses for the Analog/RF and Signal Processor simulators and for libraries, and do not affect licenses for the design environment and data display. The time-out option sets the amount of time a feature may remain idle before its license is released and reclaimed by the vendor daemon. The TIMEOUT option enables you to identify specific licenses, and the TIMEOUTALL affects all licenses (simulators and libraries).

To use TIMEOUT, add an entry for each feature to the options file using the following format:

TIMEOUT feature_name seconds
where:
feature_name is name of the feature.
seconds is the number of seconds before inactive license is reclaimed. The minimum value is 900 seconds (15 minutes). If you specify a time-out value smaller than the minimum, the minimum is used.

The option TIMEOUTALL works just like TIMEOUT, but applies to all features.

TIMEOUTALL seconds

Here are example entries you can include in your options file:

To set a time-out for the harmonic balance simulator to one hour (3600 seconds):
TIMEOUT sim_harmonic 3600

To set time-outs for multiple simulators to different periods:
TIMEOUT sim_linear 900
TIMEOUT sim_harmonic 3600
TIMEOUT sim_convolution 3600

To set a time-out for all simulators and libraries to one hour (3600 seconds):
TIMEOUTALL 3600

Updating the License File

If you have been running FLEXnet and receive updated codewords from Agilent EEsof, you can add the new licenses to the FLEXnet environment as follows:

  1. Replace the existing license.lic files on the license servers and clients with the new license.lic file.
  2. On the primary server, run lmutil lmreread. This causes the lmgrd on the primary server to re-read the license.lic file and update all of the other lmgrd processes on the network.
  3. After you have done this, you can run lmutil lmstat -a to verify that the license servers have received the new license information.

If this does not work, you may need to stop all of the lmgrd processes on your network and then restart them as described in Starting FLEXnet.

Merging Multiple Vendor Licenses

When you are running FLEXnet-licensed products from multiple vendors, you have three ways to prevent licensing conflicts during installation:

Each lmgrd can only read a single license file. With the first option you will have more license servers to monitor. With the third option you have only one server but multiple lmgrds to administer.

Your product's license file(s) define the license server(s) by hostname and hostid in the SERVER line(s) in the license file.

If you have two or more products whose license servers run on the same node (as specified by the SERVER lines in the license files), you may be able to combine the license files into a single license file.

Essentially, you can combine two license files under the following conditions:

  1. The number of SERVER lines in each file is the same.
  2. The hostid field of each SERVER line in one file exactly matches the hostid field of each SERVER line in the other file.

Some possible reasons license files may not be compatible are:

If your license files are compatible as described above, then you can combine license files and run a single lmgrd, as described in Combining License Files from Multiple Vendors If the license files are not compatible, then you must keep the license files separate and run separate copies of lmgrd for each license file, as described in the section, Using Separate License Files on the Same Server Node. For specific information about combining licenses for multiple versions of ADS, see Managing Multiple ADS Versions.

Important
There is virtually no performance or system-load penalty for running separate lmgrd processes.

Combining License Files from Multiple Vendors

If your license files are compatible, you can combine them using any text editor. To combine license files, read all of the compatible license files into one file, then edit out the extra SERVER lines so that only one set of SERVER lines remains. Write out this data, and you have your combined license file.

If you combine license files from multiple vendors, it is a good idea to keep a copy of the combined license file in each vendor's default license file location. This way, your users can avoid having to set AGILEESOFD_LICENSE_FILE, because each package finds its license information in the default place. On UNIX or Linux, you can do this with a symbolic link from each default location to the location of the combined license file.

FLEXnet Version Component Compatibility

When you combine license files for two different FLEXnet-licensed products, the products may not use the same version of FLEXnet. FLEXnet is designed to handle this situation. There are two basic compatibility rules for FLEXnet:

  1. A newer lmgrd can be used with an older vendor daemon, but a newer vendor daemon might not work properly with an older lmgrd.
  2. A newer vendor daemon (or lmgrd) can be used with an older client program, but a newer client program might not work properly with an older vendor daemon.

From these two compatibility rules come the simple rules for selecting which version of administration tools to use:

  1. Always use the newest version of lmgrd and the newest version of each vendor daemon.
  2. Use the newest FLEXnet utilities.

For specific application programs, you can use either the new or the old version (with the assumption that the vendor daemon for that application is at least as new as the application).

Using Separate License Files on the Same Server Node

You must run a separate copy of lmgrd for each license file. When you run multiple copies of lmgrd, there are two details to remember:

  1. The port number on the SERVER line of each license file must be unique. You can use a standard text editor to change the port number in each license file so that they are all different.
  2. You must make sure that you are using a compatible version of lmgrd when you start it up for a particular license file. This can be done by using an explicit path to lmgrd.

When running client programs (such as a licensed application), you can set the AGILEESOFD_LICENSE_FILE environment variable to point to multiple license files. For example, you may have a license file from vendor ABC and a license file from vendor XYZ with incompatible servers. You can place the license file from vendor ABC into:

c:\user\flexnet\abc.lic

and the license file from vendor XYZ into:

c:\user\flexnet\xyz.lic

then set the AGILEESOFD_LICENSE_FILE environment variable to point to both of them. The syntax is as follows:

AGILEESOFD_LICENSE_FILE=27000@server1;27000@server2;27000@server3

Note that each path is separated with a semi-colon.

AGILEESOFD_LICENSE_FILE can point to only one license file for FLEXlm v1.x applications.

Redundant License Servers

FLEXnet enables you to set up a redundant license server configuration. This involves configuring three license servers with one of the three servers functioning as the master server. If the master server goes down, one of the other two servers becomes the new master server, and the licenses remain available on the network.

Setting up redundant servers requires extra system administration and is not recommended unless you absolutely need it.

To set up redundant license servers, use the same FLEXnet procedures on all three servers. All three servers need to be up and running before your licenses will be made available.

Controlling License Path Settings

The lmutil utility provides the lmpath function which allows direct control over FLEXnet license path settings. You can use lmpath to add to, override, or get the current license path set in the registry. This enables you to change or view path settings without locating individual settings in the Windows registry on the PC or in the FLEXnet registry (.flexlmrc) on UNIX or Linux.

The lmutil utility is located in $HPEESOF_DIR\licenses\bin. This location must be in your PATH, or use the following command before running the utility:

cd $HPEESOF_DIR\licenses\bin

The usage for this function is:

lmutil lmpath { -status | -add | -override } { vendor_name | all } license_path_list

where

-status displays the current license path settings.

-add appends license_path_list to the front of the current license-path settings or creates the list of license-path settings, if it doesn't exist, initializing it to license_path_list. Duplicates are discarded.

-override overrides the existing list of license-path settings with the contents of license_path_list. If license_path_list is the null string, "", the specified list is deleted. For example:

  • lmutil lmpath -override agileesofd ""
    Deletes the value of AGILEESOFD_LICENSE_FILE from the registry.
  • lmutil lmpath -override vendor2 ""
    Deletes the value of VENDOR2_LICENSE_FILE from the registry.
  • lmutil lmpath -override all ""
    Deletes the value of LM_LICENSE_FILE from the registry.

vendor is a string naming a particular vendor daemon name. Affects the value of vendor _LICENSE_FILE. For example, use agileesofd to affect AGILEESOFD_LICENSE_FILE.

all refers to all vendor daemons. Affects the value of only LM_LICENSE_FILE.

license_path_list is the new path setting(s). On UNIX/Linux, this is a colon-separated list, and on Windows it is a semi-colon-separated list. If license_path_list is the null string, "", then the list is deleted for the specified vendor. Though you can enter specific license file names, you gain flexibility by entering only a path without a file name. This will include all *. lic files in the same location.

Note
Environment variable settings (set in your shell) always override these registry settings.

Checking the Status

Before you change license path settings, Agilent recommends that you display the current settings. To display the settings, enter the following commands:

lmutil lmpath -status

The following example status listing is from UNIX and is similar to PC and Linux listings:

lmutil - Copyright (C) 1989-2004 by Macrovision Corporation. All rights reserved.
Known Vendors:
_____________
agileesofd: /ads2003a/licenses/license.lic:/ads2008/licenses/license.lic
_____________
Other Vendors:
______________ 
/usr/local/flexnet/licenses/license.lic
Note
Where a path is set to a directory, each of the *.lic files are listed separately.

Changing License Path Settings

When adding or overriding path settings, lmpath sets the FLEXnet entry in the Windows registry on the PC, or changes the file $HOME/.flexlmrc on UNIX/Linux. Here are examples of how license settings may appear in each registry:
UNIX/Linux

AGILEESOFD_LICENSE_FILE = /ads2003a/licenses:/ads2008/licenses

Windows

Registry location:
My Computer\HKEY_LOCAL_MACHINE\Software\Agilent\ADS2008

Registry license path setting:
AGILEESOFD_LICENSE_FILE REG_SZ C:\ADS2008\licenses

To change license path settings, enter the appropriate command in a Command Prompt on Windows, or a terminal window on UNIX/Linux. You can adapt the following examples which change path settings for AGILEESOFD_LICENSE_FILE:

Manually Setting the License Bundle Preference

If you are using license bundles, you are aware that you must select a bundle prior to running ADS. Typically, bundles are selected by using the Agilent License Preference Tool. This tool is discussed in Using the Agilent License Preference Tool. However, system administrators and advanced users can manually configure environment variables when they need more bundle selection flexibility. Proper configuration using these environment variables control which licenses are used, and the systems using them.

The two environment variables that control bundle selection are:

ADS looks for these variables in the following locations in the order given here:

ADS first looks for AGILEESOFD_LICPREF_<hostname> in each of these locations. If ADS cannot find a value for AGILEESOFD_LICPREF_<hostname>, then ADS looks for AGILEESOFD_LICPREF. If AGILEESOFD_LICPREF is not found, no bundle is selected.

Examples

Accessing Licenses through a Firewall

There may be situations where it is necessary to check out FLEXnet licenses through a firewall (or router). This may occur when a license server is behind a company firewall and other sites or companies need to check out licenses.

Assuming your license agreement allows you to serve licenses in this manner, you can enable license checkout through a firewall by configuring your firewall to allow TCP communication through the TCP ports used by the license manager daemon (lmgrd) and any vendor daemons you will run.

For example, assume you have a license server serving EEsof EDA licenses and your license.lic file contains the following lines:

SERVER myserver 00809AC7123F8
VENDOR agileesofd c:\apps\flexnet\vendors\agileesofd
VENDOR agileesof c:\apps\flexnet\vendors\agileesof
DAEMON hpeesofd c:\apps\flexnet\vendors\hpeesofd

To set up your firewall to allow TCP access to the license server, you must specify a TCP port number for lmgrd on the SERVER line and for each vendor daemon on the VENDOR or DAEMON lines. For example:

SERVER myserver 00809AC7123F8 27005
VENDOR agileesofd c:\apps\flexnet\vendors\agileesofd port=1705
VENDOR agileesof c:\apps\flexnet\vendors\agileesof port=1706
DAEMON hpeesofd c:\apps\flexnet\vendors\hpeesofd port=1707
Note
After specifying TCP ports in your license.lic file, you must stop and restart your license server.

Next, configure your firewall or router to allow TCP communication through the TCP ports you specified in your license.lic file. In the example above this would be ports 27005, 1705, 1706, and 1707.

Finally, clients must set the AGILEESOFD_LICENSE_FILE environment variable to the port number assigned to the license server. Using the example above, the setting would be:

AGILEESOFD_LICENSE_FILE=27005@myserver

Once this has been done, clients outside of the firewall will be able to access licenses from your server.

Note
Some clients may timeout before they can connect to a license server through a firewall set up on a Windows PC. The default timeout period is 0.1 second. If you need a longer timeout period, you can set the environment variable FLEXLM_TIMEOUT to a new value. Enter the value using microseconds. Agilent EEsof recommends trying one second. For example:

FLEXLM_TIMEOUT=1000000

Depending on your network, you may need to adjust the period so it is long enough to allow connections without slowing down simulations excessively.

Managing Multiple ADS Versions

This section discusses how to manage the licenses for multiple versions of ADS.

Backward Compatibility of Codewords

The following table lists ADS versions with details of their license management:

Release Name License File Version Daemon Name FLEX Version License Environment Variable Default License File Location
ADS 1.5 1.5 hpeesofd FLEXlm 7.0g LM_LICENSE_FILE $HPEESOF_DIR/licenses/license.dat
ADS 2001 1.7 HPEESOFD_LICENSE_FILE
ADS 2002 1.9 agileesof FLEXlm 7.2h CRO AGILEESOF_LICENSE_FILE $HPEESOF_DIR/licenses/
ADS 2002C 2.1
ADS 2003A/C 2.3 agileesofd FLEXlm 8.2a CRO AGILEESOFD_LICENSE_FILE
ADS  2004A 2.34 FLEXlm 9.2a CRO
ADS 2005A 2.35 FLEXnet 10.1.3 CRO
ADS 2006 2.6 FLEXnet 10.8 CRO
ADS 2008 2.7 FLEXnet 11.4.1

The following table shows the codeword compatibility between various ADS releases. Note that codeword compatibility also depends on the whether the codeword was available in that release.

Codewords From This Release Will Work With This Release
ADS 2008 ADS 2006 ADS 2005A ADS 2004A ADS 2003C ADS 2003A ADS 2002C ADS 2002
ADS 2008 X X X          
ADS 2006   X X X        
ADS 2005A     X X X X    
ADS 2004A       X X X    
ADS 2003C         X X    
ADS 2003A         X X    
ADS 2002C             X X
ADS 2002             X X

Combining ADS Codewords with Other Agilent EEsof EDA Codewords

For ADS 2008, the vendor daemon agileesofd is used. This is the same vendor daemon that was used for ADS 2003A, 2003C, 2004A, 2005A, 2006A and 2006 Update. If you want to serve ADS 2008 licenses and earlier from the same server, you need to have the latest version of lmgrd, v9.2a, and two or three DAEMON lines in your license file, depending on how many versions you want to support. The ADS daemon names available are:

agileesofd - for ADS 2003A, 2003C, 2004A, 2005A, 2006A, and 2006 Update
agileesof - for ADS 2002 and 2002C
hpeesofd - up to and including ADS 2001

For example, the license file would include:

SERVER xyzmems 77a588a7 1700
VENDOR agileesofd c:\ads2008\licenses\vendors\agileesofd
VENDOR agileesof c:\ads2002C\licenses\vendors\agileesof
DAEMON hpeesofd c:\ads2001\licenses\vendors\hpeesofd

You would then add the INCREMENT lines for the different products to the file.

The name and extension of the license file are arbitrary (i.e., license.dat, license.lic or adslicenses.txt). By default, all ADS versions up to and including ADS 2001 look for a file named license.dat and all ADS versions from ADS 2002 to ADS 2008 look for a file named license.lic. You can use one of these names, or some other name you prefer. Whatever name you choose to use, make sure you set the environment variables to point to your license file.

The supported environment variables are:

For example, if the combined codeword file is named adslicenses.txt and you want to build a license file that contains ADS 2008, ADS 2003C, ADS 2002C, ADS 2001, and IC-CAP 2001 codewords, then:

Each version of ADS uses a certain search order to look for the environment variable:

Even though all versions of ADS will default to LM_LICENSE_FILE if that is the only environment variable that exists, it is recommended that you use the supported environment variables listed above.

Example of a Merged License File

SERVER solarone 80FB214D 1700
DAEMON hpeesofd c:\hfs\d1\local\licenses\hpeesofd 
VENDOR agileesof c:\hfs\d1\local\licenses\agileesof
VENDOR agileesofd c:\hfs\d1\local\licenses\agileesofd
#
# ADS 2001 codewords
#
INCREMENT Adapt_comp hpeesofd 1.5 03-nov-2002 5 EC7A98E3FB4AC8771142 \
        VENDOR_STRING=s=80FB214D
INCREMENT Ad_da_appkit hpeesofd 1.5 03-nov-2002 5 \
        1CCA189368AF358196C4 VENDOR_STRING=s=80FB214D
INCREMENT Ampsa_appkit hpeesofd 1.5 03-nov-2002 5 \
        0CBAB813D8101E34EB55 VENDOR_STRING=s=80FB214D
INCREMENT Analog_lib hpeesofd 1.5 03-nov-2002 5 9CEA88930822C5CF81AC \
        VENDOR_STRING=s=80FB214D
INCREMENT Tx_appkit hpeesofd 1.5 03-nov-2002 5 6C0A5873869F9624DFF5 \
        VENDOR_STRING=s=80FB214D
INCREMENT User_defined_model hpeesofd 1.5 03-nov-2002 5 \
        2CAAE8E326E3D9DD888B VENDOR_STRING=s=80FB214D
INCREMENT Verilog_code_gen hpeesofd 1.5 03-nov-2002 5 \
        FCAA489350CD03768D44 VENDOR_STRING=s=80FB214D
INCREMENT Vhdl_code_gen hpeesofd 1.5 03-nov-2002 5 \
        FC4A58B306109B640C5C VENDOR_STRING=s=80FB214D
INCREMENT Wcdma3g_des_lib hpeesofd 1.5 03-nov-2002 5 \
        DC7AA89389009E4B61BF VENDOR_STRING=s=80FB214D
INCREMENT Wcdma_des_lib hpeesofd 1.5 03-nov-2002 5 \
        7C0A38F308FA2C30CE3D VENDOR_STRING=s=80FB214D
INCREMENT Wlan_des_lib hpeesofd 1.5 03-nov-2002 5 \
        4C8A6893E259E6C86399 VENDOR_STRING=s=80FB214D
#
# IC-CAP 2001 codewords
#
INCREMENT a_si_tft agileesof 6.0 29-oct-2001 1 D0A4535DE290 \
        VENDOR_STRING=s=80FB214D
INCREMENT ac_driver agileesof 6.0 29-oct-2001 1 1A9EE36873A0 \
        VENDOR_STRING=s=80FB214D
INCREMENT analysis agileesof 6.0 29-oct-2001 1 025C2B939BD5 \
        VENDOR_STRING=s=80FB214D
INCREMENT curtice_statz_fet agileesof 6.0 29-oct-2001 1 7D88F11FEE4B \
        VENDOR_STRING=s=80FB214D
INCREMENT dc_driver agileesof 6.0 29-oct-2001 1 65C14D4C7948 \
        VENDOR_STRING=s=80FB214D
INCREMENT gummel_poon_bjt agileesof 6.0 29-oct-2001 1 8FB9632C0555 \
        VENDOR_STRING=s=80FB214D
INCREMENT ucb_bsim3 agileesof 6.0 29-oct-2001 1 BEDFA8C2810F \
        VENDOR_STRING=s=80FB214D
INCREMENT ucb_bsim4 agileesof 6.0 29-oct-2001 1 D454A8AB830D \
        VENDOR_STRING=s=80FB214D
INCREMENT ucb_mos2_mos3 agileesof 6.0 29-oct-2001 1 D9768F388827 \
        VENDOR_STRING=s=80FB214D
INCREMENT vbic_bjt agileesof 6.0 29-oct-2001 1 3DE6FB45CD8C \
        VENDOR_STRING=s=80FB214D
#
# ADS 2002C Codewords
#
INCREMENT ads_datadisplay agileesof 2.0 30-jun-2002 1 \
        VENDOR_STRING=80FB214D HOSTID=80fb214d SIGN="008E 5A70 FECF \
        8BEF 9B3A 8A67 7375 0A51 0940 A264 6B00 C335 666B 03E2 D8E7 \
        99A8 A0F9 9007 2AC4 EF7D E101"
INCREMENT ads_datadisplay agileesof 2.0 30-jun-2002 1 \
        VENDOR_STRING=80FB214D SIGN="01CB 4272 B241 5A67 A4C8 CADB \
        A080 FFB2 7796 6C29 EC02 C3A9 FD8A BE47 C0C0 F027 5552 947F \
        64CC 06BA 2201"
INCREMENT ads_drc agileesof 2.0 30-jun-2002 1 VENDOR_STRING=80FB214D \
        HOSTID=80fb214d SIGN="0138 3E48 7191 3703 8FFB 2614 067B 2A7E \
        203F 4F0C C900 79FE F186 9B1E 2B10 3B3D D650 2204 18CF 00C9 \
        3E3A"
INCREMENT trans_veriloggen agileesof 2.0 30-jun-2002 1 \
        VENDOR_STRING=80FB214D HOSTID=80fb214d SIGN="014D A119 4C16 \
        9831 16B3 B5C6 EFE7 ED11 D0AE F389 EA00 590B 0E0A E0CD 5E4D \
        9CE6 E6AD B27E 2CC4 8C1A 1D9D"
INCREMENT trans_veriloggen agileesof 2.0 30-jun-2002 1 \
        VENDOR_STRING=80FB214D SIGN="0332 DEBA 8398 B80F D2A0 0237 \
        BF97 0C7E 1CF3 CB15 2902 A5CB 47FA ECCB 9C6B BED2 E3D9 FBEB \
        EF84 FAFE 7AC8"
INCREMENT trans_vhdlgen agileesof 2.0 30-jun-2002 1 \
        VENDOR_STRING=80FB214D HOSTID=80fb214d SIGN="03D0 0C40 7E3C \
        E656 F8A8 ADF2 B161 97C1 CE6C DC0C DA00 A704 91C9 F5A0 30C6 \
        DA2A 60C0 A435 E003 02A0 C7A4"
INCREMENT trans_vhdlgen agileesof 2.0 30-jun-2002 1 \
        VENDOR_STRING=80FB214D SIGN="028D FD25 D0E4 AD1A A0B7 5D61 \
        E2A8 7CC2 8135 D605 8200 F200 39D8 E5AF 4B9E D240 3682 4BAA \
        D9BD 6FB3 E580"
#
#ADS2003C codewords
#
INCREMENT ads_datadisplay agileesofd 2.3 07-jul-2003 1 \
        VENDOR_STRING="00047518D858 : O2GAZUD WSGSONJ 2HNECZL 12WKCKE \
        LRXYGSO MWYFKGP AKBPONX LOYSO" HOSTID=00047518d858 SIGN="0246 \
        771A BBA2 A0D4 B29E 7371 6FF7 F3D9 161A 1204 EE00 2E92 8AC0 \
        1AF7 FAF9 5B2C B017 23F7 91E8 BF97 B9AD"
INCREMENT ads_drc agileesofd 2.3 07-jul-2003 1 \
        VENDOR_STRING="00047518D858 : QEGHABO KEYWTHV 1HEIWND JFAVQ2A \
        UJXJ2EW KYARWEQ GY" HOSTID=00047518d858 SIGN="02EC 9EA3 EE62 \
        BDBC 9793 019D 0551 FD3E 20DD D0C1 D301 DA95 9F79 16A8 5E11 \
        1B81 E7CC 90F8 68A0 E116 8F0B"
INCREMENT ads_encoder agileesofd 2.3 07-jul-2003 1 \
        VENDOR_STRING="00047518D858 : GONJAZX FHGGNAP BWOGIAH PBKWEYK \
        UCKGULO YSO2GAZ UDWSGS" HOSTID=00047518d858 SIGN="027B 178E \
        2893 8446 A5C4 0990 830E CC2C F215 528B 6401 9B93 9540 A54C \
        B85A A68E 0049 200F 1685 96D1 FD7F"
INCREMENT ads_layout agileesofd 2.3 07-jul-2003 1 \
        VENDOR_STRING="00047518D858 : BUYPSCY ESZGY2G PVZBPON XODFINY \
        IUIUACJ EFQGAUY XLYSX" HOSTID=00047518d858 SIGN="032E E2FE \
        1D41 5386 F290 C7AA 207B 20C6 9187 D2D5 0D00 7DB9 8FF8 531A \
        9947 9A9D 5D72 A8E6 9807 3037 F7EA"
#
# ADS2008 codewords
#
INCREMENT ads_datadisplay agileesofd 2.7 08-nov-2007 1 \
                VENDOR_STRING="8-5E7012345678 : DXNLFPQ WZBCLQ2 AUJXJ2E \
                IEKCKLI WFYQNVM DNJU1YM LHYKAQC OM" START=11-nov-2007 \
                SIGN="028C 541A A8DE F4CD 9796 2D38 BC5A 7588 F431 7E62 0601 \
                95CE F386 0A87 0B26 7EE7 7FEB 9DE4 60E9 6DDE 0340"
INCREMENT ads_schematic agileesofd 2.7 08-nov-2007 1 \
                VENDOR_STRING="8-5E7012345678 : KSGSOTJ D1JYAKF UZJFEJI \
                U2CRZDW FYANHIW HKMNMAU FQ1AQPJ UGW" START=11-nov-2007 \
                SIGN="02B0 5CFB 3F35 006F CDC5 1BBE DE50 831E 54DC A024 A301 \
                A491 42EA A1AA 3E41 C43D 5B63 E82D 3B51 8961 005D"
INCREMENT mdl_systemlib agileesofd 2.7 08-nov-2007 1 \
                VENDOR_STRING="8-5E7012345678 : PGNPGMU IWQUFPY PNDJKYU \
                GNHSULC KL2RXY2 NXAHEGC TLRDCYB RW1Q" START=11-nov-2007 \
                SIGN="02E9 3C03 1616 0BC9 5E70 C088 5D86 770F E8D4 862C D803 \
                E25B CDD5 EB9D AA31 FD4B 2C30 ED41 4635 3420 A4FD"
INCREMENT sim_convolution agileesofd 2.7 08-nov-2007 1 \
                VENDOR_STRING="8-5E7012345678 : DSXUYDA CHECD1Y 2NMAJPB \
                CESQD2M JX2LGBG QWPS1OK RTEIQGA UYDLY" START=11-nov-2007 \
                SIGN="0153 1869 9B6E C851 5225 A333 0727 E795 BE74 8C5D 0302 \
                E9BC E165 4F3D E4D4 D7BF E530 3CC5 B760 830E 9C95"

Using the Agilent License Information Tool

The Agilent License Information Tool is available to check your environment variable settings, display your license.lic file, and show your license and server status.

You can access this tool in three ways:

For a current list of codewords available from Agilent EEsof with product descriptions and part numbers, see http://www.agilent.com/find/eesof-cwtables.

Using the Agilent License Preference Tool

This section applies only to customers who have purchased license bundles.

If you have been using license packages in previous versions, you should be aware that license bundles replaced license packages beginning in ADS 2003A. License bundles are either Pay-Per-Use License (PL) bundles, or Limited Term Package (LTP) bundles. Typically, only PL or LTP bundles are available on a system - not both. A bundle looks like any other INCREMENT line in the license.lic file, but ADS recognizes the feature name as a collection, or bundle, of individual features. When ADS checks out the license bundle, it enables all the functionality associated with the individual features.

You must select a license bundle when starting ADS, and the License Preference Tool is available to help you make a selection. This sets the environment variable AGILEESOFD_LICPREF_<hostname>. Since you cannot check out more than one bundle, you have more control over which license bundles are used during an ADS session. You only need to run the License Preference Tool when you want to change the latest bundle selection. If you need more bundle selection flexibility to control which licenses are used on selected systems, see Manually Setting the License Bundle Preference.

Running the License Preference Tool

To run the License Preference Tool:

UNIX/Linux There are two ways to start the License Preference Tool. In a terminal window:

Windows There are two ways to start the License Preference Tool:

C:\ADS2008\bin\ads.exe -p

This runs the License Preference Tool every time you start ADS.

The License Preference window appears similar to the figures below. It enables you to view the available bundles and their features, and select bundles.

License Preference Tool with ltp_analog Selected

License Preference Tool Showing ltp_analog Features

How the License Preference Tool Works

Bundle-Selection Rules

The License Preference Tool controls bundle selection using the following rules. A warning message appears for any incorrect selection.

If you are using Limited Term Package Bundles

If you are using Pay-Per-Use License Bundles

 

Privacy Statement  | Terms of Use  | Legal | Contact Us  | © Agilent 2000-2008 

Contents
Additional Resources