Meraki is still working on this issue. Ticket / case is in work. ... View more

As stated by @RaphaelL L3 rules based on FQDN will break as they rely on snooping client DNS traffic. https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/MX_Firewall_Settings#FQDN_Support   L7 firewall rules and content filtering will work based on the destination IP of the client's traffic.l However you will lose L7 firewall rule enforcement based on client DNS lookup (where the MX blocks the actual DNS request due to an L7 firewall rule match) ... View more

For MX68's, since not very long you can see what client is connected to what MX68 port in the Clients overview. ... View more

Not trying to necro a post, but I came across this thread trying to figure out an XXX result that we received from a cable test on pair 2 when troubleshooting a device not connecting to the switch and this post was the only reference I found to it. I contacted support, and they gave me the following answer: "XXX means pair 2 are failed to report voltage for unknown reason." Hope this helps if anyone else comes across this. We're pretty sure the contractor installed two bad cables (the other one shows open on pair 4, so we have to force it onto 100Mbps), so we believe the result is likely accurate. ... View more

Good catch, thanks for sharing! ... View more

Its Webinterface.  ... View more

Very interesting... We also have a similar issue. We are adding an MX 67 on our spokes that goes over AutoVPN to our DC and it only happened a few times in the beginning, but now with every migration of adding an MX 67 to a spoke for SD-WAN, we need to reboot our MX.  We are also connecting to a Fritzbox and most of the time it is the 7590. We just passed the 100 mark for migrations, but our issue is with the CAP WAP traffic of Cisco AP's that do not want to show up on WLC (Flex Connect) and the only option at the moment to fix this is to reboot MX then it is fixed.  We do have an open case with Meraki and they have no clue why it is, but we can see that the UDP port is changed when it comes back to the spoke. I am going to check the firmware of the Fritzbox and see if this is related.  ... View more

Unless you are actively blocking those currently, which sounds unlikely baed on your question then you should not have to do anything except ensure anything upstream from your network is not blocking.   Short answer: no need to do anything in most cases.  Those who need to make changes would know how and where.   ... View more

There will be no perceivable impact. ... View more

If you look at the client page and add the port column, you will see for many MXs that the port shown is indeed N+1.  Therefore port 2 is the labelled port 3 as @alemabrahao stated.  Try on your network and this will confirm it for you, but it is definitely the case for an MX75. ... View more

Is there a web site available where i can input the serial no. of the MS120-8LP and see if my power supply is affected?  Appearently this is possible for Meraki engineers if i read this article, but we have approx 3000 of these in the field.   https://documentation.meraki.com/General_Administration/Support/MS120-8LP-HW_Power_Supply_Proactive_Replacement_Overview_and_FAQ   I also would like to know if there is any risk on: - firehazard - safety of users  - safety of connected equipment on the switchports - is there any risc of the MS120-8LP switch being damaged?   ... View more

Opened a case. The response i got back from Meraki is that:  - there is no switch ASIC in these MX68 / MX65 devices, and therefore these options are not available - this is also not possible using API   Best i could do was to submit a feature request..Did that.   ... View more

The last part of the doc is actually incorrect. You don't need to unbind anything to add a MG into a bound network. Steps to get it done are this. I also created a video walking through it.   1. Ensure your template supports the MG device type which is outlined in this section of the doc. More recently created combined templates should already have MG, MV, MT device groups in them. 2. Create new MG network 3. Bind that MG network to your template (requires step 1 to be completed) 4. Optional, combine the previous MX, MS, MR network with the new MG network into one bound combined network ... View more

Thanks for your extensive answer!   We are already testing and punching holes in the firewall , using the developer tools.  Will update this topic.   ... View more

I wouldn't hold my breath for that (please note that this is just my personal opinion) ... View more

If we already have the CMNO will the badge be updated to ECMS1? ... View more

Aha!  Can't wait to get my green socks! ... View more

Ye 10GTek is working well on mine MS225-48LP. Even the 10 Gig copper SFP from 10GTek is working (Cisco has no 10 Gig copper SFP!). ... View more

@AlexC Do I need to unsubscribe from every organization manually one by one? ... View more

Ha, I would be so glad if I could configure it manually at all -- not to dream of a template... ... View more

I would ask your Cisco reseller for a free trial to be sent to one of the sites.  If it works you can just pay for it and keep it.  It seems very unlikely for an ISP to be blocking Meraki.     ... View more

Thanks,  I would have to reproduce the issue then, and with that make work impossible for 300+ employees.  That's not an option.   I had hoped someone would step in with similar experiences and explanation for the same circumstances en enviroment.   Thanks anyway for the responses ... View more