An IAP can be provisioned as a Campus AP (CAP) or Remote AP (RAP) in a controller-based network.
Before converting the IAP, ensure that both the IAP and controller are configured to operate in the same regulatory domain.
Converting an IAP to RAP Mode
For RAP conversion, the Virtual Controller sends the RAP convert command to all the other IAPs. The Virtual Controller along with the other slave IAPs then setup a VPN tunnel to the remote controller, and download the firmware by FTP. The Virtual Controller uses IPsec to communicate to the Mobility Controller over the internet.
If the IAP gets AirWave information via DHCP (Option 43 and Option 60), it establishes an HTTPS connection to the AirWave server and downloads the configuration and operates in IAP mode.
If the IAP does not get AirWave information via DHCP provisioning, it tries provisioning via a firmware image server in the cloud (sends serial number MAC address). If an entry for the IAP is present in the firmware image cloud server and is provisioned as an IAP > RAP entry, the firmware image cloud server responds with controller IP address, AP group, and AP type. The IAP then contacts the controller, establishes certificate-based secure communication, and gets configuration and image from the
controller. The IAP then reboots and comes up as a RAP. The IAP then establishes an IPSEC connection with the controller and begins operating in RAP mode.
If an IAP entry for the AP is present in the firmware image cloud server, the IAP gets AirWave server information from the cloud server and downloads configuration from AirWave to operate in IAP mode.
If there is no response from the cloud server or AirWave, the IAP comes up in Aruba Instant mode.
An IAP can be converted to an Instant Campus AP and Instant Remote AP only if the controller is running Instant 6.1.4 or later.
The following table describes the supported IAP platforms and minimal AOS version for IAP to CAP/RAP conversion
Reboot the IAP after the bridging is set for the configuration to take effect.
A description of the firmware image cloud server can be found in the section named Firmware Image Server in Cloud Network, within this chapter.
A mesh point cannot be converted to RAP because mesh does not support VPN connection.
Table 13 IAP platforms and minimal AOS and IAP versions for IAP to RAP Conversion IAP Platform AOS Version Instant Version
IAP-92 6.1.4 or later 1.0 or later
IAP-93 6.1.4 or later 1.0 or later
To convert an IAP to RAP, follow the instructions below:
1. Navigate to the Maintenance tab in the top right corner of the Instant UI.
2. Click the Convert tab.
Figure 58 Maintenance — Convert Tab
IAP-104 6.1.4 or later 3.0 or later
IAP-105 6.1.4 or later 1.0 or later
IAP-134 6.1.4 or later 2.0 or later
IAP-135 6.1.4 or later 2.0 or later
IAP-175AC 6.1.4 or later 3.0 or later IAP-175P 6.1.4 or later 3.0 or later
RAP-3WN 6.1.4 or later 3.0 or later
RAP-3WNP 6.1.4 or later 3.0 or later
RAP-108 6.2.0.0 or later 3.2 or later RAP-109 6.2.0.0 or later 3.2 or later
Table 13 IAP platforms and minimal AOS and IAP versions for IAP to RAP Conversion IAP Platform AOS Version Instant Version
Instant 6.2.0.0-3.2 | User Guide Managing IAPs | 91
Figure 59 Convert options
3. Select Remote APs managed by a Mobility Controller from the drop-down list.
4. Enter the hostname (fully qualified domain name) or the IP address of the controller in the Hostname or IP Address of Mobility Controller text box. This information is provided by your network administrator.
5. Click Convert Now to complete the conversion.
Figure 60 Confirm Access Point Conversion
6. The IAP reboots and begins operating in RAP mode.
7. After conversion, the IAP is managed by the Aruba Mobility Controller which has been specified in the Instant UI.
Converting an IAP to CAP
To convert an IAP to Campus AP, do the following:
1. Navigate to the Maintenance tab in the top right corner of the Instant UI.
2. Click the Convert tab.
Ensure the Mobility Controller IP Address is reachable by the IAPs.
In order for the RAP conversion to work, ensure that you configure the Instant AP in the RAP white-list and enable the FTP service on the controller.
If the VPN setup fails and an error message pops up, please click OK, copy the error logs and share them with your Aruba support engineer.
Figure 61 Converting an IAP to CAP
3. Select Campus APs managed by a Mobility Controller from the drop-down list.
4. Enter the hostname (fully qualified domain name) or the IP address of the controller in the Hostname or IP Address of Mobility Controller text box. This is provided by your network administrator.
5. Click Convert Now to complete the conversion.
Converting an IAP to Standalone Mode
This feature allows you to deploy an Instant AP as an autonomous AP which is a separate entity from the existing Virtual Controller cluster in the same Layer 2 domain.
1. Navigate to the Maintenance tab in the top right corner of the Instant UI.
2. Click the Convert tab.
Figure 62 Standalone AP Conversion
3. Select Standalone AP from the drop-down list.
4. Select the Access Point from the drop-down list.
5. Click Convert Now to complete the conversion.
6. After the conversion the Access Point specified in the Instant UI operates in standalone mode.
Ensure the Mobility Controller IP Address is reachable by the IAPs.
Instant 6.2.0.0-3.2 | User Guide Managing IAPs | 93
Converting back to an IAP
The reset button located on the rear of an IAP can be used to reset the IAP to factory default settings. If you have converted your IAP to a campus AP or a Remote AP, pressing the reset button converts it back to an IAP.
To reset an IAP, follow the instructions below:
1. Power off the IAP.
2. Press and hold the reset button using a small, narrow object, such as a paperclip.
3. Power on the IAP without releasing the reset button. The power LED flashes within 5 seconds indicating that the reset is completed.
4. Release the reset button.
The IAP then boots with the factory default settings.