Contents

Cloud-based VE License Server Overview

The following image provides an overview of a sample VE license server topology in a cloud environment:

Points to note:

• The license server software can be combined with the Charon emulator software on one instance, or it can run on a separate system. However, it is recommended to run the VE license server on a dedicated system to avoid license invalidation caused by changes to the system which are more likely to occur on a system used for other purposes as well, for example, to run a Charon emulator. It is also recommended to install a backup license server to ensure continued operation in case of a failure or invalidation of the primary license.
• The license server typically is installed in the same cloud environment.
• Charon host and license server do not need a public IP address. They communicate across the cloud-internal LAN environment.
• Starting with Charon-SSP version 4.1.19, and with Charon-PAR and Charon-AXP/VAX from initial VE support, a backup license server has been supported.
• Important points for AutoVE deployments:
  • The AutoVE license server address must be configured prior to the first launch of the instance from a supported AL marketplace image. Otherwise, the public license servers will be used.
  • License server and Charon host must be in the same cloud environment.

VMware-based VE License Server Overview

The following images provides an overview of sample VE license server topologies in a VMware environment.

There are two basic options:

1. The license server binds to the ESXi host on which the license server VM runs. In this case, any Charon emulator using the VE license server must run either on the same VM as the VE license server or on a VM running on the same ESXi host.
2. The license server binds to the vCenter Server that manages the ESXi host on which the license server VM runs. In this case, any Charon emulator using the VE license server must run either on the same VM as the VE license server or on a VM on an ESXi host managed by the same vCenter Server.

Please note: each VE license server instance can only bind to one ESXi host or one vCenter server. For example, if a license server is needed in two separate vCenter installations, at least two license server instances are required.

VE License Server Binding with ESXi Host

The following image illustrates a topology where the VE license server binds to the ESXi host on which the VM with the license server runs. It shows one VM with license server and emulator software, and another VM on the same ESXi host with the emulator software configured to use the license server via the network.

Please note: vMotion of a VE license server VM to a different ESXi server is only possible if binding to a vCenter Server (see below) is used. vMotion of a license server VM when binding to the ESXi server will invalidate the installed licenses.

VE License Server Binding with vCenter Server

The following image illustrates a topology where the VE license server binds to the vCenter Server managing the ESXi host on which the VM with the license server runs. It shows one VM with license server and several other VMs on ESXi hosts managed by the same vCenter Server using the license server across the network.

Please note: vMotion of a VE license server VM to a different ESXi server is possible if the target server is managed by the same vCenter Server.