...
- 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 the following:
- Do you require a license with or without 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.
- Do you require an AutoVE license (available from VE license server version 1.21 and higher for supported cloud-specific Automatic Licensing marketplace images)?
- 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.
...
- 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 c2v
where[-a]
--filename <my-file>.c2v --platform <my-platform>- The optional
-a
parameter creates the fingerprint for a AutoVE license. Regular VE mode and AutoVE mode are mutually exclusive. - <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; for AutoVE: aws, oci, gcp, azure)
- The optional
- Become the root user:
- Copy the resulting C2V file to your local system (unless you can send email from the license server system).
...
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 the following:
- Do you require a license with or without 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.
- Do you require an AutoVE license (available from VE license server version 1.21 and higher for supported cloud-specific Automatic Licensing marketplace images)?
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.
...
Regular VE license on AWS | Regular VE license on VMware |
|
|
Countdown license on physical server | AutoVE license on AWS |
|
|
Div | ||
---|---|---|
| ||
The license contains a key-specific section and one or more product-specific sections.
...
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 for general VE, 24 hours for AutoVE). |
License check interval | Frequency with which the emulator will check the license availability and validity (1 hour). |
...
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 General VE mode: defines the maximum number of concurrently running emulated systems. AutoVE mode: defines the maximum number of concurrently active AL cloud instances using the AutoVE license server |
Passphrase | Defines the passphrase that must be configured on the license client system. |
...