Hi rasika,I test the same

Jhon Fredy Herrera Osorno · ‎03-22-2015

Hi to all,

I am having trouble with my lab. the wireless clients is not available to get addresses, the client is in state DHCP_RQD.

I am using vwlc 7.4.121 and the ap in flexconnect mode.

the CORE is the dhcp server

the ESXi is the server where i exectute the vWLC

See the attached screenshot

Rasika Nayanajith · ‎03-22-2015

if you configure that wireless user vlan on switch 1 wired port, does it give DHCP to a wired client ? Then try same wired PC on the Hub 1 in your diagram. In that way you can make sure DHCP working properly independent of vWLC.

On wireless end, I would check & see if DHCP address assignment checked under WLAN advanced tab configuration.

HTH

Rasika

**** Pls rate all useful responses ****

Jhon Fredy Herrera Osorno · ‎03-23-2015

Hi rasika,

Thanks for you replay. the dhcp for wired client work. and yes the DHCP address assignment is checked as you suggest.

here is the log of dhcp when the wired client request an address:

CRYCOLABCORE01#debug ip dhcp server events
DHCP server event debugging is on.
CRYCOLABCORE01#
*Mar 23 12:23:34.538: DHCPD: Sending notification of DISCOVER:
*Mar 23 12:23:34.538:   DHCPD: htype 1 chaddr 0800.27f5.ccef
*Mar 23 12:23:34.538:   DHCPD: interface = Vlan20
*Mar 23 12:23:34.538:   DHCPD: class id 4d53465420352e30
*Mar 23 12:23:34.538:   DHCPD: out_vlan_id 0
*Mar 23 12:23:34.538: DHCPD: Sending notification of DISCOVER:
*Mar 23 12:23:34.538:   DHCPD: htype 1 chaddr 0800.27f5.ccef
*Mar 23 12:23:34.538:   DHCPD: interface = Vlan20
*Mar 23 12:23:34.538:   DHCPD: class id 4d53465420352e30
*Mar 23 12:23:34.538:   DHCPD: out_vlan_id 0
*Mar 23 12:23:34.538: DHCPD: requested address 10.10.30.1 is not on subnet 192.168.20.0.
*Mar 23 12:23:36.540: DHCPD: Adding binding to radix tree (192.168.20.1)
*Mar 23 12:23:36.540: DHCPD: Adding binding to hash tree
*Mar 23 12:23:36.540: DHCPD: assigned IP address 192.168.20.1 to client 0108.0027.f5cc.ef. (25 0)

*Mar 23 12:23:36.540: DHCPD: DHCPOFFER notify setup address 192.168.20.1 mask 255.255.255.0
*Mar 23 12:23:36.544: DHCPD: Sending notification of ASSIGNMENT:
*Mar 23 12:23:36.544: DHCPD: address 192.168.20.1 mask 255.255.255.0
*Mar 23 12:23:36.544:   DHCPD: htype 1 chaddr 0800.27f5.ccef
*Mar 23 12:23:36.544:   DHCPD: lease time remaining (secs) = 86400
*Mar 23 12:23:36.544:   DHCPD: interface = Vlan20
*Mar 23 12:23:36.544:   DHCPD: out_vlan_id 0
CRYCOLABCORE01#
*Mar 23 12:23:39.336: DHCPD: Sending notification of ASSIGNMENT:
*Mar 23 12:23:39.336: DHCPD: address 192.168.20.1 mask 255.255.255.0
*Mar 23 12:23:39.336:   DHCPD: htype 1 chaddr 0800.27f5.ccef
*Mar 23 12:23:39.336:   DHCPD: lease time remaining (secs) = 86400
*Mar 23 12:23:39.336:   DHCPD: interface = Vlan20
*Mar 23 12:23:39.336:   DHCPD: out_vlan_id 0

and here is the log of the dhcp server when the wireless client request an address in the SSID (SSID20)

CRYCOLABCORE01#
*Mar 23 12:37:59.324: DHCPD: Sending notification of DISCOVER:
*Mar 23 12:37:59.324:   DHCPD: htype 1 chaddr 485a.b67c.bfb7
*Mar 23 12:37:59.324:   DHCPD: interface = Vlan11
*Mar 23 12:37:59.324:   DHCPD: class id 4d53465420352e30
*Mar 23 12:37:59.324:   DHCPD: out_vlan_id 0
*Mar 23 12:37:59.324: DHCPD: Sending notification of DISCOVER:
*Mar 23 12:37:59.324:   DHCPD: htype 1 chaddr 485a.b67c.bfb7
*Mar 23 12:37:59.324:   DHCPD: interface = Vlan11
*Mar 23 12:37:59.324:   DHCPD: class id 4d53465420352e30
*Mar 23 12:37:59.324:   DHCPD: out_vlan_id 0
CRYCOLABCORE01#
*Mar 23 12:38:01.329: DHCPD: Adding binding to radix tree (192.168.11.4)
*Mar 23 12:38:01.330: DHCPD: Adding binding to hash tree
*Mar 23 12:38:01.330: DHCPD: assigned IP address 192.168.11.4 to client 0148.5ab6.7cbf.b7. (22 0)
*Mar 23 12:38:01.330: DHCPD: DHCPOFFER notify setup address 192.168.11.4 mask 255.255.255.0
CRYCOLABCORE01#
*Mar 23 12:38:02.604: DHCPD: Sending notification of DISCOVER:
*Mar 23 12:38:02.604:   DHCPD: htype 1 chaddr 485a.b67c.bfb7
*Mar 23 12:38:02.604:   DHCPD: interface = Vlan11
*Mar 23 12:38:02.604:   DHCPD: class id 4d53465420352e30
*Mar 23 12:38:02.604:   DHCPD: out_vlan_id 0
*Mar 23 12:38:02.604: DHCPD: Sending notification of DISCOVER:
*Mar 23 12:38:02.604:   DHCPD: htype 1 chaddr 485a.b67c.bfb7
*Mar 23 12:38:02.604:   DHCPD: interface = Vlan11
*Mar 23 12:38:02.604:   DHCPD: class id 4d53465420352e30
*Mar 23 12:38:02.604:   DHCPD: out_vlan_id 0
*Mar 23 12:38:02.604: DHCPD: DHCPOFFER notify setup address 192.168.11.4 mask 255.255.255.0
!
!

i don't know why the request come from the interface vlan11, the vlan 11 is the segment of the network wirelesss devices such as APs and CONTROLLER.

What additional task is needed in the vWLC ? :s

The vWLC work as dhcp proxy (default behavior) and no dhcp bridging enable

!

here is the swtich port config where is connected the LAP:

interface Ethernet3/3
description CONNECTED-to-LABLAP01
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 11,20-22
switchport mode trunk
duplex auto
spanning-tree portfast trunk

NOTE: When disable vlan support in the advanced AP configuration tab work the dhcp. but i wish to configure multi SSID in an AP.

Rasika Nayanajith · ‎03-23-2015

i don't know why the request come from the interface vlan11, the vlan 11 is the segment of the network wirelesss devices such as APs and CONTROLLER.
What additional task is needed in the vWLC ?

This mean vlan mapping is not properly working on this AP. Refer below document & make sure vlan support is enable on this FlexConnect AP & correct vlan is mapped to the FlexConnect local switching enabled WLAN.

https://supportforums.cisco.com/document/98646/wireless-lan-flexconnect-configuration-example

HTH

Rasika

**** Pls rate all useful responses ****

Jhon Fredy Herrera Osorno · ‎03-23-2015

Hi,

i am using AIR-LAP1261N-A-K9, and from cisco it is supported.

http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn74mr02.html#pgfId-1048617

I am using vWLC version 7.4.121.0

Rasika Nayanajith · ‎03-23-2015

I am not saying your AP is not supporting FlexConnect.

There may be some configuration mismatch (hence provided the link to crosscheck). If you properly map vlan 20 to your WLAN, all client traffic to be terminated on vlan 20. So your DHCP server should get request coming from that vlan instead of vlan 11.

HTH

Rasika

Jhon Fredy Herrera Osorno · ‎03-24-2015

Hi rasika,

I test the same configuration on a physical WLC (AIR-CT5508-K9) that i am doing in my lab environment and work in the physical WLC.

I will continue my practice for get my CCNA Wireless in the vWLC cofigured the FLEXCONNECT ap without vlan support because is the only config that work for me in the vWLC.

Thanks a lot for your support.

Jh0n

Flexconnect and vWLC not working DHCP