Hi There Just wondering if someone could confirm is the below topology is supported. I have a client with 2 Independent ISP circuits delivered as /31s public ranges Circuit 1 is on a 10Gb Bearer capped at 2Gb/s and Circuit 2 is a 1Gb bearer @1Gbs Looking at the HA guide MX_Warm_Spare_-_High_Availability_Pair I cannot see anywhere where is specifies that the interfaces need to match on the MXs configured as a HA pair (unless I missed it). Only that VRRP is required across the LAN Based on this, as only one circuit runs at 10Gb, could I use 1Gb Fibre, or indeed even 1Gb Copper for connectivity (LAN/WAN or both) for the Warm Spare firewall, as the ISP uplink is only 1Gb.     Obviously aware that a better approach would be 2 X /29 with WAN switches, to allow 2 X VIP sharing across both ISPs, but for now this is not in scope. Appreciate any comments, thanks ... View more

Hi There I have a client who will be provided with 3 Stacks of 3 x C9300-48T-M switches. (9 Switches in total). There is a 2 week delay in the devices arriving. So far I have only claimed the devices in the dashboard and assigned to a network. Based on Meraki documentation (Stacking Catalyst (MS390s / C9300-M / C9300X-M) below, it recommends to physically connect the stack with devices powered off, then provide an uplink from one switch to for internet access. https://documentation.meraki.com/MS/Stacking/Switch_Stacks I was wondering what configuration I could pre-stage for instance I want to create SVIs, Routing, DHCP scopes etc, however when attempting to do this the dashboard I need to specify a switch stack, which I is not yet provisioned based on the recommendation I was wondering if it's possible to manually provision stack for these models of switches, which should allow me to preconfigure the network. If anyone has any experience or advice it would be appreciated. Thanks ... View more

Hello All   I'm in the process of replacing a customer's existing network (Cisco Catalyst 2960x switches), which has QoS enabled. We are migrating to Catalyst 9300M switches. I'll discuss with the customer about their QoS requirements (if indeed required at all) as I suspect the configuration was in place when WAN links were much lower in terms of bandwidth.   I've read some great articles on this forum relating to QoS on the MS platform (see below links).  https://community.meraki.com/t5/Security-SD-WAN/Meraki-MS-QoS-behavior-question/m-p/203036 https://community.meraki.com/t5/Switching/Recommended-QOS-settings/m-p/206113   From what I gather the Meraki MS provides a much more simplified QoS offering. I just want to ensure I am correct , in my assumption as the Meraki Documentation is rather limited. 1. To enable QoS I have to specifically configure vlan(s) via the below setting.   Switch > Configure > Switch settings. Find the section Quality of service.  Click Add a QoS rule for this network   This allows me to trust the DSCP values on the specific traffic, and/or set the DSCP value if required. By performing the above step I am automatically saying "I want to apply QoS to this traffic"   I get the DSCP to CoS mapping and also the associated CoS to Weight x 6, configurable queues. What I can't seem to find is anything to say under what conditions QoS is applied to a link/interface. In "traditional" Cisco platforms QoS only kicked in (excluding policing, shaping) when the interface was congested, assume Meraki operates in a similar manner? Is below the only Meraki documentation on QoS for the MS switches.   Meraki Documentation   https://documentation.meraki.com/MS/Other_Topics/QoS_(Quality_of_Service) https://documentation.meraki.com/MS/Other_Topics/MS_Switch_Quality_of_Service_Defined   Thanks   ... View more

Hello All   I have inherited a poorly designed non Meraki LAN and a failed migration attempt from a FortiGate Firewall to an MX 85 Appliance. The Failure was due to DHCP clients (VLAN10) were were no longer getting IP addresses from the DHCP server on VLAN 30. The attached diagram displays the LAN setup. The MX essentially replaced the FortiGate with equivalent configuration in terms of routing, and LAN IP address fw rules etc. As per diagram an IP-Helper is set up on vlan10, directing the DHCP requests to the server on VLAN30, 192.168.30.250. I believe the Issue is related to the poorly implemented routing, whereby the return DHCP traffic from the server routes via the Firewall (192.168.30.1) instead of the L3 Switch. The question I have is that this setup worked with the FortiGate, albeit sub-optimal. Does anyone know how the MX would handle the traffic. Unfortunately this migration was carried out before my time and there is no info in terms of packet captures/troubleshooting info. For info there are no firewall rules configured on MX, just the default Any to Any and there is a route for the 192.168.10.0/24 subnet on the MX via L3 switch address 192.168.30.254   Can anyone confirm/suggest if this setup should work as per diagram? Obviously I intend to fix the routing issue and have the L3 switch as GW for all local VLANs and create a transit vlan for WAN egress/ingress traffic.  Any help appreciated Thanks ... View more