No, port-channels are not configurable on MX devices. The MX does however pass through STP packets so you can connect 2 cables to the same network. One will be brought down (due to STP loop prevention) but can be used as a backup if the primary connection fails. ... View more

In that case, to keep the network traffic on the Mikrotik switch, you'll need to create a VLAN interface on the Microtik switch for the VLAN's and set it as the default gateway instead.  Otherwise you can connect both the NAS and the client on the same VLAN. In theory you can also  ... View more

For the traffic flow you described, it sounds like the default gateway for VLAN 4 or VLAN 12 (or both) reside on the upstream MX. ... View more

You're bang on that CRC's are a Layer 1 or Layer 2 issue. Most commonly it's dirty/loose/broken cables, or occasionally a bad SFP/switchport. It can also be due to MTU mismatch. If it's a 10Gb fiber link, interference is highly unlikely as fiber is relatively unaffected by RF as opposed to copper. In terms of the consistency in timing, a couple of things to note are:  - Higher CRC counts will generally correlate with higher network traffic (more packets = more likely for one to be corrupted). Is it possible that at these times the link had a higher utilization in general?  - Do you have any scheduled traffic around those times where higher MTU data is being sent (and where a mismatch might be present in the network)? In any circumstance, I would definitely suggest starting with swapping out the cable and continue troubleshooting up the stack from there. ... View more

You won't find an official document as it's 'technically' not supported, but generally speaking Cisco SFP's will work. ... View more

According to Meraki's SFP Datasheet, it is supported (bottom of the first page) meraki_datasheet_sfp.pdf (cisco.com)     ... View more

It's likely that there would be some small performance impact from enabling detailed traffic analysis but I personally haven't noticed anything. That said, my networks have a fair bit of capacity overhead so utilization isn't a noticeable problem.   With basic analysis, you can see the categories of traffic but get no further breakdown. With detailed analysis, you can see a breakdown of classified traffic into destination hostnames/IP's of each flow. An example view of the detailed traffic analysis is in the image in the below link. Switch Traffic Analytics - Cisco Meraki ... View more

Enabling MFA for a user is done in the dashboard by clicking your account name (top right) and going to profile.  To enforce MFA for the organization, go to Organization -> Settings.   As for logging, all event logging for a given network is under Network-Wide -> Event Log. You can then use filters there to narrow down what you're looking for. If you have a specific client in mind, you can also select the client from Network-Wide -> clients and click "event log" or "timeline". Edit: It just occurred to me you we looking specifically at client VPN. Meraki client VPN doesn't natively support MFA but can incorporate 3rd party solutions Two-Factor Authentication - Cisco Meraki The above info about logging is still applicable for VPN connections, you would just filter to event type. ... View more

Ok Perfect. That makes much more sense now. I had an automatic upgrade notification for a different site but it looks like that's because it has an MX75 and is getting moved from an early-stage beta release to a stable release.   Thanks @cmr  ... View more

Adding to @KarstenI 's reply. The firewall rule you've got in the screenshot is for SSH connections initiated inside your network with a destination of 1.2.3.4. It does not apply to SSH connections inbound from 1.2.3.4.   If you have inbound connections from specific IP's that you want to port forward, you can apply them in the port forwarding rule under "Allowed Remote IP's" ... View more

Right, that makes sense. I manually configured an upgrade for the switch and I can see it now set as an option. The remaining question is: With the current configuration, will the switch and MX be automatically upgraded if I leave them? I would have expected the MX to have automatically upgraded by now since the stable release available is from August.   ... View more

For Meraki switches, the different models generally coincide with features and port speed.  So which model you opt for generally depends on your architecture and need for various features. MS12x are perfectly suitable for L2 switching with no frills. MS2xx introduce physical stacking and routing MS3xx and MS4xx move into higher bandwidth and multigig territory https://meraki.cisco.com/product-collateral/ms-family-datasheet/?file   Within the models, you also need to look at the different amounts of power available for PoE+ output to connected AP's.   Generally speaking, your bottlenecks will always be the WAN connection from the MX rather than bandwidth across the switch, so a switch upgrade may not do anything to improve file transfers if they're going cross-site. ... View more

Sounds like what you're looking for is Flow Preferences under "Security & SD WAN" -> "SD WAN &Traffic Shaping". You can set a preferred uplink for specific source/destination flows. MX Load Balancing and Flow Preferences - Cisco Meraki ... View more

I don't think the different MAC address is your issue. Here is an output of my MX64 which is working fine.     As you can see, in the dashboard the MAC address ends in ...:c0 When I do a packet capture on the uplink interface, the MAC address is ...:c5   ... View more

I don't believe it can be changed. It is expected behaviour that the MAC shown on the dashboard will not match the MAC of the interfaces.   Is there a reason you need them to match? ... View more

What you're seeing in the dashboard is expected behaviour. The MAC Address seen in the dashboard is a physical identifier for the device. The MAC addresses of the uplink interfaces are different from this, typically offset by 4 or 5. The following doc describes this behaviour Calculating MX WAN MAC Addresses - Cisco Meraki   As a side note, this behaviour looks to have changed on newer MX models. I have an MX75 in which the dashboard MAC address matches the MAC showing in the connected switch's ARP table. ... View more

If you have a grounding of networking basics, navigating the dashboard is the biggest hurdle you'll face. Once you get accustomed to it, you'll find most things logically.   There's a few Youtube videos which provide a good overview of the dashboard and how to use it. Meraki Dashboard 101: Onboarding - YouTube Cisco Meraki Dashboard overview demonstration - YouTube   Beyond that, I recommend taking some time to get used to where things are laid out in the dashboard. This is especially necessary for firewall rules/ACL's as there's different places where these can be added. Also get to know Network Wide settings and Organisation Wide settings - they're typically where you'll spend the least amount of time, but do hold some key settings that you'll likely need at a later time.   Then when you have a good idea of the specific task you're trying to achieve, the Meraki documentation is typically quite good (Google usually gets you to the right place). ... View more

It sounds like you're talking about the WAN data usage (for if your ISP caps your data usage for example). If that's the case, you can find some data under "Network Wide" -> "Traffic Analysis" and select traffic analytics for your security appliances. Then next to the work "Usage", you'll see the total amount down and up. I'm not sure whether this accounts for SD-WAN tunnelled traffic.       Another interesting yet less elegant way is making a custom pie chart to track internet bound traffic vs internal traffic. It's not elegant but it may work for you. Custom Pie Charts in Meraki – dunxd.com     ... View more

It depends on what specific usage information you're looking for.   MX WAN network usage graph is under "Security & SD-WAN" -> "Appliance Status". This will give you an idea of bandwidth usage going out of the MX Client usage data is under "Network Wide" -> "Clients". This has per application breakdowns and you can drill down per client. Finally, a very handy overview of usage across the network can be found under "Organization" -> "Summary Report"   Each of these graphs defaults to the last day but there is a dropdown to change to data over the past week.   A few reference docs that might lead you further: Clients Usage Page Overview - Cisco Meraki Summary Report Overview - Cisco Meraki Device Utilization - Cisco Meraki ... View more

Sounds like contacting support is the best way to go. ... View more

There's been a couple of similar posts previously. - Solved: MR46 Wont Get DHCP IP, IP Stuck at 0.0.0.0 - The Meraki Community   If you unplug the AP and plug a different device (such as a PC) into that same switch port, does it pull an IP address? If so, try factory resetting the AP and/or opening a support case. ... View more

If the two Windows machines are on the same L2 (VLAN and subnet), it should be a fairly simple flow. What you've described is very typical of Windows firewall (especially Windows server) - blocking all inbound ping requests. For testing, I would disable the firewall completely.   Other than that, I would start by:  - Check ARP on both machines to verify whether they have address resolution for eachother. In cmd, type "arp -a"  and check for the other machine's IP.  - Run up wireshark on both machines and run a ping from one to the other to determine which direction the ping is failing.   From the above tests, you should be able to verify whether the issue is a machine not replying or the switch blocking a ping request/reply. That way you can focus your troubleshooting to the appropriate device. ... View more