I don't want the WLC do DHCP, I don't believe the 526 can either, my post reads "I've been screwing around for quites some time now trying to get DHCP to work through the WLC from servers set up on the UC520". My UC520 hosts the servers with bindings and exclusion setup per vlan as required and I want my wi-fi clients to be able to receive addresses through the WLC from the UC520's DHCP servers.

Clients are PCs, iPads, etc. normal everyday clients. 

I do have one and I did used it for some time it worked fine with UC520 but I had to removed some time ago because I am using deferent system I also had cisco 7921 wireless phone working with no problem. I agree tac was not help but I managed to get it working. I had to create separate VLAN for wireless on UC520.

I agree with David me too after 10 year been Cisco partner I dropped cisco, because I got fed-up of year after year taking the repetitive Cisco exam.

I let my certs lapse too mainly cuz those tests are real stupid created by full time test writers who have no concept of networks.  Then pile on all the sales and marketing BS.  I was thinking about going through it again but after this round of BS probably not. 

Yeah the idea that firmware upgrades aren't available for the life of the product is indeed lame and another reason some folks move away from vendors who do this.  The biz management suits that come up with these intended revenue generating ideas should have their head examined since for every $ they make they loose $$ by driving people away to other products.

Yeah I feel I need an updated firmware/software cuz I pretty much tried everything else, well almost. 

What I love about the TAC responses is that this product is dead with an EOL of over a year ago yet they want to hold on to the SW that could help make this device work which is only one week out of the box (brand new) and in the end drive me away from selling Cisco products.  Little robots sitting behind a desk adhering to their scripted responses.   

Hi Viningele,

 Little robots sitting behind a desk adhering to their scripted responses.    

I am not afraid to criticize Cisco for certain decisions that they make and publicly as well, after all they do pride themselves on being a company that accepts all forms of feedback from the community.

However though I leave the support personnel out of any of my criticism, those guys have a real hard job, they often have to work within tight constraints and very tight rules, sometimes you even get one who says "To hell with it" and steps outside of those boundaries because they have that fire in them to help someone.

Don't be down on them as they are just doing their job and doing what they are instructed to do by their employer, I would though encourage you to voice your opinion against the decisions made by the upper management who at times don't seem to think before they act, or maybe do think but just ignore the writing on the wall in front of them and just do what they think is best based upon solely their opinion.

Not havin ga go at you in any way but I will always defend the support staff as they are all a wonder crew (The majority of the time 98%).

Back to your problem, I did try and get the latest firmware for you, but yeah it is as I thought I am not able too

Cheers,

David.

Yeah, I'm not really down on the TAC techs but the suits who write the rules.  TACs hands are tied to some extent and I do understand a companies need and right to profit but when a policy is counter productive and bad for biz and the suits are too dumd to comprehend well......

Anyway, since I don't believe in surrendering I managed to get it to work.  I'm sure the newer fw/sw would have eliminated the convoluted procedure I had to go through to get it too work.

Procedure for creating a WLAN on the WLC526 that pulls DCHP from the UC520 or

other device hosting a DHCP server.

I believe the problems I was having was in part due to the order of the

various steps and where the VLAN used for the WLAN was initially created.

Otherwise I'm not doing anything different that I haven't tried dozens of times. 

Normally I create the VLANs first in the UC520 in CCA --> Configure -->

Switching --> VLANs, then go on from there but that wasn't working when I

tried using the WLC.  Maybe subsequent sofware updates corrected this "bug"

but I guess we need to pay for bug fixes. Hmmm!  

From what I'ver gathered you need to start with a fresh VLAN and WLAN.

CCA --> Configure --> Wireless --> WLANs (SSIDS) --> Create -->

Pop Up for my needs I answer "no".

WLAN Type: Check "Data" (haven't tried others yet)

SSID: My-Wi-Fi-5 (just some dumb name for testing)

Broadcast: checked

VLAN: Add Vlan --> Pop Up

VLAN: 202 (I like to use the 3rd octect of my corresponding LAN address)

VLAN Name: my-vlan-202 (only lower case which differs from Switching Vlans)

Port: 1 (my WLC connects via port 1 on the WLC)

IP Add: 192.168.202.2

Subnet: 255.255.255.0

Gateway: 192.168.202.1

DHCP: 192.168.202.1

OK --> closes Pop Up

Web Authentication: unchecked (not for this)

Security Type: WPA2-PSK

Encryption: aes

WPA Pre-Shared Key: SomeDumbKey (8 character minmum)

Ok --> close Pop Up

Apply -->  Pop Up --> Ok, Pop Up --> Ok (I get comm err 404, forget it) --> Ok

Ok --> close the WLAN (SSID) Pop Up.

Now go to Routing.

CCA --> Configure --> Routing --> IP Addresses

Find the new Vlan

Vlan202 enter IP 192.168.202.1 Mask 255.255.255.0

Apply --> Pop Up --> Ok --> Pop Up --> Ok

Ok --> closes IP Adresses

CCA --> Configure --> Routing --> DHCP Server

Select Pool Tab

Create

Name: DHCP-P-202 (pool for vlan 202)

Network: 192.168.202.0

Mask: 255.255.255.0

Default Router: 192.168.202.1

Ok --> Closes Pop Up

Apply (could wait until after exclusions but..)

Pop Up:

ip dhcp pool DHCP-P-202
network 192.168.202.0 255.255.255.0
default-router 192.168.202.1
import all
lease 1
exit

Ok --> closes Pop Up --> Pop Up --> Ok

DHCP Exclusions Tab

Create

Start 192.168.202.1

End 192.168.202.99 (this could be what ever you want to reserve)

Pop Up:

ip dhcp excluded-address 192.168.202.1 192.168.202.99

Ok --> closes DHCP Pop Up

Now in the Topology view right click on the WLC device

Double click on the Config Utility

WLC Config Utilty Page..................

I get the security certificate warning, click continue to website (not

recommended)

Login button, log in

Click on the WLANs tab, General Tab verify My-Wi-Fi-5 is present and click on

it

Status: checked (enabled)

Radio Policy: All

Interface: my-vlan-202

Broadcast: checked (enabled)

Skip Security and QOS for another day

Advanced Tab:

DHCP Server: check (override)

enter 192.168.202.1

DHCP Addr. Assign: check (required) leave off if want static clients too(?)

Apply --> Save Configuration (top right)

Interfaces --> verify my-vlan-202 and IP Address of 192.168.202.2

Left side click the Advanced button

click DHCP

Enable DHCP Proxy: checked (enabled)

Apply if changed or just for the heck of it.

Save Configuration.

Go to any PC and check for the available wi-fi and select My-Wi-Fi-5

You should be good to go to acquire an address but won't get any DNS for

surfing.

Go to a CLI utility like Inidgo Terminal Emulator (the best I've found)

Log into the UC520 via command line

UC_520>enable
Password:
UC_520#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
UC_520(config)#ip dhcp pool DHCP-P-202
UC_520(dhcp-config)#network 192.168.202.0 255.255.255.0
UC_520(dhcp-config)#default-router 192.168.202.1
UC_520(dhcp-config)#import all
UC_520(dhcp-config)#lease 1
UC_520(dhcp-config)#exit
UC_520(config)#ip dhcp excluded-address 192.168.202.1 192.168.202.99
UC_520(config)#exit
UC_520#reload

System configuration has been modified. Save? [yes/no]: yes
Building configuration...

Compressed configuration from 29490 bytes to 13449 bytes[OK]
Proceed with reload? [confirm]yes

With luck when it boots up you can connect to your new WLAN, obtain an IP

address from the DHCP server on your UC520 and surf the web.

In my case my NAT is set up for 192.168.0.0  0.0.0.0  80 so 192.168.202.0 is

already configured for HTTP (web surfing). 

On your PC clear your wi-fi settings for the new WLAN and re-connect, re-enter

the password.

Once connected check your setting and your DNS values should be imported.  I

don't know what this has to be done twice unless maybe the UC520 config wasn't

saved and reloaded but it's easy enough to and in again via CLI.

Anyway this new WLAN now works, I get my DHCP and I can surf.

FYI, my UC520 ins't my gateway but sits behind an RV082 which I will probably

remove once I get all this new (old) gear up and running.