AOS-W Instant 8.6.0.3 Release Notes PDF
AOS-W Instant 8.6.0.3 Release Notes PDF
Release Notes
Copyright Information
Alcatel-Lucent and the Alcatel-Lucent Enterprise logo are trademarks of Alcatel-Lucent. To view other trademarks used by affiliated companies of ALE
Holding, visit:
https://www.al-enterprise.com/en/legal/trademarks-copyright
All other trademarks are the property of their respective owners. The information presented is subject to change without notice. Neither ALE Holding
nor any of its affiliates assumes any responsibility for inaccuracies contained herein. (2020)
Open Source Code
This product includes code licensed under the GNU General Public License, the GNU Lesser General Public License, and/or certain other open source
licenses.
Contents 3
Revision History 5
Release Overview 6
Supported Browsers 6
Contacting Support 7
Supported OAW-IAPs 9
Regulatory Updates 11
Resolved Issues 12
Known Issues 14
Upgrading an OAW-IAP 17
This Alcatel-Lucent AOS-W Instant release notes includes the following topics:
n New Features and Enhancements on page 8
n Supported Hardware Platforms on page 9
n Regulatory Updates on page 11
n Resolved Issues on page 12
n Known Issues on page 14
n Upgrading an OAW-IAP on page 17
For the list of terms, refer Glossary.
Supported Browsers
The following browsers are officially supported for use with the AOS-W Instant WebUI:
n Microsoft Internet Explorer 11 on Windows 7 and Windows 8
n Microsoft Edge (Microsoft Edge 38.14393.0.0 and Microsoft EdgeHTML 14.14393) on Windows 10
n Mozilla Firefox 48 or later on Windows 7, Windows 8, Windows 10, and macOS
n Apple Safari 8.0 or later on macOS
n Google Chrome 67 or later on Windows 7, Windows 8, Windows 10, and macOS
Email ebg_global_supportcenter@al-enterprise.com
Worldwide 1-818-878-4507
This issue is observed when the existing connection between IAP and the management platform is lost or if Activate or OmniVista 3600 Air Manager services
are reset.
Supported OAW-IAPs
The following table displays the OAW-IAP platforms supported in AOS-W Instant 8.6.x release.
n OAW-AP 220 Series — OAW-IAP224 and OAW-IAP225 AOS-W Instant 6.3.1.1-4.0.0.0 or later
Periodic regulatory changes may require modifications to the list of channels supported by an AP. For a complete list of channels supported by an AP
using a specific country domain, access the OAW-IAP CLI and execute the show ap allowed-channels command.
For a complete list of countries and the regulatory domains in which the APs are certified for operation, refer to the Downloadable Regulatory Table or
the DRT Release Notes at service.esd.alcatel-lucent.com.
AOS-187268 — A few APs crashed and rebooted unexpectedly. The log file listed the reason for AOS-W Instant 8.3.0.0
AOS-196356 the event as Reboot caused by kernel panic: Fatal exception. This issue
occurred when 802.11w standard was enabled on the AP. The fix ensures that
the APs work as expected. This issue was observed in APs running AOS-W
Instant 8.3.0.0 or later versions.
AOS-187773 — All OAW-IAPs in a cluster rebooted randomly and the log file listed the reason AOS-W Instant 8.4.0.1
AOS-196214 for the event as Gateway Unreachable. This issue occurred due to a packet
AOS-196551 counter error that triggered the reboot. The fix ensures that the APs do not
reboot randomly and work as expected. This issue was observed in APs running
AOS-W Instant 8.4.0.1 or later versions.
AOS-195491 — An OAW-IAP randomly generated OFALD messages and affected the quality of AOS-W Instant 8.3.0.7
the network. The fix ensures that unnecessary OFALD messages are not
generated and the network quality remains unaffected. This issue was
observed in APs running AOS-W Instant 8.3.0.7 or later versions.
AOS-195564 — A client lost its IP address when roaming. This issue occurred under the AOS-W Instant 8.3.0.0
AOS-196892 following scenarios:
AOS-198878 n When the client switched from the mesh portal AP to a mesh point AP, when
no other client was connected to the mesh portal AP.
n On AOS-W Instant networks in which Client VLAN Assignment was set to
Dynamic in the Network > VLAN tab of the webUI.
The fix ensures that clients retain their IP address when roaming between APs.
This issue was observed in APs running AOS-W Instant 8.3.0.0 or later versions.
AOS-195789 — An OAW-IAP reported high channel usage on the 5 GHz radio. The debug logs AOS-W Instant 8.4.0.1
showed high number of radio resets. The fix ensures that the OAW-IAP works
as expected. This issue was observed in OAW-AP377 access points running
AOS-W Instant 8.4.0.1 or later versions.
AOS-195948 — An OAW-AP535 access point crashed unexpectedly. This issue occurred when AOS-W Instant 8.6.0.0
split 5 GHz radio was enabled on the AP. The fix ensures that the AP works as
expected when Split 5 GHz radio is enabled on the AP. This issue is observed
in OAW-AP550 Series access points running AOS-W Instant 8.6.0.0 or later
versions.
AOS-196699 — OAW-AP515 access points crashed and rebooted unexpectedly. The cause for AOS-W Instant 8.6.0.0
AOS-199431 the reboot was AP Reboot reason: BadAddr:ceee391d5e20e542 PC:wlc_
AOS-199587 mutx_bw_policy_update+0x408/0x28b8 [wl_v6] Warm-reset. The fix
AOS-199592 ensures that the APs work as expected. This issue was observed in OAW-AP515
access points running AOS-W Instant 8.6.0.0 or later versions.
AOS-197205 — An OAW-IAP crashed and rebooted unexpectedly. This issue occurred under AOS-W Instant 8.5.0.0
the following conditions:
n When a client connected to an SSID configured with bandwidth limit
contracts.
n When the AP used cellular uplink for internet connectivity.
The fix ensures that the AP does not reboot unexpectedly and works as
expected. This issue was observed in APs running AOS-W Instant 8.5.0.0 or
later versions.
AOS-197245 — The Facebook configuration link in the Configuration > Network > Security AOS-W Instant 8.4.0.6
AOS-197374 tab was not displayed. The fix ensures that the Facebook configuration link is
displayed in the webUI. This issue was observed in APs running AOS-W Instant
8.4.0.6 or later versions.
AOS-199612 — A few APs in an AOS-W Instant cluster reported the status in OmniVista 3600 AOS-W Instant 8.6.0.2
AOS-200367 Air Manager as Down and the CLI of the AP was unresponsive during this
AOS-200732 period. The fix ensures that the AP reports the correct status to OmniVista 3600
Air Manager and the CLI of the AP works as expected. This issue was observed
in AOS-W Instant AP clusters running AOS-W Instant 8.6.0.2.
This chapter describes the known issues and limitations observed in this release.
Important Update on OAW-AP210 Series, OAW-AP 220 Series, OAW-AP228, and OAW-AP270 Series Access Points
The OAW-AP210 Series, OAW-AP 220 Series, OAW-AP228, and OAW-AP270 Series access points will be deprecated for future releases and include the
following limitations in AOS-W Instant 8.6.0.x, which is the last supported software version for these access points:
n No support for BLE interface (with USB)
n The DPI engine used for AppRF will have limitations in terms of enhancements and fixes in the future.
n These APs use WolfSSL libraries in AOS-W Instant 8.6.0.0 and not OpenSSL.
n No support for WPA3 security.
All of these platforms have already been marked as end-of-sale. Please review the end-of-sale and end-of-support dates for these platforms here.
Known Issues
Following are the known issues observed in this release.
AOS-190089 — An OAW-IAP classifies YouTube application traffic as UDP traffic and not AOS-W Instant 8.4.0.3
YouTube app traffic. This issue is observed in APs running AOS-W Instant
8.4.0.3 or later versions.
AOS-192604 — Traffic between clients within the same subnet VLAN is subject to source NAT. AOS-W Instant 8.6.0.0
This issue occurs because the master OAW-IAP performs source NAT on local
traffic. This issue is observed in APs running AOS-W Instant 8.6.0.0 or later
versions.
AOS-196704 — An OAW-IAP acting as a mesh portal crashes and reboots. The log file lists the AOS-W Instant 8.5.0.2
reason as: Reboot caused by kernel panic: Rebooting the AP because of
FW ASSERT. This issue is observed in APs running AOS-W Instant 8.5.0.2 or
later versions.
AOS-198275 — Clients are not redirected to the captive portal page for reauthentication when AOS-W Instant 8.3.0.7
the radius-reauth-interval defined in the network profile expires. This issue
occurs when both 802.1X authenication and captive portal authentication are
enabled on the AOS-W Instant network. This issue is observed in APs running
AOS-W Instant 8.3.0.7 or later versions.
AOS-198363 — Clients are either unable to connect to the AP or are getting disconnected when AOS-W Instant 8.3.0.7
the SAPD process over utilizes memory. This issue is observed in OAW-IAP324
APs running AOS-W Instant 8.3.0.7 or later versions.
AOS-198787 — Uplink preemption for IAP-VPN connections does not work as expected when AOS-W Instant 8.5.0.4
AOS-198929 the primary uplink of the AP fails. This issue occurs when the primary uplink of
the AP is Cellular. This issue was observed in APs running AOS-W Instant
8.5.0.4 of later versions.
AOS-198931 — A few APs are unable to join the cluster when the software version is upgraded AOS-W Instant 8.6.0.0
to AOS-W Instant 8.6.0.0 or later versions. This issue occurs when the software
version was upgraded from AOS-W Instant 8.4.0.0 or later versions to 8.6.0.0 or
later versions on the cluster. This issue is observed in APs running AOS-W
Instant 8.6.0.0 or later versions.
AOS-198992 — Clients are unable to connect to the WLAN SSID when 802.1X authentication AOS-W Instant 8.6.0.1
with termination in enabled for the network. This issue occurs when a
ECDSA certificate is used by the authentication server configured on the
network. This issue is observed in APs running AOS-W Instant 8.6.0.1 or later
versions.
AOS-199151 — Clients connecting to a slave AP in an AOS-W Instant cluster are not redirected AOS-W Instant 8.6.0.1
to the captive portal splash page. This issue occurs because of an error that
causes the slave AP to receive a wrong firewall rule. This issue is observed in
AOS-W Instant AP clusters running AOS-W Instant 8.6.0.1 or later versions.
AOS-199449 — A few clients are unable to connect to an OAW-AP515 access point. This issue AOS-W Instant 8.6.0.2
occurs when the AP is upgraded to AOS-W Instant 8.6.0.2. This issue is
observed in OAW-AP515 access points running AOS-W Instant 8.6.0.2.
AOS-199699 — An OAW-IAP acting as a mesh portal AP crashes and reboots unexpectedly. The AOS-W Instant 8.6.0.1
log file lists the reason for the event as Reboot caused by kernel panic:
softlockup: hung tasks. This issue is observed in APs running AOS-W Instant
8.6.0.1 or later versions.
AOS-200447 — The Destination NAT rule for SSH traffic in the Inbound Firewall settings AOS-W Instant 8.5.0.5
configured under Configuration > Settings is not enforced. This issue is
observed in APs running AOS-W Instant 8.5.0.5 or later versions.
This chapter describes the AOS-W Instant software upgrade procedures and the different methods for upgrading the image on the OAW-IAP.
Topics in this chapter include:
n Upgrading an OAW-IAP Using OmniVista 3600 Air Manager Management Platform on page 17
n Upgrading an OAW-IAP Image Manually Using WebUI on page 18
n Upgrading an OAW-IAP Image Manually Using CLI on page 21
n Upgrade from AOS-W Instant 6.4.x.x-4.2.x.x to AOS-W Instant 8.6.0.x on page 21
You can manually obtain an image file from a local file system or from a remote server accessed using a TFTP, FTP or HTTP URL.
n Select the Image URL option. Select this option to obtain an image file from a HTTP, TFTP, or FTP URL.
l HTTP - http://<IP-address>/<image-file>. For example, http://<IP-address>/AlcatelInstant_Hercules_8.6.0.x_xxxx
l TFTP - tftp://<IP-address>/<image-file>. For example, tftp://<IP-address>/AlcatelInstant_Hercules_8.6.0.x_xxxx
l FTP - ftp://<IP-address>/<image-file>. For example, ftp://<IP-address>/AlcatelInstant_Hercules_8.6.0.x_xxxx
l FTP - ftp://<user name:password>@<IP-address>/<image-file>. For example, ftp://<alcatel:123456>@<IP-address>/AlcatelInstant_Hercules_
8.6.0.x_xxxx
The FTP server supports both anonymous and username:password login methods.
Multiclass OAW-IAPs can be upgraded only in the URL format, not in the local image file format.
3. Clear the Reboot all APs after upgrade check box if required. This check box is selected by default to allow the OAW-IAPs to reboot automatically
after a successful upgrade. To reboot the OAW-IAP at a later time, clear the Reboot all APs after upgrade check box.
4. Click Upgrade Now to upgrade the OAW-IAP to the newer version.
n Select the Image URL option. Select this option to obtain an image file from a HTTP, TFTP, or FTP URL.
l HTTP - http://<IP-address>/<image-file>. For example, http://<IP-address>/AlcatelInstant_Hercules_8.6.0.x_xxxx
l TFTP - tftp://<IP-address>/<image-file>. For example, tftp://<IP-address>/AlcatelInstant_Hercules_8.6.0.x_xxxx
l FTP - ftp://<IP-address>/<image-file>. For example, ftp://<IP-address>/AlcatelInstant_Hercules_8.6.0.x_xxxx
l FTP - ftp://<user name:password>@<IP-address>/<image-file>. For example, ftp://<alcatel:123456>@<IP-address>/AlcatelInstant_Hercules_
8.6.0.x_xxxx
The FTP server supports both anonymous and username:password login methods.
Multiclass OAW-IAPs can be upgraded only in the URL format, not in the local image file format.
3. Disable the Reboot all APs after upgrade toggle switch if required. This option is enabled by default to allow the OAW-IAPs to reboot
automatically after a successful upgrade. To reboot the OAW-IAP at a later time, clear the Reboot all APs after upgrade check box.
4. Click Upgrade Now to upgrade the OAW-IAP to the newer version.