(Every time a license file is changed in any way, follow these procedures again.) Verifying the Keys Before using any new keyfile received from Synopsys, run the SCL sssverify utility to identify any errors before starting the server.
Verify the Synopsys licenses using the sssverify utility, following the procedure below. Therefore, it is recommended that you maintain your temporary keys on a separate server. However, temporary keys can be voided by duplicate production keys with a later ISSUED date. Exception: If you receive temporary keys from Synopsys, you can append them to the existing revenue license file, after removing the duplicate SERVER, VENDOR and USE_SERVER lines (required). DO NOT add, remove or modify any INCREMENT lines within the license file. Use the complete license file as received from Synopsys or as retrieved from the SmartKeys system. Any changes must be saved in ASCII text format. The hostid (usually the 12- character Ethernet address of the license server) is encrypted into the license keys, so may not be modified.
#Synopsys license generator full
The SERVER line must be modified to contain the correct server hostname, and the VENDOR line must be modified to contain the full path to the snpslmd daemon. To avoid startup errors and possible license denials by the SCL license server, the following instructions must be followed: Modify only the SERVER and VENDOR lines of the license file. This document contains these sections: Modifying the Keys Obtained from Synopsys Verifying the Keys Verifying that SCL is Serving Licenses Managing Temporary Keys Troubleshooting SSS / sssverify problems Modifying the Keys Obtained from Synopsys All regular (revenue) keys for the snpslmd daemon must have a valid SSS key.
#Synopsys license generator verification
1 Synopsys License Verification This document summarizes the license file verification methodology for Synopsys licenses in the combined vendor daemon (cvd) format used by Synopsys Common Licensing.
0 kommentar(er)
