Page Comparison

...

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

• once Once before the first license is requested,
• and again 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.
   # 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;
      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: aws, oci, gcp, azure, ibm, or esxi)
3. Copy the resulting C2V file to your local system (unless you can send email from the license server system).

...

The following sample shows the output of two three active Charon-SSP licenses - once on the AWS cloud without a passphrase, once in VMware environment with a passphrase, and one AutoVE license:

Important product-specific license parameters:

...

P_RLSD is the expiration date.

...

P_MAJV and P_MINV are the major and minor product versions.

...

P_CPU_NUM defines the maximum number of CPUs in an emulated system (emulated SPARC in the example).

...

P_MAX_MEM defines the maximum amount of RAM in an emulated system.

...

P_INSTANCE defines the maximum number of concurrently running emulated systems.

...

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

Important key-specific license parameters:

• K_PLATFORMPlatform: 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.
• K_CUSTOMERCustomer 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.
• K_LICENSE_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.
• K_TYPEKey type: possible values are NORMAL (time-limited or perpetual license) or COUNTDOWN (limited to a certain number of emulator runtime hours).
• K_EXPIREDRuntime hours: 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.K_INTERVAL: configured license check interval
• Grace period: time in minutes the emulator can run after the license used by the emulator has timed out or disappeared.
• 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

...