| |
June 2008: SCL 10.9.3 is released.
For
information on the fixes and enhancements in this release, see the
release notes.
For information on OS platforms supported by SCL, click here.
SCL 10.9.3 is recommended for all customers.
Important:
SCL 10.9.3 is required for users of CE (former Sandwork)
products using standard cvd license keys issued June 9, 2008 or later.
The synplctyd daemon is not supported by SCL 10.9.3. For
information on licensing for Synplicity products, see
http://www.synplicity.com/literature/licensing.html
With SCL 10.x, Synopsys has introduced Synopsys Secure
Server (SSS) technology. Therefore, it is important that any
cvd license files received from Synopsys be verified by running the SCL sssverify tool.
If you get any sssverify errors, or any SSS errors in the license server log file,
there will be license checkout request denials until the problem is resolved.
See the Synopsys License File Verification Checklist for
details on how to run sssverify as well as troubleshooting information.
If you need assistance on SSS/sssverify issues, or any other licensing
issues, open a support case at https://solvnet.synopsys.com/EnterACall
Synopsys Common Licensing 10.x is based on Acresso Software FLEXnet and
uses common vendor daemon (cvd) technology. For a list of vendor
daemons incorporated into SCL / snpslmd, click here.
If you have not yet upgraded to SCL 10.9.3, please do the following
ASAP:
- Make sure your license servers meet the hardware and
configuration requirements.
- Deploy SCL version 10.9.3 or higher into your production
environment.
If your site is on support ("on maintenance") you may download the
software via Electronic Software Transfer.
In this Licensing QuickStart Guide you'll find SCL download
instructions, key file retrieval information, and setup instructions.
The following topics are covered:
- Pre-Installation
- Installation, Configuration & Start-Up
- Downloading & Installing SCL
(lmgrd, snpslmd)
- Downloading Your Site's License Key
File
- Customizing the License Key File
- Starting the License Server
- Setting Up the User
Environment to Access the Key File
- Troubleshooting (SolvNet
password may be required)
- Documentation (PDF or txt format)
Determining Your
Current SCL Version
- To determine your SCL version, do the following:
% cd scl_root/<platform>/bin
% ./whatscl snpslmd
===> Synopsys Corporate Licensing (SCL)
Release: version SCL_10.9.3 ...
- Alternately, on UNIX (only), you may determine your SCL version
via the UNIX strings command:
% strings /path/to/snpslmd | grep Build
Note that these results give the Synopsys version, not the
FLEXnet version. The FLEXnet version for SCL 10.9.3 is 10.8.5.x.
Installation,
Configuration & Startup
- Downloading & Installing SCL
- Download your Synopsys key file from
SmartKeys
- Customize the key file
- Start SCL
Downloading & Installing SCL
To download SCL via Electronic Software Transfer,
- Point your web browser to https://solvnet.synopsys.com/DownloadCenter
- If required, enter your Synopsys SolvNet username and password.
- Under My Product Releases, choose Synopsys Common Licensing.
- Choose the latest product version (e.g., "10.9.3") from the list of available versions.
- Click Download Here to download SCL by HTTPS.
- After reading the legal page, Click on "Yes I agree to the above terms."
- Click the download button next to the file names of the files you wish to download.
(UNIX users must choose the "common" file and the OS platform file.)
- Follow the browser prompts to select a destination download location.
This directory must be a temporary directory and not the target installation directory.
To download the Synopsys Installer (UNIX only):
- Point your web browser to https://solvnet.synopsys.com/DownloadCenter
- If required, enter your Synopsys SolvNet username and password.
- Under My Product Releases, choose Synopsys Installer.
- Choose the latest product version (e.g., "2.0") from the list of available versions.
- Click Download Here to download the Synopsys Installer by HTTPS.
- After reading the legal page, Click on "Yes I agree to the above terms."
- Click the download button next to the installer_v2.x.tar.Z file.
- Follow the browser prompts to select a destination download location.
Note: Installer version 2.0 and higher do not require that you untar CD or EST product tar files.
To install SCL:
- Type "installer" or "installer -gui" to start installation.
- Enter the path to the temporary (source) directory.
- Follow the prompts. When asked, enter the path to the target directory.
(For SCL, this should be a local path / mount and not an NFS mount.)
For more details on installing SCL, see the "Installing Synopsys Tools" and "Synopsys Common Licensing" chapters of the Installation Guide (2008.06 or later),
available at http://www.synopsys.com/install
Downloading Your
Site's License Key File
Before starting the lmgrd license daemon, you must retrieve your
license key file from the SmartKeys Web page. Complete these steps to get your license key file using the Web:
- Navigate to SmartKeys: http://www.synopsys.com/smartkeys
- If requested, enter your Synopsys (SolvNet) username and password
- At the SmartKeys main screen, click Key Retrieval.
- Under Site ID, select the correct Synopsys Site ID.
If you do not know your Site ID, obtain your Site ID in one of
the following ways:
- View the site_info file in your tool tree
($SYNOPSYS/admin/license/site_info).
The SiteID field identifies your Site ID.
- Look at an old Synopsys key file. Near the top, you will find
your Site ID.
# SYNOPSYS INC. KEY CERTIFICATE
# Site Id: xxxx [where xxxx is a number]
- Click Continue. SmartKeys processes your request and
sends you the license key file by e-mail.
Customizing the
License Key File
Your site's license key file, as received from SmartKeys, will look
something like this:
#---------------------------------------------------------------
#Server Config: 0000052142
#---------------------------------------------------------------
SERVER hostname1 807E321F 27000
VENDOR snpslmd /path/to/snpslmd
USE_SERVER
INCREMENT SSS snpslmd 1.0 20-dec-2008 1 3EE593F14EED \
VENDOR_STRING="382be a5896 de613 1618c 27e26 40bb1
40cec 13318 8da63 128" \
NOTICE="Licensed to ABC Corporation [PLEASE DO NOT
DELETE THIS SSS KEY]" \
SN=RK:0:0:802047 ISSUER="Synopsys Inc." \
START=03-oct-2005
INCREMENT hspice snpslmd 2008.03 20-dec-2008 8 VENDOR_STRING=^1+S \
SUPERSEDE ISSUED=20-jun-2008 ck=115
SN=RK:6719-0:733381:117716 \
START=03-oct-2005 AUTH={ snpslmd=(
LK=6D8411D4365F7D1C39DB) \
avantd=( LK=CDE4E1546CD26F379ACB) }
INCREMENT metawaves snpslmd 2008.03 20-dec-2008 8 VENDOR_STRING=^1+S \
SUPERSEDE ISSUED=20-jun-2008 ck=39
SN=RK:6719-0:733381:117716 \
START=03-oct-2005 AUTH={ snpslmd=(
LK=6D3441449638F796655F) \
avantd=( LK=DD44A164467F8C415694) }
#----------------------------------------------------------------
Note:
SCL 10.9.3 requires only a single "VENDOR snpslmd" line.
The SCL 10.9.3 vendor daemon supports legacy tools based on avantd, sandwork, tmald, nassd and various other vendor daemons. For a list of incorporated daemons,
click here.
Before you can use the Synopsys license key file downloaded from
Smartkeys, it must be customized for your site.
For both UNIX and Windows license servers, follow the steps below.
- Place the license key file on your system.
The recommended key file location is:
scl_root/admin/license/*.lic
Example:
- UNIX: /usr/synopsys/scl/admin/license/synopsys.lic
- Windows: C:\synopsys\scl10.9.3\admin\license\synopsys.lic
- Make sure the key file is formatted properly.
- Do NOT remove the USE_SERVER line.
This keyword should exist, on a line by itself,
before any cvd-format INCREMENT lines.
- Remove any VENDOR or DAEMON lines for non-snpslmd vendor
daemons.
With SCL 10.9 & above, they are not required or allowed.
- All lines should start with SERVER, VENDOR, USE_SERVER,
PACKAGE, INCREMENT, or #
- Lines may only wrap after a space and a continuation
character (" \")
- All comment lines must start with #
- Blank lines must NOT be present in the key file as this may
cause problems
- Strip out all extraneous characters, such as > or >>
symbols at the beginning of lines
(sometimes added by email handlers)
- Verify the accuracy of the license file.
Run "sssverify" to verify the integrity of the license file
(sssverify is
included with SCL).
The syntax is "sssverify /path/to/synopsys.lic".
Note:
If any keys have been added or removed from the key
file (except for temp keys),
sssverify will fail.
- Modify the SERVER line.
The SERVER line of your key file has the following
syntax:
SERVER hostname1 hostid tcp_port_number
Mandatory
On the SERVER line, modify the hostname1 argument with the value
returned
by the UNIX hostname command.
Note:
The hostid in the license key file (807E321F in this
example) must match your machine
hostid as determined by the scl_root/<platform>/bin/lmhostid
command.
Do not change the hostid. If you change the
hostid, you will invalidate your license key file.
If the hostid is incorrect, contact your account manager to obtain a
new license key file.
(A "rehost form" may be required.)
Optional
Modify the TCP port number (default is 27000) to any available
TCP port between 1024 and 64000.
Example:
SERVER aspen 807E321F 27020
- Modify the VENDOR line.
The VENDOR line has the following syntax:
VENDOR snpslmd /path/to/snpslmd [ /path/to/options_file ]
Mandatory
Specify the full path to snpslmd
Examples:
UNIX:
VENDOR snpslmd /usr/synopsys/scl/sparc64/bin/snpslmd
Windows:
VENDOR snpslmd C:\synopsys\scl10.9.3\msvc70\bin\snpslmd.exe
Optional
Add the path to any license option file(s) at the end of the
VENDOR line
VENDOR snpslmd /usr/synopsys/scl/sparc64/bin/snpslmd \
/usr/synopsys/scl/admin/options/synopsys.opt
- After modifications, your key file should look something like
this (changes in bold):
#---------------------------------------------------------------
#Server Config: 0000052142
#---------------------------------------------------------------
SERVER aspen 807E321F 27020
VENDOR snpslmd /usr/synopsys/scl/sparc64/bin/snpslmd
# *** No other vendor daemons required ***
USE_SERVER
INCREMENT SSS snpslmd 1.0 20-dec-2008 1 3EE593F14EED \
VENDOR_STRING="382be a5896 de613 1618c 27e26 40bb1
40cec 13318 8da63 128" \
NOTICE="Licensed to ABC Corporation [PLEASE DO NOT
DELETE THIS SSS KEY]" \
SN=RK:0:0:802047 ISSUER="Synopsys Inc." \
START=03-oct-2005
INCREMENT hspice snpslmd 2008.03 20-dec-2008 8 VENDOR_STRING=^1+S \
SUPERSEDE ISSUED=20-jun-2008 ck=115
SN=RK:6719-0:733381:117716 \
START=03-oct-2005 AUTH={ snpslmd=(
LK=6D8411D4365F7D1C39DB) \
avantd=( LK=CDE4E1546CD26F379ACB) }
INCREMENT metawaves snpslmd 2008.03 20-dec-2008 8 VENDOR_STRING=^1+S \
SUPERSEDE ISSUED=20-jun-2008 ck=39
SN=RK:6719-0:733381:117716 \
START=03-oct-2005 AUTH={ snpslmd=(
LK=6D3441449638F796655F) \
avantd=( LK=DD44A164467F8C415694) }
#---------------------------------------------------------
- Save your change.
You are now ready to start the license server.
Starting the
License Server
Choose your license server OS:
Starting a License Server under UNIX
- Since SCL 10.9.3 incorporates many vendor daemons, all
incorporated daemons
(snpslmd, avantd, sandwork, tmald, etc.) must be shut down before you will be
able to
start SCL. Click
here for a list of incorporated daemons that will need to be shut
down.
To shut down the currently running daemon process(es), enter the
following command:
% scl_root/platform/bin/lmdown -c /path/to/key file
- To start the licensing daemon, use the following command syntax:
lmgrd -c license_key file_name -l debug_log_filename
For example, on the Solaris platform (64-bit kernel), enter:
% scl_root/sparc64/bin/lmgrd -c
scl_root/admin/license/synopsys.lic \
-l scl_root/admin/logs/snps.debug.log
- Once you have started lmgrd, check the debug log file (here
"snps.debug.log") for errors.
Check the time-stamped entries to verify that
- lmgrd (FLEXnet Licensing) v10.8.5.0 or 10.8.5.3 or later has started
<--FLEXnet version
- snpslmd (SCL) v10.9.2 or 10.9.3 or later has started
<--Synopsys version
- there are no SSS security errors ("Invalid license file
fingerprint" or "WARNING: SSS errors").
- the list of available features (keys) is correct
The debug log file should show that the snpslmd daemon has
started, followed by a list of
available features (that is, keys or INCREMENT lines).
- Your UNIX license server will now be able to serve any clients on
the network, regardless of the
client operating system (UNIX, Linux, Windows).
- For each client, set a licensings environment variable (see next
section). If there are
any problems using the tools see the troubleshooting
section of this document.
- So you don't have to manually start lmgrd every time you reboot
your license server, you will need
a Synopsys license server boot script. For a boot script that you may
modify to fit your needs,
retrieve the SolvNet article, Boot Script for Synopsys License Servers.
Starting a License Server under Windows
For a given vendor daemon each license
server host can have only
one active vendor daemon process. Before starting SCL,
make sure to shut down snpslmd:
- Start lmtools (Start > Programs > Synopsys > SCL10.9.3
> launch lmtools.exe
- Click the Service/License File tab and choose Configure
using Services
- Select the correct service name(s)
- Click the Start/Stop/Reread tab and choose Stop
Server
To start the licensing daemon, follow the steps below.
- In Windows Explorer, double-click the lmtools.exe utility.
- Click System Settings.
- Make sure the Ethernet Address is correct and matches your
key file's SERVER hostid
- If you are using a dongle, make sure the FLEXid is correct.
If no FLEXid shows
in the "FLEXID" window, see the article on Dongle
Setup & Troubleshooting.
Note:
If the hostid information is incorrect, you must not
modify the key file hostid.
(If a Synopsys mistake was made, contact sales to obtain a new key file
for the correct hostid.)
- Click Services/License File.
Make sure Configure using Services is
selected.
- Click Configure Services.
- Under Service Name, type in an arbitrary service
name (for example, "Synopsys Licensing").
- Next to "Path to the lmgrd.exe file," click Browse and browse
to lmgrd.exe.
For example, browse to
C:\synopsys\scl10.9.3\msvc70\bin\lmgrd.exe.
- Next to "Path to the license file," click Browse and browse
to the Synopsys key file.
For example, browse to
C:\synopsys\scl10.9.3\admin\license\synopsys.lic.
- Next to "Debug Log File," type the path to create a debug.log
file.
(This file need not exist; it will be created for you.)
For example, type
C:\synopsys\scl10.9.3\admin\logs\debug.log.
- At the bottom of the window, check Use Services and
Start Server at Power-Up.
This will ensure that the Synopsys license server starts
automatically every time the system is booted.
- Click Save Service to save you changes.
- Click the Start/Stop/Reread tab and click Start
Server to Start the License Server.
- Verify that the SCL 10.9.3 license server has started correctly:
- Click Configure Services.
- Click View Log to view the debug.log file.
Check the time-stamped entries to verify that
- lmgrd (FLEXnet Licensing) v10.8.5.0 or later has started
<--FLEXnet version
- snpslmd (SCL) v10.9.2 or 10.9.3 or later has started
<--Synopsys version
- there are no security errors ("Invalid license file
fingerprint" or "WARNING: SSS errors").
- the list of available (started) keys is correct
For example:
7:09:39 (lmgrd) Done rereading
17:09:39 (lmgrd) FLEXnet Licensing (v10.8.5.x build 31891) started on my_server
17:09:39 (lmgrd) Copyright (c) 1988-2006 Macrovision ...
...
...
17:09:39 (lmgrd) License file(s): C:\synopsys\scl10.9.3\admin\logs\synopsys.lic
17:09:39 (lmgrd) lmgrd tcp-port 27000
17:09:39 (lmgrd) Starting vendor daemons ...
17:09:40 (lmgrd) Started snpslmd (pid 836)
17:09:40 (snpslmd)FLEXnet Licensing version v10.8.5.x build 31891
17:09:40 (snpslmd)Synopsys Corporate Licensing (SCL) Release: version SCL_10.9.3
17:09:42 (snpslmd) Server started on my_server for: APHPO
17:09:42 (snpslmd) APTIME Apollo Astro
17:09:42 (snpslmd) hspice hspice_gui metawaves
17:09:42 (snpslmd) DC-Expert DC-SDF-Interface DC-Ultra-Features
17:09:42 (snpslmd) DC-Ultra-Opt Design-Budgeting Design-Compiler
17:09:42 (snpslmd) Design-Vision DesignWare DesignWare-VERA
17:09:42 (snpslmd) Designware-Basic HDL HDL-Compiler
17:09:42 (snpslmd) PrimeTime SynLib-Eval Test-Compiler
17:09:42 (lmgrd) snpslmd using TCP-port 3789
17:09:42 (snpslmd) Serving features for the following vendor names:
snpslmd CADABRA EPIC ISE-TCADd TE_CATS adalmd anagram
avantd chrysalisd everest hscd innologd la_dmon leda metasoftd
numeritchd saber_dmn slat ssilmd synopsysd tmald vcsd
- Your SCL license server will now be able to serve any clients on
the network,
regardless of the client operating system (UNIX, Linux, Windows).
- For each client, set a licensings environment variable (see next
section).
If there are
any problems using the tools see the troubleshooting
section of this document.
Setting Up
the User Environment to Access the Key File
For each user account that will be running the Synopsys tools, set a
licensing environment variable.
The licensing variable is a pointer that tells the Synopsys tools where
to find the license file.
Licensing variables include:
- SNPSLMD_LICENSE_FILE
- LM_LICENSE_FILE
Important:
Legacy variables such as
AVANTD_LICENSE_FILE, NASSD_LICENSE_FILE, TMALD_LICENSE_FILE, etc.,
are not supported for tool releases starting with 2007.09.
Environment Variable Set-Up Examples:
Setting up the User Environment under UNIX
Set SNPSLMD_LICENSE_FILE or LM_LICENSE_FILE.
- C-Shell
Add to Synopsys source file or .cshrc:
setenv SNPSLMD_LICENSE_FILE 27000@oak
[port@host syntax--where 27000 is the TCP port specified in the license
file and"oak" is the hostname]
setenv SNPSLMD_LICENSE_FILE 27020@aspen
[where "27020" and "aspen" are the port and hostname we used in our
example]
setenv SNPSLMD_LICENSE_FILE
/usr/synopsys/scl/license/synopsys.lic
[path syntax]
setenv SNPSLMD_LICENSE_FILE 27000@oak:27020@aspen
[separate individual license file references using a colon]
- Bourne, Korn, or Bash shells
Add to Synopsys source file or .bashrc, .kshrc, or
.profile:
SNPSLMD_LICENSE_FILE=27000@oak
export SNPSLMD_LICENSE_FILE
| Type of Key File |
Variable Name |
Variable Value (UNIX OS) |
| Network License
(floating) |
SNPSLMD_LICENSE_FILE or
LM_LICENSE_FILE |
27000@my_server |
| Multiple Key Files
(separate by colons) |
SNPSLMD_LICENSE_FILE or
LM_LICENSE_FILE |
27000@oak:27020@aspen |
|
Setting up the User Environment under Windows
- Windows 2000 or higher: Click Start >
Settings > Control Panel > Advanced > Environment Variables
- Under System Variables, click New (to
create a new variable) or Edit (to edit and existing
variable).
- Under Variable Name, enter SNPSLMD_LICENSE_FILE
or LM_LICENSE_FILE
- Under Variable Value, enter the correct port@host information.
Example:
| Type of Key File |
Variable Name |
Variable Value (Windows OS) |
| Network License
(floating) |
SNPSLMD_LICENSE_FILE or
LM_LICENSE_FILE |
27000@My_Windows_Server |
Nodelocked License
(dongle or ethernet address--counted) |
SNPSLMD_LICENSE_FILE or
LM_LICENSE_FILE |
27000@My_Windows_Server |
Nodelocked License
(dongle--legacy, uncounted) |
LM_LICENSE_FILE |
C:\synopsys\scl10.9.3\admin\license\dongle.lic |
| Multiple Key Files
(separate by semicolons) |
SNPSLMD_LICENSE_FILE or
LM_LICENSE_FILE |
27000@jflores-pc;27020@aspen |
|
|
