We are starting to roll out a Meraki installation for our remote stores. I'm working on setting up a switch now and I keep getting this error, "This device is using a DHCP IP address from VLAN instead of using configured VLAN 1." I have DHCP options set in the MX65 the switch is connected to but still no go. Below are some of my configs if you all can help, I'm new to Meraki.
Management VLan setup on MX65
Basically it's telling you that the static IP config you gave it doesn't work, so it fell back to using a DHCP address on VLAN 1 to reach the cloud.
So something's wrong with connectivity on your VLAN 903. Verify that the ports you have connected are configured to carry that VLAN the same way on both sides.
Also, if you're changing the Mgmt VLAN from 1 then you should be changing that in Switch-->Configure-->Switch settings.
Check the upstream port VLAN configuration as well.
I have a couple times, but i checked again. I'm allowing all traffic on my trunk up to the MX65, and on the MX65 down to the MS210 i'm allowing all traffic.
I'm at a complete loss right now.
@jhyoung09 For the switch static IP configuration have you specified VLAN 1?
Also on that MX trunk port you may want to try setting a native VLAN of 1 instead of drop all untagged for testing. You can always tighten it up after you get it working.
I would change the native vlan on both the side to match the management vlan
same error here, nothing has changed (apart from maybe automated firmware updates) - what gives?
You need to configure both ports on the uplink for VLAN 903, if you want the MX, or any Meraki device, to use an IP on VLAN 903. It's not going to be able to use a management IP on VLAN 903 if you don't have any ports configured for it. It found an IP with internet access on VLAN1, (which is the default VLAN, or the same as no VLAN) so it used that.
This error is actually new(er/ish) in later versions of the Meraki software - it will try to find an IP if your settings don't work. Which is what it's done here. Before, in the older versions of the software, you just wouldn't get any traffic at all if it wasn't configured correctly.
When configuring an IP address statically - don't put the VLAN in if the native VLAN is the same as the VLAN with the subnet you want to get an IP address from.
I don't have any problem with the setting that you describe, Fozzy. My native VLAN is also included in the allowed VLANs and it's also the managment VLAN. Static IP set on all devices. It works fine.
Exception being switches from vendor XYZ we have connected to Meraki switches - if you configure the connection as a trunk port, the other vendor switch will not accept having a native VLAN on the connection, so we don't configure a native VLAN on those.
(Vendor XYZ not being traditional Cisco Catalyst switches, if that helps anyone)
Try the following;
1) go to Switch Port,
2) click on the proper port
4) Allow VLAN -> Type the Vlan you need, if this is not clear, type "all"
6) Reboot the Ap
Good Luck! 🙂
We are having the same issue so the AP is showing a down amber state.
We have two APs configured identically, both with DHCP using reservations and not statics. VLANS, trunks and natives all fine and the same. One AP is fine the other is reporting this error DHCP from vlan 0.
This is even though the AP is getting its correct DHCP reserved IP from the correct VLAN.
Tried changing to static and changing vlans etc but no difference.
Confirmed correct settings on both the dashboard and local AP config page.