...

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:

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.). Stromasys will send you the license data. Please also indicate if 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.
• 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.

...

Insert excerpt
PDC:__Include: Installing a License on the VE License Server PDC:__Include: Installing a License on the VE License Server name VEStepsOverview nopanel true

License Installation Using the Command-Line

The following sections will show how to perform a license installation on the VE license server. Alternatively, you can use the web-based GUI (see VE License Server Web-based Management GUI)

Running the esxi_bind Command (VMware environment only)

The esxi_bind command sets up the necessary communication connection between the VE license server and the ESXi host / the vCenter Server.

It must be run on the license server (and the backup license server, if applicable):

• once before the first license is requested, and
• again should the user credentials, the password, or the address data for the access to the ESXi host / the vCenter Server change. Please make sure that the password of the selected user account does not automatically expire after a certain time period. This would cause disruptions in the license server operation and make it impossible for clients to receive their license.

Perform the following steps:

...

1. <user> is the user for interactive login associated with your license server system
2. <license-server-ip> the ip address of your license server system
   

...

1. Become the root user: # sudo -i
2. Run the esxi_bind program: # /opt/license-server/esxi_bind -a <address> -u <username> -p <password>
where
   1. <address> is the IP address of the ESXi host or vCenter Server
   2. <username> is a user with administrative rights on the ESXi host or vCenter Server
   3. <password> is the password of the administrative user

...

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:

...

1. <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)
2. <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;
   for an instance installed from a prepackaged Charon-SSP VE marketplace image, use sshuser)
3. <license-server-ip> is the ip address of your license server system
   

...

1. Become the root user: # sudo -i
2. Run the c2v program: # /opt/license-server/c2v [-a] --filename <my-file>.c2v --platform <my-platform>
where
   1. The optional -a parameter creates the fingerprint for a AutoVE license. Regular VE mode and AutoVE mode are mutually exclusive.
   2. <my-file>.c2v is the path and name under which you want to store the fingerprint. The file type is C2V (customer-to-vendor)
   3. <my-platform> indicates the platform on which the license server runs (possible values: aws, oci, gcp, azure, ibm, or esxi)

...

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 indicate if 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.

...

Insert excerpt
PDC:__Include: Installing a License on the VE License Server PDC:__Include: Installing a License on the VE License Server name VESendC2Vupd2 nopanel true

Div
class pagebreak

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:

1. Copy the V2C file to the license server (e.g., with SFTP).
2. Use ssh to log in on the license server instance.
   # ssh -i ~/.ssh/<mykey> <user>@<license-server-ip>
   where
   1. <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)
   2. <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);
      for an instance installed from a prepackaged Charon-SSP VE marketplace image, use sshuser)
   3. <license-server-ip> is the ip address of your license server system
      
3. Become the privileged user and run the v2c program.
   1. Become the root user: # sudo -i
   2. 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).

After the installation of the V2C file, the license server will be restarted.

Please note:

• Starting with version 1.0.35, a previously installed license will be cleanly removed once a new license is installed with the v2c command.
• 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:

$ 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

...

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/license_log/license.log

The log should indicate that the license server is ready to serve licenses.

...

#/opt/license-server/license_viewer

The following sample table shows the output examples for several different licenseslicense types and platforms (please note that the output may vary depending on platform and software version) :

The license contains a key-specific section and one or more product-specific sections.

Important key-specific license parameters:

• 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: license check interval (1 hour).

Important product-specific license parameters:

• Expiration date:  is 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.

...

Using the Web Interface

The license server provides a web interface to display important license characteristics and a list of currently connected client systems and emulator instances.

Prerequisite: access to TCP port 8084 of the license server must be possible.

The following image shows sample output of a backup license with 179 hours and 57 minutes of runtime remaining:

Image Removed

The following image shows sample output of a regular license with an expiration date and one client attached:

Image Removed

The following example shows a license on a physical server with the grace period parameter:

Image Removed

...

The license contains a key-specific section and one or more product-specific sections. Please note that the product-specific section is mostly not applicable to AutoVE licenses as this license is based on the number and configuration of the cloud-based host instances.

License Verification Using the Web Interface

See VE License Server Web-based Management GUI and Additional Configuration Options - the config.ini File for more information.