"This device is using a DHCP IP address from VLAN instead of using configured VLAN"

[dstrejo]

Hi community,

I could not find much info on this topic and therefore I am posting it here to see if somebody can help me with it. I am quite new to Meraki so it might be the case I am missing a silly config.

Problem: 
I am working on a lab (MX -> MS -> MR) and for the sake of testing I have changed the default VLAN to VLAN 99 and the dashboard shows the warning from the subject on the MR33. "This device is using a DHCP IP address from VLAN instead of using configured VLAN"

Steps:
I have applied this config on the MX and MS as well and the only device showing the warning is the MR although I have also set here the IP type to "DHCP" and VLAN to 99.

On the MS I have adjusted it in the section "Switch settings -> VLAN configuration" and on the port itself too. And finally I also configured it on the port from the MX on the "Addressing and VLANs" tab. 

ps: The AP has received an IP from the pool in VLAN 99. 

Thanks for your time!

[Mloraditch · Accepted solution]

For APs if the port they are connected to is native or access mode on the VLAN you want them to receive DHCP from you do not need to specify the VLAN on the individual APs IP settings.  I suspect that's your issue.

[dstrejo]

Thanks for the prompt and accurate reply! that was the issue. After removing the VLAN from the AP, it worked. 

[AlexL1]

Hi dstrejo,

This seems to be very common issue.

For future reference I would like to highlight the following documentations - https://documentation.meraki.com/MR/Monitoring_and_Reporting/Understanding_and_Configuring_Managemen...

More detail explanation with examples - https://documentation.meraki.com/MR/Client_Addressing_and_Bridging/VLAN_Tagging_on_MR_Access_Points

In  general, Meraki APs have two types of traffic:

• Their own management traffic (Management VLAN) - any Cisco Meraki device will send upstream to the cloud controller - that's the IP address of the AP's Summary page (under Wireless > Monitor > Access Points > (AP's name)). It is important to ensure that the MR's traffic will be put on the appropriate VLAN, typically a dedicated management VLAN for cloud-bound traffic.
• Client traffic - When client devices connect to the SSID(s) either when you have a network with multiple VLANs or one VLAN different than the Management VLAN.

Point 1 - If a native VLAN is configured on an upstream 802.1Q trunk port, then ensure the access point's VLAN tag is not the same VLAN ID as the Native VLAN. Specifying the same VLAN ID would tell the access point to tag its management traffic with that VLAN ID, which would likely cause it to be dropped by the upstream trunk port.

Point 2 -  If a VLAN ID is specified, management traffic from the AP will be sent out with an 802.1q tag for that VLAN ID. In this case it is expected that return Management traffic should also be tagged appropriately. VLAN IDs can be configured so that the management interface of a MR gets an IP on a specific VLAN.

Point 3 - If a VLAN ID is NOT specified, management traffic from the AP will be sent out without an 802.1q tag for that VLAN ID. When the VLAN field it's empty, that DOES NOT mean that the AP won't receive an IP address, it means that the switchport native VLAN control what the Management VLAN is.

Point 4 - If SSIDs are not tagging specific VLANs, then the Management VLAN will also be used for client traffic.

This error message is for APs - This device is using a DHCP IP address from VLAN instead of using configured VLAN", which is similar for MS switches - https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Network_Alerts_and_No...

If you have more questions, please don't hesitate to contact us.