Anchor | ||||
---|---|---|---|---|
|
Include Page | ||||
---|---|---|---|---|
|
Contents
Table of Contents | ||||
---|---|---|---|---|
|
Important Information to Protect the License Validity
Certain actions can invalidate your license. Therefore, once you have installed your license, please note the following points:
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Overview - Requesting and Installing a License
Perform the following basic steps to request and install a license:
- VMware only: for the first license request in a VMware environment, or if the binding data has changed, use the esxi_bind command to bind the license server to its ESXi host or vCenter Server.
- Collect the fingerprint (the customer-to-vendor - or C2V - file) on the license server and (if applicable) the backup license server.
- Send the fingerprint data to Stromasys stating the license requirements based on your contract with Stromasys (product version, number of concurrent instances, is this the main or the backup license, etc.). Please also indicate whether you require a license with a passphrase (can be selected per product section). The use of a passphrase requires Charon-SSP emulator versions 4.3.x and higher and VE license server versions 1.1.x and higher.
- Stromasys will send you a license (V2C file with license data and text file with human readable license content).
- Install the license data (the vendor-to-customer - or V2C - file) on the license server and (if applicable) on the backup license server.
- Verify the license installation.
These basic steps are described in more detail below.
License Installation Using the Command-Line
Running the esxi_bind Command (VMware environment only)
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
Div | ||
---|---|---|
| ||
Collecting the Fingerprint Data on the License Server
The fingerprint is collected on the license server using the c2v utility.
Perform the following steps to collect the fingerprint on the license server and (if applicable) the backup license server:
- Use ssh to log in on the license server instance.
# ssh -i ~/.ssh/<mykey> <user>@<license-server-ip>
where- <mykey> is the private key of the key-pair you associated with your cloud instance
(for an on-premises VMware installation where login with username/password is allowed, it is not needed) - <user> is the user for interactive login associated with your license server instance (e.g., opc on OCI, centos for a CentOS instance on AWS, or the custom user on your VMware virtual machine or your physical server;
for an instance installed from a prepackaged Charon-SSP VE marketplace image, use sshuser) - <license-server-ip> is the ip address of your license server system
- <mykey> is the private key of the key-pair you associated with your cloud instance
- Become the privileged user and run the c2v program.
- Become the root user:
# sudo -i
- Run the c2v program:
# /opt/license-server/c2v --filename <my-file>.c2v --platform <my-platform>
where- <my-file>.c2v is the path and name under which you want to store the fingerprint. The file type is C2V (customer-to-vendor)
- <my-platform> indicates the platform on which the license server runs (possible values: physical, aws, oci, gcp, azure, ibm, nutanix, or esxi)
- Become the root user:
- Copy the resulting C2V file to your local system (unless you can send email from the license server system).
Sending the C2V File to Stromasys and Receive License Data File
Stromasys or your Stromasys VAR will provide you with an email address to which you should send the C2V file you created in the previous step.
Please also indicate whether you require a license with a passphrase (can be selected per product section). The use of a passphrase requires Charon-SSP emulator versions 4.3.x and higher and VE license server versions 1.1.x and higher.
In response, you will receive a so-called V2C (vendor-to-customer) file which contains the license data. The content of the license (type of emulated SPARC, expiration date, number of concurrent instances, etc.) depends on your contract with Stromasys. You may also receive a text file containing the license content in human readable form.
Div | ||
---|---|---|
| ||
Installing the License Data on the License Server
The license data is installed on the license server using the v2c utility.
Perform the following steps to install the license on the license server:
- Copy the V2C file to the license server (e.g., with SFTP).
- Use ssh to log in on the license server instance.
# ssh -i ~/.ssh/<mykey> <user>@<license-server-ip>
where- <mykey> is the private key of the key-pair you associated with your license server instance
(for an on-premises VMware installation where login with username/password is allowed, it is not needed) - <user> is the user for interactive login associated with your license server instance (e.g., opc on OCI, centos for a CentOS instance on AWS, or the custom user on your VMware virtual machine or you physical server;
for an instance installed from a prepackaged Charon-SSP VE marketplace image, use sshuser) - <license-server-ip> is the ip address of your license server system
- <mykey> is the private key of the key-pair you associated with your license server instance
- Become the privileged user and run the v2c program.
- Become the root user:
# sudo -i
- Run the v2c program:
# /opt/license-server/v2c -f <my-file>.v2c
where <my-file>.v2c is the path and name under which you want to store the fingerprint. The file type is V2C (vendor-to-customer).
- Become the root user:
After the installation of the V2C file, the license server will be restarted.
Please note:
- Please note that to install a license with a new license ID (or another changed static parameter - see below), the old license must first be removed in an additional step (see Removing a License from a VE License Server).
- In versions before 1.0.17, the license server will not start until a valid license has been installed.
The following example shows the installation of a V2C file:
Code Block | ||
---|---|---|
| ||
$ sudo /opt/license-server/v2c -f mylicense.v2c <<V2C>> Going to import "mylicense.v2c" ... <<V2C>> Imported "mylicense.v2c" successfully. <<V2C>> Restarting license server ... <<V2C>> Done |
Verifying License Installation and License Content
Checking the License Server Log file
Check the license server log file to see if the server started successfully or reported an error. Use the following command (as the privileged user):# cat /opt/license-server/log/license.log
The log should indicate that the license server is ready to serve licenses.
Div | ||
---|---|---|
| ||
Using the license_viewer Program to Display the Content of a License
The license server provides a license_viewer program to view the content of the license. To run it, use the following command (as the privileged user):
#/opt/license-server
/license_viewer
The following sample shows the output for several different licenses:
Regular VE license on AWS | Regular VE license on VMware |
|
|
Countdown license on physical server | |
|
Div | ||
---|---|---|
| ||
The license contains a key-specific section and one or more product-specific sections.
Important key-specific license parameters:
Parameter | Explanation |
---|---|
Platform | The platform for which the license has been created. This parameter cannot be changed by a license update. |
Release date | Date on which the license has been issued. |
Customer name | The owner of the license. This parameter cannot be changed by a license update. If a change is required, the existing license must be removed before creating a new fingerprint. |
License ID | In older versions, the license ID changed if the license server software was reinstalled; in newer versions, it will remain unchanged as long as the license server host instance is not re-installed. This parameter cannot be changed by a license update. If a change is required, the existing license must be removed before creating a new fingerprint. |
Key type | Possible values are NORMAL (time-limited or perpetual license) or COUNTDOWN (limited to a certain number of emulator runtime hours). |
Expiration date | Configured number of emulator runtime hours. The remaining hours can be seen in the web interface of the license server and the emulator log file. |
Grace period: | Time in minutes the emulator can run after the license used by the emulator has timed out or disappeared. Configured by Stromasys when creating the license (default: 2 hours). |
License check interval | Frequency with which the emulator will check the license availability and validity (1 hour). |
Important product-specific license parameters:
Parameter | Explanation |
---|---|
Expiration date | The expiration date. |
Major version and Minor version | The major and minor product versions. |
Maximum CPU | Defines the maximum number of CPUs in an emulated system (emulated SPARC in the example). |
Maximum virtual memory | Defines the maximum amount of RAM in an emulated system. |
Instances allowed | Defines the maximum number of concurrently running emulated systems. |
Passphrase | Defines the passphrase that must be configured on the license client system. |
Div | ||
---|---|---|
| ||
License Installation Using the Web Interface
The license server provides a web interface to display important license characteristics, to display license client systems, and to enable license updates.
Prerequisite: access to TCP port 8084 (or an alternative port configured in the file /opt/license-server/config.ini file; see also Additional Configuration Options - the config.ini File) of the license server must be possible.
The following image shows sample output of a general VE license for SSP:
The first section of the samples shows the basic characteristics of the license. The Product Section shows the licensed products and their characteristics.
See VE License Server Web-based Management GUI for more information.
Include Page | ||||
---|---|---|---|---|
|