- Start Article
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
RAP local pool too small
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Alert a Moderator
09-04-2012 05:59 AM
Hi,
Our RAP Local pool is becoming too small.
We have 2 masters and 4 localcontrollers. When a RAP boots it will be directed to one of the locals. On all our controllers we have configured the same ip range for the localpool. We used a free subnet on our wired LAN for our pool.
Is it possible to change the range without problems with our active RAP's ? In that case the range will overlap with a subnet on our wired LAN, does this give routing problems? What will happen if I choose a totally different range which is not a part of our wired LAN.
THX.
Solved! Go to Solution.
Re: RAP local pool too small
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Alert a Moderator
09-04-2012 06:06 AM
You can choose an unroutable pool for your RAPs and everything will still work correctly... My personal favorite is 8.8.8.1 to 8.8.8.250.
Re: RAP local pool too small
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Alert a Moderator
09-04-2012 06:16 AM
What will happen then with our active RAP's , will they reboot and get the new Ip address? Or will they loose connection and need a power down before they will be back online again?
Re: RAP local pool too small
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Alert a Moderator
09-04-2012 09:42 AM
No. The current RAPs will stay up & continue using assigned ip-addresses till then rebootstrap. And new RAPs will get ip from new pool created.
Re: RAP local pool too small
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Alert a Moderator
09-09-2012 11:25 PM
THX.
I will make the change.





