topic Re: Native VLAN, Management VLAN, shouldn't be this messy... in Aerohive Migrated Content

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

spurgelaurels — Thu, 10 Oct 2019 21:19:15 GMT

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)

AP-OFFICE configuration (device level)

AP-FRONT configuration (device level)

Trunk VLAN assignments on the upstream MX65 (APs are plugged into 11 and 12)

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

samantha_lynn — Thu, 10 Oct 2019 21:22:59 GMT

Does the DHCP pool for VLAN 20 have an available address for AP-OFFICE? If it does, could you SSH in to AP-OFFICE and run a VLAN probe on the CLI of the AP for VLAN 20? That command will be: int mgt0 dhcp-probe vlan-range 20

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

spurgelaurels — Thu, 10 Oct 2019 21:26:37 GMT

Yeah, there's a whole /23 for that VLAN, and barely 40 hosts on it.

Output:

DHCP Tests performed for VLANs 20-20

Passed VLANs:

20 172.20.0.0/23

Status: complete

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

spurgelaurels — Thu, 10 Oct 2019 21:28:54 GMT

And just for fun, here is some output from the other AP

DHCP Tests performed for VLANs 20-20

Passed VLANs:

20 172.20.0.0/23

Status: complete

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

spurgelaurels — Thu, 10 Oct 2019 21:29:46 GMT

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);

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

spurgelaurels — Thu, 10 Oct 2019 22:10:21 GMT

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.

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

spurgelaurels — Thu, 10 Oct 2019 22:29:14 GMT

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.

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

ashley_finch — Thu, 10 Oct 2019 22:29:38 GMT

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?