clients not getting a DHCP IP on a 2006 controller

[garyrivers]

i created the DHCP scope on the controller and then created the WLAN. in the WLAN config, under Advanced, i did not check DHCP override since the controller will handle the DHCP IPs. And I did not check the DHCP Addr. Assignment box.

well, my test client is not getting a DHCP IP.

i'm sure i'm missing some thing but not sure where so I need some guidance in where I might look.

Thanks, Gary

[Tiago Antunes]

Share with us th show run-config of the WLC and we might be able to say if there is anything wrong with the configuration of the WLC.

[Raul Manzano Barroso · Accepted solution]

First, I assume you have created an dynamic interface to map to your SSID.

If you have done this, you only attach the management IP address of the WLC into the DHCP field in the dynamic interface you mapped to the SSID.

Another frequent issue is when you create and scope people sometimes forget set to enable the scope 

Best regards.

[garyrivers]

okay, well i THOUGHT i had it fixed but i guess not.  my test laptop is getting an IP via DHCP BUT now i'm not able to get out to the switch that the controller is connected to.  i can see into the controller from the connected SW and the controller can see the SW but that's it.

Any thoughts?

Thanks

[Raul Manzano Barroso]

Ok.

In your dynamic interface, you configured a VLAN ID (or not, but most probably yes) and mapped this interface to a port of the WLAN controller.

Then you must connect this port to your Switch and:

- If is the same port as Management interface, make sure you configured this port in dot1q trunk mode and the VLAN ID of the dynamic interface and management are allowed to pass through this trunk. Please advise that if management or dynamic interface has VLAN ID 0 in WLC (no tagging) you must pass this vlan through trunk as native vlan.

- If is a different port, make sure you configured this port in dot1q trunk mode and the VLAN ID of the dynamic interface is allowed to pass through this trunk. Please advise that if dynamic interface has VLAN ID 0 in  WLC (no tagging) you must pass this vlan through trunk as native vlan.

Hope it is useful  and I hit with this issue.

Best regards.

[garyrivers]

the controller was already connected to the switch so i config-ed that port as follows:

interface GigabitEthernet0/3

description Trunked port to the AP Controller

switchport trunk encapsulation dot1q

switchport mode trunk

switchport trunk allowed vlan 1,6

no mdix auto

and i also created a new vlan on the switch for the guest WLAN and .  here it is

interface Vlan6
ip address 172.168.40.253 255.255.255.0

here's alittle bit of the WLC config

DHCP Scope:172.168.40.1 – 100

Mask: 255.255.255.0

Gateway: 172.168.40.254

Guest port IP: 172.168.40.254

[Raul Manzano Barroso]

Can you show us the configuration of both interfaces on WLC?

Best rebards.

[garyrivers]

okay, stupid question time...which two are you requesting?

the guest vlan and the management interfaces?

Gary

[garyrivers]

here are screen shots of the guest and the management interface configs.

[Raul Manzano Barroso]

Look at your DHCP configuration and Guest interface configuration.

In your guest interface configuration you set the GW the same IP assigned to this interface; this is wrong; you must set IP of the VLAN 6 (172.168.40.253) that you provide a L3 as the GW IP address. By the other hand, in your DHCP pool you also change this IP because the GW is wrong too, change to 172.168.40.253 and try again.

Best Regards.

[garyrivers]

okay, i changed the .254 to .253 under the guest interface and under guest DHCP pool settings and i'm still not able to ping out from the laptop which has an IP of .1.

one think i thought of is that i don't have IP ROUTING on on the SW the controller is connected to.