cancel
Showing results for 
Search instead for 
Did you mean: 

Native VLAN, Management VLAN, shouldn't be this messy...

Native VLAN, Management VLAN, shouldn't be this messy...

spurgelaurels
New Contributor II

I'm really confused about this. 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). If I set the Native VLAN to 20, they get a 172.20 address. All of this is entirely expected and predictable.

 

However, when the VLAN is set to 20, while the AP gets a proper management IP address, the SSIDs stop loading.

 

And if that's not confusing enough, AP-FRONT has a static IP on the DHCP server in VLAN 20 which works fine and can be pinged. AP-OFFICE however is fully dynamic and gets thrown into VLAN 1, while both devices have the same configuration all the way from the SVI to the firewall port.

 

Screenshots below

 

 

 

List of APs from the perspective of my Meraki MX65 (also DHCP server for all VLANs)

9bc8369ed7a443a6816d59f3e0995be1_0690c000008ujXSAAY.png

 

AP-OFFICE configuration (device level)2019-10-10-10:11:40

 

AP-FRONT configuration (device level) 2019-10-10-10:12:29

 

 

 

Trunk VLAN assignments on the upstream MX65 (APs are plugged into 11 and 12) 2019-10-10-10:13:03

1 ACCEPTED SOLUTION

spurgelaurels
New Contributor II

RIGHT, so I don't know why this is working now, but I changed the MGT VLAN to 1, did a full config update, set it back to 20, did a full config update.

 

 

8f0114ae49064099ae17963404af158e_0690c000008ujxkAAA.png

View solution in original post

7 REPLIES 7

ashley_finch
Contributor III

What happens when you do a 'interface mgt0 vlan 20' on the AP-Office CLI? Anything at all or does it just revert back to a 192 after a while?

spurgelaurels
New Contributor II

RIGHT, so I don't know why this is working now, but I changed the MGT VLAN to 1, did a full config update, set it back to 20, did a full config update.

 

 

8f0114ae49064099ae17963404af158e_0690c000008ujxkAAA.png

spurgelaurels
New Contributor II

AND just for fun, I configured the IP for AP-OFFICE to be static and set to 172.20.0.3

Reboots and stuff later, it's still grabbing a 192 IP address.

 

I'm feeling like this machine isn't taking the MGT VLAN properly.

spurgelaurels
New Contributor II

FROM AP-FRONT

sho int mgt0

Admin state=enabled; Operational state=up;

DHCP client=enabled;

Default IP subnet=192.168.0.0/255.255.0.0;

IP addr=172.20.0.2; Netmask=255.255.254.0; Default Gateway:172.20.0.1;

IPV6 address autoconfig enable

IPV6 link local addr=fe80::8a5b:ddff:fe51:bc40/64

VLAN id=20; Native vlan id=1;

MAC addr=885b:dd51:bc40; MTU=1500;

Rx packets=146708; errors=0; dropped=0;

Tx packets= 83672; errors=0; dropped=0;

Rx bytes=24083161 (22.967 MB); Tx bytes=17667983 (16.850 MB);

AP-FRONT#

 

 

 

FROM AP-OFFICE:

AP-OFFICE#sho int mgt0

Admin state=enabled; Operational state=up;

DHCP client=enabled;

Default IP subnet=192.168.0.0/255.255.0.0;

IP addr=192.168.1.247; Netmask=255.255.255.0; Default Gateway:192.168.1.1;

VLAN id=1; Native vlan id=1;

MAC addr=e01c:413f:f700; MTU=1500;

Rx packets=3278; errors=0; dropped=0;

Tx packets=2032; errors=0; dropped=0;

Rx bytes=840637 (820.935 KB); Tx bytes=484928 (473.562 KB);

GTM-P2G8KFN