Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all
This thread has been viewed 15 times
  • 1.  dhcp issues

    Posted Aug 07, 2014 04:03 AM

    Hi,

     

    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 ?

     

    Many thanks

     

     



  • 2.  RE: dhcp issues

    EMPLOYEE
    Posted Aug 07, 2014 04:49 AM

    did you do also on the controller,

     

    service dhcp

     

     



  • 3.  RE: dhcp issues

    Posted Aug 07, 2014 05:26 AM

    thanks, but still no joy

     

    Any ideas



  • 4.  RE: dhcp issues

    Posted Aug 07, 2014 05: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)



  • 5.  RE: dhcp issues

    Posted Aug 07, 2014 07:01 AM
      |   view attached

    Thanks but still picking up from the domain controller

     

     

    see attached

     

    many thanks

     

     

     

     

    Attachment(s)

    txt
    dhcp issue.txt   975 B 1 version


  • 6.  RE: dhcp issues

    EMPLOYEE
    Posted Aug 07, 2014 07: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.



  • 7.  RE: dhcp issues

    Posted Aug 07, 2014 07:08 AM

    it's ending up in VLAN 1 which is correct

     

    thanks

     



  • 8.  RE: dhcp issues

    EMPLOYEE
    Posted Aug 07, 2014 07:12 AM
    The mask in your vlan 1 doesn't match the mask in your scope.


  • 9.  RE: dhcp issues

    Posted Aug 07, 2014 07:33 AM

    Ah yes thanks

     

    So we can't issue a separate DHCP pool on the default vlan ?

     

     



  • 10.  RE: dhcp issues
    Best Answer

    EMPLOYEE
    Posted Aug 07, 2014 07:48 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.