We just purchased a large amount if Meraki gear for 3 different locations. I am in the process of learning the "Meraki" way, and really struggling. I come from a full Cisco shop, and only used to the CLI, so not having that is different. Our current setup are really, really old Cisco 2950s that run a flat vlan1 😞 We are moving that over to full Meraki with correct vlans. I am trying to pre-build as many Meraki switches as I can, so that when it comes time to install we have little down time. My issue is getting MGMT vlan working. I can get it working on vlan1, but that vlan will not exist Below are screenshots of what I have. Technically the transit vlan86 is going to my current core XR, which then defaults out to FTD for inet. This is how I am able to pre-build my vlan87 for MGMT and still connect to the Dashboard. when we install. I have a MS-250 switch that will be my new stacked core. This will have all my SVIs on it including a transit vlan to FTD. My issue is this new core MS-250 switch has DHCP enabled for my new MGMT vlan 87, and a downstream Meraki switch will grab an IP as it should, and I can see it in the dashboard. What I can't see is this core MS-250 switch.... I have globally set management to vlan 87, and on each switch told it to use DHCP in vlan 87. Only a downstream switch grabs and IP. How do I get the core switch to get an IP? I tried to static it, but the gateway would be itself and doesn't work. My default route works which is my new transit vlan. If it didn't then the downstream switch would never come online and it does. I have tried switching the trunk links from native 87, to no native at all, and can never get this core switch to come online. I am just confused at how the management vlan for Meraki works at the first switch. I am soooo close to not letting Meraki be the core switch and keeping my stacked XRs the core, but defeats my goal of all Meraki....
... View more
