Upcoming community maintenance Oct. 27th through Oct. 29th
For more info click here

Remote Access Point

Not applicable

In the RAP

  • Detail of AP and functionality
  • Simple device can provide multiple wireless and wireless services for different branches of users
  • Can restrict forwarding via policy to the corporate, local LAN, or internet



In the Controller


Aruba Networks high-performance controllers are built specifically to scale ArubaOS software module capabilities for enterprise networks of all sizes. All Aruba controllers share a common hardware architecture that includes a dedicated control processor, a high-performance programmable network processor unit, and a unique programmable encryption engine. Controllers aggregate network traffic from APs, process it using Aruba software, and deliver it to the network.

The controller resides in the data center or the DMZ, depending on the network design. RAPs connect to the controller using secure tunnels. The data is transmitted from the remote locations to the enterprise LAN through these secure tunnels. After the controller receives the data, it processes it and routes the data into the core network. In other words, the controller is the “gateway to the enterprise LAN” for the remote users and devices connecting to the RAP.

VPN server: Included with the RAP software license, this feature provides VPN server functionality to communicate with RAP VPN clients. The Aruba controller must have VPN server functionality configured to terminate the secure RAPs. The configuration consists of authentication protocols, an address pool for RAPs, DNS information, shared secret for RAPs, and a policy governing the shared secret including priority, encryption, hash algorithm, authentication, group and life time.


Recommended Provisioning Steps for RAPs

  1. Disconnect the power
  2. Disconnect the Ethernet uplink (E0)
  3. Push and hold the reset button using a small object such as a paper clip
  4. Re-connect the power while holding the reset button
  5. Hold the reset button for 5-10 sec while RAP is powering up (The power/status LEDs will flash rapidly – then let go the reset button at that time)
  6. Wait a few seconds (a few minutes in case of RAP-2WG) for the RAP to boot
  7. Connect your PC to Port ‘eth1’ on the RAP
  8. Wait a few seconds for your PC to obtain an IP address from the RAP
  9. Open up your favorite browser and access rapconsole.arubanetworks.com if you don’t already see that page on your browser
  10. [Optional] Configure Advanced Settings (like Static IP, PPPoE, 3G/EVDO)
  11. Enter the ‘master’ details (IP Address/Hostname) and click on ‘Save’/’Continue’ [You’ll see the button as ‘Save’ if the uplink is not connected, or ‘Continue’ if the uplink is already connected]
  12. You can now connect the uplink (E0) or reboot and connect it at a later time/different place to complete the provisioning process


Rap and Data Compression

Our application acceleration product for RAP was dropped. Sorry...


Upgrading the backup-partition on version 5.x only

See How-to: Upgrade RAP backup flash

To upgrade the backup partition use the following command:

apflash ap-name backup-partition

or use the inner ip address of the RAP:

apflash ip-addr <ip address of ap> backup-partition


  • Remote AP capable with addition of ArubaOS RAP license
  • PEF is NOT needed at all for RAPs, only if you want to do split tunnel (policy based routing) or to secure user traffic coming through a RAP.

RAP and Large installed of 5000 or more

It's a question of dividing the APs properly across multiple controllers. May need more than one cluster of controllers, and multiple Airwave servers, to make it manageable.



The maximum number of supported RAP from the same NATed public address is 4.

Version history
Revision #:
3 of 3
Last update:
‎09-25-2014 01:18 PM
Updated by:
Search Airheads
Showing results for 
Search instead for 
Did you mean: