Home > A3 Version V3.3.0 Release Notes
|
View descriptions of the newest features and review the known and addressed A3 issues on this page.
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 adds several features and includes several bug fixes.
The upgrade process is a very CPU intensive task. Before upgrading, please make sure that each of the cluster node has sufficient idle CPU cycles. If messages similar to those below are displayed in the GUI window after upgrade, then either configuration files could not be backed up within the 2 minute window or configurations changes occurred while the system was trying to perform a backup. If this is the case, you will need to try again with the system in a more quiescent state.
Gathering cluster information... done!
Checking health of cluster nodes... done!
Backing up cluster data... error at <IP address>
Cluster update was unsuccessful.
Changes in Behavior or Appearance
This version of A3 features the following changes in behavior and appearance:
| ID | Description |
|---|---|
| A3-2195 | Context sensitive help has been added to A3. It works in
two ways:
|
| A3-2583 | Fabric attach support. When defining Role by VLAN ID in Configuration > Policies and Access Control > Network Devices, Roles definition, you may now define an ID in the following format: VLAN-ID=<VLAN ID>:ISID-NSI-ID=<ISID/NSI ID>. This only applies to Summit switches when using the Extreme Summit series Type. |
| A3-2620 | Cluster recovery. The process for automatic cluster recovery has been automated. |
| A3-2632 | Send disconnect. CoA or disconnect messages may not be sent to individual Clients. |
| A3-2737 | Connection profile test tool. A new Connection Profile Test has been added to the Tools Overview > Scanning Tools menu. The new test determines the connection profile that would be matched for a set of parameters. |
| A3-2746 | WYSIWYG editor for Captive Portal sources. The editor used for the files available in Configuration > Policies and Access Control > Connection Profiles, Files tab has been upgraded. |
| A3-2751 | Improved update software function. The A3 upgrade
process available using the  has been
improved for better ease of use and resilience. |
| A3-2766 | Role selection during self-registration. Clients may now select their role during the self-registration process. |
| A3-2767 | Randomized MAC address event. A new MAC Address randomization detection event has been added to the default list of security events. If enabled, devices that use a random MAC address will be isolated with a message advising them to turn off that feature on their device. |
| A3-2768 | Multiple certificate authorities. Multiple certificate authorities may be used in the System Configuration > SSL Certificates > RADIUS > Edit, Certification Authority Certificate(s) field. The text for the certificates should be concatenated together in that field. |
| A3-2770 | Backup. The extent of the files saved in the Backup process has been expanded. Please read the restrictions described on the help page just cited. |
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:
| Description |
|---|
|
When trying to delete a client (also referred to as a node) the following error message is displayed, "<client MAC> has an open locationlog entry. Node deletion is prohibited." If you want to delete a client you should enable the node_cleanup maintenance task under Configuration > System Configuration > Maintenance. The following task parameters are most relevant: 1) Unreg window - how long a registered node should remain inactive before it becomes unregistered. 2) Delete window - how long an unregistered node should remain inactive before being deleted. This shouldn't be used if you are using port-security. Note the 'locationlog_cleanup' maintenance task can also be used to remove outdated locationlog entries from the database. |
| 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. |
| 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:
| ID | Description |
|---|---|
| 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-99 | When creating an Active Directory entry, the identifier must be alpha-numeric with no spaces. |
| A3-910 | If the initial setup is not completed by the time the current DHCP lease expires, A3 loses its IP address. |
| 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-1180 | Authentication tests do not change prompts to be applicable with the Authentication Source. Enter appropriate values into the Username and Password fields. |
| A3-1277 | When two SSID filters are used in a single connection profile, 802.1x logins fail. |
| A3-2249 | Administrative rules cannot be configured for EAP-TLS authentication. |
| A3-2510 | A3 servers with prior versions may be allowed to join a cluster. |
| A3-2579 | The Captive Portal redirection delay may be too short. The redirection may have occurred in spite of an error message. |
| A3-2624 | There is no way to delete a Role in the A3 GUI. |
| A3-2653 | Backup from the Backup & Restore page must be done on the master A3 node. |
The following issues have been addressed in this release of Extreme Networks A3:
| ID | Description |
|---|---|
| A3-2178 | GUI upgrade window not getting updated during upgrade. |
| A3-2725 | Post upgrade backup feature was not working. |
| A3-2753 | Connection profile previews generated a blank page. |
Copyright © 2020 Extreme Networks. All rights reserved. Published December 2020.
