Release Notes


A10 Harmony Controller HC-5.1.0-P2


Supported versions
Thunder 5.x
5.0.0, 5.0.0-P1, 5.1.0
Thunder 4.1.x
No Config Management:
4.1.1-P12, 4.1.1-P13, 4.1.4-GR1-P1, 4.1.4-GR1-P2
With Config Management:
Lightning ADC
4.x, 5.0.0, 5.1.0
Harmony Apps
ADC App: 5.1.0-v3.3
CGN App: 5.1.0-v3.2
GiFW App: 5.1.0-v3.2
SSLi App: 5.1.0-v3.0
GTPFW App: 5.1.0-v3.2
Kubernetes Connector (Secure Service Mesh)
ICL-2.0.6, ICL-2.0.9, ICL-3.0.0

New Features for Users Running HC-4.2.1-Px

  1. Upgrade to HC-5.1.0-P1 without data loss. You are requested to consult A10 cloud support before upgrading.
  2. Ability to deploy Harmony Controller on machines having two network interfaces.
  3. Ability to deploy Harmony Controller for Disaster Recovery (DR) in addition to already available High Availability (HA).
  4. Improved service analytics in Harmony Apps. Please see release notes of the Harmony App for details.
  5. Harmony Apps are pre-packaged with the Controller build and will be automatically installed for providers.
  6. Harmony Portal login using third-Party authentication providers – LDAP, Radius and TACACS.
  7. A new Super-admin role for settings that apply for controller instance.
  8. Four additional canned roles other than already existing Provider-admin and Tenant-admin.
  9. Provider and Tenant level summary dashboards. Provider also has a Cluster Dashboard.
  10. Provision for configuring extensive alerts for infrastructure as well as A10 Secure Application Services.
  11. Canned alerts are added for infrastructure as well as application services to improve usability.
  12. Harmony Controller can now obtain license from A10 Enterprise License Manager (ELM) in addition to A10 Global License Manager (GLM).
  13. License to a Thunder device can be assigned from the controller. Access to GLM or ELM from the device is still needed.
  14. Requirement to open port in firewall to allow traffic from Controller to Thunder is eliminated. Now, Thunders from behind a firewall can connect to Harmony Controller seamlessly.
  15. Early Access (EA) of the ability to generate PDF reports for application service analytics is provided.
  16. Early Access (EA) of Device management and configuration capability through Global Object Explorer and Harmony Apps from Harmony Portal. Legacy Thunder Device Manager (TDM) is removed.
  17. Early Access (EA) to ability to launch vThunder in VMWare vCenter, AWS and Azure environment from Harmony Portal.

New Features for Users Running HC-5.1.0

  1. Upgrade to HC-5.1.0-P2 without data loss. You are requested to consult A10 cloud support before upgrading.
  2. Four additional canned roles other than Super-admin, Provider-admin and Tenant-admin.
  3. Twelve additional canned alert triggers.
  4. Improved service analytics in Harmony Apps. Please see release notes of the Harmony App for details.
  5. Harmony Apps are pre-packaged with the Controller build and will be automatically installed for providers.

New Features for Users Running HC-5.1.0-P1

  1. Upgrade to HC-5.1.0-P2 without data loss. You are requested to consult A10 cloud support before upgrading.
  2. Many bug fixes and stability enhancements.

Known Issues

Item ID
Due to the issues in Microsoft Edge, Single Sign On (SSO) for editing
application configuration fails. Using Google Chrome is advised for smooth
While displaying difference between old and new configuration, the coloring
of config blocks may be incorrect.
In case of HA Failover, analytics show the new active device status even
for historical data that belongs to old device.
For vThunder, partition CPU usage is approximate. If only one partition
is there in Thunder device, it may not show the same value as Device
CPU usage.
Harmony APIs have changed. This may break existing automation around
Harmony APIs. Please consult A10 team for details.
Admin users created on Thunder devices after registering them to
Controller, do not get synchronized with Controller even after
configuration scan. Deregistering Thunder and registering again will fix
the problem. However,mapping Partitions to Tenants may be required again.
HARMONY- 18262
The Thunder cluster launched by Harmony Controller in VMWare vCenter,
AWS or Azure environment only supports cluster type ‘Single’. HA or
VCS clusters needs to be launched manually and attached to controller.
Harmony Controller connects to Thunder management interface only on
port 443.
Configuring multiple Thunder devices or Application services together from
Harmony Portal is temporarily not available. Backed up configuration can
still be pushed on multiple devices.
Option to schedule image upgrade of Thunder devices from Harmony
Portal is temporarily not available.
When Thunder configuration with multiple Virtual IP addresses (VIPs)
is created via Harmony Portal and pushed to a Thunder device, analytics
information for all these VIPs does not show up properly. It is recommended
to configure one VIP at a time.
When Thunder configuration is modified directly on Thunder, it does not
automatically synchronize with the Controller. Using ‘Scan’ option brings
the configuration to Controller from the device. However, making all
configuration changes from Harmony Portal (Global Object Explorer) is
recommended after registering Thunder to Controller.
Options for scheduled device configuration backup and restore from
Harmony Portal are temporarily reduced and only daily backup is available
for now.
In Harmony Portal, Tenant admins can view the devices, partitions
and associated application services that do not belong to them.
Recommended not to onboard application service that require strict
access control.
When existing configuration is imported or scanned from Thunder device,
some properties may not show up properly in Harmony Portal.
The Thunder Onboarding help that pops up on first time login does not
display how-to perform the steps. It is recommended is to use product
documentation for details.
When size of Thunder configuration is large, configuration exchange
actions (e.g. config push/scan, config backup/restore Harmony Controller
to Thunder fails.
Certain portions of Thunder configuration are not being deployed properly
when pushed to Thunder from Harmony Controller.
In some cases, to avoid disruption of environment or application traffic,
configuration push from Harmony Controller to Thunder may not succeed.
A few system created Partitions may be visible to admins. These are for
internal use by controller sub-system. Users are advised not to change
anything in those accounts.
As of now, generated alerts are stored only for 7 days.
In case of assigning device license to VCS cluster, license is allocated only to
Master. License to blades is to be allocated manually.
When configuration for a partition is modified by two different users
(Provideradmin and Tenant admin) in two different scopes (device and
application service),full configuration is pushed to Thunder when
any one of them decides to push. Co-ordination between provider and
tenant admins is recommended.
Configuration management of Thunder VCS clusters from controller
is not supported. Recommended is to convert VCS clusters to
multi-node HA clusters while registering with controller. If these
devices are deregistered from controller, recreation of VCS is
to be done manually.
A Thunder VCS cluster deployed in different network from controller
(behind firewall), cannot be registered using Tunnel feature. Traffic
from controller to Thunder management port should be allowed in
firewall for it to work.
As of now, for TACACS authentication, Controller connects to TACACS
server only on default port 49.
When Thunder cluster registers, controller provides default auto-generated
names. While upgrading from HC-4.2.1-Px, these names may change to the
new default values.
For old version of Thunders, some information like log collection rate,
request rate, detailed service status etc., may be displayed incorrectly.
Please consider upgrading Thunder to ACOS 5.x.
Newly introduced field ‘License Name’ may remain blank after upgrade for
already imported licenses.
PDF reports display time as per time zone of controller instance. This may
not match with the time shown in Harmony Portal because the portal takes
time zone of theclient browser machine.
When the configuration being pushed from controller includes password or
similar fields, for Thunders these configuration changes do not apply.
Such changes are to be made directly in Thunder. After that configuration
can be scanned from controllerfor synchronization.
When more than one administrator changes configuration of applications
deployed on same Thunder partition via Harmony Portal, final configuration
may result in inconsistent state. As of now, it is advised that changes on
one partition should be done only from one place.
When the Thunder configuration has a shared object, configuration push
from controller fails. For making either the reference to shared object
is to be removed or changes are to be made directly in Thunder. Shared
object can be linked againafter the configuration push. Or configuration
can be scanned from controller for synchronization if changes are made
directly on Thunder.
Disaster Recovery set-up breaks when controller is upgraded. Please setup
Disaster Recovery again after upgrading the controller.
Certificate Admins are able to set-up alerts and reports in addition to their assigned roles.
When Thunder is registered to controller via data interface, access device
function from Harmony Controller (SSO to Thunder management UI) is not
working. Suggested is to login to device separately.
Thunder image upgrade from Harmony Controller fails for a few versions
(4.1.1-Px) of Thunder. Please use Thunder device CLI for upgrading the


We are available at your service on Phone, and Email:

Phone: 1-888-TACS-A10 (Toll-Free USA & Canada). 1-408-325-8676 (International)