Wrong controllers processing DHCP client request

[stephendrkw]

I have internal 5508 Controllers which have an established Mobility Anchor with my DMZ 5508 Controller. (The DMZ Controller acts as a DHCP server)

Current setup

When client connects to WLAN SSID, client request is sent to the old internal controller, request is forwarded onto the DMZ controller, client receives DHCP fine from DMZ controller. When I do a "debug client mac" on DMZ WLC you can see the DHCP success.

New setup not working yet!

When client connects to New WALN SSID for some reason with a new 3600 AP and new 5508 controller, I apply a "debug client mac" on the DMZ controlller I see nothing, apply "debug client mac" on the new internal 5508 controller, I see the following:

pemReceiveTask: Jun 05 10:48:16.286: 18:00:2d:fa:12:ce 0.0.0.0 Added NPU entry of type 9, dtlFlags 0x0

*pemReceiveTask: Jun 05 10:48:16.286: 18:00:2d:fa:12:ce 0.0.0.0 Added NPU entry of type 9, dtlFlags 0x0

*DHCP Socket Task: Jun 05 10:48:16.527: 18:00:2d:fa:12:ce DHCP received op BOOTREQUEST (1) (len 308,vlan 10, port 13, encap 0xec03)

*DHCP Socket Task: Jun 05 10:48:16.527: 18:00:2d:fa:12:ce DHCP dropping packet

*apfLbsTask: Jun 05 10:48:16.602: 18:00:2d:fa:12:ce Copy AP LOCP - mode:0 slotId:1, apMac 0xcc:d5:39:ba:48:b0

*apfLbsTask: Jun 05 10:48:16.603: 18:00:2d:fa:12:ce Copy WLAN LOCP EssIndex:2 aid:1 ssid: guesttest

*apfLbsTask: Jun 05 10:48:16.603: 18:00:2d:fa:12:ce Copy Security LOCP ecypher:0x3 ptype:0x4, p:0x1, eaptype:0x6 w:0x0 aalg:0x0, PMState:  DHCP_REQD

*apfLbsTask: Jun 05 10:48:16.603: 18:00:2d:fa:12:ce Copy 802.11 LOCP a:0x0 b:0x0 c:0x0 d:0x0 e:0x1 protocol2:0x7 statuscode 0, reasoncode 99, status 3

*apfLbsTask: Jun 05 10:48:16.603: 18:00:2d:fa:12:ce Copy MobilityData LOCP status:1, anchorip:0x0

*DHCP Socket Task: Jun 05 10:48:20.451: 18:00:2d:fa:12:ce DHCP received op BOOTREQUEST (1) (len 308,vlan 10, port 13, encap 0xec03)

*DHCP Socket Task: Jun 05 10:48:20.451: 18:00:2d:fa:12:ce DHCP dropping packet

Why would the new internal controller be dealing with the client DHCP request when it's not configured as a DHCP server? shouldn't this controller forward the request onto the DMZ controller like with the current working WLAN SSID. I have the same new WLAN/SSID configuration on both DMZ and new Internal Controllers.

[Scott Fella · Accepted solution]

Are you anchoring the new SSID to the anchor and is the anchor WLC new SSID anchored to itself?

Sent from Cisco Technical Support iPhone App

[stephendrkw]

Works perfectly now, Anchors configured incorrectly.

Something I should've figured out before posting.......when you don't setup WLAN's for a year or so, you forget the config process!

[Scott Fella]

Haha.. Right away when you said the internal was processing the dhcp, I knows from experience it was the anchoring. Glad it was a quick fix for you though.

Sent from Cisco Technical Support iPhone App

[Rajhans Shere]

Hi Guys,

Even i am facing this issue today. I am not able to understand what is anchoring?

I am facing below issue

1. AP is getting the IP from DHCP server but the PC which is connecting to that AP is not able to get the IP from DHCP Server.

My DHCP server is external.

Below is my simple setup.

AP--------Switch-----------Router----------Switch----------WLC

                                                                  |

                                                                  |

                                                              DHCP

My AP is in vlan 2 and my WLC and DHCP is in VLAN 1

Clients are getting authenticated from Radius Server(MY DHCP server is my Radius server) but not able to get ip.

Below is the output of debug command

*DHCP Socket Task: Sep 21 17:58:44.146: [PA] 00:16:6f:53:35:2c DHCP successfully bridged packet to DS
*DHCP Socket Task: Sep 21 17:58:54.266: [PA] 00:21:5e:42:9e:87 DHCP received op BOOTREQUEST (1) (len 286,vlan 96, port 1, encap 0xec00)
*DHCP Socket Task: Sep 21 17:58:54.266: [PA] 00:21:5e:42:9e:87 DHCP dropping packet (no mscb) found - (giaddr 0.0.0.0, pktInfo->srcPort 68, op: 'BOOTREQUEST')
*DHCP Socket Task: Sep 21 17:59:00.150: [PA] 00:16:6f:53:35:2c DHCP received op BOOTREQUEST (1) (len 313,vlan 96, port 1, encap 0xec03)
*DHCP Socket Task: Sep 21 17:59:00.150: [PA] 00:16:6f:53:35:2c DHCP (encap type 0xec03) mstype 0ff:ff:ff:ff:ff:ff
*DHCP Socket Task: Sep 21 17:59:00.150: [PA] 00:16:6f:53:35:2c DHCP processing DHCP DISCOVER (1)
*DHCP Socket Task: Sep 21 17:59:00.150: [PA] 00:16:6f:53:35:2c DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Sep 21 17:59:00.150: [PA] 00:16:6f:53:35:2c DHCP   xid: 0xed961900 (3986036992), secs: 7168, flags: 0
*DHCP Socket Task: Sep 21 17:59:00.150: [PA] 00:16:6f:53:35:2c DHCP   chaddr: 00:16:6f:53:35:2c
*DHCP Socket Task: Sep 21 17:59:00.150: [PA] 00:16:6f:53:35:2c DHCP   ciaddr: 0.0.0.0,  yiaddr: 0.0.0.0
*DHCP Socket Task: Sep 21 17:59:00.150: [PA] 00:16:6f:53:35:2c DHCP   siaddr: 0.0.0.0,  giaddr: 0.0.0.0
*DHCP Socket Task: Sep 21 17:59:00.150: [PA] 00:16:6f:53:35:2c DHCP   requested ip: 169.254.245.191
*DHCP Socket Task: Sep 21 17:59:00.150: [PA] 00:16:6f:53:35:2c DHCP Opt82 bridge mode insertion enabled, inserts opt82 if opt82 is enabled vlan=96, datalen =18, optlen=69

Can anyone help me here?

Cheersss

Raj