Here’s the page we think you wanted. See search results instead:

 

  

Main Support:       Knowledge Center  > IC-CAP Support Home   >   IC-CAP Documentation (all releases)
Documentation:   IC-CAP 2009 Update 1   >  UNIX Installation   >  Setting up Licenses on UNIX Systems

This document contains references to Agilent Technologies. Agilent's former Test and Measurement business has become Keysight Technologies. For more information, go to www.keysight.com.


Skip to end of metadata
Go to start of metadata

Setting up Licenses on UNIX Systems

Use the following information to set up licenses for IC-CAP on UNIX systems. After you install IC-CAP using the steps described in Installing IC-CAP on UNIX Systems, you will need to set up the FLEXnet license manager and your IC-CAP license file (license.lic) before you can run IC-CAP.

IC-CAP uses Acresso's Flexible License Manager (FLEXnet) software for all software security configurations. When you run the IC-CAP 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:

  • Install a USB FLEXid hardware key.
  • Read your LAN card's ethernet ID.

For information on installing a FLEXid hardware key, see the FLEXid_README.pdf file located in the doggle_sup directory on the IC-CAP installation image (CD or downloaded). 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.

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

http://www.acresso.com/products/fnm/flexnet-manager-overview.htm

Installing Licenses

You must request and install new license codewords for IC-CAP 2009 Update 1. To learn how to request codewords, see Get Codewords for IC-CAP 2009 Update 1. To install and configure your new license file, complete the steps in the following sections.

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.

For information about linking your LAN card's Ethernet ID to your IC-CAP codewords, see Get Codewords for IC-CAP 2009 Update 1.

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 filename. 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 lapin 000086XXXXXX
VENDOR agileesofd
INCREMENT dev_bjt_gp_ee agileesofd 2.7 19-apr-2008 1 \
	VENDOR_STRING="000086XXXXXX : SYAQRDS F1AQCOM CNEXTBD FBLCHLO \
	WYGJYZD WTFLQZD WQYQBHI EFZ" HOSTID=000086XXXXXX \
	START=20-oct-2005 SIGN="00CF 6970 1933 85B7 1D14 AF45 A3FE \
	CB12 8E82 3BDC BD03 CF91 4618 77D4 0CCC B721 391C E439 A3CD \
	923A 549A"
INCREMENT dev_bsim3 agileesofd 2.7 19-apr-2008 1 \
	VENDOR_STRING="000086XXXXXX : WVRFWQG PJEL1QG AUYILYS XUYGJCY \
	L2WEYGO LSRXYBG PHEUL" HOSTID=000086XXXXXX START=20-oct-2005 \
	SIGN="0284 47D1 DBF7 041F 3F0D 9507 D914 DC36 B670 FE4D 2601 \
	C880 BCCE 5510 D478 5F44 964C 9BBB 17AD 8F99 5BC4" 

Floating-License File

The codeword file for a floating license is the same as the previous node-locked file example, with two exceptions: There is no HOSTID identifier in a floating license and the quantity can be any number, one or more, depending upon the number of licenses you own. Below is a sample of a section of a floating-license file:

SERVER A0049626 0008XXOOXXOO
VENDOR agileesofd
INCREMENT dev_bjt_gp_ee agileesofd 2.7 19-apr-2008 2 \
      VENDOR_STRING="0008XXOOXXOO : SYAQRDS F1AQCOM CNEXTBD FBLCHLO \
      WYGJYZD WTFLQZD WQYQBHI EFZ" START=20-oct-2005 SIGN="030F 496F \
      0869 F6A0 FD20 66E6 1DBF A981 22C3 4143 4B02 A946 49DC DB3B \
      A791 8140 ACEB 3211 7AFE 5FFD 7143"
INCREMENT dev_bsim3 agileesofd 2.7 19-apr-2008 2 \
      VENDOR_STRING="0008XXOOXXOO : WVRFWQG PJEL1QG AUYILYS XUYGJCY \
      L2WEYGO LSRXYBG PHEUL" START=20-oct-2005 SIGN="00E7 7925 AEFF \
      91D3 0595 5457 4C86 E596 20AB 38E8 4001 3A0D 30F3 0E13 C6C4 \
      150D 5808 DA83 6AC1 8467 1AD2" 

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.

Operating System

Command

Solaris

/bin/hostname

Linux

/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

Solaris

/bin/hostid

Linux

/sbin/ifconfig

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

  • Your license file should contain an odd number of SERVER lines; for example, 1 or 3. If you have 3 SERVER lines, the first SERVER is the primary license server and the other two are backup servers. All three SERVER lines must use the same port number.
  • You may only change the hostname and the optional port number fields.
  • Adding or removing SERVER lines requires a new license.lic file.
  • By default, Agilent EEsof sets hostname to unknown. The SERVER line does not contain a port address. FLEXnet software assigns a port address in the range of 27000 to 27009. The examples in this documentation use a port address of 27000, but your license file may differ. If you do not want to use the port address assigned by FLEXnet, specify any other unused port number for your network.

    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.

  • If the hostid is wrong, or changes for some reason, you will need to request a new license.lic file from Agilent EEsof.
    Here are examples of properly configured SERVER lines:
    SERVER joshua 2072EFE45 (default)
    SERVER isaiah 20472A3D3 27000 (optional)

VENDOR Line Format

The VENDOR line, by default, has the following format:
VENDOR daemon_name

where

daemon_name is the name of the vendor daemon.

Optionally, you may specify a path to the vendor daemon and a path to the FLEXnet options file, for example:

VENDOR agileesofd \
/my_install_dir/licenses/vendors/agileesofd \
/my_install_dir/licenses/agileesofd.opt

VENDOR Line Guidelines

  • During installation of IC-CAP, the vendor daemon is installed in the $ICCAP_ROOT/licenses/vendors and $ICCAP_ROOT/licenses/bin directories.
  • The daemon_name must be agileesofd.
  • The path to the options file is intentionally left blank. If you want to use FLEXnet options, you must add a full path to your option file. To learn about FLEXnet options, see Using FLEXnet Options. If the file does not exist and this option is not blank, a warning message will appear in the flex.log file.
  • Here is an example of a properly configured VENDOR line (without an options file):
    VENDOR agileesofd /my_inst_dir/licenses/vendors/agileesofd

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

  • None of the fields on the INCREMENT lines are editable. Any change made to any of the fields on an INCREMENT line will make that feature invalid. The only valid edit of an INCREMENT line is to add a backslash ('\') to line wrap the line. Be careful not to add an extra space between fields when using a backslash to line wrap an INCREMENT line.
  • Here are two examples of valid INCREMENT lines.

    Floating license example:

    INCREMENT dev_bjt_gp_ee agileesofd 2.7 19-apr-2008 2 \
    VENDOR_STRING="00008XXOOXXO : SYAQRDS F1AQCOM CNEXTBD \
    FBLCHLO WYGJYZD WTFLQZD WQYQBHI EFZ" START=20-oct-2005 \
    SIGN="023E 6EC8 0EAD 7537 5072 CA30 C5F9 3DAE 73BC 3168 \
    D601 453A F3BE F758 ACE2 4576 CE88 FB0E 8663 C8EE 918B" 
    

    Node-locked license example:

    INCREMENT dev_bjt_gp_ee agileesofd 2.7 19-apr-2008 1 \  
    VENDOR_STRING="000086XXXXXX : SYAQRDS F1AQCOM CNEXTBD \
    FBLCHLO WYGJYZD WTFLQZD WQYQBHI EFZ" HOSTID=000086XXXXXX \
    START=20-oct-2005 SIGN="00CF 6970 1933 85B7 1D14 AF45 \
    A3FE CB12 8E82 3BDC BD03 CF91 4618 77D4 0CCC B721 391C \
    E439 A3CD 	923A 549A" 

    The backslash used to line wrap these two INCREMENT line examples is prefaced by a space and contains a carriage return immediately after it. The '\' character is the absolute last character of the line it is on.

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

  • The recommended location for the license.lic file is:
    $ICCAP_ROOT/licenses/license.lic
  • You might need root permission to copy the license.lic file into the IC-CAP installation directory if IC-CAP was installed by a user logged in as root.
  • You can choose to locate the license.lic file someplace else on the SERVER machine(s). If you choose to do this, make sure that IC-CAP users properly set AGILEESOFD_LICENSE_FILE.
  • Make sure that the license.lic file has at least read permission for all users:
    cd $ICCAP_ROOT/licenses
    chmod 555 license.lic
    This command gives you read/executable permissions only.
  • Place a copy of the $ICCAP_ROOT/license directory on all SERVER machines or custom install the FLEXnet license server on each machine.

Start the License Server (lmgrd)

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

Note

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 IC-CAP 2009 Update 1. 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 IC-CAP 2009 Update 1 installation location ($ICCAP_ROOT/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

  • You only need to run lmgrd on the SERVER machine(s).
  • If the SERVER machine(s) has IC-CAP installed on it, you will find the FLEXnet license manager daemon ( lmgrd ) in the $ICCAP_ROOT/licenses/bin directory. If the SERVER machine does not have IC-CAP installed, you can copy the $ICCAP_ROOT/licenses directory from the machine that has IC-CAP installed.
  • IC-CAP installs version 11.4.1 of FLEXnet. Make sure you use the version 11.4.1 lmgrd and agileesofd supplied or a newer version of lmgrd. You can determine the version of lmgrd and agileesofd by typing the following commands:
    cd $ICCAP_ROOT/licenses/bin
    ./lmgrd -v
    cd $ICCAP_ROOT/licenses/vendors
    ./agileesofd -v 
    

To start lmgrd:

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

cd $ICCAP_ROOT/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 $ICCAP_ROOT/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-2008 Acresso Software Inc. All Rights Reserved.
Flexible License Manager status on Fri 6/26/2009 08:31
[Detecting lmgrd processes...]
License server status: 27000@m2606cxs
License file(s) on m2606cxs: /iccap2009/licenses/license.lic:
m2606cxs: license server UP (MASTER) v11.4
Vendor daemon status (on m2606cxs):
agileesofd: UP v11.4

Feature usage info:
Users of ac_driver:  (Total of 3 licenses available)
Users of analysis:  (Total of 3 licenses available)
Users of curtice_statz_fet:  (Total of 3 licenses available)
Users of dc_driver:  (Total of 3 licenses available)
Users of gummel_poon_bjt:  (Total of 3 licenses available)
Users of hp_eebjt2:  (Total of 3 licenses available)
Users of hp_eefet3_eehemt1:  (Total of 3 licenses available)
Users of hp_root_diode:  (Total of 3 licenses available)
Users of hp_root_fet_femt:  (Total of 3 licenses available)
Users of hp_root_mos:  (Total of 3 licenses available)
Users of iccap_environment:  (Total of 3 licenses available)
Users of lcrz_driver:  (Total of 3 licenses available)
Users of noise_driver:  (Total of 3 licenses available)
Users of philips_mextram_bjt:  (Total of 3 licenses available)
Users of philips_mos_model_9:  (Total of 3 licenses available)
Users of pulsed_sys_driver:  (Total of 3 licenses available)
Users of statistical_modeling:(Total of 3 licenses available)
Users of time_domain_driver:  (Total of 3 licenses available)
Users of ucb_bsim3:  (Total of 3 licenses available)
Users of ucb_mos2_mos3:  (Total of 3 licenses available)
Users of vbic_bjt:  (Total of 3 licenses available) 

Provide Access to Licenses

Before attempting to start IC-CAP, 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.

For example:

C Shell:

setenv AGILEESOFD_LICENSE_FILE
$ICCAP_ROOT/licenses/license.lic

Bourne/Korn Shell:

AGILEESOFD_LICENSE_FILE=$ICCAP_ROOT/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 IC-CAP 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 IC-CAP 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 IC-CAP.

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-to-PC Floating License

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

  • By copying the license.lic file from the UNIX license server to the PC's $ICCAP_ROOT/licenses folder
  • By setting the AGILEESOFD_LICENSE_FILE variable on the PC to point to the UNIX license server as follows:
    set AGILEESOFD_LICENSE_FILE=<port>@<host>

    For example:

    set AGILEESOFD_LICENSE_FILE=27000@joshua

    where

    27000 is the port number on the SERVER line in the license.lic file on the UNIX license server

    joshua is the hostname of the UNIX license server

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

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

Note

Be sure to change all references to /iccap 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 
    

Special Licensing Needs

Use the following information to accommodate any special licensing needs you may have. For details on using FLEXnet, refer to the Acresso's website at:

http://www.acresso.com/products/fnm/flexnet-manager-overview.htm

Using FLEXnet Options

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

  • Allow the use of features based on user, hostname or display name.
  • Deny the user of features based on user, hostname or display name.
  • Reserve licenses based on user, hostname or display name.
  • Control the amount of information logged about license usage.

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 /iccap2009U1/licenses/vendors/agileesofd \
/iccap2009U1/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:

  • EXCLUDE
    Deny a user access to a feature.
  • EXCLUDEALL
    Deny a user access to all feature served by this vendor daemon.
  • GROUP
    Define a group of users for use with any options.
  • INCLUDE
    Allow a user to use a feature.
  • INCLUDEALL
    Allow a user to use all features served by this vendor daemon.
  • NOLOG
    Turn off logging certain items.
  • REPORTLOG
    Specify that a logfile be written suitable for use by the FLEXadmin End-User Administration Tool.
  • RESERVE
    Reserve licenses for an individual user or groups of users.

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 /iccap2009U1/licenses/vendors/agileesofd \
    /iccap2009U1/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.
  4. Set AGILEESOFD_LICENSE_FILE to point to your license server.
  5. Run IC-CAP.

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:

  • Multiple license server nodes; each running one lmgrd and one license file
  • One license server node running one lmgrd and one license file
  • One license server node running multiple lmgrds and multiple license files

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 the license files for two or more products contain identical hostids on the SERVER line(s), then these files can be combined.
  • If the license files for two products contain different hostids on a SERVER line, then the license servers for those products will be running on different nodes and the license files cannot be combined.

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.

  • If the SERVER lines in those files have identical hostids, then you can combine the files into a single file.
  • If the SERVER lines have different hostids, then you must keep the license files separate.

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

  • The number of SERVER lines in each file is the same.
  • 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:

  • License files are set up to run on different server nodes, so hostids are different.
  • One file is set up for single server (has only one SERVER line), the other is set up for redundant servers (has multiple SERVER lines).
  • One vendor uses a custom hostid algorithm, so the hostids on the SERVER lines are different even though the files are for the same machine.

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.

Note

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

  • A newer lmgrd can be used with an older vendor daemon, but a newer vendor daemon might not work properly with an older lmgrd.
  • 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:

  • Always use the newest version of lmgrd and the newest version of each vendor daemon.
  • 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:

  • 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.
  • 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 FLEXnet 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.

The lmutil utility is located in $ICCAP_ROOT/licenses/bin. This location must be in your PATH, or use the following command before running the utility: cd $ICCAP_ROOT/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, 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 a Windows listing:

lmpath - Copyright (c) 1989-2008 Acresso Software Inc. All Rights Reserved.
Known Vendors:
_____________ 
agileesofd: /iccap2006icenses/license.lic:/iccap2009U1/licenses/license.lic
_____________ 
Other Vendors:
______________ 
/usr/local/flexlm/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. Here are examples of how license settings may appear in each registry:

UNIX:AGILEESOFD_LICENSE_FILE = /iccap2002/licenses:/iccap2009U1/licenses

Windows:

Registry location:
My Computer\HKEY_LOCAL_MACHINE\Software\Agilent\ICCAP_2009
Registry license path setting:

AGILEESOFD_LICENSE_FILE REG_SZ C:\ICCAP_2009U1\licenses

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

  • To add path settings on UNIX:
    lmutil lmpath -add agileesofd <new_lic_path1>:<new_lic_path2>
  • To add path settings on Windows:
    lmutil lmpath -add agileesofd C:\<new_lic_path1>;C:\<new_lic_path2>
  • To replace the current path settings on UNIX:
    lmutil lmpath -override agileesofd <new_lic_path>
  • To replace the current path settings on Windows:
    lmutil lmpath -override agileesofd C:\<new_lic_path>

Managing Multiple IC-CAP Versions

This section discusses how to manage the licenses for multiple versions of IC-CAP.

Backward Compatibility of Codewords

The following table lists previous IC-CAP versions with details of their license management. The compatibility of codewords with the various IC-CAP versions is discussed below.

Release
Name

License File
Version

Daemon
Name

FLEX
Version

License Environment
Variable

Default License
File Location

IC-CAP 2001

6.0

agileesof

FLEXlm 7.2h

LM_LICENSE_FILE

$ICCAP_ROOT/licenses/license.dat

IC-CAP 2002

6.1

agileesof

FLEXlm 7.2h

LM_LICENSE_FILE

$ICCAP_ROOT/licenses/license.dat

IC-CAP 2004

2.3

agileesofd

FLEXlm 8.2a CRO

AGILEESOFD_LICENSE_FILE

$ICCAP_ROOT/licenses/license.lic

IC-CAP 2006

2.3.5

agileesofd

FLEXnet 10.1.3 CRO

AGILEESOFD_LICENSE_FILE

$ICCAP_ROOT/licenses/license.lic

IC-CAP 2008

2.7

agileesofd

FLEXnet 11.4.1

AGILEESOFD_LICENSE_FILE

$ICCAP_ROOT/licenses/license.lic

IC-CAP 2009

2.7

agileesofd

FLEXnet 11.4.1

AGILEESOFD_LICENSE_FILE

$ICCAP_ROOT/licenses/license.lic

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

Codewords From
This Release

IC-CAP
2009

IC-CAP
2008

IC-CAP
2006

IC-CAP
2004

IC-CAP
2002

IC-CAP
2001

Will Work With
This Release

 

 

 

 

 

 

IC-CAP 2009

X

X

 

 

 

 

IC-CAP 2008

 

X

X

 

 

 

IC-CAP 2006

 

 

X

X

 

 

IC-CAP 2004

 

 

 

X

 

 

IC-CAP 2002

 

 

 

 

X

X

IC-CAP 2001

 

 

 

 

X

X

Combining IC-CAP 2009 Update 1 Codewords with Other Agilent EEsof EDA Codewords

For IC-CAP 2009 Update 1, the vendor daemon agileesofd is used. If you want to serve IC-CAP 2009 Update 1 licenses and earlier from the same server, you need to have the latest version of lmgrd, v11.4.1, and one or more DAEMON lines in your license file, depending on which versions you want to support. The IC-CAP daemon names available are:

agileesofd - for IC-CAP 2004/2006/2008/2009

agileesof - for IC-CAP 2002/2001

For example, the license file would include:

SERVER hpnmems 77a588a7 1700 
VENDOR agileesofd /iccap2009U1/licenses/vendors/agileesofd
VENDOR agileesofd /iccap2009/licenses/vendors/agileesofd
VENDOR agileesof /iccap2002/licenses/vendors/agileesof 

The INCREMENT lines for the different products would then be added to the file.

Note

If combining codewords for IC-CAP 2001 or IC-CAP 2002 and ADS 2002 or ADS 2002C, use the agileesof daemon included with ADS since it is a newer version than the one included with IC-CAP.

Here is how you might build a license file that contains IC-CAP 2009 Update 1, ADS 2003C, ADS 2002C, and IC-CAP 2001 codewords. The name and extension of the license file are arbitrary (i.e., license.dat, license.lic or iccaplicenses.txt). By default, all IC-CAP versions up to and including IC-CAP 2001 look for a file named license.dat and IC-CAP 2002, IC-CAP 2004, and IC-CAP 2009 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.

Supported environment variables are:

  • AGILEESOFD_LICENSE_FILE for IC-CAP 2004/2006/2008/2009
  • LM_LICENSE_FILE for IC-CAP 2002 and IC-CAP 2001

For example, if the combined codeword file is named iccaplicenses.txt, then:

  • IC-CAP 2009 Update 1 will use:
    AGILEESOFD_LICENSE_FILE=/licenses/iccaplicenses.txt
  • IC-CAP 2002 and IC-CAP 2001 will use:
    LM_LICENSE_FILE=/licenses/iccaplicenses.txt

IC-CAP uses a certain search order to look for the environment variable:

  • IC-CAP 2004/2006/2008/2009 will first look for the environment variable named AGILEESOFD_LICENSE_FILE. If AGILEESOFD_LICENSE_FILE and LM_LICENSE_FILE are both defined, IC-CAP 2004/2006/2008/2009 will use AGILEESOFD_LICENSE_FILE and ignore LM_LICENSE_FILE. If AGILEESOFD_LICENSE_FILE is not defined, then IC-CAP 2004/2006/2008/2009 will default to LM_LICENSE_FILE.
  • All previous IC-CAP versions, up to and including IC-CAP 2002 will use LM_LICENSE_FILE.

    Note

    Even though IC-CAP 2009 Update 1 will default to LM_LICENSE_FILE if that is the only environment variable that exists, it is recommended that you use the AGILEESOFD_LICENSE_FILE.

Example of a Merged License File


SERVER solarone 80FB214D 1700
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
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 
#
# ADS2005A codewords
#
INCREMENT ads_datadisplay agileesofd 2.35 08\-nov\-2005 1 \        
VENDOR_STRING="81AAAAAA : DXNLFPQ WZBCLQ2 AUJXJ2E IEKCKLI \        
WFYQNVM DNJU1YM LHYKAQC OM" HOSTID=81aaaaaa START=11\-may\-2005 \      
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.35 08\-nov\-2005 1 \        
VENDOR_STRING="81AAAAAA : KSGSOTJ D1JYAXW BOCLRMW 2YNB2HN \        
GFVU2LG FQ1AQPJ UGW" HOSTID=81aaaaaa START=11\-may\-2005 \        
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.35 08\-nov\-2005 1 \        
VENDOR_STRING="81AAAAAA : NNWCSOI WSVFWVZ JOXDHFS NRMW2YN \        
BHAHUW2 JMAJGIJ OEYHM1W ST" HOSTID=81aaaaaa START=11\-may\-2005 \       
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.35 08\-nov\-2005 1 \        
VENDOR_STRING="81AAAAAA : TS1OKRT EIQGAUY DLYSXUY LUTGOHK \        
ULCKL2R XYPNPHN EFKNVMD NGCWP" HOSTID=81aaaaaa \        
START=11\-may\-2005 SIGN="0333 DFD8 FD38 B049 9935 34CD A24B \        
91DF 8BE5 3E17 3D03 3CAB 88C2 4239 D021 526B 45F1 E539 FA55 \
#
# IC\-CAP 2009 Codewords
#
INCREMENT dev_bjt_gp_ee agileesofd 2.7 19\-mar\-2008 2 \        
VENDOR_STRING="00008XXOOXXO : SYAQRDS F1AQCOM CNEXTBD FBLCHLO \        
WYGJYZD WTFLQZD WQYQBHI EFZ" START=20\-oct\-2005 SIGN="023E 6EC8 \        
0EAD 7537 5072 CA30 C5F9 3DAE 73BC 3168 D601 453A F3BE F758 \        
ACE2 4576 CE88 FB0E 8663 C8EE 918B"
INCREMENT dev_bsim3 agileesofd 2.7 19\-mar\-2008 2 \        
VENDOR_STRING="00008XXOOXXO : WVRFWQG PJEL1QG AUYILYS XUYGJCY \        
L2WEYGO LSRXYBG PHEUL" START=20\-oct\-2005 	FFA0 0BD3 8206 B191 \        
E658 F333 440F 8D03 17F3 D6CB A53B C176 1CDF 5A91 6BB4 28D0 \        
1386 E211"
INCREMENT dev_bsim4 agileesofd 2.7 19\-mar\-2008 2 \        
VENDOR_STRING="00008XXOOXXO : WZJDCYM NBWJ1YM YMQGRFW XSUCLYD \        
GXDWYGJ YZDWTY2 NMAJ" START=20\-oct\-2005 SIGN="012B FF53 9F9D \        
3ED9 47A5 8744 E57E 4B07 9FC0 B0F1 7D03 A125 35B2 3FF2 9C97 \        
ABE9 66E5 D12D 5EDD 718D EC6A"
INCREMENT dev_bsimsoi agileesofd 2.7 19\-mar\-2008 2 \        
VENDOR_STRING="00008XXOOXXO : KKEYWEH VXGIJRV WDYLNT2 ACFUBHA \        
VU2JOEN WFMJOPB SOKTNCH 1O" START=20\-oct\-2005 SIGN="001A C20B \        
3EDE 88BE 0FAF D892 4310 DCE0 9D76 0830 B100 71FA E487 CD4F \        
EEDE E019 2E71 F2D5 D338 A728 D607"

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 IC-CAP Main window, choose Help > License Information. To run it from the terminal window, type $ICCAP_ROOT/bin/aglmtool and press Enter to display the following window:

Please help us improve
Please help us improve
Was this topic helpful? Yes No