@Layer3 wrote:
1) Do you guys make your RAP pools any unused network that will not be encompassed by a routing table entry?
2) Do you make your RAP pools local to the controller and non routable?
to item 1, yes, in general you should avoid letting the rap pool reside within any connected subnet or route that exists within your controller routing table. These IPs are allocated in a point to point manner and generally when they overlap with other routes or subnets undesirable things can happen. Quite simply, you can allocate anyrange of IP addresses to it, especially if the controller is operating at layer 2, as the end user traffic will not be routed by the controller. Just don't overlap it with anything in the route table or connected subnets
to item 2, see Colins answer, with the added note that if you stick to the above, then you have achieved what you wrote for item 2. You can also re-use the pools between controllers, as only the controller cares about that IP address for mgmt traffic, any airwave info to do with "APs" comes from the controller and doesn't care about the APs inner IP.
As Colin also mentioned, there are caveats to the above, they are pretty rare and/or, come into play when you are talking about putting HPE 2930/3801 switches at remote locations, but I digress...