Hi James,
I'm probably over my head here, so forgive me if this seems clueless,
and maybe I can learn something. (Also, we have Cicso wireless, so I
really don't know for Aruba.) But:
On Jan 17, 2012, at 3:51 PM, James M Keller wrote:
We did a work around, and enabled DHCP scopes on the master controller
and changed the DHCP helper on the test LAN to the controller and this
worked.
[...]
We obviously would prefer DHCP be
centrally managed in one place vs having to do one-off scopes on the
controller.
As a design concept, what is the benefit of having your central DNS
handle your APs? Since the wireless controller can do it, why not just
let it hand out an address range that you don't use elsewhere to its
APs, and skip the hassle of making the APs cooperate with your main DNS?
With our wireless setup, our APs are on a VLAN which lets them connect
to the their controllers, but not to much else. In particular, they
can't reach our DNS server nor any other "regular user" services. All
the wifi user VLANs are tunneled from the APs back to the controllers,
and these VLANs let the users hit our central DNS, with the users in a
separate address space than the APs. Since the APs and users are kept
separate anyhow, it does not seem odd to have them use different DNS
servers.
Of course, the only way I can find the IP of a particular AP is via
the Wireless Control Server (or directly via the wireless controller)
but in practice that is the only way I want to deal with my APs in any
case.
Steve Bohrer
Network Admin
Bard College at Simon's Rock
413-528-7645
**********
Participation and subscription information for this EDUCAUSE Constituent Group
discussion list can be found at http://www.educause.edu/groups/.
