Page Comparison

...

In some emulator products it is possible to configure the number of retries and the waiting time between them by adding parameters to the emulator configuration file. Please refer to the product documentation for the details regarding the relevant parameters: license_retry_period and license_retry_count parameters (obsolete starting with version 1.10)

2. At regular intervals during the runtime of the emulator (the default license check period of 1 hour can be changed by Stromasys using the appropriate license parameters):

...

A software license does not require any special hardware but it still requires installation of the Sentinel runtime environment. 

Please note:

• To avoid unexpected problems, do not use any Sentinel runtime software that was not provided by Stromasys without being advised to do so by your Stromasys representative.
• Software licenses are best suited for stable environments, because their correct function depends on certain characteristics of the host system. Changing any of these characteristics will invalidate the license.
  • If the Charon host runs on real hardware, software licenses are by default tightly bound to the hardware for which they were issued. If major hardware characteristics of the system are changed, the license will be disabled.
  • If the Charon host runs in a virtual environment (e.g., VMware), software licenses are normally bound to the virtual machine ID and a set of additional characteristics of the virtual machine. If any of these parameters are changed, the license will be disabled.
• Software licenses are very sensitive to even small changes on the host system. Therefore, it is especially important to provide for a backup license that will ensure continued operation should there be a problem with the software license. See Handling Multiple License Keys and Product Licenses for details.

...

Running esxi_bind before First C2V Creation on VMware

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 for the access to the ESXi host / the vCenter server change.

Perform the following steps:

1. Use ssh to log in on the license server instance.
   # 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 on the ESXi host or vCenter server. Make sure the user has at least the following permissions:

         • Datastore > Allocate Space
         • VirtualMachine > Config > AddNewDisk
         • VirtualMachine > Config > RemoveDisk

      3. <password> is the password of the 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 name VEesxi_bind nopanel true

Div
class pagebreak

Creating a VE C2V File

...