Genesys - Getting Started. Genesys Getting Started

Transcription

1

2 Genesys Getting Started 1

3 Agilent Technologies, Inc Stevens Creek Blvd, Santa Clara, CA USA No part of this manual may be reproduced in any form or by any means (including electronic storage and retrieval or translation into a foreign language) without prior agreement and written consent from Agilent Technologies, Inc as governed by United States and international copyright laws Acknowledgments Mentor Graphics is a trademark of Mentor Graphics Corporation in the US and other countries Microsoft, Windows, MS Windows, Windows NT, and MS-DOS are US registered trademarks of Microsoft Corporation Pentium is a US registered trademark of Intel Corporation PostScript and Acrobat are trademarks of Adobe Systems Incorporated UNIX is a registered trademark of the Open Group Java is a US trademark of Sun Microsystems, Inc SystemC is a registered trademark of Open SystemC Initiative, Inc in the United States and other countries and is used with permission MATLAB is a US registered trademark of The Math Works, Inc HiSIM2 source code, and all copyrights, trade secrets or other intellectual property rights in and to the source code in its entirety, is owned by Hiroshima University and STARC Drawing Interchange file (DXF) is a trademark of Auto Desk, Inc EMPOWER/ML, Genesys, SPECTRASYS, HARBEC, and TESTLINK are trademarks of Agilent Technologies, Inc GDSII is a trademark of Calma Company Sonnet is a registered trademark of Sonnet Software, Inc Errata The ADS product may contain references to "HP" or "HPEESOF" such as in file names and directory names The business entity formerly known as "HP EEsof" is now part of Agilent Technologies and is known as "Agilent EEsof" To avoid broken functionality and to maintain backward compatibility for our customers, we did not change all the names and labels that contain "HP" or "HPEESOF" references Warranty The material contained in this document is provided "as is", and is subject to being changed, without notice, in future editions Further, to the maximum extent permitted by applicable law, Agilent disclaims all warranties, either express or implied, with regard to this manual and any information contained herein, including but not limited to the implied warranties of merchantability and fitness for a particular purpose Agilent shall not be liable for errors or for incidental or consequential damages in connection with the furnishing, use, or performance of this document or of any information contained herein Should Agilent and the user have a separate written agreement with warranty terms covering the material in this document that conflict with these terms, the warranty terms in the separate agreement shall control Technology Licenses The hardware and/or software described in this document are furnished under a license and may be used or copied only in accordance with the terms of such license Portions of this product include the SystemC software licensed under Open Source terms, which are available for download at This software is redistributed by Agilent The Contributors of the SystemC software provide this software "as is" and offer no warranty of any kind, express or implied, including without limitation warranties or conditions or title and non-infringement, and implied warranties or conditions merchantability and fitness for a particular purpose Contributors shall not be liable for any damages of any kind including without limitation direct, indirect, special, incidental and consequential damages, such as lost profits Any provisions that differ from this disclaimer are offered by Agilent only With respect to the portion of the Licensed Materials that describes the software and provides instructions concerning its operation and related matters, "use" includes the right to download and print such materials solely for the purpose described above Restricted Rights Legend US Government Restricted Rights Software and technical data rights granted to the federal government include only those rights customarily provided to end user customers Agilent provides this customary commercial license in Software and technical data pursuant to FAR (Technical Data) and (Computer Software) and, for the Department of Defense, DFARS (Technical Data - Commercial Items) and DFARS (Rights in Commercial Computer Software or Computer Software Documentation) 2

4 3 Genesys Release Notes 4 Behavioral Filters 4 Calculate Now and Model Caching 4 Compatibility with Previous Genesys Versions 4 Equations 4 Graphs 5 Licensing 5 M/Filter 5 Layout 5 Momentum GX and GXF 5 Net 0 6 Notes 6 PLL and TLINE 6 Ports and footprint 6 Schematic 6 SPECTRASYS Simulation Measurements 6 Supported Operating Systems 6 Title Block Library 7 Tune Window 7 VerilogA 7 Workspace Objects may disappear 7 What's New 8 Completely New 8 Changes 8 Bug Fixes 8 Installation 10 Installation Requirements 10 Software Installation 10 Installing FlexNet USB Key (dongle) Driver 10 Network License Server Installation (Administrators Only) 16 Installing Floating Licenses on a PC Server 16 Accessing Licenses From a UNIX or Linux License Server 18 Special Licensing Needs 19 Licensing Overview 25 Using New ADS-Style Hardware Key 25 Using LAN ID 25 Genesys Authorization Process 25 Setting up Floating License Server for GENESYS (Windows XP32, XP64, Vista32, Vista64 platforms) 26 Evaluation Licensing 28 Evaluating License File with a Token (through the product) 29 Request an Evaluation License File with a Token (through the product) 29 Evaluating License File with a Token (on the web) 31 Request an Evaluation License File with a Token (on the web) 31 Evaluating License File Without a Token 33 Request an Evaluation License File Without a Token 33 Purchased Software Licensing 35 Setting up Licensing 35 Advanced Options - Using Environment Variables 36 Troubleshooting a License 38 Viewing Diagnostic Information 38 Common License Problems 39 Windows Vista 40 License Information in the License File 40 Using lmutil for Diagnostics 40

5 Genesys Release Notes For more information concerning known issues in Genesys, or to report a new issue, refer to the Forum at: Behavioral Filters Algebraic (mathematically-based) filters that were used in version are now the primary behavioral filter model Synthesized circuit filters models are available by appending an '_C' to the corresponding model names Calculate Now and Model Caching Simulations will calculate without model caching if you double-click the simulation and click the Calculate Now button in the dialog Right-clicking and picking Calculate Now or using the Run button (green triangle on the main toolbar) uses model caches if they exist You can also turn off simulation caching in Tools > Options for the same effect (this will slow down tuning and optimization) Compatibility with Previous Genesys Versions Workspaces saved in Genesys are not backward compatible with Genesys or prior versions Workspaces saved in Genesys that have newer features will behave as follows when loaded from an earlier version: Opened in Feature Live Report wsx will not load wsx will not load Momentum GX Analysis wsx will not load wsx will not load Part Distribution wsx will not load wsx will not load Supported Analysis will not load Parts with distribution types other than "None" will not load properly Supported Analysis will not load Parts with distribution types other than "None" will not load properly Supported Supported Supported Supported Supported Supported Supported Supported Supported Supported Supported Supported Supported Supported Supported Equations Built-in functions in Genesys Many of the built-in functions in Genesys are in the Eagleware Functions Equation library You can embed them and view them in your workspace using the Library Selector or the Add Item / From Library command Equations parse as an entire block If you mix input and output lines in an equation block, the output lines may not calculate (because the data is not yet valid) and as a result, the input variables will not exist Always split your equation blocks into input blocks and output blocks Tuning Equations You can not tune equations that are located locally in a design that is used as a subcircuit, unless you disable Model Caching (not recommended) Tunable variables can be put into global equation blocks and will work fine 4

6 Graphs Error on Recalculate In some very rare cases graphs may not update correctly To force an update, resize the graph or double-click the graph and click OK in the dialog Incomplete Level Diagrams In some cases a level diagram may initially show only part of itself Zoom to page or zoom out to see the entire level diagram If this does not yield the correct result, you may need to re-calculate the System Analysis Licensing To conform with the licensing models used by other Agilent products such as Advanced Design System (ADS), the older "Eagleware-style" licensing model has been discontinued Licensing is now handled by what was previously referred to as ADS-style licensing All Momentum licenses in the old Genessy product structure ( with part numbers W1609L, W1610L, W1426L, W1428L and W1438L) will need to be updated Please contact your Agilent Genesys business support to request your updated license if you have not received it by end of July 2010 Documentation for installing a license server can be found at: NetworkLicenseServerInstallation%28AdministratorsOnly%29 M/Filter As of the release, when using M/Filter to produce an Inverted Microstrip or Suspended Microstrip circuit, the stackup for Air Below is not setup correctly for use in an EM Analysis (Momentum GX or Empower) You need to manually update the Layouts layers tab to set the Air Below height equal to Advance T Lines Substrate to Ground value The "Prepare Layout for Simulation" pull-down menu on the options page does not do anything It is safe to ignore Layout Genesys has been upgraded to support a 3D layout geometry viewer The viewer is accessible from the Layout menu or from the Layout toolbar Momentum GX and GXF A new version of Momentum (called Momentum GXF) is now offered with Genesys Momentum GXF is a superset of Momentum GX and offers additional features such as an N-logN solver and multithreaded parallel solving capability which enable much faster simulations with lower memory consumption and the ability to simulate much larger structures Genesys now ships with an interactive 3D layout geometry viewer which can also be used to view animated surface currents and far-field data produced by a Momentum GX or GXF analysis The viewer is accessible by right-clicking on a Momentum analysis and selecting 3D Visualization New trapezoidal meshing algorithm in Momentum avoids thin slivery mesh to improve speed, convergennce and accuracy When drawing a layout and then subsequently launching a Momentum simulation, it is a best practice to review the Layout Properties Layers tab to ensure the correct substrate information is being used If you place a 1-port SGND part (such as a DC voltage source using the SGND symbol) then you must manually change the footprint to an appropriate 1-port footprint, such as "SIGNAL, COPLANAR, 50mil" 5

7 Net 0 Starting with Genesys we assume that net 0 (if you have one) is ground This improves compatibility with Spice import substantially When you load an existing workspace with a net 0 that is not connected to a ground (GND) you will get a dialog asking if we should rename the net Notes There may be some cases where notes do not save updates (if you just reformat, for example) Type a space / backspace (typing but doing nothing) to tell Genesys the notes have been updated PLL and TLINE PLL and TLINE are not supported on 64 bit Windows or Windows Vista (32 or 64) Until they are integrated into Genesys, PLL and TLINE will not support Win64 or Vista When exiting in Windows Vista, these programs attempt to write files on exit Ignore and press OK Ports and footprint If you want to place a port without an associated EM port you can change the footprint in the parts properties, and it will not place an EM port Schematic Annotation changes, such as text string changes are not currently undo-able on schematics SPECTRASYS Simulation Measurements Spectrasys Phase Noise Use Model Change The Spectrasys CW and Oscillator source models now have their phase noise enabled by default However, the System Analysis now defaults the Calculate Phase Noise to Off The issue is that existing System Analysis defaults the Calculate Phase Noise to On so when an existing workspace is loaded the CW and Oscillator models will now generate phase noise where it didn t use to For these workspaces the Calculate Phase Noise should simply be turned Off Amplifier Compression The compression definition was changed in Spectrasys from OP1dB = IP1dB + G, to the standard more common in the industry which is OP1dB = IP1dB + ( Gain 1 ) in version As a result, the gain of a non linear device may change slightly based on drive levels OP1DB and IP1DB Measurements Since these measurements were reformulated to improve accuracy in the release, error messages may be displayed when loading old workspaces until the workspace is recalculated Path Voltage Measurements As of the release, any path voltage measurement will need to have the "Add Voltage Measurements" option checked for each path using them When creating a new path or importing existing workspaces the default option is to only include power measurements Supported Operating Systems 6

8 Genesys supports Windows XP (32 and 64), Windows Vista Business (32 and 64), and Windows Server 2003 Genesys will run in 32 bit compatibility mode on a 64 bit platform Title Block Library Text blocks that begin with an = are treated as equations Tune Window In some cases when first introducing a tune docking window, although there are tunable variables in the schematic, the tune window does may not initialize Select the refresh icon in the small tray of icons immediately above the tune window to remedy this VerilogA The VerilogA models work with all simulators, except for the hisim model, which does not currently work with HARBEC Workspace Objects may disappear There are a few rare cases where you can name two workspace objects with the same name If you do so, you may find that one of the objects will disappear when you reload the workspace This can be edited manually in the XML workspace file (the wsx file) by finding the XName="myname" UserName="myname" fields of the offending objects and changing "myname" to something not duplicated Load the workspace in Wordpad, search for "myname" (with the quotes) to find the entry, then edit the two myname fields Always copy the file before attempting to manually edit it 7

9 What's New Completely New X-Parameters in Circuit and System simulators Nonlinear Subcircuit support in Spectrasys Changes X-Parameters are the mathematically correct extension of S-Parameters capable of characterizing nonlinear devices and circuits X-parameters are used in the same manner as S-parameters: they can be measured and simulated, but for nonlinear instead of linear components The new X-Parameter model can be simulated by all Genesys Frequency domain circuit, system and DC simulators There is no limitation on the number of ports X-parameter models can be frequency, bias, power and impedance depedent for capturing the most accurate nonlinear behavior conveniently Frequency translation components such as mixers or complete transceivers can also be represented as IP protected X-parameter blocks for use in Genesys circuit and system simulations The new CircuitLink model allows the Harmonic Balance circuit simulator to co-simulate with the Spectrasys system simulator Enables a nonlinear circuit to be tuned or optimized to meet system specs directly There is no limitation on the number of terminals Frequency translating devices such as mixers are also supported Optimizations Dramatic speed improvement (in some cases as much as 10x) compared to previous version New and improved algorithms for Gradient Optimization: Steepest Descent, Fletcher-Reeves, Polak-Ribiere, and Hestenes-Stiefel Added Random Search method, used in Automatic mode to avoid converging on local minima Added L-infinity norm cost function for additional optimization control to smooth out peaks in optimized results Improved UI for setting up optimization Workspace Import and earlier Simulation Status Window Schematics Momentum Electromagnetic Simulation Misc UI Improvements Bug Fixes Import of old Layouts is now supported Proper rotation of old schematic parts is taken into account Embedded S-parameters in old workspaces are now converted to an S- parameter dataset Graph axes are now properly set up Node numbers preserved during schematic editing to preserve graph display of node response Simulation Status window has been improved, and there is always only one status window No more annoying flashing status windows Can be optionally hidden or never shown so that your screen remains fully usable during simulation or optimization Greatly improved Copy and Paste with ghosted copied image that follows your cursor to the precise location for pasting Dramatic speed improvement for copying, pasting, deleting, and component selection Wire auto-routing now supported Enlarged gravity around component nodes for easier snap-to wiring and connections Trapezoidal meshing eliminates thin sliver mesh for better convergence and accuracy Tune Window now linked to analyses marked as AutoCalculate, and has collapsible sub-windows Confusing Red Calculator button in main toolbar has been replaced by more flexible Green Arrow button with menu 8

10 Equations EM Graphs Misc Speedup for Math Language file I/O functions Fixed modulo function crash in Engineering language Fixed Momentum simulation crash Fixed 3-D Visualization tool crash in Vista 64-bit Metal-on-metal layers now supported - with layer precedence Dielectric-on-dielectric layers now supported Viahole layout produced from schematic model now takes via lining thickness into account Fixed Smith Chart markers and zooming Fixed Spectrasys Spectral Identification format display Fixed path symbols on a level diagram Improved unit labeling in Dataset and Table displays MBN3 and MBNA models properly auto-detect adjacent line widths Improved Gerber and DXF import/export Fixed issue when tuning with mouse wheel Fixed "Show" button issues in Errors window Fixed Match synthesis hang when optimizing Fixed wiring-related undo crash Monte Carlo and Yield simulation speedup Fixed MFilter layout generation when using DisCos Fixed several Advanced TLine conversion issues Improved speed of MUI model and some TLine models for frequency-domain simulations 9

11 Installation Before beginning the installation, you should make sure you have everything needed to complete the installation and licensing steps The licensing steps depend on what type of licensing you are using Please read the Licensing Overview to determine which type of licensing applies to you Installation Requirements 1 gigabyte of free space on your hard drive Genesys can use a lot of memory We recommend a minimum of 512MB of RAM, preferably 1GB of RAM Administrator privileges Windows Vista Administrator Account Windows XP (32 and 64-bit), Windows Vista Business (32 and 64-bit), Windows 7 (32 and 64-bit), and Windows Server 2003 Genesys will run in 32 bit compatibility mode on a 64 bit platform, except for the Momentum simulator, which will run in native 64- bit on a 64-bit OS Operating system that has the most recent updates License File (or Authorization Codes, or token if evaluating) or Internet access Hardware key (for Stand-Alone license) It is recommended that the installation and Authorization (licensing) are performed logged into the Administrator account when using Windows Vista Software Installation You can download the latest version of Genesys from: Navigate to where you saved the Genesys <*version> exe installation image Run the executable (Genesys <*version> exe) Read the License Agreement and if you agree, select accept license agreement and click Next Type user name, Organization, and choose type of access and click Next Continue clicking Next and follow the instructions until you reach Install Select Install Installation will only take a few minutes Congratulations you have successfully installed Genesys The next step is to setup Licensing Follow the steps appropriate for the type of licensing you are using Installing FlexNet USB Key (dongle) Driver USB hardware key check Before performing this procedure, you must ensure that you have the correct USB Hard Key For GENESYS and later, a new style hardware key is used The new hardware key is identified with a number on it, which appears as "9-xxx" If your USB hardware key shows a four or five digit number after "S/N" on it, this is an old style key and will not work with GENESYS and later software Download USB hardware key Driver 1 Click on the link below to download USB key hardware drivers, &id= Click the link called, Windows - FLEXid Dongle Driver Installer(zip)(193 MB) The Agilent License Agreement page opens 10

12 3 4 Scroll down to the bottom of the page and click AGREE to accept the license agreement Thank You: Acknowledgment page opens displaying the ads2009_windows_dongle_subzip window prompting you to save it 5 Note If the window does not open prompting you to save ads2009_windows_dongle_subzip, click "If content does not appear: click here" #Select the option Save File and click OK to save this file to a desired location on your computer system Unzip ads2009_windows_dongle_supzip On unzipping, a folder called ads2009_windows_dongle_sup is created and it contains the following directory tree, ads2009_windows_dongle_sup dongle_sup FLEXId_Dongle_Driver_Installerexe FLEXIdCleanupUtilityexe FLEXnet_ID_Dongle_Driverspdf Install USB hardware key (dongle driver) 1 Using either My Computer or Windows Explorer, change directories to /ads2009_windows_dongle_sup/dongle_sup Double click on "FLEXId_Dongle_Driver_Installerexe" FLEXid Dongle Driver Installer window opens: 11

13 2 Click Next Select Options screen opens 3 Select the desired drivers and click Next Note FLEXid9 is the latest driver You can deselect FLEXid 6_7 and FLEXid 8 12

14 4 Start Copying Files screen opens Click Next Setup Status window opens displaying the progress bar for the installation 5 InstallShield Wizard Complete screen opens Click Finish Check for Previously Installed Drivers 13

15 Note You may skip this step if you're absolutely certain that no FLEXnet drivers have been installed on license server machine 1 Open a command line shell (DOS window) selecting Start > Run and enter cmd 2 Change directories /ads2009_windows_dongle_sup/dongle_sup 3 In the commandline, enter the command FLEXId_Dongle_Driver_Installerexe /remove The following screen opens as shown below (depending on whether the drivers are already installed or not): Situation 1: No Drivers Loaded: 4 Hit Cancel and in the next window, hit Finish Go to the next section to start the installation of the dongle driver Situation 2: One or more drivers previously installed The machine may already have earlier versions of the dongle driver installed, In the above screen shot, drivers 67, 8, and 9 are installed Drivers 67, and 8 may be there for a reason Remove FlexId 9 because this needs to be updated In other words, make sure that only "FLEXid9 Drivers" check box is selected This requires a reboot Language Pack Installation and Usage 14

16 The Genesys Language Pack provides local language support for Japanese, Korean, Chinese (Simplified and Traditional), and Russian in Genesys menu picks The following are the installation steps: 1 Unzip the desired DLL for the local language support you need 2 Copy and paste the DLL into the Genesys installation "Bin" folder This is typically located in C:\Program Files\Genesys20xxxx\Bin 3 Start Genesys, go to Tools'>Options>Language and select the language you want 4 Exit and Re-start Genesys again and you will be using the new language 15

17 Network License Server Installation (Administrators Only) These instructions use Acresso release 1160, but they apply to all releases from 100 to 11X The instructions assume you are installing on a Windows Server but can be easily interpreted for other operating systems Installing Floating Licenses on a PC Server Use the following sections to install your floating licenses You should have installed the client before you complete these steps For details on installing the client on a PC running Windows, please refer to Installation (start) Important Be sure to use the following information to update all existing license servers with the latest version of the FLEXnet software (eg, lmgrd and lmutil) The software is installed with the client 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 client installation location (c:\<installation folder>\license\bin) for information to help modify the scripts Normally the installation folder would be Program Files Genesys<version> where version is a release version, like or You will need to stop, then restart, the license server to make these updates Installing the License File The licenselic file that implements FLEXnet security must be installed The default install path is: c:\<installation folder>\license Copy the licenselic file that you received via e- mail to the c:\<installation folder>\license folder If your licenses will be served by a central server, have your system administrator install the licenselic file on the license server machine Entering the Hostname Change the default hostname setting in your license file to the actual hostname of your license server The license server is the machine that will serve the licenses on the network, and whose Ethernet address or FLEXID hardware key number, appears on the SERVER line For example, assuming that a machine with FLEXID hardware key number 8-5E700059B957 has a hostname of joshua The SERVER line should read: SERVER joshua FLEXID=8-5E700059B957 All licenselic files are generated with SERVER lines with the following format: where: SERVER <hostname> <hostid> <hostname> is set to unknown by default <hostid> is the License ID (FLEXID hardware key number or Ethernet address) of the license server You can also specify a specific TCP port number for license requests as follows: SERVER <hostname> <hostid> <tcp_port> Setting the Vendor Daemon Path By default, no path is specified for the agileesofd vendor daemon executable This is acceptable as long as lmgrd and agileesofd are in the same folder when you start FLEXnet In the typical license configuration, lmgrd and agileesofd are both located in the c:\<installation folder>\license\bin folder When lmgrd is started from the c:\<installation folder>\license\bin folder, it looks for agileesofd in the same folder If agileesofd is not in 16

18 the same folder as lmgrd, you must specify a path to it using the following syntax VENDOR agileesofd c:\<installation folder>\license\vendors\agileesofd Connecting to a License Server through a Firewall If client systems connect to a license server through an Internet firewall set up on a Windows PC, you must also specify the port number the vendor daemon uses You can specify the port number on the license file's VENDOR line If the port is not specified, the default is chosen by the operating system at run time If this port number is specified, there may be a delay restarting the vendor daemon until all clients have closed their connections to the daemon Here is an example of a properly configured VENDOR line including the daemon path and port number: VENDOR agileesofd c:\<installation folder>\license\vendors\agileesofd 1705 Some clients may timeout before they can connect to a license server through a firewall The default timeout period is 01 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= Depending on your network, you may need to adjust the period so it is long enough to allow connections without slowing down simulations excessively Starting FLEXnet FLEXnet can be started either manually or automatically You must start the FLEXnet license manager daemon (lmgrd) on the license server(s) first Once the license server(s) is running lmgrd and has started the vendor daemon(s), you can configure the other machines (clients) and user login accounts To start FLEXnet you need the following FLEXnet software installed in the c:\<installation folder>\license folder This is done when you install the client The license server machine connected to the network using the TCP/IP network protocol A local copy of the licenselic file that contains the FLEXnet licenses Every machine that will run must be able to access the licenselic file used by the license server(s) to check out a license Access to the licenselic file can be via a local copy of the licenselic file or through a network drive Properly configured SERVER and VENDOR lines in your licenselic file If you have a three-server redundant configuration, you must start FLEXnet on all three servers before the licenses will be available on the network Once you have FLEXnet running, you can configure the other machines (clients) and user login accounts that need to use the software by setting the LM_LICENSE_FILE or AGILEESOFD_LICENSE_FILE Starting FLEXnet Manually While starting FLEXnet manually is a good way to verify that FLEXnet starts correctly, it is generally not recommend for a server machine, because it requires a dedicated MS-DOS Command Prompt to be open at all times and it requires re-starting after rebooting the license server Use the following steps to start the FLEXnet executable file, lmgrdexe: 1 From a MS-DOS Command Prompt, change to c:\<installation folder>\license\bin 2 Type the following command specifying the full path and location of the license file lmgrd -app -c c:\<installation folder>\license\licenselic -l c:\<installation folder>\licenses\flexlog To shut down the license manager, enter the following at a command prompt, from the c:\<installation folder>\licenses\bin folder: lmutil lmdown -c c:\<installation folder>\license\licenselic 17

19 Starting FLEXnet Automatically Ideally you should configure FLEXnet to start up automatically each time your system is booted by installing the license manager as a Control Panel service To start the license manager automatically: 1 From a MS-DOS Command Prompt, change to c:\<installation folder>\license\bin 2 Enter the full path and filename of both the license executable file and the licenselic file The default location for the executable file is c:\<installation folder>\license\bin\lmgrdexe (The flexlog file is useful for troubleshooting) installs -e <path to lmgrd> -c <path to license file> -l <path to flexlog> For example: installs -e d:\<installation folder>\license\bin\lmgrdexe -c d:\<installation folder>\license\licenselic -l d:\<installation folder>\license\flexlog If you don't specify a flexlog file using the "-l" option when you run installsexe, FLEXnet creates a default log file in the system32 folder While this default log file does not contain as much information, it can still be useful This file is typically located in c:\winnt\system32\ and is named lmgrdlog or lmgrdxxxx where "xxxx" is the process ID number of lmgrd 3 Activate the license server by starting the FLEXnet service using the Control Panel or by rebooting the system: Start > Control Panel (in classic view) > Administrative Tools > Services To remove the license manager from the service list and cancel the automatic FLEXnet startup: From a system prompt, change to the license folder and enter: installs -r To change the path to your license file, first remove the existing FLEXnet service using the installs -r command, reinstall FLEXnet using the new location, and then reboot your system Accessing Licenses From a UNIX or Linux License Server You can access licenses from a UNIX or Linux license server by doing the following: 1 Set up the UNIX/Linux license server(s) to use FLEXnet version 116 or higher lmgrd and agileesofd daemons 2 Set up the PC to access the UNIX/Linux license server's licenselic file Note that the following section assumes you are using a license server on an ADS platform, where $HPEESOF_DIR refers to the location of the ADS installation You do not have to have ADS installed however to run a server on a UNIX/Linux platform, but you will need to download the license daemon software separately since Genesysincludes only the PC version of this software Setting Up the UNIX or Linux License Server You must use version 116 or higher of the FLEXnet daemons lmgrd and agileesofd Use the following commands to check the version of lmgrd and agileesofd on your UNIX/Linux license server: cd $HPEESOF_DIR/licenses/bin / lmgrd -version cd $HPEESOF_DIR/licenses/vendors / agileesofd -v Use the following steps to update current FLEXnet daemons on your license server(s): 1 Stop the current FLEXnet daemons on the license server: cd $HPEESOF_DIR/licenses/bin 18

20 /lmutil lmdown -c /licenselic 2 Replace the following files with the supported FLEXnet version files: $HPEESOF_DIR/licenses/bin/lmgrd $HPEESOF_DIR/licenses/bin/lmutil $HPEESOF_DIR/licenses/bin/agileesofd If you have more than one license server, make sure you do this on all of them 3 Restart the license daemons on the UNIX/Linux license server(s): cd $HPEESOF_DIR/licenses/bin / lmgrd -c /licenselic -l /flexlog Setting Up the Client(s) Your PC can access the UNIX/Linux license server's licenselic file in three ways: By copying the licenselic file from the UNIX/Linux license server to the PC's c:\<installation folder>\license folder By setting the GENESYS_LICENSE_FILE variable on the PC to point to the UNIX/Linux license server as follows: set GENESYS_LICENSE_FILE =<port>@<host> (You can also use AGILEESOFD_LICENSE_FILE, as this value will be used if GENESYS_LICENSE_FILE is not defined) By using the authorization dialogs in Genesys to set the License File location as using <port>@<host> For example: set GENESYS_LICENSE_FILE =27000@joshua where is the port number on the SERVER line in the licenselic file on the UNIX/Linux license server and joshua is the hostname of the UNIX/Linux license server Special Licensing Needs Be sure to use the lmtools utility to install a license on a server that is already running FLEXnet For details on using FLEXnet, refer to the Acresso website at: 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 to create the options file using any text editor Ideally, you should keep the options file in the same directory as your licenselic file Also, add the pathname to the options file in the licenselic file as the fourth field on the VENDOR line for agileesofd as shown in the following example (Remember to use the backslash ('\') character if the file contains wrapped lines) VENDOR agileesofd c:\<installation folder>\license\vendors\agileesofd \ c:\<installation folder>\license\agileesofdopt 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 19

21 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 TIMEOUT Works only for specified simulator and library licenses TIMEOUTALL Works for all simulator and library licenses Use the following steps to create and use an options file Details about each step located in previous sections: 1 Create an options file with your required options 2 Modify your licenselic file so that the VENDOR or DAEMON line points to this option file as shown in this example: VENDOR agileesofd c:\<installation folder>\license\vendors\agileesofd \ c:\<installation folder>\license\agileesofdopt 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 agileesofdopt file containing the TIMEOUTALL option set to 900 seconds: 17:35:14 (agileesofd) Using options file: "c:\<installation folder>\license\agileesofdopt" 17:35:15 (agileesofd) ALL FEATURES: INACTIVITY TIMEOUT set to 900 seconds 4 Set GENESYS_LICENSE_FILE to point to your license server 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 timeout 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

22 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 licenses from Agilent EEsof, you can add the new licenses to the FLEXnet environment as follows: 1 Replace the existing licenselic files on the license servers and clients with the new licenselic file 2 On the primary server, run lmutil lmreread This causes the lmgrd on the primary server to re-read the licenselic 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 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 Essentially, you can combine two license files under the following conditions: 1 2 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 Important There is virtually no performance or system-load penalty for running separate lmgrd processes 21

23 Combining License Files from Multiple Vendors If your license files are compatible, you can combine them using any text editor To combine license files, read all of the compatible license files into one file, then edit out the extra SERVER lines so that only one set of SERVER lines remains Write out this data, and you have your combined license file If you combine license files from multiple vendors, it is a good idea to keep a copy of the combined license file in each vendor's default license file location This way, your users can avoid having to set AGILEESOFD_LICENSE_FILE, because each package finds its license information in the default place On UNIX or Linux, you can do this with a symbolic link from each default location to the location of the combined license file FLEXnet Version Component Compatibility When you combine license files for two different FLEXnet-licensed products, the products may not use the same version of FLEXnet FLEXnet is designed to handle this situation There are two basic compatibility rules for FLEXnet: 1 2 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: 1 Always use the newest version of lmgrd and the newest version of each vendor daemon 2 Use the newest FLEXnet utilities For specific application programs, you can use either the new or the old version (with the assumption that the vendor daemon for that application is at least as new as the application) Using Separate License Files on the Same Server Node You must run a separate copy of lmgrd for each license file When you run multiple copies of lmgrd, there are two details to remember: 1 The port number on the SERVER line of each license file must be unique You can use a standard text editor to change the port number in each license file so that they are all different 2 You must make sure that you are using a compatible version of lmgrd when you start it up for a particular license file This can be done by using an explicit path to lmgrd When running client programs (such as a licensed application), you can set the AGILEESOFD_LICENSE_FILE environment variable to point to multiple license files For example, you may have a license file from vendor ABC and a license file from vendor XYZ with incompatible servers You can place the license file from vendor ABC into: c:\user\flexnet\abclic and the license file from vendor XYZ into: c:\user\flexnet\xyzlic 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 Redundant License Servers FLEXnet enables you to set up a redundant license server configuration This involves 22

24 configuring three license servers with one of the three servers functioning as the master server If the master server goes down, one of the other two servers becomes the new master server, and the licenses remain available on the network Setting up redundant servers requires extra system administration and is not recommended unless you absolutely need it To set up redundant license servers, use the same FLEXnet procedures on all three servers All three servers need to be up and running before your licenses will be made available Controlling License Path Settings The lmutil utility provides the lmpath function which allows direct control over FLEXnet license path settings You can use lmpath to add to, override, or get the current license path set in the registry This enables you to change or view path settings without locating individual settings in the Windows registry on the PC or in the FLEXnet registry (flexlmrc) on UNIX or Linux The lmutil utility is located in c:\<installation folder>\license\bin This location must be in your PATH, or use the following command before running the utility: cd c:\<installation folder>\license\bin The usage for this function is: lmutil lmpath { -status -add -override } { vendor_name all } license_path_list where -status displays the current license path settings -add appends license_path_list to the front of the current license-path settings or creates the list of license-path settings, if it doesn't exist, initializing it to license_path_list Duplicates are discarded -override overrides the existing list of license-path settings with the contents of license_path_list If license_path_list is the null string, "", the specified list is deleted For example: lmutil lmpath -override agileesofd "" Deletes the value of AGILEESOFD_LICENSE_FILE from the registry lmutil lmpath -override vendor2 "" Deletes the value of VENDOR2_LICENSE_FILE from the registry lmutil lmpath -override all "" Deletes the value of LM_LICENSE_FILE from the registry vendor is a string naming a particular vendor daemon name Affects the value of vendor _LICENSE_FILE For example, use agileesofd to affect AGILEESOFD_LICENSE_FILE all refers to all vendor daemons Affects the value of only LM_LICENSE_FILE license_path_list is the new path setting(s) On UNIX/Linux, this is a colonseparated 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: 23

25 lmutil lmpath -status The following example status listing is from UNIX and is similar to PC and Linux listings: lmutil - Copyright (C) Acresso Software Inc All rights reserved Known Vendors: agileesofd: /ads2006/licenses/licenselic:/<installation folder>/licenses/licenselic Other Vendors: C: \flexlm\licensedat Note Where a path is set to a directory, each of the *lic files are listed separately Changing License Path Settings When adding or overriding path settings, lmpath sets the FLEXnet entry in the Windows registry on the PC, or changes the file $HOME/flexlmrc on UNIX/Linux Here are examples of how license settings may appear in each registry: UNIX/Linux AGILEESOFD_LICENSE_FILE = /ads2003a/licenses:/ads2009u1/licenses Windows Registry location: My Computer\HKEY_LOCAL_MACHINE\Software\Agilent\<installation folder> Registry license path setting: AGILEESOFD_LICENSE_FILE REG_SZ C:\<installation folder>\license To change license path settings, enter the appropriate command in a Command Prompt on Windows, or a terminal window on UNIX/Linux You can adapt the following examples which change path settings for AGILEESOFD_LICENSE_FILE: To add path settings on UNIX/Linux: 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/Linux: lmutil lmpath -override agileesofd <new_lic_path> To replace the current path settings on Windows: lmutil lmpath -override agileesofd C:\<new_lic_path> 24

26 Licensing Overview Genesys can be licensed in two ways New ADS-Style hardware key (USB or Parallel key with serial number staring with 9- or 8- respectively) OR LAN ID (MAC address) of your PC without the need for a hardware key The new license is backward compatible with all the previous versions Using New ADS-Style Hardware Key If you have been using an Eagleware hardware key (Parallel or USB with 4 or 5 digit serial number), you will also need to request a replacement ADS-Style USB hardware key when requesting a license via the following steps: Select "New Release License Request" Fill in all required information with red check marks Select "GENESYS" under Product Selection and check the box to order replacement ADS-Style USB key Select License Type Default is "Node Locked" unless you are using a floating network license Select "Windows (PC)" under Primary License Server and submit your existing hardware key serial number in the popup window Using LAN ID If you want to lock Genesys to the LAN ID of your PC without the need for a hardware key, follow these steps when requesting a license : 1 Select "New Release License Request" 2 Fill in all required information with red check marks 3 Select "GENESYS" under Product Selection Do NOT check the box to order replacement ADS-Style USB key 4 Select License Type Default is "Node Locked" unless you are using a floating network license 5 Select Primary License Server operating system and submit your computer LAN ID (also called MAC address) in the popup window Click on "How To Find?" for instructions to get the MAC address for your operating system if needed Genesys Authorization Process When you start an unlicensed version of Genesys; the Authorization screen appears as shown below: 25

27 Depending on the type of license you have, please select the option from the Authorization screen: 1 2 Evaluation (start) Purchased Software (start) For troubleshooting information: Troubleshooting a License (start) Setting up Floating License Server for GENESYS (Windows XP32, XP64, Vista32, Vista64 platforms) Download License server software and drivers 1 Click on the link below to download the required license server software and drivers: &id= Select link for Windows (32-bit & 64-bit) FLEXnet 116 Windows, When the zip file is completely downloaded, unzip it A folder called "FLEXnet116_Windows" is created IF your license file is going to be tied to a USB hardkey (dongle), you will need to FIRST download and install the dongle driver software and install dongle driver Please refer to document called "InstallingDongleDriverdoc" The USB hardware key should have a number on it to the tune of "9-xxx" If your license is tied to the Ethernet address of your network card, you may continue forward with this procedure Edit your license file 1 To continue, you should have received a licenselic file from Agilent EEsof Business Support to run Genesys If you have never received a licenselic file or may have lost it, contact Agilent EEsof Business Support to obtain the file, or ceda_bsc@agilentcom 2 Edit license file and enter name of license server in SERVER line For example, in the file below, the name "redwood" has been entered The original file had the word "unknown" 26

28 Run lmtoolsexe (acquired from download described in Section I) 1 Change directories to location where License Server Software was downloaded and unzipped There is a folder, "FLEXnet116_Windows" in this location having folders for 32 bit and 64 bit Depending upon your Windows operating system, change directories to the desired folder: Windows XP32, Vista 32-go into "32bit" folder Windows XP64, Vista 64-go into the "64bit" folder 2 Launch the lmtoolsexe application to start the license server setup process 3 4 Make sure Configuration using Services is selected Click the Config Services tab The initial contents of that tab appear as shown below: 5 Now, enter the following fields: Enter Service name You may use a name of your choice such as Agilent License Server Use Browse to enter path to lmgrd Use Browse to enter path to license file Enter same path as above and give debug file name SELECT buttons (that is place a check mark) "Use Services" and "Start Server at Power Up" (IMPORTANT: Use Services must first be selected to be able to select Start Server at Power up) Lastly, press Save Service The completed window should appear something like as shown below: 27

29 6 Go to Start/Stop/Reread tab as shown below and press start server NOTICE THAT SERVICE NAME APPEARS IF not there could be a problem 7 As a final step to ensure things are okay, go back to the Config Services tab and click "View Log" button You should see a message that agileesofd and lmgrd are UP Evaluation Licensing Evaluation Token - is a pre-approved way Agilent distributes evaluation licenses for Genesys The token is issued by an Agilent employee, allowing you to request a license without any further approval If you do not have a token, you can still request an evaluation license file Getting an Evaluation Up and Running This is a three step process: 1 Download and Install Genesys ( ) 2 Request an Evaluation License There are three ways you can request an evaluation license: With an Evaluation Token (on the web) (start) With an Evaluation Token (through the product) (start) Without an Evaluation Token (start) 3 Activate the Evaluation License by authorizing Genesys using the licenselic file This will depend on what you choose in step 2, and the instructions are described in those sections 28

30 Evaluating License File with a Token (through the product) If you are an existing customer that is already running the version of Genesys you are requesting an evaluation for, this process will change your licensing options and you will need to change them back after the evaluation period Request an Evaluation License File with a Token (through the product) 1 Install Genesys using the Web Installation Instructions (start) 2 Open Genesys from the shortcut on your desktop or from Start/All Programs/Genesys<*Version>/Genesysexe where, <*Version> is the version of interest 3 Choose Evaluation as shown below and click Next 4 Choose I have a token and want to request a license file as shown below and click Next 5 The next screen explains the steps for obtaining an evaluation license with a token There is also a link to the Agilent privacy policy 6 There will be two screens were you will enter information needed to complete the evaluation request Your MAC address is pre-filled Under most circumstances this is the MAC address to use but if you know that you have multiple NIC cards installed, you may want to verify that this is the MAC address for the wired LAN NIC card you use to access the internet You can query the addresses of your interfaces by running ipconfig /all in a Command Prompt window 29

31 7 Next you will see the Successful request screen Click Finish to end the request process 8 When you receive the with the licenselic file attached, copy the file in the C:\Program Files\ Genesys<*Version>\License folder 9 Open Genesys from the shortcut on your desktop or from Start/All Programs/ Genesys<*Version>/Genesysexe, where <*Version> is the version of interest 10 Choose Evaluation and click Next as shown in Genesys License Authorization figure above 11 Choose I have a license file and click Next as shown in Genesys License Authorization-Request Method 12 Click the Change Path button as shown in Genesys License Authorization- Path/Bundle Selection below Please add the path where the licenselic file was saved in step 8 The recommended path is C:\Program Files\ Genesys<*Version>\License, which should be the default location selected using the Browse button If there are any other "@path" paths noted, please delete them Click OK 13 Click Change Bundle button for Current Bundle Selection The Agilent License Preference window will open If Genesys bundles starting with b_sv_ are shown under the Available License Bundles the licenselic file was detected 14 Select the Genesys bundle and click on "Add >>" Click OK 15 Once the License Path and the bundle have been selected, it will be displayed under the Licensing Options section Click Finish 16 Once the Authorization process has been finished, a prompt that Genesys needs to be restarted will appear 17 Open Genesys from the shortcut on your desktop or from Start/All Programs/ Genesys<*Version>/Genesysexe, where <*Version> is the version of interest 18 If a Authorization Failed prompt appears, please check Show My Current License Status If the message is not clear, please a screen shot of this window to support Contact information is on the page Agilent Technical Support Please be sure to include your host ID or your demo token in your correspondence 30

32 Evaluating License File with a Token (on the web) If you are an existing customer that is already running the version of Genesys you are requesting an evaluation for, this process will change your licensing options and you will need to change them back after the evaluation period Use of Remote Desktop Connection is considered network usage of the product and is not supported with the node locked evaluation licenses Request an Evaluation License File with a Token (on the web) 1 Go to From this web page: Click the button Request a Product Demo Select the second radio button Redeem an Evaluation Token After the Send Request button has been selected, an will be sent with an attached licenselic file (request processed within seconds) 2 Install Genesys using Step 1 in the Evaluation License that is sent to you 3 Once the installation is finished, copy the licenselic file that was attached to the in the C:\Program Files\ Genesys<*Version>\License folder 4 Open Genesys from the shortcut on your desktop or from Start/All Programs/Genesys<*Version>/Genesysexe, where <*Version> is the version of interest 5 Choose Evaluation as shown below and click Next 6 Choose I have a license file as shown below and click Next 31

33 7 Click the first Change Path button as shown in Genesys License Authorization- Path/Bundle Selection below Please add the path where the licenselic file was saved in step 3 The recommended path is C:\Program Files\ Genesys<*Version>\License, which should be the default location selected using the Browse button If there are any other "@path" paths noted, please delete them Click OK 8 Click on the second Change Bundle button for Current Bundle Selection: The Agilent License Preference window will open If one or more Genesys bundles starting with b_sv_ are shown under the Available License Bundles the licenselic file was detected 9 Select the Genesys bundle and click on "Add >>" Click OK 10 Once the License Path and the bundle have been selected, it will be displayed under the Licensing Options section Click Finish 11 Once the Authorization process has been finished, a prompt that Genesys needs to be restarted will appear 12 Open Genesys from the shortcut on your desktop or from Start/All Programs/Genesys(*Version)/Genesysexe, where (*Version) is the version of interest 13 If a Authorization Failed prompt appears, please check Show My Current License Status If the message is not clear, please a screen shot of this window to support Contact information is on the page Agilent Technical Support Please be sure to include your host ID or your demo token in your correspondence 32

34 Evaluating License File Without a Token Request an Evaluation License File Without a Token Make the request: Go to From this webpage: Click the button Request a Product Demo Select the radio button Request an Evaluation License and fill in the form with the appropriate information Approval will typically occur within 48 hours After you are approved, an evaluation license will be sent to the address entered on the form After the license file is received: Install Genesys using Step 1 in the Evaluation License that is sent to you Once the installation is finished, copy the licenselic file that was attached to the in the C:\Program Files\ Genesys<*Version>\License folder Open Genesys from the shortcut on your desktop or from Start/All Programs/Genesys<*Version>/Genesysexe, where <*Version> is the version of interest Select Evaluation and click Next Select I have a license file as shown below and click Next Click the Change Path button as shown in the Genesys License Authorization-Path/Bundle Selection below Please add the path where the licenselic file was saved in step 2 The recommended path is C:\Program Files\ Genesys<*Version>\License, which should be the default location selected using the Browse button If there are any other "@path" paths noted, please delete them Click OK 33

35 Click the Change Bundle button for Current Bundle Selection The Agilent License Preference window will open If Genesys bundles starting with b_sv_ are shown under the Available License Bundles the licenselic file was detected Select the Genesys bundle and click on "Add>>" Click OK Once the License Path and the bundle have been selected, it will be displayed under the Licensing Options section Click Finish Once the Authorization process has been finished, a prompt that Genesys needs to be restarted will appear Open Genesys from the shortcut on your desktop or from Start/All Programs/ Genesys<*Version>/Genesysexe, where <*Version> is the version of interest If a Authorization Failed prompt appears, please check Show My Current License Status If the message is not clear, please a screen shot of this window to support Contact information is on the page Agilent Technical Support Please be sure to include your host ID in your correspondence 34

36 Purchased Software Licensing Before you begin: You will need to know the full path to the local license file (licenselic), or the name of your company's license server Note: Use of Remote Desktop Connection is considered network usage of the product and is not supported with node locked licenses Advanced Design System (ADS) Users ONLY If you don't own or use this product, skip to Setting up Licensing If you already have ADS installed, or plan to install ADS, and are using default setting for home directory, ADS will share the same configuration file with Genesys for license preferences settings The default settings create a home directory at C:\users\default If you plan to use a different HOME setting other than the default, then define SV_HOME in your Windows Environment before you run Genesys for the first time This can be set to the same setting as HOME for your ADS installation, which will enable sharing the same configuration file, or a separate location if you don't want to share the configuration file with ADS The ADS configuration file will be located at HOME\hpeesof\config\hpeesofcfg and the Genesys configuration file will be located at SV_HOME\hpeesof\config\hpeesofcfg If not defined, SV_HOME will be assumed to be the same as HOME and if not defined HOME will be assumed to be C:\users\default See Advanced Options below for more information on Window Environment variables Setting up Licensing 1 Open Genesys from the shortcut on your desktop or from Start/All Programs/Genesys<*Version>, where <*Version> is the version of interest, ie If you are currently running Genesys choose Update Authorization Info as shown below from the Help menu 2 Select Purchased Software and click Next as shown below: 3 Click the Change Path button for Current License Path as shown below: 35

37 4 If you have a nodelocked license, use the Browse button to easily browse to the directory where the licenselic file is located If the licenses you need are available from a License server, enter the server location (with "@" preceding server name), for example, if the server is called server1, you would enter "@server1" You can also precede sign with the port number for you license; this is not required but it can improve the performance of license search Tip: when using a combination of local and license server licenses, list the local license file locations first in your path 5 Click the Change Bundle button for Current Bundle Selection 6 The bundles available will be listed in the left pane and selected bundles in the right pane The bundles that apply to your product will appear in bold color To select a license bundle, choose the bundle (click to highlight it) from the left pane and click Add >> After the license bundle is listed in the right pane; click OK as shown below: 7 Click Finish You will be prompted to re-launch Genesys for the changes to take effect 8 Genesys will start Advanced Options - Using Environment Variables As an advanced option (mainly for System Administrators) you can manually set the license path and bundle name using Windows Environment variables Generally these should be defined before you run Genesys for the first time, since these values can affect 36

38 the Authorization process To define Windows Environment variables: On Windows XP, choose Start > Settings > Control Panel > System > Advanced tab > Environment Variables button Your environment variable can be entered either as a user variable or as a system variable The user variable affects only the currently logged-in user; the system variable affects all users Environment variables of interest: HOME This is used to define the home directory for ADS, which Genesys will use if defined The default value for ADS is C:\users\default The home directory defines the location for saving the ADS preference configuration file, located at HOME\hpeesof\config\hpeesofcfg SV_HOME This is used to define the home directory for Genesys, if defined If not defined SV_HOME is assumed to be the same as HOME The home directory defines the location for saving the Genesys preference configuration file, located at SV_HOME\hpeesof\config\hpeesofcfg If more than one user will be sharing the same computer, and they desire to use different preference settings, each user will need to define desired location of the home directory be setting SV_HOME in the user variable section of the Windows Environment Other environment variable settings: AGILEESOFD_LICENSE_FILE This can be set in lieu of setting License Path in the Authorization dialog in Genesys It should point to the directory location of your license file or to the network server This value should include license locations for other Agilent EEsof products as well, since this value can be used by all Agilent EEsof products The path list is a semicolon-separated list AGILEESOFD_LICPREF This can be set in lieu of setting Bundle Preferences in the Authorization preference dialog to set the bundle preference you prefer Again, this value can be used by other programs and so should include desired bundle preferences for other Agilent EEsof products Note that a bundle that does not apply for the product you are running will be skipped during license search The Windows Registry will contain a value that is used by Flex licensing software to location licenses as a backup if licenses cannot be found using the normal paths The Windows Registry can be edited with regedit run using Start- >Run For Agilent EEsof products, the registry key for License Path is HKEY_LOCAL_MACHINE\Software\Agilent\Flexlm License Manager\AGILEESOFD_LICENSE_FILE Flex licensing will add to this path any new location which has been successfully used to check out a license, so this path will generally include all of the license path settings for potentially a number of product If you know that some of these locations are no longer valid, you can safely delete them Both of the above variables will be overridden if you set preferences using the Authorization dialogs from within Genesys, so they are not necessary to set in the Windows Environment for running Genesys Do not edit the Windows Registry unless you know what you are doing, as small mistakes can affect the Windows environment itself, and/or keep the PC from running 37

39 Troubleshooting a License This section is provided to assist you in diagnosing licensing issues It is not intended to be complete, but should solve most issues that you may encounter If you need additional assistance, please contact Agilent Technical Support: Agilent Technical Support Viewing Diagnostic Information On the initial authorize screen select the Show My Current License Status button Note The License Status information will identify the license file or server used if it is found, as well as any error reported in the license Read the error messages to determine the cause of the licensing issue Some of the error messages that might be shown are: Invalid host The hostid of this system does not match the hostid specified in the license file Hardware Key drivers not installed License server machine is down or not responding No such feature exists (License does not contain a bundle by the name you provided, or other license with the needed feature) 38