This device is using a dhcp ip address from vlan 0 instead of using configured vlan 1. Jul 19, 2018 · Hello, I am receiving a message on my access point containing the following. 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. I noticed this first when a laptop reported no network connectivity, but upon closer inspection noticed that it did get IP, network mask, DHCP, and DNS info from the DHCP server, but from another VLAN. " is displayed on the AP dash board. However, when the VLAN is set to 20, while the AP gets a proper management IP address, the SSIDs stop Nov 21, 2022 · Hello, I am experiencing a problem that has been existing for a while so far, Well, the issue is that 1~10% of the endpoints when attempt to connect to the SSID, it fails obtain IP address, and it shows on Meraki dashboard (DHCP server did not response), while DHCP server is responding and able to p. An incorrect static IP is assigned to the hardware, and it reverted to DHCP as a backup. Nov 4, 2003 · On each router interface (vlan) you need to configure an "ip helper" address that points to a dhcp server, so the router can redirect dhcp discovers to the correct server - unless the dhcp server exists in the same vlan as the dhcp client. The alert is caused when: A VLAN tag is set for DHCP, and DHCP IP assignment fails with that VLAN. Jul 28, 2023 · The Core have SVI on Vlan 1 and have IP helper-address pointing to DHCP server which is connected to the Core. I am getting the message "This device is using a DHCP IP address from VLAN 0 instead of using configured VLAN 1. If you connect your laptop to the core directly in one interface on vlan 1, do you face the same problem? Sep 12, 2023 · 1 Some devices (printers and laptops) that are moved to another building with a different VLAN will not release the IP address assigned. If I set the Native VLAN to 20, they get a 172. " when I access the access point from the Meraki dashboard. When there is an IP addressing issue, a Meraki Go device will attempt to find another working IP address via DHCP on other networks (or VLANs). All of this is entirely expected and predictable. The connectivity bar color is the yellow/brown color. "This device is using a DHCP IP address from VLAN 0 instead of using configured VLAN 1. Aug 15, 2022 · I have a MR44 connected to a C3560CX that keeps alerting a DHCP IP and VLAN issue, even though both the device and the trunk port are set to VLAN 250 and neither 0 nor 1 are being used. 1Q trunk port, then ensure the access point's VLAN tag is not the same VLAN ID as the Native VLAN. May 22, 2023 · HI all, With Meraki support's advice, I managed to solve the issue. May 20, 2023 · This device is using a DHCP IP address from VLAN 0 instead of using configured VLAN 1 Solved Jan 30, 2025 · "This device is using a DHCP IP address from VLAN 0 instead of using configured VLAN 1. Wireless > Access Point, on AP's LAN IP tab, set the type to "DHCP" and the important part is to leave the "VLAN" field empty!! Mar 4, 2025 · Point 1 - If a native VLAN is configured on an upstream 802. Jun 21, 2018 · "This device is using a DHCP IP address from VLAN 0 instead of using configured VLAN 1. " Oct 10, 2019 · When I set Native VLAN on the upstream port to VLAN 1, the APs get a 192 address (default for that vlan on the meraki dhcp server). 20 address. ezi sfstb ejspwee xwtm aoqf eohdwm zzap cjhnah rzliyic herc