Please be aware that the 1.1.3.x IP range is public assigned. You may see unpredictable connectivity issues.
Although the RAP pool is only used between the AP and controller, it means that AP and controller can't externally communicate with those IP addresses. It's better to use non-routable IP space, like 169.254.0.0/16 or 100.64.0.0/10; or allocate a block in your internal IP addressing plan. When changing, it may be a good moment to reconsider the IP address space.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------
Original Message:
Sent: Mar 27, 2026 07:16 AM
From: spann3rs
Subject: Aruba RAP IP Pool Increase
Hi All,
We're getting uncomfortably close to the default RAP IP address pool limits. What's the best way to increase this limit as there's no netmask for a conventional subnet?
IP addresses used in pool home-rap-pool
1.1.3.25-1.1.3.247
IPv4 pool : Total - 223 IPs used - 3 IPs free - 226 IPs configured
Should I simply change the range to 1.1.3.25-1.1.4.254? And what would be the implication for the current RAPs that're terminated and active?
Thanks in advance.
------------------------------
Jase
------------------------------