Is there a pro/con, or best practice regarding the ip addressing for your AP's when having them connected to wireless controllers?
Basically I am trying to decide if the AP's should just use the same VLAN and subnet as what the wireless clients will use, or something different?
I know that part of the LWAPPs process for finding controllers depends on it grabbing a DHCP address which if you configure the switch port right for the AP according to the deployment guide you are setting the access vlan to that which your wireless clients will use. So the AP will grab DHCP from the client scope then broadcast out on that subnet looking for a controller.
So far all seems fine and good, and I know you can change the IP address of the AP if you want once it is homed into the controller. But I simply don't know if there is a best practice regarding this.
Leave the APs IP on same subnet/vlan as the wireless clients or move the AP's to a new one.
Maybe I am over thinking this, and it really doesn't matter?
I have two controllers at two main locations, each going to support about 15 AP's. Same SSID at each location and using PEAP.
Thinking about basically allocating two class c's one for each location for the wireless clients and just do some reservations from each class c scope for the AP's.
What would be the negatives of doing things this way? Any suggestions or pros/cons would be appreciated.