08-07-2014 01:02 AM
I've created initial VLAN and 1 ssid (Corp). Then I've created a dhcp scope for that VLAN.
Basically my wireless clients are still getting a dhcp address from our domain controller and not the allocated range on the Aruba wlc
What am I missing ?
Solved! Go to Solution.
08-07-2014 02:49 AM - edited 08-07-2014 02:50 AM
If there are multiple DHCP servers for a network available (in your case the controller and Windows), the first one to respond is where clients will get an IP address from.
First confirm DHCP is setup properly on the controller:
show ip dhcp database
show ip dhcp statistics
show ip interface brief (the controller needs an IP on the VLAN)
Second, if you cannot turn off the scope no the Windows server, you can configure a DHCP helper for the VLAN in question to try and direct the request to where you want.
interface vlan XX
ip helper-address x.x.x.x (IP of controller)
Systems Engineer, Northeast USA
ACCX | ACDX | ACMX
08-07-2014 04:03 AM
Type "show user-table verbose" and see what VLAN# the user is ending up in. It would be in parentheses in the last column.
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
08-07-2014 04:47 AM
The network on the scope needs to match that of your vlan interface, otherwise it won't respond.
If you want to keep using the Windows server for other devices, you should put exclusions in place on both to ensure there is no overlap and ip conflicts.
If my post is helpful please give kudos, or mark as solved if it answers your post.
ACCP, ACMP, ACMX #294