This scl_INSTALL_README.txt document contains installation instructions for the Synopsys Common Licensing (SCL) v10.9.3, v11.0, and v11.1 tool in the following sections: * General Information / Recommended SCL version * Operating System Support * Download & Installation Procedure * Obtaining and Verifying the License File * Starting the SCL Server & Setting up the User Environment ----------------------------------------------------------------- General Information / Recommended SCL version ----------------------------------------------------------------- As of December 7, 2009, Synopsys Common Licensing 11.1 is released. This is the recommended version of SCL. - SCL 11.1 is required for Synplicity customers. - SCL 11.0 or later is required for CHIPit customers. - SCL 10.9.3 or later is required for other customers. ** To use SCL cvd-format license files issued on December 7, 2009 or later, SCL 11.1 must be installed by Synplicity customers. ** This document contains quick-start installation assistance for SCL product files downloaded from Synopsys by Electronic Software Transfer (EST). To obtain your latest Synopsys license key file, go to the SmartKeys Web page at http://www.synopsys.com/smartkeys For start-up and troubleshooting information, see the Synopsys Licensing QuickStart Guide at http://www.synopsys.com/licensing ----------------------------------------------------------------- Operating System Support ----------------------------------------------------------------- Note that HP-UX 11.x support has been discontinued as of SCL 11.0. Red Hat Enterprise 3 and Solaris 8 support will end after June 2010, so please migrate to a supported operating system such as RHEL 4, RHEL 5, or Solaris 10. To obtain information on hardware platforms and OS versions supported by SCL 10.9.3 and later, see the supported OS table at http://www.synopsys.com/Support/LI/Licensing/Pages/SupportedOS.aspx ----------------------------------------------------------------- Download & Installation Procedure ----------------------------------------------------------------- This section contains the following information: - Installation Prerequisites - Installing by Electronic Software Transfer (EST) Installation Prerequisites ===================================================================== To install SCL, you must have write and execute permissions in the installation directory. Installing by Electronic Software Transfer (EST) ===================================================================== Below you will find a sample SCL download session. A Solvnet user name and password are required. The download instructions are for ftp. Alternatively, you may download SCL via HTTP by browsing to the Synopsys Download Center at https://solvnet.synopsys.com/DownloadCenter. Choose "Synopsys Common Licensing" as the product. This section contains installation information for the following platforms: - UNIX - Windows UNIX -------- 1. Create a destination directory for SCL. Download any SCL files to the destination directory. You will need to download * An OS platform file, which is specific to the operating system and hardware platform you will be using * A "common file" Note: SCL requires the Synopsys Installer version 2.1 or later. Download example (for SCL 11.1): # Get the product file(s) % cd /usr/temp/ % ftp ftp.synopsys.com 220 Synopsys FTP server ready Name: Password: 230 User logged in. ftp> binary ftp> cd /rev ftp> cd scl_v11.1 ftp> get scl_v11.1_.tar ftp> get scl_v11.1_common.tar where is one or more of linux, sparcOS5, and so on. 2. Untar the common file and the platform files. Example: % tar xvf scl_v11.1_common.tar % tar xvf scl_v11.1_linux.tar SCL will be found in the //bin directory. For example, /usr/scl/11.1/linux/bin 3. Add the installer directory to your UNIX path. % set path=(/usr/usr/installer $path) 4. To install the software, enter one of the following installer commands: % installer #To use a text script % installer -gui (or setup.sh) #To use a GUI 5. Answer the installer prompts. When you are prompted to choose a location for installing the software, do not select the temporary directory. You must specify a new location. Note: SCL must be installed into a local directory. Do not install it into an NFS directory or there may be perfomance problems. If you encounter any installer problems, please see SolvNet article 023842, Synopsys Installer 2.x Troubleshooting, at https://solvnet.synopsys.com/retrieve/023842.html/. 6. Obtain and verify the latest license key file. See the next section, "Obtaining and Verifying the License File." 7. Start SCL. See the section, "Starting the SCL License Server", below. 8. Modify the user environment to point to the license server. See the "Post-Installation Steps" section, below. Windows -------------- SCL 10.9.3 supports Windows 2000 and Windows XP. Windows Server 2003 and Vista are binary-compatible. SCL 11.0 supports Windows XP and higher. (Windows 7 has not been tested but should be compatible.) All SCL Windows binaries are 32-bit. If you have a dongle, make sure to use only 32-bit drivers. 1. Copy the single .exe file to a temporary directory. 2. Double-click this file to extract to a destination folder using Winzip or a similar tool. Be sure to choose the option to extract all files. 3. Use use lmtools to start SCL. For detailed information on using lmtools, see http://www.synopsys.com/support/keys/keys.html#start_win 4. To enable the users to access the license server, the user environment must be modified to set a licensing variable. For more information, see the "Post-Installation Steps" section, below. ----------------------------------------------------------------- Obtaining and Verifying the License File ----------------------------------------------------------------- This sections contains the following information: - Obtaining & Customizing the Latest License File - Verifying the license file with sssverify Obtaining & Customizing the Latest License File =================================================================== Before starting SCL, you must first obtain and customize the license file. To obtain your site's latest license ("key") file, go to Smartkeys at http://www.synopsys.com/smartkeys Click "Key Retrieval". A Synopsys username and password are required. Under "Key Retrieval", make sure that the correct Site ID is specified. Click "Continue". You license file(s) will be emailed to your SolvNet-registered email address. To customize the license file, perform the following steps: 1. Modify the SERVER line so that the "hostname1" field contains the correct system host name. For example, SERVER my_server 87654321 27000 2. Modify the VENDOR (or DAEMON) line so that it contains the full path to snpslmd. For example, VENDOR snpslmd /usr/scl/11.1/linux/bin/snpslmd 27000 Note: SCL requires only the snpslmd vendor daemon. Remove any "DAEMON" lines that refer to avantd, tmald, CADABRA, Innologd, ISE_TCAD, numeritechd, nassd, TE_CATS, synplctyd (starting with SCL 11.1) or any other Synopsys vendor daemons incorporated into SCL. 3. Make sure all lines wrap properly. Comment lines must start with # and not wrap. Every line must start with either # or one of the following keywords: SERVER, VENDOR, INCREMENT, or PACKAGE. Lines may only wrap after a continuation character (" /"). 4. Do not add any keys (except temp keys) to your production keys. Such an action will void your license file. For details, see the next section, "Verifying the License File with sssverify". 5. Save any changes in ASCII (.txt) format only. Verifying the License File with sssverify =================================================================== With SCL 10.x and later, Synopsys has introduced a new security technology, Synopsys Secure Server. To avoid "SSS"-related license checkout denials, it is important that you verify the license file with the sssverify tool included with SCL. 1. It is important that no keys (INCREMENTs) be added to the license file, or the license file will be invalidated. The only exception is for unexpired temporary keys with an issued date equal to or later than the issued date of the Smartkeys "production" or "release" keys. For example: If I retrieve productions keys from Smartkeys with an issued date of 25-jun-2009 ("ISSUED=25-jun-2009"). For the given hostid, I may add unexpired temp keys to this license file only if the temp keys have an issued date of 25-jun-2009 or later. 2. Verify the integrity of the license file with sssverify. For example: % cd /usr/scl/11.1/linux/bin % sssverify /usr/scl/11.1/admin/license/synopsys.lic The result should be: Integrity check report for license file "synopsys.lic". Report generated on Checking the integrity of the license file... Valid SSS feature found. License file integrity check passed. ------------------------------------------------------------------------------------- Starting the SCL Server & Setting up the User Environment ------------------------------------------------------------------------------------- This sections contains the following information: - Starting the SCL License Server - Setting up the User Environment Starting the SCL License Server =================================================================== Unix ------- 1. For the SCL license server, use lmdown to bring down all Synopsys daemons (incorporated into SCL), avantd, snpslmd, tmald, CADABRA, Innologd, ISE_TCAD, nassd, sandwork, TE_CATS, pdld, etc. (If these daemons are running, SCL will not start.) Note: For SCL 11.1, you must also bring down the synplctyd daemon. lmdown -c /path/to/license.dat 2. Start SCL with the following command: scl_root//bin/lmgrd -c scl_root/admin/license/synopsys.lic \ -l scl_root/admin/logs/synopsys.log -reusaddr Note: * All components of SCL should be locally mounted, including SCL binaries, license file, and logfiles. This avoids possible NFS performance problems. * A UNIX boot script is recommended. A sample SCL boot script is included in the scl_root/examples directory. 3. Verify that lmgrd started correctly by viewing the debug.log. It should show that lmgrd and snpslmd started, followed by a list of available features. If SCL did not start properly, there will be an appropriate error message. Use this to debug the problem, or send the license file and debug.log information to your local Synopsys Suppport Center. To open a case on the Web, browse to http://www.synopsys.com/support and choose "Open a Support Case." Windows ------- 1. Use lmtools to bring down all Synopsys daemons (incorporated into SCL) such as avantd, snpslmd, nassd, sandwork, etc. (If these daemons are running, SCL will not start.) Note: For SCL 11.1, you must also bring down the synplctyd daemon. 2. Use lmtools 10.8.5 or later to start SCL. lmtools is included with SCL. For detailed information on using lmtools, see http://www.synopsys.com/support/keys/keys.html#start_win Note: If your system has a dongle, first verify that the dongle hostid is recognized. For more information on this, see http://www.synopsys.com/support/keys/dongle.html 3. Verify that lmgrd started correctly by viewing the debug.log. It should show that lmgrd and snpslmd started, followed by a list of available features. If SCL did not start properly, there will be an appropriate error message. Use this to debug the problem, or send the license file and debug.log information to your local Synopsys Suppport Center. To open a case on the Web, browse to http://www.synopsys.com/support and choose "Open a Support Case." Setting Up the User Environment ======================================================== - UNIX - Windows UNIX ---- To set up your users, you must create a Synopsys source file, or modify each user's $HOME setup files (typically .cshrc, .profile, or .bashrc), as follows. 1. Set SNPSLMD_LICENSE_FILE, LM_LICENSE_FILE or a tool-specific licensing variable. This variable specifies the path to the Synopsys FLEXlm license server. Note: To reduce tool start-up time, it is recommended that you set a daemon- or tool-specific licensing variable. SNPSLMD_LICENSE_FILE is supported by most but not all Synopsys tools. LM_LICENSE_FILE is supported by all Synopsys tools. If unsure of which variable to set, set both variables. In the following example, it is assumed that the Synopsys license server is using TCP port 27000, the default port. (However, you can specify another port by modifying the SERVER line of your site's keyfile--for example, "SERVER myserver 8308a297 26585.") Example: * Add to .cshrc setenv SNPSLMD_LICENSE_FILE 27000@my_server or setenv LM_LICENSE_FILE 27000@my_server * Add to .profile or .bashrc SNPSLMD_LICENSE_FILE=27000@my_server; export SNPSLMD_LICENSE_FILE or LM_LICENSE_FILE=27000@my_server; export LM_LICENSE_FILE Note: Path syntax (/path/to/synopsys.lic) is not supported unless a USE_SERVER line is present at the top of the license file, before any feature (INCREMENT) lines. 2. Add the lmutilities (lmutil, lmstat, etc.) executable files to the user path. Example: * Add to .cshrc: set path=(/usr/scl//bin $path) * Add to .profile or .bashrc: PATH=/usr/scl//bin:$PATH export PATH Windows ------- 1. Set SNPSLMD_LICENSE_FILE, LM_LICENSE_FILE or a tool-specific licensing variable. This variable specifies the path to the Synopsys FLEXlm license server. Set this variable in Control Panel: Control Panel > System > Advanced > Environment Variables Example: * Add to the System Variables section: Variable: SNPSLMD_LICENSE_FILE Value: 27000@my_server or Variable: LM_LICENSE_FILE Value: 27000@my_server