A3 Version 2.0.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 the current release of A3:

Limitations

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 Extreme Networks A3 v2.0.0:

Description
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. To join addition 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 network interface configuration of an A3 cluster through the UI after initial configuration. Ensure the accuracy of your initial setup when configuring network interfaces.
When performing software update on a cluster, progress does not appear incrementally, but appears all at once at the end of the process.
A3 currently supports only one Ethernet interface.
Administrators might not be able to log in to A3 if the system 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.
Configure clusters only 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.

Known Issues

The following are known issues in Extreme Networks A3 v2.0.0:

ID Description
A3-704 Joining A3 nodes to an Active Directory domain is unsuccessful when the node hostname is more than 15 characters.
A3-700 When removing nodes from an A3 cluster, it is currently necessary to remove all inactive nodes before removing any active nodes.
A3-615 The Cloud Integration page currently does not work with Microsoft browsers (IE and Edge).
A3-543 The network interface configuration UI currently displays IPv6 and inlines settings, despite these features being unsupported.
A3-526 Joining an Active Directory domain is sometimes unsuccessful on the first attempt.
A3-202 Certificate information display currently does not work with Firefox and Microsoft browsers.
  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 Safari browser.
  Clicking Restart All to restart services on the Services page does not successfully restart some services and can result in unpredictable behavior.

Addressed Issues

The following issues have been addressed in Extreme Networks A3 v2.0.0:

ID Description
A3-77 Google Play Store and Windows contained an incorrectly branded version of the A3 agent.

Additional resources

The following guides are available for Extreme Networks A3 v2.0.0:

 


Extreme Networks Documentation PortalExtreme Networks BlogsHiveCare Community Forum

Copyright ©  Aerohive Networks, Inc.