Page Comparison

...

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

...

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

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, the password, or the address data for the access to the ESXi host / the vCenter server Server change.

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 c2v 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 serverServer
      2. <username> is a user with administrative rights on the ESXi host or vCenter serverServer
      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).

...

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

...

• K_PLATFORM: the platform for which the license has been created. This parameter cannot be changed by a license update.
• K_CUSTOMER: 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_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_TYPE: possible values are NORMAL (time-limited or perpetual license) or COUNTDOWN (limited to a certain number of emulator runtime hours).
• K_EXPIRED: 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.

...