@PhilipDAth I've actually been really impressed with the accuracy of the immediate readings.  I have the MT10 sat next to a sensor for a weather station and so far each time I've checked they are within 0.1°C down to -1°C so far.   Unfortunately as there isn't a calibration certificate I may just have got lucky... ... View more

On the site where the MX is being the internet for the management traffic, connect the MPLS to the LAN and connect the internet to the WAN.  It won't be part of the auto VPN so works better that way. ... View more

@NolanHerring after @KarstenI 's post I just upgraded all our sites and they seem to be working okay.  At the moment we have hardly any traffic so cannot be 100% sure that there aren't some issues but I'm planning to go to a mixed site next week and will do some testing to confirm that there aren't issues. ... View more

Maintaining fewer major releases is easier I guess 😉 ... View more

We use MXs for almost all of our public WiFi provision as well, it is excellent as you don't need to get to the "management interface" that most firewalls have either on a physical port or mapped to an internal interface.  Soooo much better than the ASAs we have moved away from. ... View more

Just following up to provide some snippets of my actual config file, here's how I have it configured (generalized for privacy). Also, if there's any way to clean this all up, any input is much appreciated. I am a novice with Linux and even more-so with syslog-ng.     #define syslog source -- a.b.c.d in this section referring to the syslog server. #source s_net { udp(ip(0.0.0.0) port(514)); }; #source s_net { tcp(ip(0.0.0.0) port(514) max-connections (5000)); udp(); }; source s_net { udp(ip(a.b.c.d) port(514)); }; source s_meraki_flfw { udp(ip(a.b.c.d) port (514)); }; source s_meraki_cafw { udp(ip(a.b.c.d) port (514)); }; source s_meraki_cofw { udp(ip(a.b.c.d) port (514)); }; source s_meraki_gafw { udp(ip(a.b.c.d) port (514)); }; source s_meraki_mnfw { udp(ip(a.b.c.d) port (514)); };   #filtering filter f_meraki_vmx100_urls { host(x.x.x.x) and match("urls" value ("MESSAGE")); }; filter f_meraki_vmx100_flows { host(x.x.x.x) and match("flows" value ("MESSAGE")); }; filter f_meraki_flfw_flows { host(x.x.x.x) and match("flows" value ("MESSAGE")); }; filter f_meraki_flfw_urls { host(x.x.x.x) and match("urls" value ("MESSAGE")); }; filter f_meraki_cafw_flows { host(x.x.x.x) and match("flows" value ("MESSAGE")); }; filter f_meraki_cafw_urls { host(x.x.x.x) and match("urls" value ("MESSAGE")); }; filter f_meraki_cofw_flows { host(x.x.x.x) and match("flows" value ("MESSAGE")); }; filter f_meraki_cofw_urls { host(x.x.x.x) and match("urls" value ("MESSAGE")); }; filter f_meraki_gafw_flows { host(x.x.x.x) and match("flows" value ("MESSAGE")); }; filter f_meraki_gafw_urls { host(x.x.x.x) and match("urls" value ("MESSAGE")); }; filter f_meraki_mnfw_flows { host(x.x.x.x) and match("flows" value ("MESSAGE")); }; filter f_meraki_mnfw_urls { host(x.x.x.x) and match("urls" value ("MESSAGE")); };   #destination files destination df_meraki_vmx100_urls { file("/var/log/meraki_urls.log"); }; destination df_meraki_vmx100_flows { file("/var/log/meraki_flows.log"); }; destination meraki_flfw_flows {file("/var/log/firewalls/meraki/flfw/mx_flows.log"); }; destination meraki_flfw_urls {file("/var/log/firewalls/meraki/flfw/mx_urls.log"); }; destination meraki_cafw_flows {file("/var/log/firewalls/meraki/cafw/mx_flows.log"); }; destination meraki_cafw_urls {file("/var/log/firewalls/meraki/cafw/mx_urls.log"); }; destination meraki_cofw_flows {file("/var/log/firewalls/meraki/cofw/mx_flows.log"); }; destination meraki_cofw_urls {file("/var/log/firewalls/meraki/cofw/mx_urls.log"); }; destination meraki_gafw_flows {file("/var/log/firewalls/meraki/gafw/mx_flows.log"); }; destination meraki_gafw_urls {file("/var/log/firewalls/meraki/gafw/mx_urls.log"); }; destination meraki_mnfw_flows {file("/var/log/firewalls/meraki/mnfw/mx_flows.log"); }; destination meraki_mnfw_urls {file("/var/log/firewalls/meraki/mnfw/mx_urls.log"); };   #bundle source, filter & destination rules log { source ( s_net ); filter( f_meraki_vmx100_urls ); destination ( df_meraki_vmx100_urls ); }; log { source ( s_net ); filter( f_meraki_vmx100_flows ); destination ( df_meraki_vmx100_flows ); }; log { source ( s_meraki_flfw); filter( f_meraki_flfw_flows); destination ( meraki_flfw_flows ); }; log { source ( s_meraki_flfw); filter( f_meraki_flfw_urls); destination ( meraki_flfw_urls ); }; log { source ( s_meraki_cafw); filter( f_meraki_cafw_flows); destination ( meraki_cafw_flows ); }; log { source ( s_meraki_cafw); filter( f_meraki_cafw_urls); destination ( meraki_cafw_urls ); }; log { source ( s_meraki_cofw); filter( f_meraki_cofw_flows); destination ( meraki_cofw_flows ); }; log { source ( s_meraki_cofw); filter( f_meraki_cofw_urls); destination ( meraki_cofw_urls ); }; log { source ( s_meraki_gafw); filter( f_meraki_gafw_flows); destination ( meraki_gafw_flows ); }; log { source ( s_meraki_gafw); filter( f_meraki_gafw_urls); destination ( meraki_gafw_urls ); }; log { source ( s_meraki_mnfw); filter( f_meraki_mnfw_flows); destination ( meraki_mnfw_flows ); }; log { source ( s_meraki_mnfw); filter( f_meraki_mnfw_urls); destination ( meraki_mnfw_urls ); }; ... View more

connect via mpls, and DIA ... View more

That was an easy one , I'm always having to convert the change logs.    If only we could get something like Cisco ( service timestamps log datetime localtime show-timezone )  ... View more

I won´t buy this switch when issue-list is longer than the feature-list.  😉 ... View more

I still had an issues WiFi  Performance hop from 2 to 3 dots on my iOS and Mac devices on one of my AP.  Also roaming between 2 AP working not as expected. I use 802.11r adaptive since most of my devices came from Apple. I disable client balancing and relay on 802.11r and 802.11v but I don’t see 802.11k. I use wpa2 enterprise network with Cisco Cloud authentication and since half year I see lots of disconnections. Only option is to disable and enable WiFi on clients.  unfortunately Meraki support still can’t resolve this  issue. My devices are 2 MR33, mx67 an ms 220 8 port when I using Ruckus or Extreme Network AP I don’t see this kind of problems  PS. Why Meraki Cloud don’t support WPA3 Enterprise? ... View more

                                                                                 Network Diagram            I think that I'm missing is a failover route at the backup site to redirect Internet traffic to the MX at the MX site or the configuration between Meraki MX or Meraki Switch.   I just add the 10.82.0.0**/16 route to** 10.10.80.1 on MX. Basically it is Wan 2 through Meraki switch Port 23 to ME router to Backup Link.     Backup side   Now on backup side Switch only default route 0.0.0.0 0.0.0.0 10.82.1.X (to Firewall), both ME router (Metro E) use BVI to connect each other. We use switch through Metro E Router connect to Meraki Side when I unplug the internet link from backup side firewall. Then we are not able to ping 8.8.8.8 / 8.8.4.4 and do not have internet access from Meraki side, but able to ping or go to Meraki side MX and MX management side, Switch IP and able to RDP to Meraki side server only. Will that help us to grant internet access (Wan 1), if I set on Flow preferences Internet traffic as Any 10.82.0.0/16 Any 210.x.x.0/29 any Wan 1 ?   I tried to set this setting before. It still not getting internet in backup site from Meraki site.  I think that I may miss the configuration between Meraki MX or Meraki Switch. What do you have any suggestion on that?   ... View more

What is the status of having this fixed? We too have a Cisco L3 core upstream from our MS stacks and trying to find a client from a MAC Address or IP can be very frustrating at times. ... View more

I'd like the MX to do the work if it can? Managing 100's of host files will be cumbersome. Is this not something the Meraki can do? We came from Fortinet and they had this option. ... View more

Hi,   I finally got it properly working. changes I've made: igmp querier and BCC server in same vlan and subnet, Although the latter is not really a hard requirement, but better to do anyhow. More important and very obvious but easy to overlook, disable unknown multicast stream flooding on all switches. 🙂 Tracing shows, clients need to explicitly join the streams and block these when leaving/changing the stream. it is all IGMPv3.   What I do lack is a proper overview of the clients joining particular streams. Meraki is currently the only switch vendor not showing this. I made a request to Meraki to have this incorporated in the Meraki features.   Thanks to all for your feedback ... View more

    It sounds like to me the link is being overloaded and then packets get dropped.   have you tried prioritizing some of the traffic via traffic shaping / QoS.     ... View more

Thank you. I look forward to many more Meraki discussions, boosting my knowledge and sharing it with others.   Congratulations to all other winners. ... View more

@AMackie if you use load balancing for auto VPN the traffic should failover pretty much instantly.  We have circuits go down for planned maintenance regularly and the users at the site don't get Citrix or VDI sessions disconnected and there is no interruption to surveillance live viewing ... View more

I'd look at the dashboard API for that, probably better to post in the API forum. ... View more

I think the edge device might be closing down sessions or similar, we have most of our APs and switches on DHCP and don't have of these problems, our edge devices are either Meraki MXs or Sophos XGs  ... View more

Although they are devices with randomized addresses, they are still real for a time window and can be counted. Is there the possibility to change this default as they provide over in Cisco DNA? ... View more

Seen this ? https://documentation.meraki.com/MS/Monitoring_and_Reporting/Loop_and_MAC_Flap_Detection_on_MS ... View more

That's how I have to handle my environment due to the sheer density of clients we serve, which is a school environment. ... View more

@cmr Well spotted. I actually asked about this 7 -> 5 years thingy from my reps and they told that Meraki is ciscofying the aftersales support timewindow. As you know MR55 was killed very quickly and they still applied "the Meraki way 7 year window" The models EOSd in January 2021 have a "Cisco approach of 5 years". ... View more