We will continue to publish important new information on this page as it becomes available.

This category applies to the following products:

Steps to Upgrade your License Server:

For these products, upgrading the license server is not possible. Instead, the latest version of the product containing the latest version of the license server should be installed.

After you download the latest version of the software, install it by using the regular product installation steps.

After this stage, the license server embedded inside the software is ready to use.

CloudLens 6.x (Unified)

Product Specific Instructions

Release: Version 6.2 (includes licensing structure changes)

Release date: September 2, 2022

Download link: CloudLens 6.X (Unified)

What will differ after the licensing structure change:

There will be no changes to product behavior.

CloudLens vLM (CloudLens vPB)

Product Specific Instructions

Release: Version 1.7 (includes licensing structure changes); offline upgrade

Release date: August 31, 2022

Download link: CloudLens vLM (vPB)

Blackout dates: None

If you have a vPB or vAppStack version before CloudLens vLM 1.7, you will be required to upgrade to version 1.7 to perform any licensing operations. If you are not performing any licensing operations, there is no immediacy to upgrade. CloudLens vLM 1.7 was released on August 29, 2022.

Licensing operations: add new licenses, de-register licenses, update license for warranty update

All new installations must use version 1.7 or higher.

What will differ after the licensing structure change:

There will be no changes to product behavior.

IFC-CM (Indigo Pro)

Product Specific Instructions

Release: Version 7.6.3 (includes licensing structure changes)

Release date: September 16, 2022

If you have a version of IFC-CM before version 7.6.3, you will be required to upgrade to version 7.6.3 to perform any licensing operations. If you are not performing any licensing operations, there is no urgent need to upgrade.

What will differ after the licensing structure change:

After upgrading to 7.6.3 IFC CM release or later, the license that was already installed on the server will be automatically migrated to the new implementation. This means that after the upgrade, you will have access to all of the managed devices and features as before. If, at this point, you want to do a fulfillment, you will request this as before and install the fulfillment license on top of what his server has. After restarting, you will see your newly added license alongside with the already installed ones. With this workflow, nothing changes from your perspective.

If you want to do a deactivation, you must do a sync operation first. After that, you can proceed with the deactivation steps as normal.

In case you want to request a sync license, you may receive one or two files, depending on what part numbers you requested in the past. For the two files scenario, you will need to upload one of the files, and then the server will notify you that the second file is needed (this has changed from prior behavior, second file was not required before 7.6.3). After that, the server will restart and you should see the same installed licenses.

When requesting a deactivation, you may also receive one or two files, depending on your purchased licenses. The behavior is the same as in the sync use case, only that after uploading the last file, a confirmation code will appear. You will need to paste the confirmation code in your KSM account portal page so that the deactivation can be completed.

Summary version:

After upgrading to 7.6.3, no action from you is needed. The fulfillment requests can be done as until now. If you want to do a deactivation, you need to do a sync first (one-time only action needed), and then proceed with the deactivation. If the deactivation or sync requests will have two files, both should be uploaded.

LoadCore

This category applies to the following products:

  • LoadCore—version 3.4 or earlier

Steps to Upgrade your License Server:

If you are using an embedded license server in an ESX/KVM/AWS/Azure virtual machine environment:

1. Download the licensing upgrade .tar file here.

2. Sign in to the LoadCore UI by using the admin user credentials. 

3. On the top right side, select Administration > Software Updates.

4. Choose Select Packages for Upload.

5. Select the downloaded .tar file.

6. Select Start Update. After the process starts, a progress indicator appears. When the patch installation is complete, you will receive a notification.

After this stage, the license server that is embedded inside the Virtual Machine is updated and ready to use.

If you are using an embedded license server in a Kubernetes (k8s/Anthos/OpenShift/EKS) environment:

1. Download the container licensing patch .zip file here. In the zip archive, you will find the docker image for the new Embedded License Server, and also the folder with the charts modified.

2. Unzip the archive. After unzipping this archive, you will find the docker image and a folder.

3. Where you extracted LoadCore-MDW-3.4.0-3490-268-AGENT-3.4.0-9 archive, find a charts directory. Delete from that directory the kcos-licensing as follows: 

  • rm -rf charts/kcos-licensing
  • Move the kcos-licensing folder (which is compressed in the zip archived) to the charts directory.

4. Load the docker image by using:

docker load -i <docker image name>

For example: docker load -i kcos-licensing-0.3.5_20220727.134517.db24dc3f.tar.gz

5. Tag the docker image as follows:

docker tag <IMAGE ID> <registry_name>/<project_name>/kcos-licensing:0.3.5_20220727.134517.db24dc3f

For example: docker tag 014439e08129 default-route-openshift-image-registry.apps.cluster.keysight.lab/loadcore-root/kcos-licensing:0.3.5_20220727.134517.db24dc3f

6. Push the image inside our repository.

docker push <registry_name>/<project_name>/kcos-licensing:0.3.5_20220727.134517.db24dc3f

For example: docker push default-route-openshift-image-registry.apps.cluster.keysight.lab/loadcore-root/kcos-licensing:0.3.5_20220727.134517.db24dc3f

7. Install LoadCore with the new Embedded License Server:

./loadcore-kube-setup install-mw

After this stage, the license server that is embedded inside the Kubernetes is updated and ready to use.

If you are using LoadCore-Licensing-1.7.0-4 and want to upgrade the image in-place:

1. Download the licensing patch .tar file here.

2. Sign in to the Licensing UI by using the admin user credentials.

3. In the Licensing UI, select the Gear menu > Administration > Software Updates.

4. Choose Select Packages for Upload and select the downloaded .tar file.

5. Select Start Update. After the process starts, a progress indicator appears. When the patch installation is complete, you will receive a notification in the bottom right corner.

After this stage, the license server is updated and ready to use.

If you are using legacy licensing or LoadCore-Licensing-1.7.0-4 and want to deploy a new image:

1. Download the licensing image:

2. De-activate your licenses from the old licensing deployment.

If you are using offline licenses, please contact Support for deactivation / reactivation.

Please call +1 818 595 2599 for Ixia Global Support or send an email to support.ix@keysight.com.

You can find Support local phone numbers and a form to complete to open a support case here.

3. Deploy the downloaded images.

4. Activate your licenses on the new deployment.

5. Point your middleware to the new licensing deployment.

Metronome

This category applies to the following products:

  • Metronome—version 2.2.1 or earlier

Steps to Upgrade your License Server:

For Metronome, upgrading the license server is not possible. Instead, the product should be upgraded to the latest version, which already contains the licensing software upgrade.

To download the latest version of Metronome, use the following link:

After you download the latest version of the software, install it by performing the following steps:

1. Connect to the Metronome UI and select Upgrade > Upgrade.

2. Browse to the downloaded file to begin the process.

The upgrade can take up to 15 minutes. After completion, any license operations can be resumed.

On signing back in, if the upgrade is not complete, an upgrade activity bar will appear, and no functions will be available to the user.

If an error occurs during an upgrade such as a power outage, the upgrade is canceled, and the Metronome reverts to the previous state. The upgrade process will need to be restarted.

Network Emulator 2

This category applies to the following products:

  • Network Emulator 2—version 3.7 or earlier

Steps to Upgrade your License Server:

For Network Emulator 2, upgrading the license server is not possible. Instead, the product should be upgraded to the latest version, which already contains the licensing software upgrade.

To download the latest version of Network Emulator 2, use the following link:

After you download the latest version of the software, install it by performing the following steps:

1. Connect to the Network Emulator 2 UI and select System > Upgrade > Upgrade.

2. Browse to the downloaded file to begin the process.

The upgrade can take up to 15 minutes. After completion, any license operations can be resumed.

On signing back in, if the upgrade is not complete, an upgrade activity bar will appear, and no functions will be available to the user.

If an error occurs during an upgrade such as a power outage, the upgrade is canceled, and the Network Emulator reverts to the previous state. The upgrade process will need to be restarted.

Network Emulator 3

This category applies to the following products:

  • Network Emulator 3—version 3.7 or earlier

Steps to Upgrade your License Server:

For Network Emulator 3, upgrading the license server is not possible. Instead, the product should be upgraded to the latest version, which already contains the licensing software upgrade.

To download the latest version of Network Emulator 3, use the following link:

There are three packages that you need to download and update:

  • NE3 System Pkg
  • NE3 Chassis Management Pkg
  • NE3 App Pkg

Because the download files are quite large, we recommend you to have the management PC located in the same subnet as the Network Emulator 3.

After you download the latest packages, install it by performing the following steps:

1. Connect to the Network Emulator 3 UI and select System > About > Upgrade.

2. Browse to the downloaded file to begin the process.

The upgrade can take up to 15 minutes for each package. After completion, any license operations can be resumed.

On signing back in, if the upgrade is not complete, an upgrade activity bar will appear, and no functions will be available to the user.

If an error occurs during an upgrade such as a power outage, the upgrade is canceled, and the Network Emulator reverts to the previous state. The upgrade process will need to be restarted.

ThreatARMOR (users of individual appliances)

This category applies to the following products:

  • ThreatARMOR—version 3.12.1.8

Steps to Upgrade your License Server:

To upgrade the license server on your ThreatARMOR unit, perform the following steps:

1. Ensure that a valid license is deployed on the device before performing the next steps.

2. Ensure that the ATI Subscription is not expired. In case it has expired, the next steps will not work.

3. Select Settings >  System Updates > Check for Updates.

4. Select Download.

5. Wait for the download to complete.

6. Select Install.

7. Wait for the installation to complete. After this stage, the license server that is embedded inside the software is ready to use.

Notes/Limitations:

  • Rollback after applying the preceding steps will invalidate the licenses.

What changed:

After the upgrade, there are some changes in the way the licenses are handled by the user:

  • The Upload License button has the same functionality: Select the button and select the license file to upload.
  • In some cases, there may be two license files to upload. These must be uploaded one after another.
  • The Download Licenses button will download a zip file, instead of a single .lic file.

ThreatARMOR Central (the central management solution)

This category applies to the following products:

  • ThreatARMOR Central—all versions

Steps to Upgrade your License Server:

To upgrade the license server on your ThreatARMOR Central deployment, perform the following steps:

1. Sign in to your ThreatARMOR Central console.

2. Update the individual appliances to the latest software version by using ThreatARMOR Central.

3. Open a Support ticket to update the ThreatARMOR Central software. Customers cannot update ThreatARMOR Central themselves. This is a necessary step before installing new licenses on individual ThreatARMOR appliances.

4. Sync and download new/updated licenses from the KSM portal if and when needed, and then use ThreatARMOR Central to push the licenses out to individual appliances.

Vision Edge OS (NPB SW for Whitebox Switches)

Product Specific Instructions

Release: Version 6.0.0 (includes licensing structure changes); offline upgrade

Release date: September 19, 2022

Download link: Vision Edge OS (NPB SW for Whitebox Switches)

If you have a version of Vision Edge OS before version 6.0.0, you will be required to upgrade to version 6.0.0 to perform any licensing operations. If you are not performing any licensing operations, there is no immediacy to upgrade.

Product behavior changes with KSM/instructions:

After upgrading to the 6.0.0 Vision Edge OS release or later, the license that was already installed will be automatically migrated to the new implementation. We recommend you to perform a sync operation before any other license operation. Later, you may perform any license operation as normal.

In case you want to request a sync license, you may receive one or more files, depending on what part numbers you requested in the past. For multiple files, you will need to upload all the files at the same time. The server will notify you if the group of files that you’ve uploaded is incorrect or incomplete.

When requesting a deactivation, you may also receive one or more files, depending on your purchased licenses. The behavior is the same as in the sync use case, but a confirmation code will appear. You will need to paste the confirmation code in your KSM account portal page so that the deactivation can complete.

6.0.0+ version: After upgrading to 6.0.0, no action from your side is needed.

Need Assistance?

Please call +1 818 595 2599 for Ixia Global Support. Local phone numbers and template to open a Support case can be found here.