NO DHCP response' associated

[celma972]

Dear  All,

I am seeing frequently the following message on my meraki  dashboard event log :

client made a request to the DHCP server, but it did not respond

Client attempted to associate 265 times on the 2.4 GHz band

The AP are MR33 firwmware version 28.1

There are two SSID VLAN :

- VLAN 1 is for datas and is used by RF Android scanner devices.

- VLAN 2 is used for voice by client devices with Android Crosscall smarphone 

VLAN 1 and VLAN 2 subnets are not the same

DHCP server for both subnets is a Windows 2016 server. It is on VLAN 1.

routing between subnet is working.  

Scanner devices connected to VLAN 1 are getting  DHCP IP from VLAN 1

Voice devices connected to VLAN 2  are getting a DHCP IP from VLAN  2

there are 33 AP MR33. So, the client devices are roaming.

Do you know how can I fix that ?

Do you know how can I setup on a cisco L3 switch that VLAN 2 will be voice only nothing else, is it possible?

I set this command 

switchport voice vlan

but I am not sure if it prohibit datas flow. 

Thks in advance

[Bruce]

The port that connects to the AP should be configured as a trunk port and you should allow VLAN 1, VLAN 2, and whatever VLAN your AP is using for management (if it’s not VLAN 1). There really isn’t a way to restrict a VLAN to just voice traffic, it all depends what devices you permit to connect to that VLAN/SSID (you technically could use access-lists, but it’s not pretty). What are you trying to achieve?

With regards to DHCP, the devices connecting to the SSID on VLAN 1 really shouldn’t have a problem if the server is in the same VLAN. For VLAN 2 you need to configure a DHCP relay on the Layer 3 interface, the ‘vlan’ interface, on the switch - in IOS this is the ‘ip helper-address’.

Hope this helps.

[celma972]

Hi Bruce,

Trunk and ip helper-address are setup already. 

VLAN 2 clients and VLAN 1 clients are receiving DHCP ip addresses.

But I am still seeing on the meraki dashboard logs :

client made a request to the DHCP server, but it did not respond

Client attempted to associate 265 times on the 2.4 GHz band

Can this be a result of roaming between AP, bad coverage, etc....?

Thks