Aruba Instant 8.8.0.0 Release Notes

Aruba Instant 8.8.0.0

Release Notes

Copyright Information©Copyright 2021 Hewlett Packard Enterprise Development LP.

Open Source CodeThis product includes code licensed under theGNU General Public License, the GNU Lesser GeneralPublic License, and/or certain other open source licenses. A completemachine-readable copy of thesource code corresponding to such code is available upon request. This offer is valid to anyone inreceipt of this information and shall expire three years following the date of the final distribution ofthis product version by Hewlett Packard Enterprise Company. To obtain such source code, send acheck ormoney order in the amount of US $10.00 to:

Hewlett Packard Enterprise Company6280 America Center DriveSan Jose, CA 95002USA

Contents

Contents

Contents 3

Revision History 4

Release Overview 5

Related Documents 5

Supported Browsers 5

Terminology Change 6

Contacting Support 6

New Features and Enhancements 7ARM 7Authentication 7Central 8Datapath 8Firewall 8IoT 9Mesh 10Platform 10Security 11SNMP 11VPN 12

Supported Hardware Platforms 13

Regulatory Updates 14

Resolved Issues 15

Known Issues and Limitations 24Limitations 24Known Issues 24

Upgrading an Instant AP 26Upgrading an Instant AP and Image Server 26Upgrading an Instant AP Using the Automatic Image Check 28Upgrading to a New VersionManually Using theWebUI 29Upgrading an Instant AP ImageUsing CLI 31Upgrade from Instant 6.4.x.x-4.2.x.x to Instant 8.8.0.x 32

Aruba Instant 8.8.0.0 | Release Notes 3

4 | Revision History Aruba Instant 8.8.0.0 | Release Notes

Revision HistoryThe following table provides the revision history of this document.

Revision Change Description

Revision 03 AOS-211828 and AOS-222011 was added to the Resolved Issueslist.

Revision 02 Air Slice support introduced on additional Instant AP platforms.

Revision 01 Initial release.

Table 1: Revision History

Chapter 1Release Overview

Release OverviewThis Aruba Instant release notes includes the following topics:

n New Features and Enhancements on page 7n Supported Hardware Platforms on page 13n Regulatory Updates on page 14n Resolved Issues on page 15n Known Issues and Limitations on page 24n Upgrading an Instant AP on page 26

For the list of terms, refer to theGlossary.

Related DocumentsThe following guides are part of the complete documentation for the Aruba user-centric network:

n Aruba AP Software Quick Start Guiden Aruba Instant User Guiden Aruba Instant CLI Reference Guiden Aruba Instant REST API Guiden Aruba Instant Syslog Messages Reference Guiden Aruba Instant AP Troubleshooting Guide

Supported BrowsersThe following browsers are officially supported for usewith the Instant WebUI:

n Microsoft Internet Explorer 11 onWindows 7 andWindows 8n Microsoft Edge (Microsoft Edge 38.14393.0.0 andMicrosoft EdgeHTML 14.14393) onWindows 10n Mozilla Firefox 48 or later onWindows 7, Windows 8, Windows 10, andmacOSn Apple Safari 8.0 or later onmacOSn Google Chrome 67 or later onWindows 7, Windows 8, Windows 10, andmacOS


https://www.arubanetworks.com/techdocs/Glossary/Default.htm

6 | Terminology Change Aruba Instant 8.8.0.0 | Release Notes

Terminology ChangeAs part of advancing HPE's commitment to racial justice, we are taking amuch-needed step in overhaulingHPE engineering terminology to reflect our belief systemof diversity and inclusion. Some legacy productsand publicationsmay continue to include terminology that seemingly evokes bias against specific groups ofpeople. Such content is not representative of our HPE culture andmoving forward, Arubawill replaceracially insensitive terms and instead use the following new language:

Usage Old Language New Language

Campus Access Points +Controllers

Master-Slave Conductor-Member

Instant Access Points Master-Slave Conductor-Member

Switch Stack Master-Slave Conductor-Member

Wireless LAN Controller Mobility Master Mobility Conductor

Firewall Configuration Blacklist, Whitelist Denylist, Allowlist

Types of Hackers Black Hat, White Hat Unethical, Ethical

Contacting Support

Main Site arubanetworks.com

Support Site https://asp.arubanetworks.com/

Airheads Social Forums and KnowledgeBase

community.arubanetworks.com

North American Telephone 1-800-943-4526 (Toll Free)1-408-754-1200

International Telephone arubanetworks.com/support-services/contact-support/

Software Licensing Site lms.arubanetworks.com

End-of-life Information arubanetworks.com/support-services/end-of-life/

Security Incident Response Team Site: arubanetworks.com/support-services/security-bulletins/Email: [email protected]

Table 2: Contact Information

http://www.arubanetworks.com/

https://asp.arubanetworks.com/

http://community.arubanetworks.com/

http://www.arubanetworks.com/support-services/contact-support/

http://lms.arubanetworks.com/

http://www.arubanetworks.com/support-services/end-of-life/

http://www.arubanetworks.com/support-services/security-bulletins/

mailto:[email protected]

Chapter 2New Features and Enhancements

New Features and EnhancementsThis chapter describes the features and enhancements introduced in this release.

ARM

Uplink MU-MIMO TransmissionAruba Instant 8.8.0.0 supports the uplink MU-MIMO transmission of 802.11ax protocol. Prior to Instant8.8.0.0, MU-MIMO allowed to send data frames from access points to clients. Now, the uplink MU-MIMOtransmission allows to send data frames from clients to APs. It also helps in achieving throughput gainswhen applications need to upload large amount of data. It also enables themultiple spatially separatedclients to access the channel at the same time and it is also useful in scenarios where stations have limitednumber of antennas. The uplink MU MIMO transmission is supported only in 5 GHz band. Only AP-535 andAP-555 access points support uplink MU MIMO transmission.

Support for Zero-Wait DFSDynamic Frequency Selection (DFS), amandate for radio systems operating in the 5 GHz band to identifyand avoid interferencewith Radar systems now supports the zero-wait feature. When an 802.11 radiodetects radar, it vacates its channel and switches to another channel. Thismight result in a oneminuteoutage. Starting fromAruba Instant 8.8.0.0, the zero-wait DFS feature provides seamless change ofchannels and avoids the oneminute outage. Hence, stations do not lose its connectivity when an APmovesto a DFS channel. This feature is enabled by default.

Authentication

Configuring a Timeout Duration for 802.1X AuthenticationA new CLI command ap1x-timeout is added to configure a timeout duration for 802.1X authenticationwhen the AP is used as a supplicant for 802.1X authentication

Configuring Ageout Time for PMK Cache EntriesA new setting, delete-pmkcache, is introduced in theWLAN SSID profile to delete client information in thePMK cachemaintained for fast roaming. Configuring this setting deletes client information in the PMK cacheimmediately after a client disconnects or times out from the network as opposed to the default ageout timeof 8 hours. This is configured using the CLI.

Support for New CoA TypeAruba Instant supports a new CoA type for the radius attributeAcct-Session-Id.

Support for New Diffie-Hellman Groups for OWEAruba Instant supports theDiffie-Hellman Groups 20 and 21 for Enhanced Open security.


8 | New Features and Enhancements Aruba Instant 8.8.0.0 | Release Notes

Central

Automatic Installation of DRT UpdatesInstant APsmanaged by Central can now automatically download and install the latest DRT file available onActivate. TheDRT file includes the details of approved regulatory certifications and allowed RF transmissions(channels, EIRP, and so on..) for an AP at any geographical region or country.

Enhancements to Telemetry Information Sent to CentralThe AP now includes the following information in the telemetry data sent to Aruba Central:

n Status of uplink interfacesn Health of uplink interfacesn Uplink failover events with the reason for failover

Support for Green APsInstant APs supports Aruba Central's green AP featurewhich puts an AP into deep sleepmodewhen theservices required from the AP isminimal to nil. This helps in reducing the power used by the AP andconserves energy whenever possible. When the AP's service is required, Aruba Central wakes the AP fromdeep sleepmode through an active AP in the same subnet.

Datapath

Enabling SFTP TransfersAruba Instant now supports transfer of files using SFTP from the server to an AP. A new CLI command isintroduced to support downloading and uploading of a configuration file using SFTP.

The following command restores the configuration through SFTP:(Instant AP)# copy sftp <addr> <file> <username> system config

The following command is used to backup the configuration through SFTP:(Instant AP)# copy config sftp <addr> <file> <username>

Parameter Description

<addr> Denotes the IP address of remote sftp server.

<file> Denotes the configuration file’s absolute path of the remoteserver.

<username> Denotes the user name used to establish an ssh connection to theremote server.

Reboot the AP for the configuration changes to take effect.

Firewall

Increase in the Data Rate Range for Bandwidth Limit Contracts andApplication Throttling

Aruba Instant 8.8.0.0 | Release Notes New Features and Enhancements | 9

The upper limit for throttling application traffic and bandwidth limit contract for users is increased to 2Gbps. This changes the range for bandwidth-limit, throttle-upstream, and throttle-downstreamparameters in thewlan access-rule command. The new range for these parameters is 1-2147482 Kbps.

IoT

IoT Support for BLE Data forwarding for all Device ClassesAruba Instant now allows forwarding of BLE data for all device classes.

IoT Support for Coexistence

IoT Support for New Authentication TypeAruba Instant 8.8.0.0 introduces a new IoT authentication type, Client Credentials. The newauthentication type can be configured in the IoT transport profile.

IoT Support for New BLE SensorsAruba Instant now supports the following BLE vendors:

n Googlen Minewn DirActn GwaHygienen Polestarn Blyott

IoT Support for SES ImagotagAruba Instant now allows an AP to authenticate with SES-Imagotag ESL server and verify the TLS FQDN.Instant also supports channel 127 for SES Imagotag ESL.

IoT Support for Piera SensorAruba Instant now supports USB-based dongles fromPiera.

IoT Support for SoluM ESL GatewayAruba Instant now supports Solu M NEWTON USBG2 GWZigbee-based USB gateway.

IoT Support for New USB-Based Sensors from EnOceanAruba Instant now supports all sub-1-GHz USB-based sensors from EnOcean.

IoT Support for Per-Frame FilteringAruba Instant now supports applying transport profile filters to each frame rather than on the device. Thisallows bleDataForwarding to treat payload content as packet filter.

IoT WebUI Enhancements


Newparameters and fields have been added to configure radio profiles, zigbee profiles, include newvendors.

IoT Support for Zigbee SnifferAruba Instant supports IoT Zigbee sniffer to capture packets and debug zigbeemessages. The internal radioand external USB dongle radio supported by the Instant AP can be used as zigbee sniffers. However, theinternal or external radio typemust beNordic-based (AP-5xx access points or USB Zigbee radio) for thisfeature to work.

Support for New Endpoint TypeA new endpoint type Azure IoT Hub is introduced to allow secure, bi-directional communication betweendevices and the Azure cloud through amanaged device that acts as a gateway.

WiFi Co-existence Support for AP-534, AP-535, and AP-555 AccessPointsAruba Instant now supportsWi-Fi and BLE coexistence on the radio of AP-534, AP-535, and AP-555 accesspoints. This prevent simultaneous transmissions on the radio of an AP. A new parameter called iot-coexistence-disable is added to the rf dot11g-radio-profile command to allow enabling or disabling ofthe BLE andWi-Fi coexistence feature on the 802.11g radio.

Mesh

Enhancements to Topology Optimization ScanningTopology optimization scanning, a scan performed by the AP to identify better links to themesh portal, cannow be configured onmesh point APs. This allows themesh point APs to periodically scan the RF networkand identify better connection to themesh portals. The settings to configure the scan are available in thewlan mesh-profile command.

Platform

802.11mc Support802.11mc standard (Wi-Fi Round Trip Time) is supported on 500 Series, 500H Series, 510 Series, AP-518,530 Series, 550 Series, 560 Series, and 570 Series access points. This enables the AP to act as an Fine TimingMeasurement (FTM) responder and send responses to timemeasurement queries from FTM capable clients.

Support for Air Slice on Additional Instant AP PlatformsAir Slice is now supported on 500 Series, 510 Series, 530 Series, 570 Series, and AP-555 access points.

Discovering Disconnected AntennasThe show ap antenna status command has been introduced to display the operational antenna status ofAPs. This command helps in identifying broken or disconnected antennas and thus, helps in fastertroubleshooting.

Enhancements to 530 Series and 550 Series Access Points

Aruba Instant 8.8.0.0 | Release Notes New Features and Enhancements | 11

530 Series and 550 Series access points are optimized for better powermanagement in the followingscenarios:

n For PoE 802.3at on E0 and PoE 802.3af on E1, the AP power changes to failovermode and gives priorityto E0 port so that the overall power is IEEE 802.3at.

n For PoE 802.3bt on E0 and PoE 802.3af on E1, the AP power changes to failovermode and gives priorityto E0 port so that the overall power is IEEE 802.3bt.

Formore information, see 530 Series Access Point Installation Guide and 550 Series Access Point InstallationGuide.

Fast Roaming with Mesh APsThe fast roaming feature inmesh deployments is now supported on 203H Series, 203R Series, 207 Series,340 Series, 500 Series, 500H Series, 510 Series, 530 Series, 550 Series, 560 Series, and 570 Series accesspoints.

Dual Ethernet Uplink SupportBoth Ethernet ports, Eth0 and Eth1, of AP-318, 320 Series, 330 Series, 370 Series, 510 Series, 530 Series,and 570 Series access points operate as uplink ports by default. The Eth1 port of other APs withmore thantwo Ethernet ports operate as downlink ports by default. The operationmode of the Ethernet ports can beconfigured using thewebUI and the CLI.

Multiple Ethernet Uplink SupportInstant APs enable the configuration of multiple Ethernet ports for uplink. This allows you to configuremultiple Ethernet uplinks to function as active and backup uplink for the AP.

Single AP ModeA new AP deployment mode, Single APmode, is introduced. The Single APmode is a type of standalone APdeployment that includes additional security features designed for Instant deployments with only one AP ina site.

Support for New 4G ModemAruba Instant supports GTCNETSTICK GLU-194ST 4G USB Modem for Sprint on Instant APs except for AP-303H.

Security

Enhancements to Fast BSS TransmissionFast BSS transition is now operational withWPA3-Enterprise CNSAmodewith GCM-256 encryption.

SNMP

Addition of SNMP traps for Association Failure on APTwo new SNMP trapmessages have been added:


n An SNMP trap is sent when PSK client authentication fails.n An SNMP trap is sent when the client is rejected after reaching themaximum clients count.

To generate SNMP V3 traps, you need to first configure the SNMPV3 users, then configure the SNMP trapserver details.

VPN

Increase in Number of Route Entries for IAP-VPNThemaximumnumber of static route entries has been increased from 32 to 160.

Support for Public Dynamic DNSAruba Instant supports the configuration of Public Dynamic DNS for the Instant AP and its DL3 clients. Thisenables the AP to send its IP address updates and its clients IP address updates to public DDNS offered byChangeiP, DynDNS, and No-IP.

Chapter 3Supported Hardware Platforms

Supported Hardware PlatformsThe following table displays the Instant AP platforms supported in Aruba Instant 8.8.0.x release.

Instant AP Platform Minimum Required Instant Software Version

500H Series — AP-503H560 Series — AP-565 and AP-567

Instant 8.7.1.0 or later

500H Series — AP-505HAP-518 — AP-518570 Series — AP-574, AP-575, and AP-577570EX Series — AP-575EX and AP-577EX


500 Series — AP-504 and AP-505 Instant 8.6.0.0 or later

530 Series — AP-534 and AP-535550 Series — AP-555


303 Series — AP-303P387 Series — AP-387510 Series — AP-514 and AP-515


303 Series — AP-303318 Series — AP-318340 Series — AP-344 and AP-345370 Series — AP-374, AP-375, and AP-377370EX Series — AP-375EX and AP-375EX


203H Series — AP-203H Instant 6.5.3.0 or later

203R Series — AP-203R and AP-203RP303H Series — AP-303H and AP-303HR360 Series — AP-365 and AP-367


207 Series — IAP-207300 Series — IAP-304 and IAP-305

Instant 6.5.1.0-4.3.1.0 or later

310 Series — IAP-314 and IAP-315330 Series — IAP-334 and IAP-335

Instant 6.5.0.0-4.3.0.0 or later

320 Series — IAP-324 and IAP-325 Instant 6.4.4.3-4.2.2.0 or later

Table 3: Supported Instant AP Platforms


Chapter 4Regulatory Updates

Regulatory UpdatesThis chapter contains theDownloadable Regulatory Table (DRT) file version introduced in this release.

Periodic regulatory changesmay requiremodifications to the list of channels supported by an AP. For acomplete list of channels supported by an AP using a specific country domain, access the controllerCommand Line Interface (CLI) and execute the show ap allowed-channels country-code <country-code> ap-type <ap-model> command.

For a complete list of countries and the regulatory domains in which the APs are certified for operation, referto theDownloadable Regulatory Table or theDRT ReleaseNotes at asp.arubanetworks.com.

The following DRT file version is part of this release:

n DRT-1.0_79479


http://asp.arubanetworks.com/

Chapter 5Resolved Issues

Resolved IssuesThis release includes an update to JQuery, which has been upgraded to version 3.5.1 to address CVE-2020-11022 and CVE-2020-11023.Additionally, the following issues are resolved in this release.

New Bug ID Old Bug ID Description ReportedVersion

AOS-153932AOS-211583

189128 A 303H Series access point crashed and rebootedunexpectedly. The log file listed the reason for rebootas: Reboot caused by kernel panic: Fatalexception. The fix ensures that the AP works asexpected. This issue was observed in APs using a3G/4G USB modem for uplink. The crash was triggeredwhen the USB modem lost WAN connectivity. Thisissue was observed in 303H Series access pointsrunning Aruba Instant 8.5.0.10 or later versions.

Aruba Instant8.5.0.10

AOS-178788AOS-208860

181307 An AP crashed and rebooted unexpectedly. The log filelists the reason for the event as: BadPtr:00000010PC:wlc_scb_iternext+0x94/0xc0 [wl] Warm-reset.The fix ensures that the AP works as expected. Thisissue was observed in APs running Aruba Instant8.3.0.6 or later versions.


AOS-181197AOS-208313

192623 An AP reloaded with a different subnet mask after areboot. This issue occurred when the AP fails to findthe DHCP server during AP boot. The fix ensures thatthe AP reboots with the correct subnet mask. Thisissue was observed in APs running Aruba Instant8.4.0.0 or later versions.


AOS-186317AOS-211873

— Clients were unable to connect to an Instant AP.Enhancements to the wireless driver resolved thisissue. This issue was observed in 210 Series and 220Series access points in a virtual controller role in anInstant cluster running Aruba Instant 8.3.0.0 or laterversions.


AOS-196842 — Clients connected to a mesh point AP failed toauthenticate to a WLAN guest network. This issueoccurred in cloud guest networks which wereconfigured with Anonymous authentication. The fixensures that clients can authenticate to cloud guestnetworks frommesh point APs. This issue wasobserved in Aruba Central managed AP-375 accesspoints running Aruba Instant 8.5.0.5 or later versions.


Table 4: Resolved Issues in Instant 8.8.0.0


16 | Resolved Issues Aruba Instant 8.8.0.0 | Release Notes


AOS-197400 — An AP failed to switch uplink interfaces during anuplink failover event. This issue occurred when the APwas configured with two Ethernet uplinks. The fixensures that the AP switches uplink interfaces duringuplink failover. This issue was observed in APs runningAruba Instant 8.6.0.1 or later versions.


AOS-198417AOS-209440

— An AP-387 access point reported highmemoryutilization. This issue occurred due to the large file sizeof a process log. The fix ensures that the size of theprocess log is regulated and the AP works as expected.This issue was observed in AP-387 access pointsrunning Aruba Instant 8.5.0.0 or later versions.


AOS-199744AOS-209046

— The output of show iap table long command did notdisplay any values for BID (Subnet Name) column,when the command was executed on the controller.This issue was observed in backup controllers when anInstant AP branch failed over from the primarycontroller in an IAP-VPN deployment. Upgrade thecontroller to ArubaOS 8.7.1.1 to resolve the issue. Thisissue was observed in IAP-VPN deployments that hadcontrollers running ArubaOS 8.3.0.0 or later versions.


AOS-200633 — Users were unable to view the Instant webUI inInternet Explorer browser. A Certificate Invalid errormessage was displayed. The fix ensures that theInstant WebUI works as expected in Internet Explorer.This issue was observed in APs running Aruba Instant8.6.0.5 or later versions.


AOS-200816AOS-210175AOS-210892

— Clients were unable to connect to Instant APs due toover utilization of memory. The fix ensures that theOut of Memory issue is resolved. This issue wasobserved in AP-305, AP-315, and AP-365 access pointsrunning Aruba Instant 8.6.0.2 or later versions.


AOS-205319AOS-216577AOS-218524

— Some AP-535 and AP-555 access point crashed andrebooted unexpectedly. The log file listed the reasonfor reboot as: Fatal exception in interrupt. This fixensures that the AP functions as expected. This issuewas observed in AP-535 and AP-555 access pointsrunning Aruba Instant 8.6.0.6 or later versions.


AOS-205389 — A few APs in an Instant cluster intermittently reportedconfig checksum errors and failed to syncconfigurations with the conductor AP. The fix ensuresthat member APs sync configurations from theconductor AP without any checksum errors. This issueoccurred in AirWave managed Instant networks. Thisissue was observed in APs running Aruba Instant8.5.0.7 or later versions.



Aruba Instant 8.8.0.0 | Release Notes Resolved Issues | 17


AOS-205932 — Some client devices were disconnected from thenetwork when roaming from one AP to another. Thisissue occurred when broadcast andmulticast trafficfor clients were blocked due to Group Transient Key(GTK) sync failure between the neighboring APs. Thefix ensures that APs sync GTK successfully and clientscan roam without any interruption in connection. Thisissue was observed in 802.11r enabled APs runningAruba Instant 8.4.0.2 or later versions.


AOS-206840 — The checksum ID and radio information of an AP werenot updated on the Virtual Controller. This issueoccurred in APs that are configured with a staticchannel. The fix ensures that the AP updateschecksum ID and radio information on the VirtualController. This issue was observed in 300 Series, AP-315, 320 Series, 330 Series, 360 Series, and 370 Seriesaccess points running Aruba Instant 8.4.0.6 or laterversions.


AOS-207070 — Clients were unable to authenticate into the networkusing captive portal authentication when it wasconfigured with an external RADIUS server. This issueoccurred when the duration of TCP handshake processwith the RADIUS server exceeded 400ms due to WANissues. The fix ensures that clients can connect tonetworks using captive portal authenticationconfigured with an external RADIUS server asexpected. This issue was observed in APs runningAruba Instant 8.5.0.0 or later versions.


AOS-207415 — The access request of some clients were rejected bythe RADIUS server. This issue occurred when theaccess request sent from the AP to the RADIUS serverwas missing the State attribute. The fix ensures thatclients can authenticate with the RADIUS server asexpected. This issue was observed in APs runningAruba Instant 8.4.0.0 or later versions.


AOS-207599AOS-207665

— The local WebUI for some APs displayed the errormessage: ERR_SSL_SERVER_CERT_BAD_FORMAT.This issue occurred when the web browser used toaccess the local WebUI was Google Chrome, MicrosoftEdge 79 and later versions, or Apple Safari. The fixensures that the local webUI of the AP works asexpected. This issue was observed in APs that wererebooted in the factory default state after upgrading toAruba Instant 8.7.0.0.





AOS-207602 — An Instant AP failed to complete 802.1X authenticationwhen Validate server option was selected in theConfiguration > System > Show advancedoptions> Uplink > AP1X section in the webUI. Thedebug log lists the reason for failure as: Servervalidation failed. The fix ensures that the APcompletes 802.1X authentication and works asexpected. This issue was observed in 200 Seriesaccess points running Aruba Instant 8.6.0.4 or laterversions.


AOS-207781AOS-210105AOS-211820

— An Instant AP learned wrong IP addresses for certaindomain names. The fix ensures that the AP learns thecorrect IP address. This issue was observed in APsrunning Aruba Instant 8.5.0.0 or later versions.


AOS-207893 — Clients were unable to get an IP address. This occurreddue to highmemory utilization in the AP caused by theBLE daemon process. The fix ensures that memoryutilization in the AP is regulated by the creation of anew boot log file at every restart instance of the BLEdaemon process. This issue was observed in APsrunning Aruba Instant 8.5.0.3 or later versions.


AOS-208330 — AirWave reported incorrect client data transfer speedsin the RF dashboard. The fix ensures that AirWavereports the correct data transfer speeds in the RFdashboard. This issue was observed in AirWavemanaged APs running Aruba Instant 8.6.0.2 or laterversions.


AOS-208474 — An Instant AP disconnected itself from the cluster andthen rejoined it. The log file lists the reason for theevent as: stm | PAPI_Send failed, send_papi_message_with_args, 1215: Resource temporarilyunavailable. The fix ensures that the AP staysconnected to the cluster. This issue was observed inAPs running Aruba Instant 8.6.0.5 or later versions.


AOS-208648 — The system log of an Instant AP randomly registered alot of Swarm quit factory default status by : ssid_configmessages. The fix ensures that the syslog ofthe AP does not generate randommessages. Thisissue was observed in APs running Aruba Instant8.7.0.0 or later versions.


AOS-208681 — The Instant webUI gets stuck on the uploading screenduring firmware upgrade. This issue occurred whenInternet Explorer was used to access the webUI. Thefix ensures that the Instant webUI works as expectedwhen accessed using Internet Explorer. This issue wasobserved in access points running Aruba Instant8.6.0.5 or later versions.





AOS-208783 — Some GUI elements in the new webUI were not visiblewhen accessed using Internet Explorer. This issueoccurred when the system used to access the webUIhad the font download option disabled in the firewallsettings. The fix ensures that the new webUI isrendered as expected. This issue was observed in APsrunning Aruba Instant 8.6.0.0 or later versions.


AOS-209148 — Clients were unable to reach the splash page forcaptive portal authentication. This issue occurredwhen the AP failed to process DNS queries fromcaptive portal clients. The fix ensures that clients jointhe captive portal network as expected. This issue wasobserved in Aruba Instant 8.6.0.0 or later versions.


AOS-209239 — An Instant AP operating as a DHCP server failed toserve IP addresses to clients connected to it. This issueoccurred when the subnet for the DHCP scope was thesame as the IP address of the AP. This fix ensures thatthe AP serves IP addresses to clients connected to it.This issue was observed in APs running Aruba Instant8.3.0.0 or later versions.


AOS-209306 — Clients were either unable to connect to the AP orwere getting disconnected from it. This issue occurredwhen the SAPD process over utilized CPU memory.The fix ensures that the memory usage of SAPDprocess is regulated and clients connect to the accesspoint as expected. This issue was observed in AP-324access points running Aruba Instant 8.4.0.0 or laterversions.


AOS-209855AOS-210214AOS-211809AOS-212590AOS-212823AOS-214704

Some Instant APs crashed and rebooted unexpectedly.The log file listed the reason for the event as: Kernelpanic - not syncing: Fatal exception in interrupt.The fix ensures that the APs work as expected. Thisissue was observed in APs running Aruba Instant8.7.0.0 or later versions.


AOS-210059 — An Instant AP failed to install CA certificate for 802.1Xauthentication. The AP displayed the error message:Validate certificate file failed. The fix ensures thatCA certificate is installed on the AP as expected. Thisissue was observed in APs running Aruba Instant8.5.0.9 or later versions.


AOS-210095 — The Instant AP logs were flooded with awc: wsc:callback_centralmessages. These logs were reportedby the SAPD module of the AP, when it processedmessages for Central. The fix ensures that the SAPDmodule does not process Central messages. This issueis observed in Aruba Central-managed APs runningAruba Instant 8.5.0.10 or later versions.





AOS-210141 — An Instant AP sent RADIUS accounting messages withincorrect IP information. This issue occurred when theclient moved from one user role to another afterconnecting to the network and the SSID had EnforceDHCP enabled. The fix ensures that the AP sends thecorrect IP information in RADIUS accounting messageswhen Enforce DHCP is enabled on the SSID. This issuewas observed in APs running Aruba Instant 8.6.0.2 orlater versions.


AOS-210224 — Twomember APs in a cluster were broadcasting onthe same channel when other free channels wereavailable. The fix ensures that the member APsbroadcast on different channels to optimize bandwidthusage. This issue was observed in APs running ArubaInstant 8.5.0.6 or later versions.


AOS-210290 — An Instant AP failed to update the service ID ofAirGroup services when the service ID was configuredthrough the Instant WebUI and Central. This issueoccured when the name of the service ID contains a "."character. This issue was observed in APs runningAruba Instant 8.7.0.0 or later versions.


AOS-210338 — Instant APs scanned by Qualys server reportedQID:11827 indicating that theInstant AP HTTP POSToperationmissed one or more headers. The fixensures that the headers are included in theHTTP POST operation. This issue was observed inAruba Instant 8.6.0.2 or later versions.


AOS-210440 — Administrator authentication failed when accessingthe Instant AP through the WebUI. This issue occuredwhen the administrator password included specialcharacters such as " or '. This issue was observed inAPs running Aruba Instant 8.6.0.5 or later versions.


AOS-210717AOS-212956

— The Client-view heatmap window inDashboard >Clients page of the Instant WebUI did not display anydata. This issue occurred when the number of clientmatch history record exceeds 300. This issue wasobserved in APs running Aruba Instant 8.7.0.0 or laterversions.


AOS-210855AOS-213801

— The conductor AP in an Instant cluster randomlyencountered a CLI core crash and reset the Age forAPs in the output of show aps command. The fixensures that the AP works as expected. This issue wasobserved in APs running Aruba Instant 8.5.0.0 or laterversions.





AOS-210903 — Clients were getting de-authenticated from Instant APswith a message:No reason available. The fix ensuresthat the clients do not get de-authenticated from theAP without reason. This issue was observed in AP-535access points running Aruba Instant 8.7.0.0 or laterversions.


AOS-211394 — An Instant AP dropped clients and did not allow newclients to join the network. During this period the APreported a highmemory usage warning in ArubaCentral. This issue occurred when ARP Poison Checkand Deny Intra VLAN Traffic was enabled in the AP.The fix ensures that the AP works as expected. Thisissue was observed in Aruba Central managed InstantAPs running Aruba Instant 8.6.0.6 or later versions.


AOS-211407 — Clients connected to an Instant AP were unable to sendand receive traffic. This issue was observed innetworks configured with Deny intra VLAN traffic andthe client IP assignment was set to Virtual Controllermanaged. This issue occurred after a conductor APfailover event in the Instant cluster. The fix ensuresthat clients can send and receive traffic in Instant APclusters as expected. This issue was observed in APsrunning Aruba Instant 8.6.0.4 or later versions.


AOS-211525AOS-212652

— An Instant AP inherits the gateway IP of the layer 2switch in the event of a switch outage and causes an IPaddress conflict when the switch is back online. The fixensures that the AP does not inherit the gateway IP ofthe layer 2 switch in the event of a switch outage. Thisissue was observed in APs running Aruba Instant8.5.0.5 or later versions.


AOS-211828AOS-222011

— Clients were unable to associate to Instant APs and thereason reported in Aruba Central was: AP is resourceconstrained. This issue occurred when Client Matchsteered the client from one radio band to another.During band steering, all radios except the target radiodeny the client's association request. This wasreported as a AP is resource constrained event inAruba Central. The fix ensures that the reason to denyclient's association request because of Client Match islogged as a Client Match event. This issue wasobserved in Aruba Central-managed APs runningAruba Instant 8.5.0.0 or later versions.


AOS-211665 — An Instant AP was unable to connect to Central using aproxy server. The output of the show ap debugcloud-server command listed the reason as HTTPSproxy error. This issue occurred when FreeProxy wasused as the proxy server. The fix ensures that theInstant AP is able to connect to Aruba Central using aproxy server. This issue was observed in APs runningAruba Instant 8.5.0.7 or later versions.





AOS-212238 — An Instant AP failed to update device-owner andshared-user-list attributes sent from the ClearPassPolicy Manager server in the AirGroup CPPM entriestable. The fix ensures that the device owner, shared-user-list, and other shared attributes are displayed inthe table.This issue was observed in APs runningAruba Instant 8.7.0.0 or later versions.


AOS-213257 — An Instant AP failed to remove the domain name suffixwhen logging username entries in the AirGroup userstable. The fix ensures that the AP logs the usernameentry in the AirGroup table as expected. This issueoccurred when Enforce ClearPass registration wasenabled in the Configuration > Services > AirGroupsection of the WebUI. This issue was observed in APsrunning Aruba Instant 8.3.0.0 or later versions


AOS-213941AOS-215575

— An Instant AP stopped broadcasting and rebootedunexpectedly. The log file lists the reason for rebootas: Reboot due to trigger the cooldown event. Thefix ensures that the AP is able to pass traffic even atsub-zero temperatures. This issue is observed in APsrunning Aruba Instant 8.7.1.0 or later versions.


AOS-214199 — An Instant AP failed to establish an SSL connection withOpenDNS servers. This issue occurred due toincompatibility with the content-header message sentby the OpenDNS server. The fix ensures that the SSLconnection is successfully established with theOpenDNS server. This issue was observed in APsrunning Aruba Instant 8.5.0.11 or later versions.


AOS-214595 — Instant APs failed to respond to the ArubaPhyTypeand ArubaHTModeMIB queries. This issue is resolvedby:

n Redefining the ArubaHTMode and ArubaPhyTypelabels and adding newmib OIDs aiClientPhyType andaiClientHtMode in the Instant AP MIB.

n Redefining the labels SiemensHTMode andSiemensPhyType and adding newMIB OIDssieClientPhyType and sieClientHtMode in theSiemens MIB.

This issue was observed in Instant APs running ArubaInstant 8.6.0.6 or later versions.


AOS-215475 — The uplink preemption feature did not work on AP-203R. This issue occurred as the Eth0 port status wasnot updated. The fix ensures that the uplinkpreemption feature works as expected. This issue wasobserved in APs running Aruba Instant 8.6.0.0 or laterversions.





AOS-215577 — The 5 GHz secondary radio status was incorrectlyshown as disabled on Aruba Central. This issueoccurred when tri-radio was configured on a memberAP in a cluster managed by Central. The fix ensuresthat all radio statuses are displayed corrected inCentral. This issue was observed in AP-555 accesspoints running Aruba Instant 8.7.1.0 or later versions.


AOS-216194 — Modifications to the ESSID name of an AP throughAruba Central were not reflecting in the Instant webUIunder Networks. The fix ensures that the changesmade on Aruba Central to the ESSID name aredisplayed correctly in the Instant webUI. This issue wasobserved in APs running Aruba Instant 8.6.0.0 or laterversions.


AOS-216793AOS-217849

— An AP crashed and rebooted unexpectedly. The log filelisted the reason for reboot as: Critical process/aruba/bin/stm [pid 26982] DIED, process markedas RESTART. This fix ensures that the AP functions asexpected. This issue was observed in APs runningAruba Instant 8.6.0.0 or later versions.


AOS-216834 — Clients were unable to connect to some APs due totheir high memory usage. This issue occured whenDHCP or DNS events were subscribed and changes tothe clarify configuration increased the process runtime. The fix ensures that the clients are able toconnect to the APs without issues. This issue wasobserved in APs running Aruba Instant 8.6.0.7 or laterversions.



Chapter 6Known Issues and Limitations

Known Issues and LimitationsThis chapter describes the known issues and limitations observed in this release.

LimitationsThis section describes the limitations in Aruba Instant 8.8.0.0.

AP Hostname Character Limit ExtensionThe number of ASCII characters allowed in the Instant AP hostname is increased from 32 to 128 characters.The following configuration settings do not support the new limit of 128 ASCII characters in Instant 8.8.0.0:

n The AP Name field in Role Derivation or VLAN Derivation.

n The AP Name field in beacon and probe response frames.

n The AP Name field in the show ap mesh link and ap mesh neighbor commands.

Dynamic Multicast Optimization Unsupported with VLAN DerivationAruba Instant does not support DynamicMulticast Optimization when the SSID is configured withVLAN derivation.

Inbound FirewallThe apip-all configuration is not supported by the inbound-firewall command in Instant AP clusterdeployments. It is only supported in standalone or single-AP modes of deployment.

Uplink Failover LimitationUplink failover or pre-emption between eth0 andWi-Fi uplink is currently not supported.

Unified Communications ManagerUCM does not prioritize NAT traffic.

Known IssuesFollowing are the known issues observed in this release.

Bug ID Description ReportedVersion

AOS-203279 An AP-565 access point crashes and fails to reboot when softwareversion prior to Aruba Instant 8.7.1.0 is installed. This issue is observedin AP-565 access points running Aruba Instant 8.7.1.0 or later versions.


Table 5: Known Issues in Instant 8.8.0.0


25 | Known Issues and Limitations Aruba Instant 8.8.0.0 | Release Notes

Bug ID Description ReportedVersion

AOS-203311 An AP-565 access point reboots and disables FIPS mode. This issue isobserved in AP-565 access points running Aruba Instant 8.7.1.0 or laterversions.


AOS-208450 An AP-503H access point operating as a mesh point sends incorrectsource MAC address in LLDP messages. This issue is observed in AP-503H access points running Aruba Instant 8.7.1.0 or later versions.


AOS-209405AOS-212894AOS-213220AOS-214438

An Instant AP fails to block certain application and service traffic despitehaving ACLs configured to block them. This issue occurs withapplications and services that use QUIC protocol, which is currently notsupported by AppRF. This issue is observed in APs running Aruba Instant8.3.0.0 or later versions.

Workaround: Add an ACL rule to deny traffic in UDP ports 443 and 80.This configures the AP to deny traffic when the ACL is applied and forcesthe application to use TLS instead of QUIC protocol.


AOS-214157 Whenmultiple DL3 clients with the same host name connect to thesame AP, the AP updates the IP address of the most recently connectedclient. This issue is observed in networks configured with public DDNS.This issue is observed in APs running Aruba Instant 8.8.0.0.


AOS-214948 Some mesh APs display incorrect mesh link information in the output ofshow ap mesh link command. This issue is observed in APs runningAruba Instant 8.7.1.0 or later versions.


AOS-215513 An Instant AP fails to resolve DNS when the following configurations areapplied:n Uplink VLAN configured is not 1.n Primary VPN is configured and the default gateway is the IPSec

tunnel.This issue is observed in APs running Aruba Instant 8.8.0.0.


AOS-218747 The Instant AP database in the controller is not populated with DL3entries. This issue occurs when an apostrophe (‘) character is used inthe Instant AP branch name. This issue is observed in APs running ArubaInstant 8.6.0.9 or later versions.


Table 5: Known Issues in Instant 8.8.0.0

Chapter 7Upgrading an Instant AP

Upgrading an Instant APThis chapter describes the Instant software upgrade procedures and the different methods for upgradingthe image on the Instant AP.

While upgrading anInstant AP, you can use the image check feature to allow the Instant AP to find new softwareimage versions available on a cloud-based image server hosted andmaintained by Aruba. The location of theimage server is fixed and cannot be changed by the user. The image server is loaded with the latest versions ofthe Instant software.

Topics in this chapter include:

n Upgrading an Instant AP and Image Server on page 26n Upgrading an Instant AP Using the Automatic Image Check on page 28n Upgrading to a New VersionManually Using theWebUIn Upgrading an Instant AP ImageUsing CLI on page 31n Upgrade from Instant 6.4.x.x-4.2.x.x to Instant 8.8.0.x on page 32

Upgrading an Instant AP and Image ServerInstant supportsmixed Instant AP class Instant deployment with all Instant APs as part of the same virtualcontroller cluster.

Image Management Using AirWaveIf themulti-class Instant AP network ismanaged by AirWave, image upgrades can only be done through theAirWaveWebUI. The Instant AP images for different classesmust be uploaded on the AMP server. If newInstant APs joining the network need to synchronize their softwarewith the version running on the virtualcontroller, and if the new Instant AP belongs to a different class, the image file for the new Instant AP isprovided by AirWave. If AirWave does not have the appropriate image file, the new Instant AP will not beable to join the network.

The virtual controller communicates with the AirWave server if AirWave is configured. If AirWave is not configuredon the Instant AP, the image is requested from the Image server.

Image Management Using Cloud ServerIf themulti-class Instant AP network is not managed by AirWave, image upgrades can be done through theCloud-Based Image Check feature. If a new Instant AP joining the network needs to synchronize its softwareversion with the version on the virtual controller and if the new Instant AP belongs to a different class, theimage file for the new Instant AP is provided by the cloud server.

Configuring HTTP Proxy on an Instant APIf your network requires a proxy server for Internet access, ensure that you configure theHTTP proxy on theInstant AP to download the image from the cloud server. TheUsername and Password configuration is


27 | Upgrading an Instant AP Aruba Instant 8.8.0.0 | Release Notes

supported only for cloud services. After setting up theHTTP proxy settings, the Instant AP connects to theActivate server, AMP, Central, OpenDNS, or web content classification server through a secure HTTPconnection. The proxy server can also be configured and used for cloud services. You can also exemptcertain applications fromusing theHTTP proxy (configured on an Instant AP) by providing their host nameor IP address under exceptions.

In the Old WebUITo configure theHTTP proxy settings:

1. Navigate to System > Proxy. The Proxy configuration window is displayed.2. Enter theHTTP proxy server IP address in the Server text box.3. Enter the port number in the Port text box.4. If you want to set an authentication username and password for the proxy server, select the Proxy

requires authentication checkbox.5. Enter a username in theUsername text box.6. Enter a password in the Password text box.7. If you do not want theHTTP proxy to be applied for a particular host, clickNew to enter that IP

address or domain name of that host in the Exceptions section.

In the New WebUITo configure theHTTP proxy settings:

1. Navigate to Configuration > System > Proxy.2. Enter theHTTP proxy server IP address in theAuth Server text box.3. Enter the port number in the Port text box.4. If you want to set an authentication username and password for the proxy server, enable the Proxy

requires authentication toggle switch.5. Enter a username in theUsername text box.6. Enter a password in the Password text box.7. If you do not want theHTTP proxy to be applied for a particular host, click + to enter that IP address

or domain name of that host in the Exceptions section.8. Click Save.

In the CLITo configure theHTTP proxy settings:

(Instant AP)(config)# proxy server 192.0.2.1 8080 example1 user123(Instant AP)(config)# proxy exception 192.0.2.2(Instant AP)(config)# end(Instant AP)# commit apply

HTTP Proxy Support through Zero Touch ProvisioningInstant APs experience issues when connecting to AirWave, Central, or Activate through theHTTP proxyserver which requires a user name and password. The ideal way to provide seamless connectivity for thesecloud platforms is to supply the proxy information to the Instant AP through aDHCP server.

Starting with Aruba Instant 8.4.0.0, besides being able to authenticate to theHTTP proxy server, the factorydefault Instant APs can also communicatewith the server through aHTTP proxy server DHCP which doesnot require authentication.

Aruba Instant 8.8.0.0 | Release Notes Upgrading an Instant AP | 28

In order for the factory default Instant AP to automatically discover the proxy server, you need to configuretheHTTP proxy information in theDHCP server option. The Instant AP will receive the proxy informationand store it in a temporary file.

To retrieve the port and the proxy server information, you need to first configure theDHCP option 60 toArubaInstantAP as shown below:

(Instant AP)(config)# ip dhcp <profile_name>(Instant AP)("IP DHCP profile-name")# option 60 ArubaInstantAP

Secondly, use the following command to configure the proxy server:

(Instant AP)(config)# proxy server <host> <port> [<username> <password>]

Use the text string option 148 text server=host_ip,port=PORT,username=USERNAME,password=PASSWORD to retrieve the details of the proxy server.

Rolling Upgrade on Instant APs with AirWaveStarting fromAruba Instant 8.4.0.0, Rolling Upgrade for Instant APs in standalonemode is supported withAirWave. The upgrade is orchestrated through NMS and allows the Instant APs deployed in standalonemode to be sequentially upgraded such that the APs upgrade and reboot one at a time. With RollingUpgrade, the impact of upgrading a site is reduced to a single AP at any given point in time. This enhancesthe overall availability of thewireless network. Formore information, see AirWave 8.2.8.2 Instant DeploymentGuide and AirWave 8.2.8.2 Release Notes.

Upgrading an Instant AP Using the Automatic Image CheckYou can upgrade an Instant AP by using the Automatic Image Check feature. The automatic image checksare performed once, as soon as the Instant AP boots up and every week thereafter.

If the image check locates a new version of the Instant software on the image server, theNew versionavailable link is displayed on the Instant main window.

If AirWave is configured, the automatic image check is disabled.

In the Old WebUITo check for a new version on the image server in the cloud:

1. Go toMaintenance > Firmware.2. In theAutomatic section, click Check for New Version. After the image check is completed, one of

the followingmessages is displayed:n No new version available—If there is no new version available.n Image server timed out—Connection or session between the image server and the Instant AP is

timed out.n Image server failure—If the image server does not respond.n A new image version found—If a new image version is found.

3. If a new version is found, theUpgrade Now button becomes available and the version number is


displayed.4. Click Upgrade Now.

The Instant AP downloads the image from the server, saves it to flash, and reboots. Depending on theprogress and success of the upgrade, one of the followingmessages is displayed:

n Upgrading—While image upgrading is in progress.n Upgrade successful—When the upgrade is successful.n Upgrade failed—When the upgrade fails.

If the upgrade fails and an errormessage is displayed, retry upgrading the Instant AP.

In the New WebUITo check for a new version on the image server in the cloud:

1. Go toMaintenance > Firmware.2. In theAutomatic section, click Check for New Version. After the image check is completed, one of

the followingmessages is displayed:n No new version available—If there is no new version available.n Image server timed out—Connection or session between the image server and the Instant AP is

timed out.n Image server failure—If the image server does not respond.n A new image version found—If a new image version is found.

3. If a new version is found, theUpgrade Now button becomes available and the version number isdisplayed.

4. Click Upgrade Now.

The Instant AP downloads the image from the server, saves it to flash, and reboots. Depending on theprogress and success of the upgrade, one of the followingmessages is displayed:

n Upgrading—While image upgrading is in progress.n Upgrade successful—When the upgrade is successful.n Upgrade failed—When the upgrade fails.

If the upgrade fails and an errormessage is displayed, retry upgrading the Instant AP.

Upgrading to a New Version Manually Using the WebUIIf the Automatic Image Check feature is disabled, you canmanually obtain an image file from a local filesystemor from a remote server accessed using a TFTP, FTP or HTTP URL.

In the Old WebUITomanually check for a new firmware image version and obtain an image file:

1. Navigate toMaintenance > Firmware.2. UnderManual section, perform the following steps:

a. Select the Image file option. Thismethod is only available for single-class Instant APs. Thefollowing table describes the supported image file format for different Instant APmodels:


Access Points Image File Format

AP-344, AP-345, AP-514, AP-515, AP-518, AP-574, AP-575, AP-575EX, AP-577, and AP-577EX

ArubaInstant_Draco_8.8.0.x_xxxx

AP-503H, AP-504, AP-505, AP-505H, AP-565, andAP-567.

ArubaInstant_Gemini_8.8.0.x_xxxx

IAP-314, IAP-315, IAP-324, IAP-325, AP-374, AP-375, AP-377, AP-318, and AP-387

ArubaInstant_Hercules_8.8.0.x_xxxx

IAP-334 and IAP-335 ArubaInstant_Lupus_8.8.0.x_xxxx

AP-534, AP-535, and AP-555 ArubaInstant_Scorpio_8.8.0.x_xxxx

AP-303, AP-303H, 303P Series, IAP-304, IAP-305,AP-365, and AP-367

ArubaInstant_Ursa_8.8.0.x_xxxx

AP-203H, AP-203R, AP-203RP, and IAP-207 ArubaInstant_Vela_8.8.0.x_xxxx

b. Select the Image URL option. Select this option to obtain an image file from aHTTP, TFTP, or FTPURL.n HTTP - http://<IP-address>/<image-file>. For example, http://<IP-address>/ArubaInstant_

Hercules_8.8.0.x_xxxxn TFTP - tftp://<IP-address>/<image-file>. For example, tftp://<IP-address>/ArubaInstant_

Hercules_8.8.0.x_xxxxn FTP - ftp://<IP-address>/<image-file>. For example, ftp://<IP-address>/ArubaInstant_

Hercules_8.8.0.x_xxxxn FTP - ftp://<user name:password>@<IP-address>/<image-file>. For example,

ftp://<aruba:123456>@<IP-address>/ArubaInstant_Hercules_8.8.0.x_xxxx

The FTP server supports both anonymous and username:password login methods.

Multiclass Instant APs can be upgraded only in the URL format, not in the local image fileformat.

3. Clear theReboot all APs after upgrade check box if required. This check box is selected by defaultto allow the Instant APs to reboot automatically after a successful upgrade. To reboot the Instant APat a later time, clear theReboot all APs after upgrade check box.

4. Click Upgrade Now to upgrade the Instant AP to the newer version.

In the New WebUI (Instant 8.4.0.0 or later versions)Tomanually check for a new firmware image version and obtain an image file:

1. Navigate toMaintenance > Firmware.2. UnderManual section, perform the following steps:

a. Select the Image file option. Thismethod is only available for single-class Instant APs. Thefollowing table describes the supported image file format for different Instant APmodels:


Access Points Image File Format

AP-344, AP-345, AP-514, AP-515, AP-518, AP-574, AP-575,AP-575EX, AP-577, and AP-577EX

ArubaInstant_Draco_8.8.0.x_xxxx

AP-503H, AP-504, AP-505, AP-505H, AP-565, and AP-567.

ArubaInstant_Gemini_8.8.0.x_xxxx

IAP-314, IAP-315, IAP-324, IAP-325, AP-374, AP-375, AP-377,AP-318, and AP-387

ArubaInstant_Hercules_8.8.0.x_xxxx

IAP-334 and IAP-335 ArubaInstant_Lupus_8.8.0.x_xxxx

AP-534, AP-535, and AP-555 ArubaInstant_Scorpio_8.8.0.x_xxxx

AP-303, AP-303H, 303P Series,IAP-304, IAP-305, AP-365, andAP-367

ArubaInstant_Ursa_8.8.0.x_xxxx

AP-203H, AP-203R, AP-203RP,and IAP-207

ArubaInstant_Vela_8.8.0.x_xxxx

b. Select the Image URL option. Select this option to obtain an image file from aHTTP, TFTP, orFTP URL.n HTTP - http://<IP-address>/<image-file>. For example, http://<IP-address>/ArubaInstant_

Hercules_8.8.0.x_xxxxn TFTP - tftp://<IP-address>/<image-file>. For example, tftp://<IP-address>/ArubaInstant_

Hercules_8.8.0.x_xxxxn FTP - ftp://<IP-address>/<image-file>. For example, ftp://<IP-address>/ArubaInstant_

Hercules_8.8.0.x_xxxxn FTP - ftp://<user name:password>@<IP-address>/<image-file>. For example,

ftp://<aruba:123456>@<IP-address>/ArubaInstant_Hercules_8.8.0.x_xxxx

The FTP server supports both anonymous and username:password login methods.

Multiclass Instant APs can be upgraded only in the URL format, not in the local image fileformat.

3. Disable theReboot all APs after upgrade toggle switch if required. This option is enabled bydefault to allow the Instant APs to reboot automatically after a successful upgrade. To reboot theInstant AP at a later time, clear theReboot all APs after upgrade check box.

4. Click Upgrade Now to upgrade the Instant AP to the newer version.5. Click Save.

Upgrading an Instant AP Image Using CLI


To upgrade an image using a HTTP, TFTP, or FTP URL:

(Instant AP)# upgrade-image <ftp/tftp/http-URL>

The following is an example to upgrade an image by using the FTP URL :

(Instant AP)# upgrade-image ftp://192.0.2.7/ArubaInstant_Hercules_8.8.0.x_xxxx

To upgrade an imagewithout rebooting the Instant AP:

(Instant AP)# upgrade-image2-no-reboot <ftp/tftp/http-URL>

The following is an example to upgrade an imagewithout rebooting the Instant AP:

(Instant AP)# upgrade-image2-no-reboot ftp://192.0.2.7/ArubaInstant_Hercules_8.8.0.x_xxxx

To view the upgrade information:

(Instant AP)# show upgrade infoImage Upgrade Progress----------------------Mac IP Address AP Class Status Image Info Error Detail--- --------- -------- ------ ---------- ------------d8:c7:c8:c4:42:98 10.17.101.1 Hercules image-ok image file noneAuto reboot :enableUse external URL :disable

Upgrade from Instant 6.4.x.x-4.2.x.x to Instant 8.8.0.xBefore you upgrade an Instant AP running Instant 6.5.4.0 or earlier versions to Instant 8.8.0.x, follow theproceduresmentioned below:

1. Upgrade from Instant 6.4.x.x-4.2.x.x or any version prior to Instant 6.5.4.0 to Instant 6.5.4.0.2. Refer to the Field Bulletin AP1804-1 at support.arubanetworks.com.3. Verify the affected serial numbers of the Instant AP units.

http://support.arubanetworks.com/Documentation/tabid/77/DMXModule/512/Command/Core_Download/Method/attachment/Default.aspx?EntryId=29756

Date post:	11-Nov-2021
Category:	Documents
Upload:	others
View:	18 times
Download:	0 times