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

 

  

Main Support:       Knowledge Center  > ADS Support Home   >   ADS Documentation (all releases)
Documentation:   ADS 2009 Update 1   >  UNIX and Linux Installation   >  UNIX and Linux License Setup

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

ADS License Setup for Unix / Linux

Click on the respective box in the flowchart below for further details on the selected topic.

ADS License Setup Flowchart
  1. ELSM - Extended License Search Mechanism
  2. LPT - License Preference Tool

Get Host Id / Hardware Key

Host Id (License ID) 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.

  • If ADS is already installed on your machine, you can obtain the Host Id (Ethernet Address / License Id) from license_info.html which is available in the ADS installation directory, for example, <ADS installation folder> where <ADS installation folder> is the destination folder you specified during ADS installation.

    Note

    Agilent recommends the usage of Host Id highlighted with green color.

  • If ADS is not installed, you can obtain the Host Id (Ethernet Address / License Id) by using the below command (as per your operating system):

    Operating System

    Command

    Red Hat Linux & Suse

    /sbin/ifconfig -a eth0

    Solaris

    /sbin/ifconfig –a

Notes

  1. The 12-digit Host Id / Physical Address should be used without dashes, for example, 000805E1A8DF.
  2. This example applies to LAN card users. Wireless Network Card users should locate their network card in the text file and use that Physical Address.
  3. To obtain Host Id of a Solaris machine, you must have the administrator permissions.

Back to Licensing Flowchart

Obtain ADS License File

You can place the ADS license request for:

  1. New Sale License Request
  2. New Release License Request
  3. Renew Expired License Early Access
  4. License Request Change / Transfer
  5. Evaluation License / Token Redemption / Renewal Request

Click here to order ADS evaluation / trial version

Back to Licensing Flowchart

Check License Type

ADS supports the following license types on Unix / Linux machines:

  1. Node Locked Counted: The license 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"

  2. Floating: The license file for a floating license is the same as the node-locked file example, with following exceptions:
    • There is no HOSTID identifier in a floating license.
    • The quantity can be any number, one or more, depending upon the number of ADS licenses you own.
      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"

Back to Licensing Flowchart

Floating License Setup

The license.lic file that implements FLEXnet security must be obtained from Agilent Business Support to run ADS. For any licensing setup, ADS must be installed on your machine / server. If your licenses will be served by a central server, use the following sections to install your ADS floating licenses.

Place License File

Save the ADS license file license.lic file on your system that you received from the Agilent EEsof Business Support. Most licenses 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. See SERVER Line Guidelines and VENDOR Line Format for more 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.

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, and ensure that no blank space is added after the backslash. You also have the option to remove the backslash and make each INCREMENT line one continuous line.
In the license file, # can be used to comment out the incremental codewords.

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.
  • hostid (License ID) 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.

    Note

    The evaluation form accepts these addresses as one continuous 12-digit number, without the colons. You can also obtain this by looking into the <ADS installation folder>/license_info.htm file, if ADS is already installed on the machine.

  • 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
  1. Your license file should contain an odd number of SERVER lines; for example, 1, 3, 5, and so on. 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.
  2. You may only change the hostname and the optional port number fields.
  3. Adding or removing SERVER lines requires a new license.lic file.
  4. 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.

  5. If the Host Id is wrong, or changes for some reason, you must request a new license file from Agilent EEsof business support. Here are examples of properly configured SERVER lines:
    SERVER joshua 2072EFE45 (default - FLEXnet assigns port address)
    SERVER isaiah 20472A3D3 27000 (optional - port address is specified) 

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
  1. During installation of ADS, the vendor daemon is installed in the $HPEESOF_DIR/licenses/vendors and $HPEESOF_DIR/licenses/bin directories.
  2. The daemon_name must be agileesofd.
  3. 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, refer to 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.
  4. Here is an example of a properly configured VENDOR line including the daemon path, options file path, and port number:
    VENDOR agileesofd /my_install_dir/licenses/vendors/agileesofd \
    /my_install_dir/licenses/agileesofd.opt 27000
  5. For client systems connecting to a license server through an Internet firewall set up on Windows PC, the port number the vendor daemon uses must be specified. 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 vendor daemon.

    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=1000000Depending on your network, you may need to adjust the period so it is long enough to allow connections without slowing down simulations excessively.

License Placement Guidelines

  1. The recommended location for the license.lic file is $HPEESOF_DIR/licenses/license.lic , where $HPEESOF_DIR is ADS Installation location.
  2. You may require root permission to copy the license.lic file into the ADS installation directory if ADS was installed by a user logged in as root.
  3. 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 ADS users properly set AGILEESOFD_LICENSE_FILE.
  4. Make sure that the license.lic file has at least read permission for all users:
    cd $HPEESOF_DIR/licenses
    chmod 555 license.lic
    This command provides only read/executable permissions.
  5. Place a copy of the $HPEESOF_DIR/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 ADS 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 ADS 2009 Update 1 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

  1. You only need to run lmgrd on the SERVER machine(s).
  2. If the SERVER machine(s) has ADS installed on it, you will find the FLEXnet license manager daemon (lmgrd) in the $HPEESOF_DIR/licenses/bin directory. If the SERVER machine does not have ADS installed, you can copy the $HPEESOF_DIR/licenses directory from the machine that has ADS installed.
  3. ADS installs version 11.6 of FLEXnet. Make sure you use the version 11.6 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 $HPEESOF_DIR/licenses/bin
    ./lmgrd -v
    cd $HPEESOF_DIR/licenses/vendors
    ./agileesofd -v 

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 for about 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-2007 Acresso Software Inc. All Rights Reserved.
Flexible License Manager status on Mon 9/22/2007 12:42
License server status: 27000@joshua
    License files on joshua: ads2009U1/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\)

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

Back to Licensing Flowchart

Node Locked Counted License Setup

For Node Locked license setup, follow the same steps as in Floating License setup.

Note

In SERVER line of your ADS license file replace the Host name of SERVER with your local machine Host name. For example, in "SERVER joshua 2072EFE45" statement replace the server name "joshua" with your local machine host name.

Back to Licensing Flowchart

Configure User Account

To start the ADS, you must configure the user accounts as follows:

C Shell

Add the following at the end of $HOME/.cshrc:

setenv HPEESOF_DIR <install_directory> 
set path = ( . $HPEESOF_DIR/bin $path ) 

Bourne or Korn Shell

Add the following at the end of $HOME/.profile:

HPEESOF_DIR=<install_directory> 
PATH=.:$HPEESOF_DIR/bin:$PATH 

Note

If you are running Common Desktop Environment (CDE) or HP VUE, your user account may be using $HOME/.dtprofile or $HOME/.vueprofile respectively to set up your user account instead of .cshrc or .profile. The .dtprofile and .vueprofile files contain a line that can be uncommented to activate the use of .cshrc or .profile. Please see your system administrator or CDE or VUE documentation for details.

Once the user accounts are configured, each user should log in and verify that the new environment variables are set. Type the env command and check that HPEESOF_DIR and AGILEESOFD_LICENSE_FILE are set and that PATH contains a path to the ADS bin subdirectory.
If you installed ADS as root, the ownership of directories and files will be set to user id 1313 and group id 22. To change this, enter:

cd $HPEESOF_DIR
chown -R root *
chgrp -R sys *

Provide Access to Licenses

Before starting the ADS, you must configure each user's login environment to allow access to the licenses. To do this you must also 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.

Following are the two options to access the licenses:

  1. Option 1:
    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
  2. Option 2: 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 be as follows:
      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

Accessing Multiple License Server

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 a colon (:).

The following two sections are applicable only for accessing the floating license:

  1. Accessing Licenses through a Firewall
  2. Using a UNIX/Linux-to-PC Floating License

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.

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:

  1. By copying the license.lic file from the UNIX/Linux license server to the Windows PC's $HPEESOF_DIR/licenses folder
  2. By setting the AGILEESOFD_LICENSE_FILE variable on the Windows PC to point to the UNIX/Linux 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/Linux license server
  • joshua is the hostname of the UNIX/Linux 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/Linux computer can be set to point to it in the same way by using its host name or IP address.

Back to Licensing Flowchart

Search for "ads_schematic" in License File

ads_schematic is an incremental codeword that enables you to launch ADS design environment.

Open the license file (license.lic) in text editor and search for "ads_schematic" string in the license file. If ads_schmetic is found ADS can be directly launched without any further setup (such as license preference etc.).

Back to Licensing Flowchart

First Time ADS Installation

If you have installed ADS for the first time on this machine then you can directly launch ADS otherwise you need to select the ADS License Bundle or Set ELSM ON before launching the ADS.

Back to Licensing Flowchart

ELSM / LPT

Set ELSM ON (ELSM Settings)

To Set ELSM ON, you can invoke the ADS License Preference Tool in following two different ways:

  1. When starting ADS, enter ads -p in your Unix terminal window to run the License Preference Tool.
  2. To run the tool as a standalone utility, enter $HPEESOF_DIR/bin/aglmpref in your Unix terminal window to start only the License Preference Tool.
    Once License Preference Tool is opened ,select Extended License Search Settings from the Options menu of License Preference Tool. Uncheck the "Turn off extended license searching" and click OK as shown in the following figure:

After above changes you are ready to launch the ADS.

Back to Licensing Flowchart

Choose License Bundle

Before choosing the ADS license bundle please ensure that Environment Variables setting is already done.

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
To select the ADS license bundle, invoke the ADS License Preference Tool using following
There are two ways to start the License Preference Tool. In a terminal window:

  1. When starting ADS, enter ads -p. This runs the License Preference Tool
  2. To run the tool as a standalone utility, enter $HPEESOF_DIR/bin/aglmpref. This runs only the License Preference Tool.

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

  1. To see the features available in a bundle, click the expansion icon next to the bundle name under Available License Bundles.
  2. To select a bundle, choose one of the bundles listed under Available License Bundles, then click Add. The selected bundle appears under Selected License Bundles.
  3. To accept your choice, click OK. This sets the environment variable AGILEESOFD_LICPREF<hostname> in $HOME/hpeesof/config/hpeesof.cfg.

Note

You must have write permissions to update this file.

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
  1. LTP bundles (except ltp_design_guides) contain a design environment license (ads_schematic) enabling ADS to run. You must select an LTP bundle containing a design environment license for a license preference to occur.
  2. Only one LTP bundle containing a design environment license can be selected at a time.
  3. The ltp_design_guides bundle (if available) can be selected with any other LTP bundle except ltp_iccap.
  4. Any PL bundles available on your system cannot be selected with an LTP bundle.
  5. If ADS and RF Design Environment are installed on the same UNIX or Linux system, RFDE bundles cannot be selected with LTP bundles.
If you are using Pay-Per-Use License Bundles
  1. The pl_desenv and pl_ui bundles contain a design environment license (ads_schematic) enabling ADS to run. You must select either pl_desenv or pl_ui for a license preference to take place. Other PL bundles appearing under pl_desenv are not selectable.
  2. Any LTP bundles available on your system cannot be selected with PL bundles.
  3. After selecting a PL bundle, you cannot select any additional bundles except for the following conditions:
    The pl_design_guides bundle (if available) can be selected with the PL bundle.
    If ADS and RF Design Environment are installed on the same UNIX or Linux system, only the pl_rfde bundle (if available) can be selected for RFDE.

Back to Licensing Flowchart

Launch ADS

Environment variables must be set before you can run ADS. To set the environment variables, see Configuring User Accounts.

Your FLEXnet license file must be properly configured and installed before you can run ADS. To set up your license file, follow the instructions in Setting Up Licenses for UNIX and Linux Installation.

To run ADS, open a terminal window and enter the command:

ads

Choose Help > Topics and Index > Quick Start for help on getting started with ADS.

Starting ADS in Verbose Mode (Debug Mode)

ADS 2006 Update can be started in verbose (debug) mode to display more information about what is occurring as ADS runs. This extra information can be very useful to debug a problem with ADS both at startup and in general operation. In verbose mode, ADS writes log files that can be used by Agilent EEsof EDA Technical Support to help track down any problems.

To start ADS in verbose mode, do the following:

  1. Open a terminal window.
  2. Type ads_verbose.

This will start ADS. You will see some messages indicating the location of two log files. Note the location of these files as indicated in the messages. The file names are as follows:

ads_daemon.log
ads_verbose.log

Note

If ads_verbose is not found, you may need to set the HPEESOF_DIR and PATH environment variables.

Run ADS until the problem you are trying to debug occurs, then take a look at the ads_daemon.log and ads_verbose.log files for errors.

If you can't locate the trouble based on the contents of the log files, please contact Agilent EEsof EDA Technical Support. You will want to e-mail the log files to the support engineer working with you.

Using 32-bit Simulators on a 64-bit Operating System

On a 64-bit operating system, you can either use the default 64-bit simulators or you can use the 32-bit simulators. To use the 32-bit simulators on a 64-bit system, do one of the following:

  • Set the EESOF_64BIT environment variable as follows:
    EESOF_64BIT=0

or

  • Start ADS by opening a terminal window and entering the command:
    ads -32bit

Back to Licensing Flowchart

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