Versions Compared

Old Version 86

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: Typo correction

...

Table of Contents
excludeContents
stylesquare

Div
classpagebreak


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:

Operational Information and Logging
Insert excerpt
Operational Information and Logging
PDC:__Include: Installing a License on the VE License Server
PDC:__Include: Installing a License on the VE License Server
nameVELicInvalidationCaveat
nopaneltrue

Div
classpagebreak


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

These basic steps are described in more detail below.

...

classpagebreak

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

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

...

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

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 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

...

  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; for AutoVE: aws, oci, gcp, azure)

...

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

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

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

Div
classpagebreak


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 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).

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:

...

languagetext

...

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

Verifying License Installation and License Content

...

#/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) :

# /opt/license-server/license_viewer
Regular VE license on AWSRegular VE license on VMwarephysical server

<<License Viewer>> Current license:
License fingerprintFingerprint: 07792211fc8ce3fdc085 <truncated>
Customer nameName: Stromasys
License ID: 01.00000001.002.020
Key typeType: NORMAL
Platform: amazon.aws
Release dateDate: 2021-06-17 13:08:01
Grace periodPeriod: 120 minutes
License check intervalCheck Interval: 60 minutes

Virtual Hardware: Charon-SSP/4M,Charon-SSP/4U
Product codeCode: Charon-SSP/ALL
Expiration dateDate: 2021-12-22 23:55:00
Major Version: 5
Minor Version: 3
Maximum CPU: 64
Maximum virtual memoryVirtual Memory: 1048576MB
Instances allowedAllowed: 3# /opt/license-server/license_viewer

<<License Viewer>> Current license:
License fingerprintFingerprint: 07792211fc8ce3fd 07792211fc8ce3fdc085 <truncated>
Customer nameName: Stromasys
License ID: 03.00000003.002.006
Key typeType: NORMAL
Platform: vmwarephysical.esximachine
Release dateDate: 2021-0612-17 08 13:0818:0132
Grace periodPeriod: 120 minutes
License check intervalCheck Interval: 60 minutes

Virtual Hardware: Charon-SSP/4M,Charon-SSP/4U
Product code: Charon-SSP/ALL
Expiration date: 2021-12-22 -PA9-64-L1
Product Code: CHPA9-64-L1-IP
Expiration Date: 2022-06-08 23:55:00
Major Version: 53
Minor Version: 30
Maximum CPU: 641
Maximum virtual memoryVirtual Memory: 1048576MB2048MB
Instances allowedAllowed: 310
Passphrase: DYRB77U8-KHDWHXR9-0CUQVUFK-5B6V1B9V


Countdown license on physical serverAutoVE license on AWS

<<License Viewer>> Current license:
License fingerprintFingerprint: 5f9d9f13f390e3b071 <truncated>
Customer nameName: Stromasys
License ID: 01.00000001.002.194
Key typeType: COUNTDOWN
Expiration dateDate: 240 hour(s)
Platform: physical.machine
Release dateDate: 2021-07-29 09:06:15
Grace periodPeriod: 480 minutes
License check intervalCheck Interval: 60 minutes


Virtual Hardware: Charon-SSP/4U
Product codeCode: test
Major Version: 5
Minor Version: 3
Maximum CPU: 4
Maximum virtual memoryVirtual Memory: 10240MB
Instances allowedAllowed: 4



<<License Viewer>> Current license:
License fingerprintFingerprint: 5aaa364f9fc602323eaab2c   <truncated>
Customer nameName: Stromasys
License ID: 03.00000003.002.007
Key typeType: NORMAL
Expiration dateDate: 2022-02-14 23:55:00
Platform: amazon.aws
Release dateDate: 2021-07-27 10:42:44
Grace periodPeriod: 1440 minutes
Instances allowedAllowed: 3
Passphrase:
Auto licenseLicense: true



Div
classpagebreak



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

Important key-specific license parameters:

...

Important product-specific license parameters:

...

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

...

classpagebreak

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:

Image Removed

...

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.

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

License Verification Using the Web Interface

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

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

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc