A3 Version 2.2.0 Release Notes
View descriptions of the newest features and review the known and addressed A3 issues on this page.
New Features and Enhancements
You can access the A3 Web Admin interface by using the URL https://<ip_address>:1443, where <ip_address> is the IP address of the A3 virtual machine.
The following new features and enhancements were added in this release of Extreme Networks A3:
This version of A3 features the following changes in behavior and appearance:
Online Help Now Available:
When the A3 2.2.0 Help function is invoked from the A3 GUI, a new toolbar at the top of the page includes Table of Contents, Theory, and GUI links. The Table of Contents link shows all contents, the Theory link displays Theory of Operation topics, and the GUI link displays help topics for policy configuration pages.
Default Placeholder Date and Time:
When an admin encounters a field that requires a date or time, A3 now provides a default value. Default start values use the current date and time, and the default stop values use a date and time that is two hours ahead of the current time.
Network Interface Enhancements:
A3 2.2.0 enhanced initial setup flow and network interface configuration.
The scripts automatically restart services after you change the host name for a cluster or change the management IP address.
A3 2.2.0 enhances existing Fingerbank cloud integration by prioritizing A3 queries.
In this release you can modify the management interface IP address more simply, which eases overall network administration. This added flexibility applies to the management interface of individual nodes and to clusters. Normal constraints restricting the number of management interfaces to exactly one are still in place.
A3 2.2.0 cloud dashboard added a cluster health report which shows the number of successful and unsuccessful RADIUS authentications across all A3 deployments for the last 24 hours.
A3 2.2.0 cloud dashboard added a cluster health report which shows the number of DHCP leases used.
A3 2.2.0 prevents deletion of the admin account created during setup and features an email-based password recovery mechanism.
A3 2.2.0 supports configuring DNS settings with a netcfg account or by using the management interface.
Limitations are not necessarily software nonconformances or issues, but might affect workflow, and are presented here for your reference and consideration.
The following are known software limitations in this release of Extreme Networks A3:
|You must upload the HTTPS and EAP-TLS certificates of a cluster to the cluster primary and not to the member nodes.|
|When setting up a cluster, you can only join one node to the cluster at a time. Before joining additional nodes, be sure to wait for the previous join process to complete.|
|When linking to an Aerohive cloud account, reports only include data from that moment onward, and do not include historical data prior to linking.|
|You cannot change the management network interface of an A3 cluster using the UI after initial configuration. Ensure the accuracy of your setup when you initially configure the management network interface.|
|When performing a software update on a cluster, progress appears all at once at the end of the process instead of appearing incrementally during the process.|
|Administrators might not be able to log in to A3 if the clock on the A3 system is not accurate.|
|After adding an Active Directory domain, always restart A3 services in the following order to prevent service dependency issues: radiusd, radsniff, netdata, pfstat.|
|In a cluster environment, all configuration must occur on the cluster primary.|
|When you remove a node from an A3 cluster, it can neither rejoin the cluster, nor function as a standalone and must be discarded.|
The following are known issues in this release of Extreme Networks A3:
|A3-1525||An A3 node cannot join a cluster when there is no virtual IP address configured for an interface.|
|A3-1247||RADIUS logs are unavailable on the VIP RADIUS debug page when device authentication is on a slave node.|
|A3-1224||The A3 Tools page does not appear properly on some macOS versions.|
|A3-1179||A3 sometimes prompts the admin to enter a user name and password when performing authentication tests using sources that do not require this type of authentication.|
|A3-920||When an admin restarts an entire cluster, one of the cluster node databases sometimes cannot start properly.|
|A3-910||If the initial setup is not completed by the time the current DHCP lease expires, A3 loses its IP address.|
|A3-860||When an admin attempts to restore a cluster from VM snapshots, A3 sometimes does not start properly.|
|A3-857||A3 does not start properly after an admin removes an active node from a multiple-node cluster that has an inactive node.|
|A3-1691||DNS Settings configured using the UI are overwritten by new adding new physical interfaces through the VM.|
|Some in-product documentation links within the A3 interface do not link correctly to the documentation.|
|Profile installation on macOS requires the captive web portal to be opened using the Safari browser.|
|Clicking Restart All to restart services on the Services page does not successfully restart some services and can
result in unpredictable behavior.
The following issues have been addressed in this release of Extreme Networks A3:
|A3-1531||RADIUS logs are unavailable on the VIP RADIUS debug page when devices are authenticated on a slave node.||2.2.0|
The following guides are available for Extreme Networks A3 :
Copyright © Aerohive Networks, Inc.