VLAN mismatch on edge switch - Design issue?

[MSakr]

Hi All

After adding an MX to our Network, our edge switch stack is showing VLAN mismatch warning between the switch uplink configured on an inside VLAN and used for the switch IP configuration and communication with the dashboard and the edge VLAN needed for our edge appliances (MXs) communication with the ISP equipment.. 

How to solve such an issue, knowing that we cannot assign a public IP for the Edge switches due to lack of available public IPs and mostly even if we had these, for security..

Thanks

[alemabrahao · Accepted solution]

Have you validated whether the native vlan defined on the trunk ports is the same as the one defined for the switch management?

You can also open a support case or call them directly.

[MSakr]

Hi

Strange that the error message doesn't appear all the time, now it disappeared.. 

The Edge VLAN connections are set as access ports.. only the internal management port is set as trunk with a default native VLAN 1 (not set anywhere) but will allow all VLAns

[GIdenJoe]

You should check if there are multiple downstream connections coming from your MX downstream to the switches.
Since the MX just forwards any BPDU or CDP/LLDP message you could run into an issue where another device on a different vlan or with a different trunk port config is reaching your switch this way and then the MS will complain about VLAN mismatch.

[MSakr]

UPD: After reaching out to Meraki support, they mentionned this is a normal temporary behaviour after POST