DHCP behavor

athan1234
A model citizen

DHCP behavor

Dear all:
 
  
I was observingone of my clients client He  has a DHCP problem; 

no_offers_received, vap: 0, vlan: 1

 

Searching on meraki forum I found  this post :

VLAN/DHCP Issue - The Meraki Community

 

As I read it, my suspicions grew.
 
I try to describe the client topology, but I'm not sure if it will be the issue.
 
athan1234_0-1664207695017.png

 

athan1234_1-1664207853609.pngathan1234_2-1664207888915.png

 

athan1234_3-1664207971460.png

 

 
Is it possible that the native vlan was the cause of the issue for any reason?  maybe the  way to configure this clients is not the best way to do it .
 
Best 

 

7 Replies 7
ww
Kind of a big deal
Kind of a big deal

I dont really see a config issue

Is that logging from mx or mr event log?

Is i just 1 client having issues?

athan1234
A model citizen

Hi sorry for my delay response 

 

I get again the same error 

 

athan1234_0-1664883680484.png

athan1234_1-1664883871106.png

 

RaphaelL
Kind of a big deal
Kind of a big deal

You are having DHCP errors on vlan '1' but you did configure vlan 1 to not respond to DHCP request.

athan1234
A model citizen

Yes I know , Why does  that behavor ?

RaphaelL
Kind of a big deal
Kind of a big deal

You have a configuration that allows a client to do DHCP requests on vlan 1. 

 

Your configuration on Vlan 1 is set to : Do not respond to DHCP requests.

Take a packet capture , you will find the client that is doing DHCP requests on vlan 1 and you will be able to trace back the configuration.

athan1234
A model citizen

Thanks for your reply 

How is it possible that someone requested that DHCP be turned off for Vlan 1? 

 

The same  organitation behavior but a different  network 

athan1234_0-1664895754381.png

 

athan1234_1-1664895818785.png

 

 

 

 

 

RaphaelL
Kind of a big deal
Kind of a big deal

If your configurations are 100000% correct AND the logs are on the MR and you are running something above MR28.X I suggest opening a case. 

 

I have one opened for months which suggest that it is a known bug but seems to lack traction to get fixed.

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