A3 Version V3.1.2 Release Notes
View descriptions of the newest features and review the known and addressed A3 issues on this page.
New Features and Enhancements
The A3 Web Admin interface is accessed through the https://<ip_address>:1443 URL, where <ip_address> is the IP address of the A3 virtual machine.
This release of Extreme Networks A3 is a maintenance release and includes only bug fixes.
Limitations are not necessarily software 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:
|When setting up a cluster, only one node should be added to the cluster at a time. Additional nodes should only be added after the previous join process has completed.|
|When linking to an Extreme Networks 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.|
|Administrators might not be able to log in to A3 if the clock on the A3 system is not accurate.|
|In a cluster environment, all configuration must be performed through the cluster's VIP address.|
|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:
|Prior to upgrading from a pre-V3.x version, Extreme Networks recommends powering down your server or cluster members. If the RAM associated with the A3 VM still uses the old default of 8 GB, it should be increased to 16 GB.|
|This issue pertains to A3 instances in which the A3 server or cluster was connected to HiveManager prior to the upgrade. After performing the upgrade, the administrator should log into the local A3 GUI and unlink the server or cluster from Hive Manager. The setting for this is at Configuration > System Configuration > Cloud Integration. After a moment, the server can be relinked to the HiveManager account. This may be necessary if an administrator can not log into the A3 cloud GUI from HiveManager.|
|Profile installation on macOS requires the captive web portal to be opened using the Safari browser.|
|The Network Detection feature of the Captive Portal is always enabled, regardless of the setting of the switch in Configuration > Advanced Access Configuration > Captive Portal.|
|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-860||When an admin attempts to restore a cluster from VM snapshots, A3 sometimes does not 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-920||When an admin restarts an entire cluster, one of the cluster node databases sometimes cannot start properly.|
|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. Enter any value.|
|A3-1691||DNS Settings configured using the UI are overwritten by new adding new physical interfaces through the VM.|
|A3-2244||Radiusd must be restarted when joining a domain or editing a realm, although the UI does not provide a warning or a button.|
|A3-2332||When a service is restarted in a cluster, it must be individually started on all members. GUIs must be opened for all cluster members, although administration is occurring on the Master.|
A security event with an Event Action of Register can be created, but will not be saved.
|A3-2390||Let's Encrypt certificate usage is not currently supported.|
The following issues have been addressed in this release of Extreme Networks A3:
|A3-2474||Client devices attempting to register using the self-registration process were sometimes encountering a registration error.||
|When using authentication servers that disable NTLM v1, A3 reported NTLM errors and often prevented device authentication.||V3.1.2|
|A3-2441||A3 OS detection database was not updating correctly.||V3.1.2|
Copyright © Aerohive Networks, Inc.