SystemVue - Getting Startededadownload.software.keysight.com/eedl/systemvue/2010_07/... · 2014. 7. 24. · SystemVue - Getting Started 3 Agilent. The Contributors of the SystemC

SystemVue - Getting Started

1

SystemVue 2010.072010

Getting Started


2

© Agilent Technologies, Inc. 2000-2010395 Page Mill Road, Palo Alto, CA 94304 U.S.A.No part of this manual may be reproduced in any form or by any means (includingelectronic storage and retrieval or translation into a foreign language) without prioragreement and written consent from Agilent Technologies, Inc. as governed by UnitedStates and international copyright laws.

Acknowledgments Mentor Graphics is a trademark of Mentor Graphics Corporation inthe U.S. and other countries. Microsoft®, Windows®, MS Windows®, Windows NT®, andMS-DOS® are U.S. registered trademarks of Microsoft Corporation. Pentium® is a U.S.registered trademark of Intel Corporation. PostScript® and Acrobat® are trademarks ofAdobe Systems Incorporated. UNIX® is a registered trademark of the Open Group. Java™is a U.S. trademark of Sun Microsystems, Inc. SystemC® is a registered trademark ofOpen SystemC Initiative, Inc. in the United States and other countries and is used withpermission. MATLAB® is a U.S. registered trademark of The Math Works, Inc.. HiSIM2source code, and all copyrights, trade secrets or other intellectual property rights in and tothe source code in its entirety, is owned by Hiroshima University and STARC.

Errata The SystemVue product may contain references to "HP" or "HPEESOF" such as infile names and directory names. The business entity formerly known as "HP EEsof" is nowpart of Agilent Technologies and is known as "Agilent EEsof". To avoid broken functionalityand to maintain backward compatibility for our customers, we did not change all thenames and labels that contain "HP" or "HPEESOF" references.

Warranty The material contained in this document is provided "as is", and is subject tobeing changed, without notice, in future editions. Further, to the maximum extentpermitted by applicable law, Agilent disclaims all warranties, either express or implied,with regard to this manual and any information contained herein, including but not limitedto the implied warranties of merchantability and fitness for a particular purpose. Agilentshall not be liable for errors or for incidental or consequential damages in connection withthe furnishing, use, or performance of this document or of any information containedherein. Should Agilent and the user have a separate written agreement with warrantyterms covering the material in this document that conflict with these terms, the warrantyterms in the separate agreement shall control.

Technology Licenses The hardware and/or software described in this document arefurnished under a license and may be used or copied only in accordance with the terms ofsuch license.

Portions of this product is derivative work based on the University of California PtolemySoftware System.

In no event shall the University of California be liable to any party for direct, indirect,special, incidental, or consequential damages arising out of the use of this software and itsdocumentation, even if the University of California has been advised of the possibility ofsuch damage.

The University of California specifically disclaims any warranties, including, but not limitedto, the implied warranties of merchantability and fitness for a particular purpose. Thesoftware provided hereunder is on an "as is" basis and the University of California has noobligation to provide maintenance, support, updates, enhancements, or modifications.

Portions of this product include code developed at the University of Maryland, for theseportions the following notice applies.

In no event shall the University of Maryland be liable to any party for direct, indirect,special, incidental, or consequential damages arising out of the use of this software and itsdocumentation, even if the University of Maryland has been advised of the possibility ofsuch damage.

The University of Maryland specifically disclaims any warranties, including, but not limitedto, the implied warranties of merchantability and fitness for a particular purpose. thesoftware provided hereunder is on an "as is" basis, and the University of Maryland has noobligation to provide maintenance, support, updates, enhancements, or modifications.

Portions of this product include the SystemC software licensed under Open Source terms,which are available for download at http://systemc.org/ . This software is redistributed by

http://systemc.org/


3

Agilent. The Contributors of the SystemC software provide this software "as is" and offerno warranty of any kind, express or implied, including without limitation warranties orconditions or title and non-infringement, and implied warranties or conditionsmerchantability and fitness for a particular purpose. Contributors shall not be liable forany damages of any kind including without limitation direct, indirect, special, incidentaland consequential damages, such as lost profits. Any provisions that differ from thisdisclaimer are offered by Agilent only.With respect to the portion of the Licensed Materials that describes the software andprovides instructions concerning its operation and related matters, "use" includes the rightto download and print such materials solely for the purpose described above.

Restricted Rights Legend If software is for use in the performance of a U.S.Government prime contract or subcontract, Software is delivered and licensed as"Commercial computer software" as defined in DFAR 252.227-7014 (June 1995), or as a"commercial item" as defined in FAR 2.101(a) or as "Restricted computer software" asdefined in FAR 52.227-19 (June 1987) or any equivalent agency regulation or contractclause. Use, duplication or disclosure of Software is subject to Agilent Technologies´standard commercial license terms, and non-DOD Departments and Agencies of the U.S.Government will receive no greater than Restricted Rights as defined in FAR 52.227-19(c)(1-2) (June 1987). U.S. Government users will receive no greater than LimitedRights as defined in FAR 52.227-14 (June 1987) or DFAR 252.227-7015 (b)(2) (November1995), as applicable in any technical data.

http://systemc.org/


4

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Silent Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Uninstall Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Network License Server Installation (Administrators Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Installing Floating Licenses on a PC Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Accessing Licenses From a UNIX or Linux License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Special Licensing Needs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Licensing Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 SystemVue Authorization Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Setting up Floating License Server for SystemVue 2010.0x (Windows XP32, XP64, Vista32,Vista64 platforms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Evaluation Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Evaluating License File with a Token (through the product) . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Request an Evaluation License File with a Token (through the product) . . . . . . . . . . . . . . . . . 21

Evaluating License File with a Token (on the web) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Request an Evaluation License File with a Token (on the web) . . . . . . . . . . . . . . . . . . . . . . . 23

Evaluating License File Without a Token . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Request an Evaluation License File Without a Token . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Purchased Software Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Setting up Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Advanced Options - Using Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Troubleshooting a License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Viewing Diagnostic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Common License Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Windows Vista . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 License Information in the License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Using lmutil for Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

SystemVue 2010.07 Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 What's New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Issues Fixed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36


5

InstallationBefore beginning the installation, you should make sure you have everything needed tocomplete the installation and licensing steps. The licensing steps depend on what type oflicensing you are using. Please read the Licensing Overview (start) to determinewhich type of licensing applies to you.

If you would like to request a demo of any part of SystemVue, please seehttp://www.agilent.com/find/eesof-systemvue-evaluation

Installation Requirements2.0GB of free space on your hard driveRecommended minimum of 1GB of RAM, prefer 2GB of RAMAdministrator privileges

Windows Vista Administrator Account (start)Operating system that has the most recent updatesLicense File (or Authorization Codes, or token if evaluating) or Internet access

Operating Systems Supported versions 32-bit 64-bit

Windows XP Pro, SP2, SP3 Yes Yes

Windows Vista Business, Enterprise, or Ultimate SP1 Yes Yes

Windows 7 (Newly Supported) Business, Ultimate Yes Yes

Installation ProcedureYou can download the latest version of SystemVue from:1.http://www.agilent.com/find/eesof-systemvue-latest-downloads .Navigate to where you saved the SystemVue <*version>.exe installation image.2.Run the executable (SystemVue_<*version>_ .exe).3.The InstallAnywhere extracts the components and displays the Introdution tab. Click4.Next to proceed.Read the License Agreement and if you agree, select I accept the terms of the5.License Agreement and click Next.

The Choose Install Set tab appears. You can select from Complete, Typical6.(Default), Minimal and Custom options.

http://www.agilent.com/find/eesof-systemvue-evaluation


http://www.agilent.com/find/eesof-systemvue-latest-downloads



6

The Choose Install Folder tab appears. You can type a new location or proceed with7.the default location (C:\Program Files\SystemVue2010.01). Click Next to proceed.The Install FLEXid Drivers tab appears. You can select Yes or No depending upon8.whether you want to install FLEXid driver on your system or not. Click Next toproceed.The Pre-Installation Summary tab appears. Click Install to proceed with the9.installation or click previous to change any previously made choice.

Congratulations you have successfully installed SystemVue. The next step is to setup Licensing (start).Follow the steps appropriate for the type of licensing you are using.

Silent InstallationsThe InstallAnywhere program provided with SystemVue supports a silent installationmode. A normal (non-silent) installation receives the necessary input from the person


7

installing the software in the form of responses to prompts in dialog boxes. However, asilent installation does not display prompts for inputs. InstallAnywhere supports a silentmode that has no end-user interaction, and runs either using the defaults provided for acomplete install or using a response file that contains the values for variousInstallAnywhere variables, which control the installation.

Silent Installation Overview

Here is an overview on how to set up and run a silent installation.

If needed, run a silent uninstallation before hand to remove SystemVue.1.Run the SystemVue<*version>.exe utility using arguments for a silent installation2.(see below).

Running a Silent Installation

To run a silent installation, run the SystemVue<*version>.exe utility using the silentinstallation arguments shown below:

On the client PC, verify that SystemVue installation folder does not already exist.1.There should not be a C:\Program Files\SystemVue<*version> folder since the silentinstallation process is not expecting it to be there. If SystemVue has been installed,uninstall it before you continue.On the client PC, open a Command Prompt or DOS prompt window. In a command2.prompt, change to the folder that where SystemVue<*version>.exe is. The locationof the SystemVue<*version>.exe can be on a server.On the client PCs, perform one of the following actions to run a silent installation of3.SystemVue:

NoteWhen a silent installation is running you won't see any confirmation that the installer is running.However, the process monitor will show ads_install.exe processes running in the background.

Complete Silent InstallTo perfrom a complete silent installation without requiring any user interaction,type the following command from the command line:setup.exe -i silent

Custom Silent InstallThe custom silent installation gets its input from the response fileinstallvariables.properties created during a custom installation. To perform acustom silent installation without requiring any user interaction, create aresponse file then type the following command from the command linespecifying the path to the response file:setup.exe -f c:\tmp\your_response_file.txt -i silent

Creating Your Own Response File

When a normal installation runs, the inputs to prompts that are entered manually intodialog boxes are automatically recorded to a response file. By default, all of the variablesdefined in your installation are recorded. A response file is always generated after thesuccessful completion of an installation. InstallAnywhere creates this file when theinstallation exits, storing the values of the applicable properties in the file. This is usefulfor saving a record of a specific installation execution session that can later be reused in asilent or custom installation.

This response file is a plain text file that uses a simple key=value format. If you want tochange the settings in a particular response file, you can edit the response file directly orcreate your own from scratch.

The properties in the response file might look like:

INSTALLER_UI=silent

USER_INSTALL_DIR=c:\Program Files\SystemVue<*version>

CHOSEN_INSTALL_SET=complete

USER_SELECTED_FOLDER=c:\users\myuser

USER_DEFAULT_HOME=users\myuser

USER_HOME_FOLDER=c:\users\myuser

INSTALLER_UI allows you to specify the installer mode in the properties file, negating


8

the need to use the -i silent command-line switch.USER_INSTALL_DIR is the location where you wish to install SystemVue.USER_DEFAULT_HOME_FOLDER is the location where you wish to save yourconfiguration files and projects.CHOSEN_INSTALL_SET can be set to a value of either complete or custom.If you set it to "complete", you don't need to add theCHOSEN_INSTALL_FEATURE_LIST variable. The "complete" selection will install all ofthe SystemVue modules.If you select "custom", you need to set the CHOSEN_INSTALL_FEATURE_LIST.

Troubleshooting

The most effective way to troubleshoot errors with the silent install/uninstall process is torun the same type of installation in normal or visual mode.

Uninstall ProcedureSelect Start > All Program > SystemVue 2010.01 > Uninstall SystemVue1.2010.01The Uninstall dialog box appears. Select Uninstall Product and select Next to proceed2.and completely uninstall SystemVue 2010.01 from your system.

Note: To completely uninstall SystemVue 2010.01 from your PC, delete the SystemVue 2010.01 installfolder (default:C:\Program Files\SystemVue2010.01) and the following registry entryHKEY_CURRENT_USER > Software > Agilent > SYSTEMVUE2010.01.


9

Network License Server Installation(Administrators Only)

These instruction use Acresso release 11.6.0, but they apply to all releases from 10.0 to 11.XThe instructions assume you are installing on a Windows Server but can be easily interpreted for otheroperating systems.

Installing Floating Licenses on a PC ServerUse the following sections to install your floating licenses. You should have installed theclient before you complete these steps. For details on installing the client on a PC runningWindows, please refer to Installation (start).

ImportantBe sure to use the following information to update all existing license servers with the latest version of theFLEXnet software (e.g., lmgrd and lmutil). The software is installed with the client. Using older versionsmay 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 inuse. Run lmutil directly from the client installation location (c:\<installation folder>\license\bin) forinformation to help modify the scripts. Normally the installation folder would be Program FilesSystemVue<version> where version is a release version, like 2009.04 or 2009.08.

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

Installing the License File

The license.lic file that implements FLEXnet security must be installed. The default installpath is: c:\<installation folder>\license. Copy the license.lic 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 installthe license.lic file on the license server machine.

Entering the Hostname

Change the default hostname setting in your license file to the actual hostname of yourlicense server. The license server is the machine that will serve the licenses on thenetwork, and whose Ethernet address or FLEXID hardware key number, appears on theSERVER 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 license.lic files are generated with SERVER lines with the following format:

SERVER <hostname> <hostid>

where:

<hostname> is set to unknown by default<hostid> is the 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 isacceptable 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 thec:\<installation folder>\license\bin folder. When lmgrd is started from the c:\<installationfolder>\license\bin folder, it looks for agileesofd in the same folder. If agileesofd is not in


10

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 aWindows PC, you must also specify the port number the vendor daemon uses. You canspecify the port number on the license file's VENDOR line. If the port is not specified, thedefault 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 theirconnections to the daemon. Here is an example of a properly configured VENDOR lineincluding 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 0.1 second. If you need a longer timeout period, you can setthe environment variable FLEXLM_TIMEOUT to a new value. Enter the value usingmicroseconds. 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 toallow connections without slowing down simulations excessively.

Starting FLEXnet

FLEXnet can be started either manually or automatically. You must start the FLEXnetlicense 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 othermachines (clients) and user login accounts.

To start FLEXnet you need the following.

FLEXnet software installed in the c:\<installation folder>\license folder. This is donewhen you install the client.The license server machine connected to the network using the TCP/IP networkprotocol.A local copy of the license.lic file that contains the FLEXnet licenses. Every machinethat will run must be able to access the license.lic file used by the license server(s) tocheck out a license. Access to the license.lic file can be via a local copy of thelicense.lic file or through a network drive.Properly configured SERVER and VENDOR lines in your license.lic file.

If you have a three-server redundant configuration, you must start FLEXnet on all threeservers before the licenses will be available on the network. Once you have FLEXnetrunning, you can configure the other machines (clients) and user login accounts that needto 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 isgenerally not recommend for a server machine, because it requires a dedicated MS-DOSCommand Prompt to be open at all times and it requires re-starting after rebooting thelicense server. Use the following steps to start the FLEXnet executable file, lmgrd.exe:

From a MS-DOS Command Prompt, change to1.c:\<installation folder>\license\binType the following command specifying the full path and location of the license file.2.lmgrd -app -c c:\<installation folder>\license\license.lic -l

c:\<installation folder>\licenses\flex.log

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

lmutil lmdown -c c:\<installation folder>\license\license.lic


11

Starting FLEXnet Automatically

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

To start the license manager automatically:

From a MS-DOS Command Prompt, change to1.c:\<installation folder>\license\bin.Enter the full path and filename of both the license executable file and the license.lic2.file. The default location for the executable file is c:\<installationfolder>\license\bin\lmgrd.exe. (The flex.log file is useful for troubleshooting.)installs -e <path to lmgrd> -c <path to license file> -l <path to flex.log>

For example:installs -e d:\<installation folder>\license\bin\lmgrd.exe -cd:\<installation folder>\license\license.lic -l d:\<installation folder>\license\flex.logIf you don't specify a flex.log file using the "-l" option when you run installs.exe,FLEXnet creates a default log file in the system32 folder. While this default log filedoes not contain as much information, it can still be useful. This file is typicallylocated in c:\winnt\system32\ and is named lmgrd.log or lmgrd.xxxx where "xxxx" isthe process ID number of lmgrd.Activate the license server by starting the FLEXnet service using the Control Panel or3.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 FLEXnetstartup:

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 theinstalls -r command, reinstall FLEXnet using the new location, and then reboot yoursystem.

Accessing Licenses From a UNIX or Linux LicenseServerYou can access licenses from a UNIX or Linux license server by doing the following:

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

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 installedhowever to run a server on a UNIX/Linux platform, but you will need to download the licensedaemon software separately since SystemVueincludes only the PC version of this software.

Setting Up the UNIX or Linux License Server

You must use version 11.6 or higher of the FLEXnet daemons lmgrd and agileesofd. Usethe following commands to check the version of lmgrd and agileesofd on your UNIX/Linuxlicense 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):

Stop the current FLEXnet daemons on the license server:1.cd $HPEESOF_DIR/licenses/bin


12

. /lmutil lmdown -c ../license.licReplace the following files with the supported FLEXnet version files:2.$HPEESOF_DIR/licenses/bin/lmgrd$HPEESOF_DIR/licenses/bin/lmutil$HPEESOF_DIR/licenses/bin/agileesofdIf you have more than one license server, make sure you do this on all of them.Restart the license daemons on the UNIX/Linux license server(s):3.cd $HPEESOF_DIR/licenses/bin. / lmgrd -c ../license.lic -l ../flex.log

Setting Up the Client(s)

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

By copying the license.lic file from the UNIX/Linux license server to the PC'sc:\<installation folder>\license folderBy setting the SYSTEMVUE_LICENSE_FILE variable on the PC to point to theUNIX/Linux license server as follows:set SYSTEMVUE_LICENSE_FILE =<port>@<host> (You can also useAGILEESOFD_LICENSE_FILE, as this value will be used if SYSTEMVUE_LICENSE_FILEis not defined.)By using the authorization dialogs in SystemVue to set the License File location asusing <port>@<host>For example:set SYSTEMVUE_LICENSE_FILE =27000@joshua

where 27000 is the port number on the SERVER line in the license.lic file on theUNIX/Linux license server and joshua is the hostname of the UNIX/Linux licenseserver.

Special Licensing NeedsBe sure to use the lmtools utility to install a license on a server that is already runningFLEXnet. For details on using FLEXnet, refer to the Acresso website at:

http://www.acresso.com/

Using FLEXnet Options

An options file enables the license administrator to control the security parameters ofFLEXnet. 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, youshould keep the options file in the same directory as your license.lic file. Also, add thepathname to the options file in the license.lic file as the fourth field on the VENDOR linefor 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\agileesofd.optYou can include comments in your options file by starting each comment with a poundsign '#'. Everything in the options file is case-sensitive. Be sure that user names andfeature names, for example, are entered correctly. The available options are:

EXCLUDEDeny a user access to a feature.EXCLUDEALLDeny a user access to all feature served by this vendor daemon.GROUPDefine a group of users for use with any options.




13

INCLUDEAllow a user to use a feature.INCLUDEALLAllow a user to use all features served by this vendor daemon.NOLOGTurn off logging certain items.REPORTLOGSpecify that a logfile be written suitable for use by the FLEXadmin End-UserAdministration Tool.RESERVEReserve licenses for an individual user or groups of users.TIMEOUTWorks only for specified simulator and library licenses.TIMEOUTALLWorks for all simulator and library licenses.

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

Create an options file with your required options.1.Modify your license.lic file so that the VENDOR or DAEMON line points to this option2.file as shown in this example:VENDOR agileesofd c:\<installation folder>\license\vendors\agileesofd \c:\<installation folder>\license\agileesofd.optStart up your license server (lmgrd) that is pointing to your license file. You must3.stop it first if it is running. It's important that a message is displayed or recorded inthe FLEXnet log verifying the license manager is using the options file. The followingexample shows that the license manager is using the agileesofd.opt file containingthe TIMEOUTALL option set to 900 seconds:17:35:14 (agileesofd) Using options file: "c:\<installationfolder>\license\agileesofd.opt"17:35:15 (agileesofd) ALL FEATURES: INACTIVITY TIMEOUT set to 900 secondsSet SYSTEMVUE_LICENSE_FILE to point to your license server.4.

Specifying the TIMEOUT Option

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

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

TIMEOUT feature_name secondswhere:feature_name is name of the feature.seconds is the number of seconds before inactive license is reclaimed. Theminimum value is 900 seconds (15 minutes). If you specify a time-out valuesmaller 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 (3600seconds):TIMEOUT sim_harmonic 3600

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


14

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, youcan add the new licenses to the FLEXnet environment as follows:

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

Merging Multiple Vendor Licenses

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

Multiple license server nodes; each running one lmgrd and one license fileOne license server node running one lmgrd and one license fileOne 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 morelicense servers to monitor. With the third option you have only one server but multiplelmgrds to administer.

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

If the license files for two or more products contain identical hostids on the SERVERline(s), then these files can be combined.If the license files for two products contain different hostids on a SERVER line, thenthe license servers for those products will be running on different nodes and thelicense files cannot be combined.

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

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

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

The number of SERVER lines in each file is the same.1.The hostid field of each SERVER line in one file exactly matches the hostid field of2.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 forredundant servers (has multiple SERVER lines).One vendor uses a custom hostid algorithm, so the hostids on the SERVER lines aredifferent even though the files are for the same machine.

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


15

Combining License Files from Multiple Vendors

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

If you combine license files from multiple vendors, it is a good idea to keep a copy of thecombined license file in each vendor's default license file location. This way, your userscan avoid having to set AGILEESOFD_LICENSE_FILE, because each package finds itslicense information in the default place. On UNIX or Linux, you can do this with a symboliclink 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 productsmay not use the same version of FLEXnet. FLEXnet is designed to handle this situation.There are two basic compatibility rules for FLEXnet:

A newer lmgrd can be used with an older vendor daemon, but a newer vendor1.daemon might not work properly with an older lmgrd.A newer vendor daemon (or lmgrd) can be used with an older client program, but a2.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 ofadministration tools to use:

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

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

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 copiesof lmgrd, there are two details to remember:

The port number on the SERVER line of each license file must be unique. You can use1.a standard text editor to change the port number in each license file so that they areall different.You must make sure that you are using a compatible version of lmgrd when you start2.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 theAGILEESOFD_LICENSE_FILE environment variable to point to multiple license files. Forexample, you may have a license file from vendor ABC and a license file from vendor XYZwith incompatible servers. You can place the license file from vendor ABC into:

c:\user\flexnet\abc.lic

and the license file from vendor XYZ into:

c:\user\flexnet\xyz.lic

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

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

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

Redundant License Servers

FLEXnet enables you to set up a redundant license server configuration. This involves


16

configuring three license servers with one of the three servers functioning as the masterserver. If the master server goes down, one of the other two servers becomes the newmaster server, and the licenses remain available on the network.

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

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

Controlling License Path Settings

The lmutil utility provides the lmpath function which allows direct control over FLEXnetlicense path settings. You can use lmpath to add to, override, or get the current licensepath set in the registry. This enables you to change or view path settings without locatingindividual 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 inyour 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 settingsor creates the list of license-path settings, if it doesn't exist, initializing it tolicense_path_list. Duplicates are discarded.

-override overrides the existing list of license-path settings with the contents oflicense_path_list. If license_path_list is the null string, "", the specified list isdeleted. 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 ofvendor _LICENSE_FILE. For example, use agileesofd to affectAGILEESOFD_LICENSE_FILE.

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

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

NoteEnvironment 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 currentsettings. To display the settings, enter the following commands:


17

lmutil lmpath -status

The following example status listing is from UNIX and is similar to PC and Linux listings:lmutil - Copyright (C) 1989-2007 Acresso Software Inc. All rights reserved.Known Vendors:_____________agileesofd: /ads2006/licenses/license.lic:/<installation folder>/licenses/license.lic_____________Other Vendors:______________C: \flexlm\license.dat

NoteWhere a path is set to a directory, each of the *.lic files are listedseparately.

Changing License Path Settings

When adding or overriding path settings, lmpath sets the FLEXnet entry in the Windowsregistry on the PC, or changes the file $HOME/.flexlmrc on UNIX/Linux. Here are examplesof 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 onWindows, or a terminal window on UNIX/Linux. You can adapt the following exampleswhich 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>


18

Licensing OverviewThe new license is backward compatible with all the previous versions.

SystemVue Authorization ProcessWhen you start an unlicensed version of SystemVue; the Authorization screen appearsas shown below:

Depending on the type of license you have, please select the option from the Authorizationscreen:

Evaluation (start)1.Purchased Software (start)2.

For troubleshooting information:

Troubleshooting a License (start)

Setting up Floating License Server for SystemVue2010.0x (Windows XP32, XP64, Vista32, Vista64platforms)

Download License server software and drivers

Click on the link below to download the required license server software and drivers:1.

http://www.home.agilent.com/agilent/editorial.jspx?action=download&cc=US&lc=eng&ckey=1662355&nid=-34275.0&id=1662355

Select link for Windows (32-bit & 64-bit) FLEXnet 11.6 Windows,2.When the zip file is completely downloaded, unzip it. A folder called"FLEXnet11.6_Windows" is created.IF your license file is going to be tied to a USB hardkey (dongle), you will need to3.FIRST download and install the dongle driver software and install dongle driver.Please refer to document called "InstallingDongleDriver.doc". The USB hardware keyshould have a number on it to the tune of "9-xxx...". If your license is tied to theEthernet address of your network card, you may continue forward with thisprocedure.

Edit your license file

To continue, you should have received a license.lic file from Agilent EEsof Business1.Support to run SystemVue 2010.0x. If you have never received a license.lic file or





19

may have lost it, contact Agilent EEsof Business Support to obtain the file, 1-877-563-1688 or [email protected] license file and enter name of license server in SERVER line. For example, in the2.file below, the name "redwood" has been entered. The original file had the word"unknown"

Run lmtools.exe (acquired from download described in Section I).

Change directories to location where License Server Software was downloaded and1.unzipped. There is a folder, "FLEXnet11.6_Windows" in this location having foldersfor 32 bit and 64 bit. Depending upon your Windows operating system, changedirectories to the desired folder:

Windows XP32, Vista 32-go into "32bit" folderWindows XP64, Vista 64-go into the "64bit" folder

Launch the lmtools.exe application to start the license server setup process.2.

Make sure Configuration using Services is selected.3.Click the Config Services tab. The initial contents of that tab appear as shown below:4.

Now, enter the following fields:5.Enter Service name. You may use a name of your choice such as Agilent LicenseServer.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 atPower Up" (IMPORTANT: Use Services must first be selected to be able to selectStart Server at Power up).


20

Lastly, press Save Service. The completed window should appear something likeas shown below:

Go to Start/Stop/Reread tab as shown below and press start server.6.

NOTICE THAT SERVICE NAME APPEARS. IF not there could be a problem.

As a final step to ensure things are okay, go back to the Config Services tab and click7."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 SystemVue. Thetoken is issued by an Agilent employee, allowing you to request a license without any further approval. Ifyou 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:

Download and Install SystemVue ( http://www.agilent.com/find/eesof-1.systemvue-latest-downloads ).Request an Evaluation License. There are three ways you can request an2.evaluation license:

With an Evaluation Token (on the web) (start)With an Evaluation Token (through the product) (start)Without an Evaluation Token (start)

Activate the Evaluation License by authorizing SystemVue using the license.lic3.file. This will depend on what you choose in step 2, and the instructions are describedin those sections.





21

Evaluating License File with a Token(through the product)

If you are an existing customer that is already running the version of SystemVue you are requesting anevaluation for, this process will change your licensing options and you will need to change them back afterthe evaluation period.

Request an Evaluation License File with a Token(through the product)

Install SystemVue using the Web Installation Instructions (start)1.Open SystemVue from the shortcut on your desktop or from Start/All2.Programs/SystemVue<*Version>/SystemVue.exe where, <*Version> is the versionof interestChoose Evaluation as shown below and click Next.3.

Choose I have a token and want to request a license file as shown below and4.click Next.

The next screen explains the steps for obtaining an evaluation license with a token.5.There is also a link to the Agilent privacy policy.There will be two screens were you will enter information needed to complete the6.evaluation request. Your MAC address is pre-filled. Under most circumstances this isthe 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 youuse to access the internet. You can query the addresses of your interfaces by running


22

ipconfig /all in a Command Prompt window.Next you will see the Successful request screen. Click Finish to end the request7.process.When you receive the email with the license.lic file attached, copy the file in the8.C:\Program Files\ SystemVue<*Version>\License folder.Open SystemVue from the shortcut on your desktop or from Start/All Programs/9.SystemVue<*Version>/SystemVue.exe, where <*Version> is the version of interest.Choose Evaluation and click Next as shown in SystemVue License Authorization10.figure above.Choose I have a license file and click Next as shown in SystemVue License11.Authorization-Request MethodClick the Change Path button as shown in SystemVue License Authorization-12.Path/Bundle Selection below. Please add the path where the license.lic file wassaved in step 8. The recommended path is C:\Program Files\SystemVue<*Version>\License, which should be the default location selected usingthe Browse button. If there are any other "@path" paths noted, please delete them.Click OK.

Click Change Bundle button for Current Bundle Selection. The Agilent License13.Preference window will open. If SystemVue bundles starting with b_sv_ are shownunder the Available License Bundles the license.lic file was detected.Select the SystemVue bundle and click on "Add >>". Click OK.14.Once the License Path and the bundle have been selected, it will be displayed under15.the Licensing Options section. Click Finish.Once the Authorization process has been finished, a prompt that SystemVue needs to16.be restarted will appear.Open SystemVue from the shortcut on your desktop or from Start/All Programs/17.SystemVue<*Version>/SystemVue.exe, where <*Version> is the version of interest.If a Authorization Failed prompt appears, please check Show My Current18.License Status.... If the message is not clear, please email a screen shot of thiswindow 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.

http://www.home.agilent.com/agilent/contactInformation.jspx?lc=eng&cc=US&nid=-34360.0.00&pageMode=SS



23

Evaluating License File with a Token(on the web)

If you are an existing customer that is already running the version of SystemVue you are requesting anevaluation for, this process will change your licensing options and you will need to change them back afterthe evaluation period.

Use of Remote Desktop Connection is considered network usage of the product and is not supported withthe node locked evaluation licenses

Request an Evaluation License File with a Token (onthe web)

Go to http://www.agilent.com/find/eesof-systemvue-evaluation . From this web1.page:

Click the button Request a Product DemoSelect the second radio button Redeem an Evaluation Token. After the SendRequest button has been selected, an email will be sent with an attachedlicense.lic file. (request processed within seconds)

Install SystemVue using Step 1 in the Evaluation License email that is sent to you.2.Once the installation is finished, copy the license.lic file that was attached to the3.email in the C:\Program Files\ SystemVue<*Version>\License folder.Open SystemVue from the shortcut on your desktop or from Start/All4.Programs/SystemVue<*Version>/SystemVue.exe, where <*Version> is the versionof interestChoose Evaluation as shown below and click Next.5.

Choose I have a license file as shown below and click Next.6.




24

Click the first Change Path button as shown in SystemVue License7.Authorization-Path/Bundle Selection below. Please add the path where thelicense.lic file was saved in step 3. The recommended path is C:\Program Files\SystemVue<*Version>\License, which should be the default location selected usingthe Browse button. If there are any other "@path" paths noted, please delete them.Click OK.

Click on the second Change Bundle button for Current Bundle Selection:. The8.Agilent License Preference window will open. If one or more SystemVue bundlesstarting with b_sv_ are shown under the Available License Bundles the license.licfile was detected.Select the SystemVue bundle and click on "Add >>". Click OK.9.Once the License Path and the bundle have been selected, it will be displayed under10.the Licensing Options section. Click Finish.Once the Authorization process has been finished, a prompt that SystemVue needs to11.be restarted will appear.Open SystemVue from the shortcut on your desktop or from Start/All12.Programs/SystemVue(*Version)/SystemVue.exe, where (*Version) is the version ofinterest.If a Authorization Failed prompt appears, please check Show My Current13.License Status.... If the message is not clear, please email a screen shot of thiswindow 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.




25

Evaluating License File Without a Token Request an Evaluation License File Without a Token

Make the request:Go to http://www.agilent.com/find/eesof-systemvue-evaluation .

From this webpage:Click the button Request a Product DemoSelect the radio button Request an Evaluation License and fill in the formwith the appropriate information.

Approval will typically occur within 48 hours. After you are approved, an evaluation license willbe sent to the email address entered on the form.

After the license file email is received:Install SystemVue using Step 1 in the Evaluation License email that is sent toyou.Once the installation is finished, copy the license.lic file that was attached to theemail in the C:\Program Files\ SystemVue<*Version>\License folder.Open SystemVue from the shortcut on your desktop or from Start/AllPrograms/SystemVue<*Version>/SystemVue.exe, where <*Version> is theversion 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 SystemVue LicenseAuthorization-Path/Bundle Selection below. Please add the path where thelicense.lic file was saved in step 2. The recommended path is C:\Program Files\SystemVue<*Version>\License, which should be the default location selectedusing the Browse button. If there are any other "@path" paths noted, pleasedelete them. Click OK.




26

Click the Change Bundle button for Current Bundle Selection. The AgilentLicense Preference window will open. If SystemVue bundles starting with b_sv_are shown under the Available License Bundles the license.lic file wasdetected.Select the SystemVue bundle and click on "Add>>". Click OK.Once the License Path and the bundle have been selected, it will be displayedunder the Licensing Options section. Click Finish.Once the Authorization process has been finished, a prompt that SystemVueneeds to be restarted will appear.Open SystemVue from the shortcut on your desktop or from Start/All Programs/SystemVue<*Version>/SystemVue.exe, where <*Version> is the version ofinterest.If a Authorization Failed prompt appears, please check Show My CurrentLicense Status.... If the message is not clear, please email a screen shot ofthis window to support. Contact information is on the page Agilent TechnicalSupport . Please be sure to include your host ID in your correspondence.





27

Purchased Software LicensingBefore you begin:You will need to know the full path to the local license file (license.lic), or the name of your company'slicense server.

Note: Use of Remote Desktop Connection is considered network usage of the product and is not supportedwith node locked licenses.

Advanced Design System (ADS) Users ONLYIf 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 SystemVue for license preferences settings. The defaultsettings create a home directory at C:\users\default. If you plan to use a different HOME setting otherthan the default, then define SV_HOME in your Windows Environment before you run SystemVue for thefirst time. This can be set to the same setting as HOME for your ADS installation, which will enable sharingthe same configuration file, or a separate location if you don't want to share the configuration file withADS. The ADS configuration file will be located at HOME\hpeesof\config\hpeesof.cfg and the SystemVueconfiguration file will be located at SV_HOME\hpeesof\config\hpeesof.cfg. If not defined, SV_HOME will beassumed to be the same as HOME and if not defined HOME will be assumed to be C:\users\default. SeeAdvanced Options below for more information on Window Environment variables.

Setting up LicensingOpen SystemVue from the shortcut on your desktop or from Start/All1.Programs/SystemVue<*Version>, where <*Version> is the version of interest, i.e.2009.05. If you are currently running SystemVue choose Update AuthorizationInfo as shown below from the Help menu.Select Purchased Software and click Next as shown below:2.

Click the Change Path button for Current License Path as shown below:3.


28

If you have a nodelocked license, use the Browse button to easily browse to the4.directory where the license.lic file is located. If the licenses you need are availablefrom 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 alsoprecede the @ sign with the port number for you license; this is not required but itcan improve the performance of license search. Tip: when using a combination oflocal and license server licenses, list the local license file locations first in your path.

NoteNodelock installation of multiple license filesTo have Multiple license files (issued with the same name) tied to different hardware keys need tobe installed on a single computer, the licensing system only looks for the .lic extension and not thename in front of it. This means that the 3 license.lic files can be renamed license1.lic, license2.licand license3.lic and copied to the same license folder without collision. Then when the USB key 1 isplugged in, it will look for license1.lic.

Click the Change Bundle button for Current Bundle Selection.1.The bundles available will be listed in the left pane and selected bundles in the right2.pane. The bundles that apply to your product will appear in bold color. To select alicense bundle, choose the bundle (click to highlight it) from the left pane and clickAdd >>. After the license bundle is listed in the right pane; click OK as shownbelow:


29

Click Finish. You will be prompted to re-launch SystemVue for the changes to take3.effect.SystemVue will start.4.

Advanced Options - Using Environment VariablesAs an advanced option (mainly for System Administrators) you can manually set thelicense path and bundle name using Windows Environment variables. Generally theseshould be defined before you run SystemVue for the first time, since these values canaffect the Authorization process. To define Windows Environment variables:

On Windows XP, choose Start > Settings > Control Panel > System > Advancedtab > Environment Variables button.Your environment variable can be entered either as a user variable or as a systemvariable. The user variable affects only the currently logged-in user; the systemvariable affects all users.Environment variables of interest:

HOME This is used to define the home directory for ADS, which SystemVue willuse if defined. The default value for ADS is C:\users\default. The home directorydefines the location for saving the ADS preference configuration file, located atHOME\hpeesof\config\hpeesof.cfg.SV_HOME This is used to define the home directory for SystemVue, if defined.If not defined SV_HOME is assumed to be the same as HOME. The homedirectory defines the location for saving the SystemVue preference configurationfile, located at SV_HOME\hpeesof\config\hpeesof.cfg.

If more than one user will be sharing the same computer, and they desire to use differentpreference settings, each user will need to define desired location of the home directory besetting 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 inthe Authorization dialog in SystemVue. It should point to the directory locationof your license file or to the network server. This value should include licenselocations for other Agilent EEsof products as well, since this value can be usedby all Agilent EEsof products. The path list is a semicolon-separated list.AGILEESOFD_LICPREF This can be set in lieu of setting Bundle Preferences inthe Authorization preference dialog to set the bundle preference you prefer.Again, this value can be used by other programs and so should include desiredbundle preferences for other Agilent EEsof products. Note that a bundle thatdoes not apply for the product you are running will be skipped during licensesearch. The Windows Registry will contain a value that is used by Flex licensingsoftware to location licenses as a backup if licenses cannot be found using thenormal paths. The Windows Registry can be edited with regedit run using Start->Run... For Agilent EEsof products, the registry key for License Path isHKEY_LOCAL_MACHINE\Software\Agilent\Flexlm LicenseManager\AGILEESOFD_LICENSE_FILE. Flex licensing will add to this path anynew location which has been successfully used to check out a license, so thispath will generally include all of the license path settings for potentially anumber of product. If you know that some of these locations are no longer valid,you can safely delete them.


30

Both of the above variables will be overridden if you set preferences using the Authorizationdialogs from within SystemVue, so they are not necessary to set in the Windows Environmentfor running SystemVue.

Do not edit the Windows Registry unless you know what you are doing, as smallmistakes can affect the Windows environment itself, and/or keep the PC fromrunning.


31

Troubleshooting a LicenseThis section is provided to assist you in diagnosing licensing issues. It is not intended tobe complete, but should solve most issues that you may encounter. If you need additionalassistance, please contact Agilent Technical Support:Agilent Technical Support

Viewing Diagnostic InformationOn 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 asany 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 thelicense 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 youprovided, or other license with the needed feature.)




32

Common License ProblemsThe license file or server cannot be found. The License Path you specified does1.not point to a valid license file, or the server you are trying to use is not available. Ifyou are using a license file, check the directory location you entered. Note that thisnormally is a directory, and all files in the directory with .lic extension are read aslicense files. Note that although we typically send licenses in a file called license.licthe root name of the file can be changed as needed to allow multiple files in the samelicense directory.License file is found, or server appears to be available but licenses are not2.checked out even though the license path contents appear valid. There can beseveral possible causes to this problem, but some of the most common are:

The MAC address is incorrect, or the interface for that address is disabled andnot visible to the software.The license is configured for a USB hardware key, but the key is not present, orit is the wrong key for the license. Note that Eagleware USB keys are notsupported for SystemVue.The license file used is configured for floating license but no server has been setup. In this case you should download and setup the server software.Remote Desktop Connection is used with a node locked license. This isconsidered network usage and is not supported with a node locked license.The license file is for an older version of the program, and cannot be used forthe current software.

No SystemVue bundles are displayed for bundle selection The SystemVue3.bundle names start with b_sv_ and will be displayed in bold color. If no bundles aredisplayed, or they are all in light font, then the license file read is probably the wrongone - not for SystemVue. Check the License Path definition.The Authorization dialogs seem to freeze during the authorization process.4.Most likely a prompt dialog requiring input is being displayed, but another window ison top and obscuring it, so the prompt cannot be seen. Try using the Alt-ESC keycombination until the correct window pops to the forefront.A License Path is selected and correctly used for Bundle Selection, but on5.running SystemVue a second time, another License Path is apparently beingused, and authorization is required each time SystemVue is started. TheLicense Path override value is saved in the file HOME\hpessof\config\hpeesof.cfg, where HOME may be defined in the Windows environment. If HOME is not defined,it is assumed to be C:\users\default. This response can be due to the file not beingwritable - either because it has been set as read only, or Windows is protecting thefile or directory. Another cause can be that HOME is improperly defined, and does notspecify a valid directory location. Note that if you have ADS installed, you can use thesame HOME location for SystemVue.


33

Bundle Selection seems to be successful, but on second entry, no bundle is6.displayed. The Bundle Selection cannot be saved in the hpeesof.cfg file. See theprevious item as the same reasons will apply. If the License Path and BundlePreference are not defined for SystemVue but correctly defined for ADS in theWindows Environment (AGILEESOFD_LICENSE_FILE), or Windows Registry(HKEY_LOCAL_MACHINE\Software\Flexlm LicenseManager\AGILEESOFD_LICENSE_FILE), SystemVue may still run successfully usingautomatic bundle selection, and the SystemVue bundle with fewest features will beautomatically selected.Startup time is very long. This can be due to server based licensing problems. If7.you are using a local license file for SystemVue, and do not require a server, you candelete the sever references from the SystemVue License Path. If you are using serverbased licenses, network license response time can be shortened by explicitlyspecifying the license port number in the form of port@server. Your licenseadministrator can give you the correct port number. If you are using a combination ofa local license file with additional server based features, list the local license path firstin the semicolon-separated path list. It may also be helpful to reduce the timeoutsetting for waiting on servers to responde. This can be done by setting theFLEXLM_TIMEOUT value in the Windows environment (right-click "My Computer", goto Properties, Advanced, Environment Variables). If you set FLEXLM_TIMEOUT to 0this will turn off delay altogether, but then you might get a denial too quickly if thereis some latency in the network. The units are microseconds, so you might try using asetting like 1000 or less, which sould allow a reasonable time but shorten things upquite a bit.After installing ADS, SystemVue ceases to run. This can happen if HOME was8.not defined when you installed SystemVue, and you define HOME to a differentlocation than C:\users\default during ADS installation. In this case, you can enableSystemVue to find the License Path and Bundle Selection settings by definingSV_HOME to C:\users\default in the Windows Environment, or by re-entering thesesettings through the Authorization procedure.If you are not using ADS, you can probably delete the environment variables9.LM_LICENSE_FILE and AGILEESOFD_LICENSE_FILE. These will not normally be usedby SystemVue unless you have not defined the license path during SystemVueauthorization. Note that other non-EEsof products may also use LM_LICENSE_FILE,so if there are references to non-EEosf licensing in this value, it is safest to keep it.To reduce license confusion, backup and remove all license files you have used in the10.past but are not currently using, and keep only current licenses. The Flex licensingfiles will normally have an extension of .lic.

Windows VistaInstallation using the Vista operating system can sometimes be more difficult due to strictUser Access Control policies enforced by Vista. In general you will need to haveAdministrator privilages to sucessfully install on Vista. In particular, the HOME directorymust be writable, as some configuration will be written to the subdirectory hpeesof underthe HOME directory. HOME can be defined in the Windows environment, and if not definedthe software will use the location C:\users\default for locating the configurationinformation. For more Vista information, see:

Windows Vista Administrator Account (start)Disabling Hide the List of User Accounts In Windows Vista (start)

License Information in the License FileQuite a bit of information about your licenses can be easily determined by reading thelicense file. Here are some general pointers on understanding the contents:

A SERVER line at the top of the file identifies a server-based floating license. Notethat the second and third fields in this line identify the actual name of the hostcomputer running the server, and the host ID expected for that computer.Each INCREMENT line identifies a license. The fourth and fifth fields on this lineidentify the license version and expiration date. The sixth field indicates the usecount allowed. For node-locked licenses this is typically "uncounted".In the INCREMENT line, the HOSTID= value embedded in the VENDOR_STRINGindicates the host ID required by the license. Licenses locked to a LAN MAC addresshave a 12-digit hexadecimal number for a host ID. License locked to a USB hardwarekey identify the key number preceded by FLEXID=


34

Using lmutil for Diagnosticslmutil is a useful tool that is typically found in the bin subdirectory of your productinstallation. You can run this utility from a Command Prompt window. Here are someuseful functions of the utility:

Use lmutil lmhostid -flexid to read the key number from a USB hardware key, orlmutil lmhostid -ether to list the LAN MAC adresses found on your computer. (Notethat if you have more than one LAN interface on your computer, you will get moreinformation identifying the interfaces by using ipconfig -all.)Use lmutil lmstat -c @servername to determine if a server is running and able torespond to license requests.Use lmutil lmdiag -c @servername to list out all licenses available on a server.

Disabling Hide the List of User Accounts (Vista Business andUltimate only)

Open the Start menu Search box, type secpol.msc and press Enter1.Expand the Local Policies branch and click on the Security Options folder.2.In the right pane, double-click the Interactive logon: Do not display last user3.name option, select Enabled, and click OK.

Windows Vista Administrator Account

To enable the Administrator account in Windows Vista (32,64):

Open the Start menu, type lusrmgr.msc in the Search box and press Enter to start1.the Local Users and Groups toolIn the left pane, select Users2.In the middle pane, double click on Administrator3.Turn off the Account is disabled option, and click OK.4.Right-click Administrator and select Set Password5.Choose a password for the new account, type it into both boxes, and click OK6.Close the Local Users and Groups window when finished7.Log out of current session, and then log in as Administrator. If the Administrator8.account does not appear on the Welcome Screen, please see Disabling Hide the Listof User Accounts In Windows Vista (start).


35

SystemVue 2010.07 Release NotesSystemVue 2010.07 is an application-oriented release, delivering new products forRADAR and IBIS-AMI model generation. SystemVue 2010.07 also adds severalconvenience and maintenance items for greater productivity, concentrating on the coreSystemVue environment.

What's New

Improvements to the Core Platform (W1461)

Improved interface to MATLABAllows your separate installation of MATLAB (and any add-on personalities) to besubstituted directly as the math language parser on an object-by-object basis inSystemVue MathLang parts, Equation windows, and Graphs. (requires anyappropriate MATLAB licenses)Allows easier integration, re-use, and debugging of existing .m files, use of PLOTcommands, and other MathWorks features, such as the MEX compiler, forultimate confidence in your system-level design flow.

New link to Agilent's N1010A FlexDCA oscilloscope software for visualization

SystemVue now provides free access to the base configuration of the AgilentN1010A FlexDCA analysis and visualization softwareAppears as a new SystemVue "measurement sink"Allows visualization, automated measurement, and run-time tuning of time-domain waveforms (using the "oscilloscope" mode) or eye diagrams (using the"eye" mode). Note that the Jitter and De-embedding personalities of theN1010A FlexDCA software are added-cost options. They are availableseparately from your Agilent test equipment representative.The N1010A FlexDCA software is a separate download from SystemVue. Availability begins in mid-September 2010. For more information on the N1010A FlexDCA product, please refer tohttp://www.agilent.com/find/n1010a

Direct support for co-simulation with Agilent ADS Ptolemy Allows SystemVue users who are doing architectural or baseband hardwaredevelopment to co-simulate directly with RF circuit design tools, to capture RFphysical design details & memory effects for use at the system-level.Conversely, this link also allows RF circuit designers using ADS to co-simulatewith SystemVue, in order to take advantage of the latest DSP algorithms, codedBER/EVM testing, and wireless standards supportRequirements

ADS 2009 Update 1 or later with ADS PtolemyBoth SystemVue and ADS must be running on the same MS Windowsmachine. ADS Circuit Envelope is optional, but offers additional capability toSystemVue users, using ADS Ptolemy as a co-sim bridge.Requires some additional ADS configuration and installation. Please referto the Agilent KnowledgeCenter support article athttp://edocs.soco.agilent.com/x/YoFvBg

Verilog co-simulation supportNow use the same SystemVue UI to import either Verilog or VHDL intoSystemVue as a co-simulation blockCo-verify your existing IP in ModelSim with both instruments and/or algorithmicIP in SystemVue

"SDATA" - RF S-parameter model improvementsAllows you to include more robust RF frequency response effects in yourbandpass envelope Dataflow simulations, using modulated carriers

New ADC modelsAdds system-level performance parameters as input, such as SFDR, SINAD, andharmonic levels, to facilitate architectural studiesUpdated 2010 models for Analog Devices converters

*Local-language menu support in 5 new languages"SystemVue now supports user interface menus in Japanese, Korean, Russian,Simplified Chinese, and Traditional Chinese.Check your SystemVue download page for these additional files and installationinstructions.

http://www.agilent.com/find/n1010a

http://www.agilent.com/find/n1010a

http://edocs.soco.agilent.com/x/YoFvBg.

http://edocs.soco.agilent.com/x/YoFvBg.


36

Continued enhancements to the free OFDM algorithmic model setAdditional applications examples

New examples have been added for ADCs, Fixed-point/Hardware design,OFDM/Comms, and other topics.

Improvements to Optional Libraries

New Products

New Product: W1905 RADAR Model LibraryReference blockset for RADAR architures and hardware verificationStudy realistic scenarios and then continue leveraging your environment forwideband signal generation and verification with Agilent test equipment

New Product: W1714 AMI Modeling KitProvides top-down electronic system-level (ESL) interface to gigabit SerDesdesignIncludes IBIS-AMI equalization and channel blocksetAllows IBIS-AMI model generation, for use in signal integrity channel simulatorsfrom a variety of vendors

Beta/Preview ProductsNot included in this installation, but available on request, are new PHY referenceproducts to be commercially available in late 2010. If you are interested inthese libraries, please contact your local Agilent representative to apply foradmission to the SystemVue Early Access Program (EAP).W1916 3G Baseband Verification LibraryW1917 WLAN Baseband Verification Library

Upgrades to Existing Products

W1910/W1912 LTE Baseband Libraries - New examplesGenerate E-UTRA test models for both TDD and FDD, as defined in TS 36.141Generate standalone Win32 DLL's for LTE DL/UL signal sources, for use in otherprograms, including ADS. Download LTE DL signals to Agilent ESG/MSG signal generators withoutwraparound pahse discontinuities

W1715 MIMO Channel BuilderDirect support for Agilent EMPro data formats (3DEM simulation), for defininguser-defined radiation patterns for MIMO antenna elements that degradesystem-level 3.9G/4G performance.New support for both 2D and 3D antenna patterns as input (up to 8 antennas)New corrleation matrix outputs for MIMO arrays

Issues FixedUninstalling SystemVue 2010.01 disables the 89601 VSA software

Problem: Uninstalling SystemVue unregistered an ActiveX componentAgltrace.ocx required for the Agilent VSA software to run. The file was present,but needed to be re-registred in Windows.Status: Resolved.

Missing DLL in DPD exampleProblem: the custom memory effect amplifier model used in one of the DPDexamples was not usable on some machines, due to a dependence on MicrosoftVisual Studio.Status: Resolved.

DeMapper block crashes when using the "user-defined" settingProblem: Demapper block crashes when defining states for a custommodulation format.Status: Resolved.

Demo licenses often appear not to runProblem: License files for SystemVue evaluations sometimes do not seem towork, when placed in a license directory or search path with older demolicenses.Status: Resolved. The new demo licenses work fine, but the softwaresometimes finds the old license first. If you have trouble, remove any olderlicense files so that SystemVue only finds the new license.

Known Issues


37

Summary Complicated Equations with the auto-calculate flag set may causeSystemVue to crash

Work Around: Turn off the auto-calculate flag and force execution of equationsmanually by pressing the Go button.

Documents

SystemVue - Getting Startededadownload.software.keysight.com/eedl/systemvue/2010_07/... · 2014. 7. 24. · SystemVue - Getting Started 3 Agilent. The Contributors of the SystemC