My original question can be modified to say "USB" instead of "built-in." The question then is, can the uplink labeled "WAN 3" and the one labeled "Cellular" be enabled on the same MX, and if so, does WAN 3 take precedence? And if uplinks WAN 1, 2, and 3 are all down, would the MX then fail over to "Cellular"? ... View more

So just to clarify: does this mean that all MX models show "Cellular" in the GUI, but on some models this field indicates built-in cellular, and on other models it just refers to the historical USB port? ... View more

The Sydney MX75 used in dCloud Meraki Launchpad shows a Cellular port in the GUI, in addition to the WAN 3 port.   ... View more

If an MX has this third uplink enabled, AND the built-in cellular enabled, which takes precedence? As always, the documentation is extremely lacking. The documentation page for this feature is very small:   https://documentation.meraki.com/MX/MultiWAN_Backup_Uplink There is not a single mention of how (or if) the two backup ports (cellular, and the new "third port") behave together. ... View more

In the Meraki dashboard, you can view and configure all of the switchports in a network in a single list. That is just how the GUI is designed. This design is called "virtual stacking." It is not actually stacking at all. It's just a marketing term for the GUI design, having all the ports in one list. This feature is automatically always-on, for all switches. Virtual stacking does not have members or non-members, and it is not an operating mode of the switches. It is simply a characteristic of the GUI. Any time you go into the Switchports page of a network, and see all of the ports in that network showing up on that page, that's what "virtual switching" is. It is a GUI feature that allows you to view and configure all of the ports in a network, from the same GUI page. All of the ports in the entire network are presented in a single list. Virtual stacking does not include any stacking functionality, nor does it have the concept of switches being members or non-members. ... View more

The data sheet does say that, but it also says that both models have the same stacking hardware. which is two 40g ports. Switch vendors sometimes list bandwidth numbers in their marketing as doubled, for example, counting each 10g port as 20g, because it is full duplex, and 10g in each direction is 20g. It seems that they are doing that for the MS350, counting the two 40g ports as 80g each, for a total of 160g. Is this the case, or is there some other way that the MS350 can provide 160g of stacking with two 40g ports? ... View more

Thanks, that was what I missed. In my GUI, the "unique" button is right under the "Dual Stack Config" label, so I overlooked it, thinking it was some IPv6-related setting. ... View more

Okay, mystery solved. I see what I was missing. The WAN IP address is not on the "Configure > Addressing & VLANs" page, it's on the "Monitor > Appliance Status" page. In fact, there are a lot of configuration settings that are under Monitor rather than Configure. So, when VLANs mode is not enabled, there must be two internal VLANs not visible to the customer, one for the WAN side and one for the LAN side.  ... View more

How is the MX able to route between LAN and WAN if it only has one IP address?  ... View more

I know that the MX needs static routes. But with VLANs mode enabled, requiring static routes on the L3 switches (or other neighboring routers) is the part that sounds crazy. Why does turning on VLANs disable the outbound OSPF, forcing the customer to either type static routes on the other devices for all the subnets learned via Auto-VPN, or use the MX as the default gateway for all traffic.  And the second part of my question is, if the MX is in Single LAN mode, doesn't that disable the routing function? How is that still considered Routed mode, if the MX has only one IP address in one subnet?  ... View more

It's clearly a typo for the word "deprecated." ... View more