Ok, we only use the on-controller dhcp server for the guest portion of our wireless deployment, which in most cases is very small.
We recently put in a new controller at a new site, and set up the guest ssid and catpive portal, etc, but it stopped working earlier today. This is what I found-
lease 172.20.0.253 {
starts Thu Nov 15 20:33:13 2012
ends Thu Nov 15 21:03:13 2012
binding state active;
next binding state free;
hardware ethernet 38:aa:3c:f6:28:e1;
uid "\0018\252<\366(\341";
}
lease 172.20.0.253 {
starts Thu Nov 15 20:33:14 2012
ends Thu Nov 15 21:03:14 2012
binding state active;
next binding state free;
hardware ethernet 38:aa:3c:f6:28:e1;
uid "\0018\252<\366(\341";
}
lease 172.20.0.253 {
starts Thu Nov 15 20:33:15 2012
ends Thu Nov 15 21:03:15 2012
binding state active;
next binding state free;
hardware ethernet 38:aa:3c:f6:28:e1;
uid "\0018\252<\366(\341";
}
lease 172.20.0.253 {
starts Thu Nov 15 20:33:16 2012
ends Thu Nov 15 21:03:16 2012
binding state active;
next binding state free;
hardware ethernet 38:aa:3c:f6:28:e1;
uid "\0018\252<\366(\341";
}
lease 172.20.0.253 {
starts Thu Nov 15 20:33:17 2012
ends Thu Nov 15 21:03:17 2012
binding state active;
next binding state free;
hardware ethernet 38:aa:3c:f6:28:e1;
uid "\0018\252<\366(\341";
}
lease 172.20.0.253 {
starts Thu Nov 15 20:33:19 2012
ends Thu Nov 15 21:03:19 2012
binding state active;
next binding state free;
hardware ethernet 38:aa:3c:f6:28:e1;
uid "\0018\252<\366(\341";
}
lease 172.20.0.253 {
starts Thu Nov 15 20:33:20 2012
ends Thu Nov 15 21:03:20 2012
binding state active;
next binding state free;
hardware ethernet 38:aa:3c:f6:28:e1;
uid "\0018\252<\366(\341";
}
lease 172.20.0.253 {
starts Thu Nov 15 20:33:21 2012
ends Thu Nov 15 21:03:21 2012
binding state active;
next binding state free;
hardware ethernet 38:aa:3c:f6:28:e1;
uid "\0018\252<\366(\341";
}
lease 172.20.0.253 {
starts Thu Nov 15 20:33:22 2012
ends Thu Nov 15 21:03:22 2012
binding state active;
next binding state free;
hardware ethernet 38:aa:3c:f6:28:e1;
uid "\0018\252<\366(\341";
}
lease 172.20.0.253 {
starts Thu Nov 15 20:33:23 2012
ends Thu Nov 15 21:03:23 2012
binding state active;
next binding state free;
hardware ethernet 38:aa:3c:f6:28:e1;
uid "\0018\252<\366(\341";
}
lease 172.20.0.253 {
starts Thu Nov 15 20:33:24 2012
ends Thu Nov 15 21:03:24 2012
binding state active;
next binding state free;
hardware ethernet 38:aa:3c:f6:28:e1;
uid "\0018\252<\366(\341";
}
lease 172.20.0.253 {
starts Thu Nov 15 20:33:25 2012
ends Thu Nov 15 21:03:25 2012
binding state active;
next binding state free;
hardware ethernet 38:aa:3c:f6:28:e1;
uid "\0018\252<\366(\341";
}
lease 172.20.0.253 {
starts Thu Nov 15 20:33:27 2012
ends Thu Nov 15 21:03:27 2012
binding state active;
next binding state free;
hardware ethernet 38:aa:3c:f6:28:e1;
uid "\0018\252<\366(\341";
}
lease 172.20.0.253 {
starts Thu Nov 15 20:33:28 2012
ends Thu Nov 15 21:03:28 2012
binding state active;
next binding state free;
hardware ethernet 38:aa:3c:f6:28:e1;
uid "\0018\252<\366(\341";
}
This actually would go on and on and on, several hundred entries of the same lease to the same mac. Also I should point out that the clients never get an address.
I restarted the dhcpd process, didn't fix it, restarted the controller, no joy, and even deleted the dhcp server settings, restarted the controller, and reconfigured the dhcp server and it didn't do anything different.
Anyone seen this before? It's not a huge issue at the moment but I will opening a TAC case tomorrow unless someone has a fix for it.