Setting Up Licenses for UNIX and Linux Installation

Use the following information to set up licenses for ADS on UNIX and Linux systems. 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.

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 Linux systems, you can use one of the following methods to run the FLEXnet licensing system on your PC:

For information on installing a FLEXid hardware key, see Installing a Hardware Key on Linux.

For information about linking your LAN card's Ethernet ID to your ADS codewords, see Get Codewords for ADS 2008.

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

http://www.macrovision.com/

Choose Products > FLEXnet

Installing Licenses

You must request and install new license codewords for ADS 2008. To learn how to request codewords, see Get Codewords for ADS 2008. To install and configure your new license file, complete the steps in the following sections.

Note
If you are using the Mentor Graphics IFF interface for ADS, you need to install Mentor codewords in a separate procedure. Obtain information from your Mentor Graphics representative.

Installing a Hardware Key on Linux

One way to run the FLEXnet licensing system on your PC is to install the FLEXid hardware key (also called a dongle) on your computer's USB port. 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.

To install the hardware key, see the FLEXid_README.pdf file located in the UNIX/dongle_sup directory on the ADS DVD. This directory also contains the files needed to install a USB hardware key. For the most up-to-date files, contact your hardware key vendor.

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.

For information about linking your LAN card's Ethernet ID to your ADS codewords, see Get Codewords for ADS 2008.

Save the License File

When you receive your codeword file from Agilent EEsof Business Support, it will be called license.lic. Save the license.lic file using the same file name. Most codewords are distributed by e-mail.

Edit the License File

Edit your license.lic file to correct the SERVER line and add information to the VENDOR line. Refer to SERVER Line Guidelines and VENDOR Line Guidelines for details. You can use the Agilent License Information Tool to check your environment variable settings, display your license.lic file, and show your license and server status. For details, refer to Using the Agilent License Information Tool.

Note
Each line in the license.lic file must be a single continuous line with each field separated by a single space. You may line wrap lines using the backslash ('\') character, but be very careful not to add a space after the backslash. Otherwise, you can remove the backslash and make each INCREMENT line one continuous line.

Node-Locked File

The codeword file must follow the format shown in the following example. This example is from a node-locked file where the quantity, displayed on the first line after the date, is typically "1":

SERVER unknown 81AAAAAA
VENDOR agileesofd
INCREMENT ads_datadisplay agileesofd 2.7 08-nov-2007 1 \
                VENDOR_STRING="81AAAAAA : DXNLFPQ WZBCLQ2 AUJXJ2E IEKCKLI \
                WFYQNVM DNJU1YM LHYKAQC OM" HOSTID=81aaaaaa START=11-nov-2007 \
                SIGN="0169 4457 1B00 5266 852D 7813 5FB6 F38F 941A 1D0F E300 \
                F868 5245 2627 CF7B 03B9 037F 9F0F 6BAE 32F6 321C"
INCREMENT ads_layout agileesofd 2.7 08-nov-2007 1 \
                VENDOR_STRING="81AAAAAA : KSGSOTJ D1JYAXW BOCLRMW 2YNB2HN \
                GFVU2LG FQ1AQPJ UGW" HOSTID=81aaaaaa START=11-nov-2007 \
                SIGN="0115 CEDE 58A8 A734 FF5C 8AC8 A3AC DAE6 FD7E E9D2 C002 \
                EB4B 0FF8 884C 61BE 84D7 AB0F A3E2 47EA EC43 A5E6"
INCREMENT ads_schematic agileesofd 2.7 08-nov-2007 1 \
                VENDOR_STRING="81AAAAAA : NNWCSOI WSVFWVZ JOXDHFS NRMW2YN \
                BHAHUW2 JMAJGIJ OEYHM1W ST" HOSTID=81aaaaaa START=11-nov-2007 \
                SIGN="03E6 6359 6509 5297 45E2 6EB6 DBAF B148 04BF DE83 C502 \
                E872 86AA 522C 9257 369B BE71 A3F5 4FDE 16E2 F13F"
INCREMENT mdl_multilayer agileesofd 2.7 08-nov-2007 1 \
                VENDOR_STRING="81AAAAAA : TS1OKRT EIQGAUY DLYSXUY LUTGOHK \
                ULCKL2R XYPNPHN EFKNVMD NGCWP" HOSTID=81aaaaaa \
                START=11-nov-2007 SIGN="0333 DFD8 FD38 B049 9935 34CD A24B \
                91DF 8BE5 3E17 3D03 3CAB 88C2 4239 D021 526B 45F1 E539 FA55 \
                B415 52C9"
INCREMENT mdl_rfelements agileesofd 2.7 08-nov-2007 1 \
                VENDOR_STRING="81AAAAAA : WGPLO1S OVRAEOK EYWZHVU DEAAKNJ \
                F1GR2AB PXJEQW1 GJXMAJC OM" HOSTID=81aaaaaa START=11-nov-2007 \
                SIGN="01DF 9875 C78C 73C9 30C8 29C1 1C03 8629 6D57 E3C8 B303 \
                7198 9355 4B6C 1D5D 08B3 7628 C27C FA84 BD76 64DB"

Floating-License File

The codeword file for a floating license is the same as the previous node-locked file example, with these exceptions:

Below is a sample of a section of a floating-license file:

SERVER unknown 77542052

VENDOR agileesofd
INCREMENT ads_datadisplay agileesofd 2.7 08-nov-2007 1 \
                VENDOR_STRING="2002002002 : DXNLFPQ WZBCLQ2 AUJXJ2E IEKCKLI 
                WFYQNVM DNJU1YM LHYKAQC OM" START=11-may-2007 SIGN="03CC 8B82 \
                5582 2A7F 7A5D B54F 05C8 ED12 3789 AFD6 DB00 D838 8120 E013 \
                DF09 F741 CD95 4240 7B56 C012 822E"
INCREMENT ads_schematic agileesofd 2.7 08-nov-2007 1 \
                VENDOR_STRING="2002002002 : KSGSOTJ D1JYAKF UZJFEJI U2CRZDW \
                FYANHIW HKMNMAU FQ1AQPJ UGW" START=11-may-2007 SIGN="023A 5C67 \
                FFF1 FB55 24B7 0298 23AD 9480 0B84 2BCF 6A00 D20D FA99 C216 \
                3189 0C0A 2CDA C208 EE6F C153 A672"
INCREMENT mdl_adv_comm agileesofd 2.7 08-nov-2007 1 \
                VENDOR_STRING="2002002002 : LCSOIWS VFWVZJX WWCYUN1 AJUCJXZ \
                DIUCJYZ DWSMCTE NHM1WST NW" START=11-may-2007 SIGN="023C B57A \
                DF45 672E 5679 6C4F F705 48AC A4C9 4568 B600 356D AC99 EDDA \
                E523 160F 9BEB D788 95FA D551 30F3"
INCREMENT mdl_ant_array agileesofd 2.7 08-nov-2007 1 \
                VENDOR_STRING="2002002002 : NGMUIWQ UFPCUTQ UALAXBK TGR2ABP \
                XJ2QGPB OGUAMGF VRW1QGN P" START=11-may-2007 SIGN="0318 C721 \
                85CE 15F3 99EB 79F8 9CDA 3E1A CA1B 6DA5 6B00 DE35 4002 077B \
                32FB E942 2733 3557 1308 A52D B1FC"
INCREMENT mdl_ant_cdma agileesofd 2.7 08-nov-2007 1 \
                VENDOR_STRING="2002002002 : EHABUQQ QVHABUC T2EDLTF SUKRXYA \
                GIAJGJU 1YMLHYK AQCOMXN" START=11-may-2007 SIGN="01AD 66A1 \
                3949 C2CC E75B E2F2 7C64 6671 9774 1EE2 0F01 CDDE 20DB 672C \
                8180 ADBE E62D 544B B6D2 E17E 30D2"

SERVER Line Format

The SERVER line, by default, has the following format:

SERVER hostname hostid [port]

where:

hostname is the network name of the machine whose hostid appears in field 3 of the SERVER line. Use one of the following commands to read the hostname for your system:

Operating System Command
Red Hat Linux /bin/hostname
Solaris /bin/hostname

hostid is the unique machine ID of the license server machine running Solaris. On Linux, it is either the unique machine ID of the license server machine or the LAN card's Ethernet ID. Use one of the following commands to read the hostid for your system:

Operating System Command
Red Hat Linux /sbin/ifconfig
Solaris /bin/hostid

port is an optional entry naming the TCP/IP port number that the license server will listen at for license requests. An example port number is 27000.

SERVER Line Guidelines
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. Also, set the environment variable AGILEESOFD_LICENSE_FILE as described in "Place License File".

VENDOR Line Format

The VENDOR line, by default, has the following format:
VENDOR daemon_name [daemon_path] [options_file_path] [port]

where:

daemon_name is the name of the vendor daemon.

daemon_path is an optional entry specifying a path to the vendor daemon.

options_file_path is an optional entry specifying a path to the FLEXnet options file.

port is an optional entry naming the daemon TCP/IP port number to use. A port number must be used when connecting to the daemon through a firewall.

VENDOR Line Guidelines
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.

INCREMENT Line Format

The INCREMENT lines must have the following format:

INCREMENT feature vendord ver exp num vendorstring hostid sign

where:

feature is the name of the feature licensed by this line.

vendord is the name of the vendor daemon that will manage this feature.

ver is the version of the feature licensed by this line.

exp is the expiration date of this license.

num is the number of licenses this line enables.

vendorstring is the CPU ID of the primary license server.

hostid is an optional field. If this field exists, it is the hostid of the machine that this license is node-locked to. Only the machine whose hostid appears in this field may checkout this license.

sign is the encrypted codeword.

INCREMENT Line Guidelines

Place License File

A copy of the license.lic file must be placed on all SERVER machine(s) listed in the license.lic file.

License Placement Guidelines

Start the License Server (lmgrd)

Use the following procedure and guidelines to start the license server, lmgrd, on the SERVER machine.

Important
Be sure to use the following guidelines 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.

Guidelines for Starting lmgrd

To start lmgrd:

Change the directory to where lmgrd resides on the SERVER machine and execute lmgrd. For example:

cd $HPEESOF_DIR/licenses/bin
./lmgrd -c ../license.lic > ../flex.log

The login executing lmgrd must have full permissions to the licenses/bin directory and at least write permissions to the directory specified for flex.log.

All error, warning and status messages will be redirected to the flex.log file. After starting lmgrd, wait approximately 30 seconds, then look at the contents of flex.log to see if there are any errors that need to be corrected.

To verify that the licenses are available:

Make sure that the flex.log file does not contain any errors, then run lmstat as follows:

cd $HPEESOF_DIR/licenses/bin
./lmutil lmstat -a -c ../license.lic | more

Or, you may launch the Agilent License Information Tool to do this. Refer to Using the Agilent License Information Tool for more information.

If the licenses are available, you should see a listing similar to the following:

lmutil - Copyright \(C\) 1989-2004 Macrovision Corporation. All rights reserved
Flexible License Manager status on Mon 9/22/2007 12:42
License server status: 27000@joshua
    License files on joshua: ads2008/licenses/bin/../license.lic:
    joshua: license server UP \(MASTER\) v10.1
Vendor daemon status \(on joshua\):
  agileesofd: UP v10.1
Feature usage info:
Users of ads_schematic: \(Total of 3 licenses available\)
Users of ads_layout: \(Total of 3 licenses available\)
Users of trans_iges:  \(Total of 3 licenses available\)
Users of trans_dgsii:  \(Total of 3 licenses available\)
Users of trans_iff:  \(Total of 3 licenses available\)
Users of ads_lite:  \(Total of 3 licenses available\)
Users of ads_datadisplay:  \(Total of 3 licenses available\)
Users of sim_linear:  \(Total of 3 licenses available\)
Users of sim_harmonic:  \(Total of 3 licenses available\)

Provide Access to Licenses

Before attempting to start ADS, you must configure each user's login environment to allow access to the licenses on the SERVER machine(s). To do this you need to configure the environment variable named AGILEESOFD_LICENSE_FILE in the user's .profile or .cshrc.

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.

For example:
C Shell:

setenv AGILEESOFD_LICENSE_FILE $HPEESOF_DIR/licenses/license.lic

Bourne/Korn Shell:

AGILEESOFD_LICENSE_FILE=$HPEESOF_DIR/licenses/license.lic
export AGILEESOFD_LICENSE_FILE

You can avoid the need to have a copy of the license.lic file directly on the machine running ADS by setting AGILEESOFD_LICENSE_FILE as follows:

AGILEESOFD_LICENSE_FILE=<port>@<SERVER_hostname>

where

port is the TCP port number from the SERVER line(s) of the license.lic file.

SERVER_hostname is the network name of a SERVER machine serving ADS licenses. This must be a name that the SERVER is known by on the network. You should be able to successfully ping this name from the machine that will run ADS.

Or, if your license server is set up to search for an available port, your AGILEESOFD_LICENSE_FILE should read:

AGILEESOFD_LICENSE_FILE=@<SERVER_hostname>

For example,

C Shell:

setenv AGILEESOFD_LICENSE_FILE 27000@joshua

OR

setenv AGILEESOFD_LICENSE_FILE@joshua

Bourne/Korn Shell:

AGILEESOFD_LICENSE_FILE=27000@joshua

export AGILEESOFD_LICENSE_FILE

OR

AGILEESOFD_LICENSE_FILE=@joshua

export AGILEESOFD_LICENSE_FILE

The syntax to access multiple license servers is as follows.

C Shell:

setenv AGILEESOFD_LICENSE_FILE 27000@server1:27000@server2:27000@server3

Bourne/Korn Shell:

export AGILEESOFD_LICENSE_FILE=27000@server1:27000@server2:27000@server3

However, in this case, "server" should be replaced by the actual license server name or IP address, and the "27000" may need to be changed to the actual port number on the license server. Note that the list of servers is separated by colons (:). For details on running FLEXnet-licensed products from multiple vendors refer to Merging Multiple Vendor Licenses.

Using a UNIX/Linux-to-PC Floating License

A Windows PC system can access the UNIX or Linux license server's license.lic file in either of two ways:

Conversely, the license server can be a Windows PC with a floating license locked to a LAN card or dongle hardware key and the UNIX/Linux computer can be set to point to it in the same way by using its host name or IP address.

Automating FLEXnet License Manager Startup

You can automate the FLEXnet startup so that lmgrd is started automatically each time the license server machine is rebooted by adding the following three lines for a startup routine to the appropriate rc file for your operating system:

/ads/licenses/bin/lmgrd -c /ads/licenses/license.lic > /ads/licenses/flex.log &
echo "Starting Agilent EEsof FLEXnet license daemon......"
/usr/bin/sleep 5

Note
Be sure to change all references to /ads to the actual path of your Agilent EEsof software installation directory.

Following are instructions for the supported operating systems:

  1. Change to the appropriate directory:
    /etc/rc.d/init.d (Linux)
    /etc/rc3.d (Solaris)
  2. Create a file in this directory named Sagileesofd.
    Note
    The S is capitalized. All other letters are in lower-case.
  3. Place the FLEXnet startup routine (shown above) into this file.
  4. Set the permissions for this file as follows:
    chmod 755 Sagileesofd
    chown root Sagileesofd
    chgrp sys Sagileesofd
  5. For Linux license servers, create the following soft links:
    ln -s /etc/rc.d/init.d/Sagileesofd rc3.d/S99Sagileesofd
    ln -s /etc/rc.d/init.d/Sagileesofd rc4.d/S99Sagileesofd
    ln -s /etc/rc.d/init.d/Sagileesofd rc5.d/S99Sagileesofd

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

Use the following information to accommodate any special licensing needs you may have. 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 below 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 /ads2008/licenses/vendors/agileesofd \
/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 Installing Licenses:

  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 /ads2008/licenses/vendors/agileesofd \
/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: "/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 the section "Installing Licenses".

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.

More precisely, 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".

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, merge 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 and 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:

/user/flexnet/abc.lic

and the license file from vendor XYZ into:

/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

You can set up a redundant or backup license server(s), in case a primary server is unavailable. If your license.lic file has the maximum number of SERVER lines (three), you have a redundant license server configuration. The license setup is identical to a single SERVER configuration, with the exception that no licenses will be available until a majority of the license servers are running. That is, if you have three SERVER lines, at least two must be up and running before any licenses will be available for checkout. Be sure that the FLEXnet software is loaded and running on each server.

Note
If you have more than one SERVER line in the license.lic file, you must start lmgrd on all the SERVER machines to enable the licenses.

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 and 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 and 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 Linux and Windows 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 and Linux. Here are examples of how license settings may appear in each registry:
UNIX and 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 and 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

AGILEESOFD_LICPREF_ALPHA=pl_desenv

to the configuration file

$HOME/hpeesof/config/hpeesof.cfg
where $HOME is Joe's home directory

AGILEESOFD_LICPREF_BETA=pl_ui and
AGILEESOFD_LICPREF=ltp_mmic

to the configuration file

$HPEESOF_DIR/custom/config/hpeesof.cfg

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 /apps/flexnet/vendors/agileesofd
VENDOR agileesof /apps/flexnet/vendors/agileesof
DAEMON hpeesofd /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 /apps/flexnet/vendors/agileesofd port=1705
VENDOR agileesof /apps/flexnet/vendors/agileesof port=1706
DAEMON hpeesofd /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 releases 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, 2006 Update, and 2008. 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, 2006 Update, 2008
agileesof - for ADS 2002 and 2002C
hpeesofd - up to and including ADS 2001

For example, the license file would include:

SERVER hpnmems 77a588a7 1700
VENDOR agileesofd /ads2008/licenses/vendors/agileesofd
VENDOR agileesof /ads2002C/licenses/vendors/agileesof
DAEMON hpeesofd /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 200A 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 /hfs/d1/local/licenses/hpeesofd 
VENDOR agileesof /hfs/d1/local/licenses/agileesof
VENDOR agileesofd /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
#
# 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
#
# 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"
#
#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"
#
# ADS2008 codewords
#
INCREMENT ads_datadisplay agileesofd 2.7 08-nov-2007 1 \
                VENDOR_STRING="81AAAAAA : DXNLFPQ WZBCLQ2 AUJXJ2E IEKCKLI \
                WFYQNVM DNJU1YM LHYKAQC OM" HOSTID=81aaaaaa START=11-nov-2007 \
                SIGN="0169 4457 1B00 5266 852D 7813 5FB6 F38F 941A 1D0F E300 \
                F868 5245 2627 CF7B 03B9 037F 9F0F 6BAE 32F6 321C"
INCREMENT ads_layout agileesofd 2.7 08-nov-2007 1 \
                VENDOR_STRING="81AAAAAA : KSGSOTJ D1JYAXW BOCLRMW 2YNB2HN \
                GFVU2LG FQ1AQPJ UGW" HOSTID=81aaaaaa START=11-nov-2007 \
                SIGN="0115 CEDE 58A8 A734 FF5C 8AC8 A3AC DAE6 FD7E E9D2 C002 \
                EB4B 0FF8 884C 61BE 84D7 AB0F A3E2 47EA EC43 A5E6"
INCREMENT ads_schematic agileesofd 2.7 08-nov-2007 1 \
                VENDOR_STRING="81AAAAAA : NNWCSOI WSVFWVZ JOXDHFS NRMW2YN \
                BHAHUW2 JMAJGIJ OEYHM1W ST" HOSTID=81aaaaaa START=11-nov-2007 \
                SIGN="03E6 6359 6509 5297 45E2 6EB6 DBAF B148 04BF DE83 C502 \
                E872 86AA 522C 9257 369B BE71 A3F5 4FDE 16E2 F13F"

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.

To run this tool from the ADS Main window, choose Tools > License Information.

To run it from the terminal window, type the following line

$HPEESOF_DIR/bin/aglmtool

and press Enter to display the following window:

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 and 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:

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

Note
You must have write permissions to update this file.

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