Versions Compared

Old Version 80

changes.mady.by.user W.Erber

Saved on

compared with

New Version Current

changes.mady.by.user W.Erber

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: pdf layout

...

Insert excerpt
Operational Information and Logging
Operational Information and Logging
nopaneltrue

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 the following:Do whether 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 version 1.13 and higher for supported AWS AMIs)?
  • 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.

...

classpagebreak


License Installation Using the Command-Line

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. Use ssh to log in on the license server instance (assuming that username/password login is possible for an on-premises VMware installation).
    # ssh <user>@<license-server-ip>
    where
    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
  2. Become the privileged user and run the esxi_bind program.
    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
  3. If the command is successful, it will create the file /opt/license-server/config.ini containing the connection data (the password is encrypted).

Insert excerpt
PDC:__Include: Installing a License on the VE License Server
PDC:__Include: Installing a License on the VE License Server
nameVEesxi_bind
nopaneltrue

Div
classpagebreak


Collecting the Fingerprint Data on the License Server

...

  1. 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 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 or your physical server;
      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
  2. Become the privileged user and run the c2v program.
    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: physical, aws, oci, gcp, azure, ibm, nutanix, or esxi)
  3. 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 the following:

...

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.

...

  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 )or you physical server;
      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).

...

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.

...

: 5aaa364f9fc602323eaab2c   <truncated>
Customer name: Stromasys
License ID: 03.00000003.002.007
Key type: NORMAL
Expiration date: 2022-02-14 23:55:00
Platform amazon.aws
Release date: 2021-07-27 10:42:44
Grace period: 1440 minutes
Instances allowed: 3
Auto license: true<<License Viewer>> Current license:
License fingerprint:
Regular VE license on AWSRegular VE license on VMware

# /opt/license-server/license_viewer

<<License Viewer>> Current license:
License fingerprint: 07792211fc8ce3fdc085 <truncated>
Customer name: Stromasys
License ID: 01.00000001.002.020
Key type: NORMAL
Platform: amazon.aws
Release date: 2021-06-17 13:08:01
Grace period: 120 minutes
License check interval: 60 minutes

Virtual Hardware: Charon-SSP/4M,Charon-SSP/4U
Product code: Charon-SSP/ALL
Expiration date: 2021-12-22 23:55:00
Major Version: 5
Minor Version: 3
Maximum CPU: 64
Maximum virtual memory: 1048576MB
Instances allowed: 3

# /opt/license-server/license_viewer

<<License Viewer>> Current license:
License fingerprint: 07792211fc8ce3fd <truncated>
Customer name: Stromasys
License ID: 03.00000003.002.006
Key type: NORMAL
Platform: vmware.esxi
Release date: 2021-06-17 13:08:01
Grace period: 120 minutes
License check interval: 60 minutes

Virtual Hardware: Charon-SSP/4M,Charon-SSP/4U
Product code: Charon-SSP/ALL
Expiration date: 2021-12-22 23:55:00
Major Version: 5
Minor Version: 3
Maximum CPU: 64
Maximum virtual memory: 1048576MB
Instances allowed: 3
Passphrase: DYRB-KHDW-0CUQ-5B6V


AutoVE license on AWSCountdown license on physical server

<<License Viewer>> Current license:
License fingerprint

:

5f9d9f13f390e3b071 <truncated>
Customer name: Stromasys
License ID: 01.00000001.002.194
Key type: COUNTDOWN
Expiration date: 240 hour(s)
Platform: physical.machine
Release date: 2021-07-29 09:06:15
Grace period: 480 minutes
License check interval: 60 minutes


Virtual Hardware: Charon-SSP/4U
Product code: test
Major Version: 5
Minor Version: 3
Maximum CPU: 4
Maximum virtual memory: 10240MB
Instances allowed: 4



Div
classpagebreak



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

Important key-specific license parameters:

ParameterExplanation
PlatformThe platform for which the license has been created. This parameter cannot be changed by a license update.
Release dateDate on which the license has been issued.
Customer nameThe 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 IDIn 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 typePossible values are NORMAL (time-limited or perpetual license) or COUNTDOWN (limited to a certain number of emulator runtime hours).
Expiration dateConfigured 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
Frequency with which the emulator will check the license availability and validity (1 hour).


Important product-specific license parameters:

ParameterExplanation
Expiration dateThe expiration date.
Major version and Minor versionThe major and minor product versions.
Maximum CPUDefines the maximum number of CPUs in an emulated system (emulated SPARC in the example).
Maximum virtual memoryDefines the maximum amount of RAM in an emulated system.
Instances allowedDefines the maximum number of concurrently running emulated systems.
PassphraseDefines the passphrase that must be configured on the license client system.


Div
classpagebreak


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.

...