MR 36 AP Keeps sending DHCP Discover Requests even after getting a valid DHCP Lease

Solved
GrumpyBug
Conversationalist

MR 36 AP Keeps sending DHCP Discover Requests even after getting a valid DHCP Lease

I've got two Meraki MR36 AP's that boot up and receive their IP addresses and leases just fine. Then, after about 3 minutes, they send out a DHCP Discover Packet, then the DHCP server sends an offer (With the existing IP address), and the transaction goes no further. The Security Appliance (MX75) logs a "DHCP problem-extra: no_offers_received, vap: 0, vlan: 498"

Wireshark capture verifies this behavior.

I've reset the AP's to Mfr Defaults, still getting this behavior.

The AP's otherwise behave normally, and no interruption to WiFi service is observed.

Any thoughts from the Meraki gurus out there?

1 Accepted Solution
GrumpyBug
Conversationalist

Interesting Update -   I had someone suggest trying to set static IP's for the AP's.  As it turns out, I had set them to a static address during initial testing/setup (This is a network begin pre-configured prior to deployment).  Despite being setup for Static - the AP's were still requesting a DHCP address.  I set them to DHCP, and they are no longer misbehaving.

View solution in original post

4 Replies 4
ConnorL
Meraki Employee
Meraki Employee

Hey @GrumpyBug, this is expected behaviour.

 

When an AP is starting up, it'll request an IP via DHCP. Once it has checked in & downloaded its configuration from Dashboard, it'll renew the IP address again (which commonly will result in it being assigned the same IP).

GrumpyBug
Conversationalist

True, and understood.  Problem is that even after booting and getting its address, every two minutes or so, it sends another Discover Request, the server sends its offer, but the AP goes no further - thus causing the problem in the event log.

ConnorL
Meraki Employee
Meraki Employee

Hmm, I'll reach out via DM.

GrumpyBug
Conversationalist

Interesting Update -   I had someone suggest trying to set static IP's for the AP's.  As it turns out, I had set them to a static address during initial testing/setup (This is a network begin pre-configured prior to deployment).  Despite being setup for Static - the AP's were still requesting a DHCP address.  I set them to DHCP, and they are no longer misbehaving.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels