AP doesn't get a DHCP IP address

[#1]

DHCP Socket Task: Dec 17 10:35:40.105: fc:99:47:c8:4a:9d DHCP received op BOOTREQUEST (1) (len 322,vlan 0, port 1, encap 0xec00)

*DHCP Socket Task: Dec 17 10:35:40.105: fc:99:47:c8:4a:9d DHCP received a REQUEST on 'management' interface from AP -- bouncing to local DHCP server.

*DHCP Socket Task: Dec 17 10:35:40.105: fc:99:47:c8:4a:9d DHCP sending to local dhcp server (0.0.0.0:68 -> 10.197.2.84:1067, len 314)

*DHCP Socket Task: Dec 17 10:35:40.144: fc:99:47:c8:4a:9d DHCP received op BOOTREPLY (2) (len 310,vlan 0, port 1, encap 0xec00)

*DHCP Socket Task: Dec 17 10:35:40.144: fc:99:47:c8:4a:9d DHCP dropping packet (no mscb) found - (giaddr 10.197.2.1, pktInfo->srcPort 67, op: 'BOOTREPLY')

*DHCP Socket Task: Dec 17 10:35:40.331: fc:99:47:c8:4a:9d DHCP received op BOOTREPLY (2) (len 310,vlan 0, port 1, encap 0xec00)

*DHCP Socket Task: Dec 17 10:35:40.331: fc:99:47:c8:4a:9d DHCP dropping packet (no mscb) found - (giaddr 10.197.2.1, pktInfo->srcPort 67, op: 'BOOTREPLY')

*DHCP Socket Task: Dec 17 10:35:43.105: fc:99:47:c8:4a:9d DHCP received op BOOTREQUEST (1) (len 322,vlan 0, port 1, encap 0xec00)

*DHCP Socket Task: Dec 17 10:35:43.105: fc:99:47:c8:4a:9d DHCP received a REQUEST on 'management' interface from AP -- bouncing to local DHCP server.

*DHCP Socket Task: Dec 17 10:35:43.105: fc:99:47:c8:4a:9d DHCP sending to local dhcp server (0.0.0.0:68 -> 10.197.2.84:1067, len 314)

*DHCP Socket Task: Dec 17 10:35:43.144: fc:99:47:c8:4a:9d DHCP received op BOOTREPLY (2) (len 310,vlan 0, port 1, encap 0xec00)

*DHCP Socket Task: Dec 17 10:35:43.144: fc:99:47:c8:4a:9d DHCP dropping packet (no mscb) found - (giaddr 10.197.2.1, pktInfo->srcPort 67, op: 'BOOTREPLY')

*DHCP Socket Task: Dec 17 10:35:43.331: fc:99:47:c8:4a:9d DHCP received op BOOTREPLY (2) (len 310,vlan 0, port 1, encap 0xec00)

*DHCP Socket Task: Dec 17 10:35:43.331: fc:99:47:c8:4a:9d DHCP dropping packet (no mscb) found - (giaddr 10.197.2.1, pktInfo->srcPort 67, op: 'BOOTREPLY')

*DHCP Socket Task: Dec 17 10:35:46.105: fc:99:47:c8:4a:9d DHCP received op BOOTREQUEST (1) (len 322,vlan 0, port 1, encap 0xec00)

*DHCP Socket Task: Dec 17 10:35:46.105: fc:99:47:c8:4a:9d DHCP received a REQUEST on 'management' interface from AP -- bouncing to local DHCP server.

DHCP server is Infoblox with LWAPP setting.

[kcnajaf]

Hi ERIC,

Log shows the request is goin to local dhcp server? Is this DHCP server ip 10.197.2.1?

Which version of image are you running?

Do you have DHCP proxy enabled? If so try disabling it.

Regards

Najaf

[Amjad Abdullah]

Najaf:

If you are using the local DHCP server the DHCP proxy must be enabled. You should not disable it if you are using the local DHCP server.

"You must enable DHCP proxy on the controller to allow the internal DHCP server to function"

http://tiny.cc/on1hpw

Make sure that you use Cisco lightweight APs, not any other kind of APs that you need it to use the internal DHCP. Make sure DHCP Proxy is enabled.

Also make sure you put the management IP address as the DHCP address in the management interface. The APs must reach the management interface in order to take the IP. The Management interface should be configured correctly for the correct VLAN. ( I can see you are using now the default vlan (untagged) as the management vlan. right?).

HTH

Amjad

Rating useful replies is more useful than saying "Thank you"

[kcnajaf]

Hi Amjad,

I'm with you.

But looks like you have not noticed the last statment on ERIC's post. He was saying "DHCP server is Infoblox" which is as external dhcp server as far as I know.

And my suggestion of disabling the DHCP proxy was based on ERIC's posting which says DHCP server is an External Server and Not Internal one.

Hope that make sense.

Regards

Najaf

[George Stefanick]

NOTE!

If you disable proxy you NEED to put a ip helper pointing to the DHCP server on the SVI.

__________________________________________________________________________________________
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
__________________________________________________________________________________________
‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."

[#6]

I want thanks everyone's input on this request.

This issue has been resolved. I am using AP 3600 and WLC 5508 with 7.2.110. There is nothing wrong with WLC configuration. The solution of this issue is I have to console to the AP and assign a static IP address on interface BVI. After image upgrade, AP rebooted and got a DHCP IP address.

The 10 APs I bought in Singapore had this problem. I never ran into this issue in US and Europe.

Sent from Cisco Technical Support iPad App