...

Starting with VE license server version 1.1.13, the previous information-only web interface has been changed to a management interface. It provides the following functions:

Prerequisites:

• The TCP port used by remote systems to web-based management interface must be permitted on the license server, and by any intermediate firewall.
  Default: TCP/8084; an alternative port can be configured in /opt/license-server/config.ini.
• TCP port 80 must be available to the license server to redirect HTTP requests to HTTPS. For remote connections, the port must also be permitted through intermediate firewalls. Starting with version 1.1.25, redirection (and thereby use of TCP port 80) can be enabled or disabled in /opt/license-server/config.ini.
• Important: at the time of writing, the web-server component of the license server applications will not start if a port required by the web server is already used by another application. This will also prevent the licensing component from starting.

Accessing the Management GUI and Logging in

...

Use localhost as the hostname for accessing the GUI of a license server running on the local system. Example: https://localhost:8084. Using just http://<license-server-ip> will redirect to https on the default configured HTTPS port.

Please note: any intermediate firewall must allow the TCP port ports used for the management GUI.

...

After logging in, you will be presented with a list of menu options on the left pane of the screen and the content of the selected option on the right hand. Please change the default password immediately.

Certificate Warning when Connecting to the Management GUI

...

• either obtain a certificate for the host from one of the commercial certification authorities, or
• they must create their own self-signed certificate and add it to the web browser.

The new certificates replace the server.pem certificate in /opt/license-server/certs (move the old certificate to a save place).

Steps to create a self-signed certificate:

...

• Create the combined server certificate for the license server:
  # cp servercert.cer server.pem
# cat servercert.key.pem >> server.pem
• Restart the license server (# systemctl start licensed)

• Import the root CA (ca.cer) into your browser’s Trusted Root Certification Authorities Certificate Store.

Please note: at the time of  writing, the custom certificate was overwritten by upgrading or downgrading the license server software. Therefore, make sure to back up you certificate and to restore it after an upgrade or downgrade of the license server.

...

See Certificates Used by the VE License Server for more information.

Displaying the License Information

...

Please note: Charon-PAR license clients cannot inform the license server about the configured number of CPUs and amount of memory. Hence, for these clients, the corresponding fileds fields in the display will be empty.

...

As an alternative to the command-line program for C2V export, you can create your C2V file via the management GUI. The section for C2V export has two input fields described below:

...

License Type

Options:

• VE License: select if the license server operates in general VE license mode.
• AutoVE License: select if the license server operates in AutoVE mode.

General VE license mode and AutoVE mode are mutually exclusive.

Platform

Drop-down menu to select platform on which the license server runs. This list is different depending on the mode in which the VE license server runs:

Platforms supported by general VE license mode:

• Amazon AWS
• Oracle OCI
• Microsoft Azure
• Google GCP
• IBM Cloud
• Nutanix AHV
• VMware ESXi
• Physical Machine

The platform selected must match the platform on which the license server host system runs.

Platforms supported by AutoVE mode:

• Amazon AWS
• Oracle OCI
• Microsoft Azure
• Google GCP

The platform selected must match the platform on which the license server host system runs.

Steps to export a C2V file

...

1. Enter the correct License Type.
2. Select the correct Platform.
   1. If the chosen platform is VMware ESXi, there will be an additional menu indicated by three dots. Click on this option to open the esxi_bind configuration window.
      
      
      
      Enter the IP address and the login information of the ESXi host or vCenter Server to which the license server should bind.
      Then press Submit.
      
      

      Insert excerpt
      PDC:__Include: Installing a License on the VE License Server PDC:__Include: Installing a License on the VE License Server name VEesxiUserInfo nopanel true

3. Click on Export to create the C2V file.
4. After a successful export, a download option will be displayed that allows you to download the created file to your local system (see below).
   

Send the C2V file to Stromasys for them to create a license.

...

Importing a V2C File

In response to the C2V file sent, you will receive two files from Stromasys. One text file containing the license content in human-readable form, and the V2C license file.

...