The following License Editions are available for Keysight Elastic Network Generator:
|Ixia-c Traffic Port Capacity||4 x 1/10GE||50GE||400GE||800GE|
|Test Concurrency||1 Seat||1 Seat||8 Seats||16 Seats|
|Requires a valid license||N||Y||Y||Y|
|Includes Ixia-c Software Test Ports||Y||Y||Y||Y|
|Works with UHD400T Hardware||N||N||Y||Y|
|Works with IxOS Hardware||N||N||N||Y|
The Ixia-c Traffic Port Capacity is determined as a sum of the configured Ixia-c test port speeds with the possible values of: 100GE, 50GE, 40GE, 25GE, 10GE, and 1GE. The Maximum data plane performance of an Ixia-c port may be less than the configured port speed, depending on the capabilities of the underlying hardware and software drivers.
The Test seat concurrency applies to a number of controller instances that are running with a configuration that exceeds the capabilities of the Community Edition.
The Restricted protocol scale supports the maximum of 4 BGP sessions per test.
The Capabilities of the Limited protocol scale depend on the protocol. For details, contact Keysight Support.
Keysight Elastic Network Generator can simultaneously consume multiple licenses to increase the capabilities of a test. For example, if the Ixia-c Traffic Port Capacity configured in one test is 100GE, two Developer licenses will be consumed if available.
If you require capabilities beyond those provided by the Community Edition, use Keysight Elastic Network Generator product page to request an evaluation or a quote.
Keysight uses a license server to manage floating or network shared licenses for its software products. The license server enables licenses to float and not be tied to a specific Elastic Network Generator instance. The Elastic Network Generator controllers must be able to reach the License server.
In order to use capabilities of Elastic Network Generator that require a valid license, you need to deploy a Keysight License Server. The License Server is a virtual machine and it is distributed as OVA and QCOW2 images (you only need one of them depending on your hypervisor).
- QCOW2 image, ~6GB
To make a decision where to deploy the License Server VM, take into the account the following requirements:
- For Linux-based QEMU or KVM, use the QCOW2 image
- 2 vCPU cores
- 4GB of RAM
- 100GB storage
- 1 vNIC for network connectivity. Note that DHCP is the preferred option, and this is also how the VM is configured to obtain its IP address.
Network connectivity requirements for the License Server VM
- Internet access from the VM over HTTPS is desirable for online license activation, but not strictly required. Offline activation method is available as well.
- Access from a user over SSH (TCP/22) for license operations (activation, deactivation, reservation, sync)
- Access from any
keng-controllerthat needs a license during a test run over gRPC (TCP/7443) for license checkout and check-in
Here is an example of how different components communicate with the License Server:
Configuring a static IP address
If your network doesn't provide DHCP, you can configure a static IP address for the License Server VM. Access the VM console and go through two-step login process:
* first prompt:
console (no password)
* second promt:
admin. Run the following commands to configure a static IP address, where
x.x.x.x is the IP address,
yy is the prefix length,
z.z.z.z is the default gateway,
b.b.b.b are DNS servers:
You will now be able to activate licenses and use the License Server on your Elastic Network Generator setup. Go to
https://your-license-server-hostname to access the application. Enter credentials:
admin to login.
If you have an activation code, to perform an online activation, click "Activate Licenses", enter the code and click "Activate". For offline mode, choose "Offline Operations" instead.
You can also use a command-line session, via console or SSH, to perform license operations. Run
kcos licensing --help to see the list of available commands.
Connecting Elastic Network Generator to the License Server
To connect the Elastic Network Generator controller instance to the License Server, use
--license-servers="server1 server2 server3 server4" argument when launching the controller. An alternative way is to use an environment variable
LICENSE_SERVERS. The argument accepts a space-separated list of hostnames or IP addresses of the License Servers, up to four. The controller will try to connect to the License Servers in the order they are specified in the list. If the first License Server is not available, or doesn't have enough available licenses to run the test, the controller will try to connect to the next one in the list.