Table of Contents
Advertisement
Activate and is provisioned as an IAP > Remote AP, Activate responds with mobility controller IP address, IAP
group, and IAP type. The IAP then contacts the controller, establishes certificate-based secure
communication, and obtains configuration and image from the controller. The IAP reboots and comes up as
a Remote AP. The IAP then establishes an IPsec connection with the controller and begins operating in the
Remote AP mode.
If an IAP entry is present in Activate and a provisioning rule is configured to return the IP address or host
l
name of the AirWave server, the IAP downloads configuration from AirWave and operates in the IAP mode.
If there is no response from Activate, the access point comes up with default configuration and operates in
l
the IAP mode.
A mesh point cannot be converted to Remote AP, because mesh access points do not support VPN
connection.
An IAP can be converted to a Campus AP and Remote AP only if the controller is running ArubaOS 6.1.4 or later
versions:
The following table describes the supported IAP platforms and minimal ArubaOS version required for the
Campus AP or Remote AP conversion.
Table 76: IAP Platforms and Minimum ArubaOS Versions for IAP-to-Remote AP Conversion
IAP Platform
IAP-314/315
IAP-334/335
IAP-324/325
IAP-205H
IAP-228
IAP-277
IAP-214/215
IAP-204/205
IAP-274/275
IAP-103
IAP-114/115
355
| IAP Maintenance
ArubaOS Release
ArubaOS 6.5.0.0 or later
versions
ArubaOS 6.4.4.0 or later
versions
ArubaOS 6.4.3.1 or later
versions
ArubaOS 6.4.2.0 or later
versions
ArubaOS 6.4.1.0 or later
versions
ArubaOS 6.4 or later versions
ArubaOS 6.4 or later versions
ArubaOS 6.3.1.1 or later
versions
Instant Release
Instant 4.3.0 or later versions
Instant 4.2.2 or later versions
Instant 4.2 or later versions
Instant 4.1.1 or later versions
Instant 4.1.1 or later versions
Instant 4.1 or later versions
Instant 4.1 or later versions
Instant 4.0 or later versions
Aruba Instant 6.5.0.0-4.3.0.0 | User Guide
Hide quick links:
Advertisement
Table of Contents
