Synopsys CVD Licen Verification Checklist
This document summarizes the licen file verification methodology for Synopsys licens
in the combined vendor daemon (cvd) format ud by Synopsys Common Licensing.
This document contains the ctions:
∙Overview of Synopsys Secure Server Technology
∙Verifying the Keys Obtained from Synopsys
∙Verifying that SCL is Serving Licens
∙Managing Temporary Keys
托马斯教育加盟∙Troubleshooting SSS / sssverify problems
Overview of Synopsys Secure Server Technology
Synopsys Secure Server, or SSS, is a curity technology that is incorporated into SCL binaries that re英语四级高频词汇
quires a valid licen file curity feature name (SSS or SSST) in every Synopsys licen file using the standard combined vendor daemon (cvd) format. This technology is designed to ensure that customers u only the most recent licens received from Synopsys, without any additions or subtractions.
jason earlesAll regular (relea) keys must have a valid SSS key. Temporary keys require an SSST feature.
A licen file should never contain more than one SSS feature, but may have more than one SSST feature if multiple temporary licens have been issued. A missing or invalid SSS
(or SSST) key makes the licen file invalid and will result in licen checkout denials.
To avoid possible licen denials by the SCL licen rver, the following instructions must be followed:
∙U the complete licen file as received from Synopsys or as retrieved from the SmartKeys system. DO NOT add, remove or modify any INCREMENT lines within the licen file.
Exception: If you receive temporary keys from Synopsys, you can append them to the套装英文
existing revenue licen file. However, it is recommended that you maintain a parate
rver for temporary keys. See the “Managing Temporary Keys” ction of this
太原培训学校document for details.
∙Verify the Synopsys licens using the procedure below. (Every time a licen file is changed in any way, follow the procedures again.)
Verifying the Keys Obtained from Synopsys
Before using any new keyfile received from Synopsys, run the SCL“sssverify” utility to identify any errors before starting the rver. For example:
% scl_root/linux/bin> sssverify –v
Synopsys Corporate Licensing (SCL) Relea: version
SCL_11.1, Build 1; Label: SCL_11.1; Built on Sep 22 2009
at 23:41:36
Synopsys supports SCL versions 10.9.3 or later; ignore the Build number. Also, SCL 11.1 or later is r
equired to support Synplicity licens in the SCL / snpslmd combined vendor daemon format.
Note:
If you have Synplicity features in the licen file, you must u only the 32-bit binary
(“sparcOS5”). for the Solaris platform. Also, if you have a dongle on a Linux platform, you must u only 32-bit binaries (“linux” or “su32”). See the SCL 11.1 Relea Notes for details.
% scl_root/linux/bin> sssverify /path/to/synopsys.lic
围巾哥The “sssverify” utility verifies the integrity of the licen file and detects any formatting errors in the file. If there are no errors in the licen file, you will e a message like the one below: % sssverify synopsys.lic
Integrity check report for li cen file “synopsys.lic”.
Report generated on 07-Dec-2009
----------------------------------------------------------
Checking the integrity of the licen file…
Valid SSS feature found.
Licen file integrity check PASSED
----------------------------------------------------------
You may now u this licen file to start the licen rver.
As indicated in this message, it is safe to u the licen file if there are no SSS errors.
If the licen file is corrupt, you will receive one of the following errors:
If the SSS (or SSST) key is missing or corrupt, you will receive this message: Checking the integrity of the
No SSS or SSST features were found in the licen file.
All revenue keys ("SN=RK:..." on feature line) have been excluded.
Licen file integrity check FAILED!
---------------------------------------------------------
This is an INVALID licen file. You SHOULD NOT u this licen file.
Plea u the licen file as received from Synopsys, Inc.
If you have removed any features from the licen file, you will e a message like this: Checking the integrity of the licen file…
Valid SSS feature found. Invalid licen file fingerprint.
2 features are missing from this file.
[Or, “You have added 2 new features to this file,” followed by a list
of features.]
Licen file integrity check FAILED!
----------------------------------------------------------
This is an invalid licen file. You should not u this licen file.
Plea u the licen file as received from Synopsys, Inc.
As indicated in the above error messages, if the integrity check fails, the licen file
SHOULD NOT be ud to start the licen rver.
Verifying that SCL is Serving Licens
1. Check the Debug Logfile for Start-Up errors
Search the SCL rver debug logfile and make sure that lmgrd and snpslmd have started properly. Also, arch for “SSS” and make sure there are no errors. Below are two possible error messages that might be prent in the debug logfile. (This step needs to be performed only after verifying the licen file with sssverify, and starting the licen rver.)
Error 1: Warning
----------------------------------------------------------------------------------------------------------------
(snpslmd) WARNING: SSS errors.
(snpslmd) U the sssverify utility to check the integrity of your licen file.
(snpslmd) The licen file should be ud exactly as received from Synopsys, Inc.
---------------------------------------------------------------------------------------------------------------- Error 2: Fingerprint error
---------------------------------------------------------------------------------------------------------------- (snpslmd) Valid SSS feature found. INVALID licen file fingerprint. (snpslmd) This feature is required to enable other keys in your licen file. (snpslmd) 91 features are missing from this file.
(snpslmd) All revenue keys ("SN=RK:..." on feature line) have been excluded. ---------------------------------------------------------------------------------------------------------------- IMPORTANT:
If the licen rver log file has either of the above error message, urs will experience licen denials. To resolve this, e the “Troubleshooting SSS / sssverify Problems” ction, below. 2. Verify that a Licen Can Be Checked Out
If the debug logfile does not show any checkouts (“OUT”) or denials (“DENIED”), you can u the sclsh utility included with SCL to verify that a licen can be checked out. For example,
% tenv SNPSLMD_LICENSE_FILE 27000@my_rver
% /synopsys/scl/linux/bin/sclsh
(sclsh) co hspice
No job handle for snpslmd, init being done for you
chain: 1-th handle[0] lc_init(snpslmd) = 0
lc_checkout(*1,hspice,1.0,1,LM_CO_NOWAIT,&code,4000)=0什么条件可以移民美国
hspice: checked out
After a successful checkout, there will be a corresponding, time-stamped message in the debug logfile:
9:53:29 (snpslmd) OUT: "hspice" jflores@jove
If there is a checkout failure, this will also be entered into the debug logfile. For example,
----------------------------------------------------------------------------------------------------------------
8:35:58 (snpslmd) ERROR: SSS feature is required!
8:35:58 (snpslmd) DENIED: hspice - excluded by SSS. Server is unstable.
----------------------------------------------------------------------------------------------------------------
Managing Temporary Keys
All temporary keys (except for non-cvd-format temporary keys issued for a legacy daemon) require an SSST feature. (A licen file should never contain more than one SSS feature
but may contain more than one SSST feature if multiple temporary licen files have been merged.)
Maintain a parate rver for temporary keys
By design, an on-support “revenue” key will void a temporary key with the same feature name and a prior issued date. If possible, keep your temporary keys and production keys parated, by hosting them on parate rvers. This will endure that the temporary keys are not voided by later production (revenue) keys.
Temporary keys must be added or removed as a block, not individually
Since temporary keys are issued in “blocks” of two or more, they may never be removed individually. Instead, they must be added or removed as blocks, where all the keys in the block contain the same transaction ID. For example, consider the keys:
INCREMENT SSST snpslmd 1.0 31-may-2010 1 0DB62FEB8D74757952F2 \
VENDOR_STRING="a88b1 297ef b3e2c e314e 15518 a3784 a5314 e1551…" \
NOTICE="Licend to XYZ Corp. [DO NOT DELETE/MODIFY SSST…]" \
SN=TK:0:0:593733 ISSUER="Synopsys Inc. [12/28/2009 21:09:09 1234]" \
START=31-may-2009
INCREMENT PrimeTime snpslmd 2009.06 31-may-2010 1 ISSUED=31-may-2009 \
shake that
ck=36 SN=TK:3222-0:229054:593733 START=31-may-2009 AUTH={ \
snpslmd=( LK=6D48B13764E3B921D8D9)}
INCREMENT PrimeTime-SI snpslmd 2009.06 31-may-2009 1 \
callas
ISSUED=31-may-2009 ck=11 SN=TK:3222-0:229054:593733 \
START=31-may-2009 AUTH={ snpslmd=( LK=6D7881C7D0A033B1E33E)}
In this example, the INCREMENT lines are temporary keys (SN=TK) that contain
the same transaction ID (593733). Thus, the keys must be added to or removed from the licen file only as a block.
For more details on adding or removing temporary keys from a licen file, e the SolvNet article on managing temporary keys at /retrieve/023020.html Troubleshooting SSS / sssverify Problems
sssverify fails
The following three steps resolve 99.5% of sssverify or other SSS curity errors:
1.Download the latest licen file from SmartKeys at /keys
2.Make sure the SCL version is 10.9.3 or later. (SCL 11.1 is required if your cvd-format
licen file contains Synplicity licens.)
You can determine the snpslmd version by arching the debug logfile for “SCL.” If
necessary, upgrade to the latest version of SCL.
3.Do not add or remove any keys to the licen file. The only exception is for temporary
keys, which may be added or removed as a block (that is, all the temporary keys issued at one time may be added, or they may all be removed). See the ction titled “Managing Temporary Key s” for details.
Note:
If production keys have expired, do not remove them. Instead, obtain a new licen
file from SmartKeys.
Other things to look for:
∙The licen file must contain only one SERVER and VENDOR line. (If you have redundant licens,
there must be three SERVER lines.)
∙There must be a USE_SERVER line following the VENDOR line. Remove any duplicate USE_SERVER lines that might be prent in the file.
∙Remove any keys for third-party daemons and licens from the file.
∙Make sure all comment lines start with # and do not wrap.会计助考
∙Make sure all INCREMENT keywords are at the beginning of the line.
∙An INCREMENT key may only wrap after a space and a continuation character (“ \”).
sssverify pass, but the debug logfile has SSS or fingerprint errors
∙Check the licen rver debug logfile to make sure that the SCL version is 10.9.3 or later.
If necessary, upgrade to the latest version of SCL. SCL 11.1 is required if your cvd-format licen file contains Synplicity licens.
∙Restart the licen rver
If you are not able to rectify the sssverify errors (or SSS error messages in debug logfile) then open a ca with the Synopsys Support Center. You may open a ca on the Web at /EnterACall. (To route the call to the correct application engineer, choo “Keys” or “Synopsys Common Licensing” as the product.)
Alternately, you may call (800) 245-8005 or nd e-mail to support_
If you are located outside North America, contact your local Synopsys Support Center.
