...
| 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
...
| 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).
...
...
| class | pagebreak |
|---|
Sending the C2V File to Stromasys and Receive License Data File
...
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.
| Div | ||
|---|---|---|
| ||
Installing the License Data on the License Server
...
| 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.
...