Hi    I'm sorry. Can you elaborate on this part:   I then managed to adjust the routing by modifying the Routing Table in our vNet   Many thanks ... View more

I can share the basics: User > Third-party owned Access > Aruba Core (with multiple MST instances) > LACP Trunk > Meraki Core  ... View more

I plan for this deployment to use the sfp from the MX-105 to my first switch MS-225  and then do a stack of 6 switches in total.  ... View more

Totally agree. ... View more

Not unnecessary if you have pinned firmware for devices @John_on_API Then it would be very valuable to get the per device firmware. Also this is something that should be possible: To have different firmwares for devices in the same network. ... View more

It is also worth to notice that the firmware version displayed in Dashboard doesn't have to be the actual firmware running on the device. It is just what is configured for the Network. If the firmware version displayed on the device page is different from what is displayed in the Firmware Upgrade page, we have to assume it is a UI Bug. ... View more

Meraki runs RSTP which i basically the same as MSTP, only with one instance. If you run MSTP with one instance (default instance 0) and allow vlan 1 on the trunk you should be fine. ... View more

I've used Cisco BIDI SFP (not SFP+) on MS250s before and that worked ok. ... View more

It is a common issue with the MS390 switches (use Google). ... View more

Nolan, All very good points. I will bring these items to our team for consideration. I really like the comparison idea. As for antennas and other products, visit this cost calculator. You can get a short description comparison and see what products, accessories, and licenses are available. https://meraki.cisco.com/product-catalog ... View more

I got word from the low voltage team that they are only setting up 2 IDFs (although there are 3 floors) - Basement and 2nd Floor.  This changes my design...  I am going to Stack the MS225-48LP switches (1 stack per floor)... I am also installing some MS350-24X for the mGig ports for MR56 WAP uplinks - these will be a separate stack per floor...     Since 2 separate switches can be directly connected to the MX with no STP issues, maybe I will go with connecting a core MS350-24X and a core MS225-48LP to the MX...   I will test that out first... but overall, I may just go the easier route.    Thank you all for your input - you all really helped me out. ... View more

What Tore says.  There limitation is the number of VLAN ID's created on the switch not the actual number used. This is because on any switch other than Meraki MS (classic) switches you need to actually "create" a VLAN before it can be used on an access port or allowed through a trunk. Did you ever have a Catalyst switch problem where you allowed a VLAN over a trunk but it just would not appear in the forwarding list because you forgot to create it? If you don't have a big number of VLAN's I suggest you make an explicit VLAN allow list and configure the trunks identical on both sides. ... View more

@GIdenJoe  thanks so much for your quick response. ... View more

MA-CBL-40G is a stacking cable and should be used to stack switches.   The MS450 needs these stacking cables: MA-CBL-100G (MA-CBL-40 i not supported) The MS390 needs these: MA-CBL-120G   In the uplink module ports of the MS390 and the ports on the 450 you would need the approriate SFPs for the fiber cables you need. Typically either SR/LR or MM/SM ... View more

Just my 2c on this. It would be great if Meraki also extended this technology to switch trunking. Auto trunk and LAG inter switch links. That would make the majority of switch connections idiot proof. ... View more

It looks like MS210 and up are good choices to get new features. MS120s sometimes get excluded. ... View more