...
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Overview - Requesting and Installing a License
Perform the following basic steps to request and install a license:
...
These basic steps are described in more detail below.
...
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:
...
- <user> is the user for interactive login associated with your license server system
- <license-server-ip> the ip address of your license server system
...
- Become the root user:
# sudo -i - Run the esxi_bind program:
# /opt/license-server/esxi_bind -a <address> -u <username> -p <password>where- <address> is the IP address of the ESXi host or vCenter Server
- <username> is a user with administrative rights on the ESXi host or vCenter Server
- <password> is the password of the administrative user
...
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Div | ||
|---|---|---|
| ||
Collecting the Fingerprint Data on the License Server
...
- Use ssh to log in on the license server instance.
# ssh -i ~/.ssh/<mykey> <user>@<license-server-ip>
where- <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) - <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) - <license-server-ip> is the ip address of your license server system
- <mykey> is the private key of the key-pair you associated with your cloud instance
- Become the privileged user and run the c2v program.
- Become the root user:
# sudo -i - Run the c2v program:
# /opt/license-server/c2v --filename <my-file>.c2v --platform <my-platform>where- <my-file>.c2v is the path and name under which you want to store the fingerprint. The file type is C2V (customer-to-vendor)
- <my-platform> indicates the platform on which the license server runs (possible values: physical, aws, oci, gcp, azure, ibm, nutanix, or esxi)
- Become the root user:
- Copy the resulting C2V file to your local system (unless you can send email from the license server system).
...
- Copy the V2C file to the license server (e.g., with SFTP).
- Use ssh to log in on the license server instance.
# ssh -i ~/.ssh/<mykey> <user>@<license-server-ip>
where- <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) - <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) - <license-server-ip> is the ip address of your license server system
- <mykey> is the private key of the key-pair you associated with your license server instance
- Become the privileged user and run the v2c program.
- Become the root user:
# sudo -i - Run the v2c program:
# /opt/license-server/v2c -f <my-file>.v2cwhere <my-file>.v2c is the path and name under which you want to store the fingerprint. The file type is V2C (vendor-to-customer).
- Become the root user:
...
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.
...
Important key-specific license parameters:
| Parameter | Explanation |
|---|---|
| Platform | 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. |
| Customer 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. |
| 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. |
| Key type | Possible values are NORMAL (time-limited or perpetual license) or COUNTDOWN (limited to a certain number of emulator runtime hours). |
| Expiration date | 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. |
| 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). |
| License check interval |
| Frequency with which the emulator will check the license availability and validity (1 hour). |
Important product-specific license parameters:
| Parameter | Explanation |
|---|---|
| Expiration date | 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. |
| Div | ||
|---|---|---|
| ||
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.
...