It was a HA pair for 105s. This is what was being logged. There was no power issues, assumed the box was crashing. It's only passing SD-WAN traffic.    Feb 14 08:01:19 Sterling DC - Primary   Device boot Device boot reason: power event or other   ... View more

Installed 18.208 on a few MX85's with out issues, but the MX105 was a desaster, boxes were unstable and rebooting every 20 minutes or so. Rolled them back to 18.107.2     ... View more

Doesn't show in the event logs, as the layer 7 rules are not logged. Packet capture would show it, if you did it post firewall (i.e. you would not see the packets). ... View more

Too bad the geoblocks are not logged via syslog. ... View more

This was a problem for a couple of our customers with MX's.  So not just an AP issue.   Boy wouldn't be nice if the country blocks would actually be logged. Novel idea, I know.... ... View more

  Ok, on the MX you can't just create a VLAN, like on a switch. You have to create the IP on the vlan interface you create. Use a different IP on the MX then what you virgin router is, say 192.168.255.0/30, and put the MX at 192.168.255.1. On the MX goto the DHCP configuration for the subnet and disable it.   Then just plug your broadband router into one of those ports that are configured for the new vlan and plug in your devices. They should pick up an ip from your router in the 192.168.0.0/24 subnet.    Your clients will not see the MX because the subnet/mask is different.        ... View more

In the portal, goto the addressing & vlans section. Then part way down the page there's Routing, make sure use vlans box is checked.  Click the add vlan button and add a vlan/subnet for your local network.    Once you've added the vlan, goto the Per-port VLAN Settings section of the page, (just below the routing section) Check the boxes for the ports you want to use for your local LAN. Hit the edit button. Set the port type to "access" and set the vlan to the vlan you just created. When done hit the save button at the bottom of the page.    When you pick a subnet for your local LAN you will want to use something that your company does not use.      ... View more

And 12.13 has now been released.   Looks like a  MS390 bug fix is the only change.   Switch firmware versions MS 12.13 changelog Alerts MS210/225/250 switches cannot forward IPv6 Router Advertisement and Neighbor Solicitation packets when flood unknown multicast is disabled (has always been true) Additions Support for MS390 Series Switches Loop Detection on MS210/225/250/350/355/410/420/425/450 series switches MAC Flap Detection on MS210/225/250/350/355/410/420/425/450 series switches MS390 Local Status Page identifies ports on other stack members by name instead of MAC address Features now supported on MS390: RADIUS Testing Bug fixes MS390 ports do not reflect PoE status in Dashboard Known issues MS390 stack members may not report client-level detail MS390 series switches Max MTU is limited to 9198 bytes MS390 series switches will not display packet details in the DHCP Servers page MS390 series switches do not support the 'next-server' or 'bootfile' parameters in DHCP messages Rebooting a single switch in an MS390 stack will reboot the entire stack LLDP frames from MS390 series switches will use a single system name instead of the Dashboard given name MS390 series switches will not display the advertising router ID for OSPF MS390 series switches with OSPF enabled will default to an IP MTU of 1500 bytes on every OSPF enabled interface MS390 series switches do not support the multicast routing livetool MS390 series switches do not support tagged traffic bypass for voice on ports with a Multi-Auth access policy Dynamic VLAN assignment from a RADIUS server on MS390 series switches must already be an allowed VLAN on the port for it to function MS390 series switches may not display link state on links at mGig speeds (2.5G, 5G) MS390 series switches do not currently support the following features: VRRP, SM Sentry, Syslog server, SNMP, Traceroute, IPv6 connectivity to dashboard, Meraki Auth, URL Redirection, MAC Whitelisting, RADIUS Accounting, RADIUS CoA, QoS, Power Supply State, PoE power status/usage, Loop Detection, UDLD, MAC Flap Detection ARP entry on L3 switch can expire despite still being in use (predates MS 10.x) SM Sentry does not support Windows based clients (predates MS 10.x) MS425 series switches do not forward frames larger than 9416 bytes (predates MS 10.x) MS350-24X and MS355 series switches do not negotiate UPoE over LLDP correctly (predates MS 10.x) Other Various performance and stability improvements ... View more

we had a couple customer orders for Z3’s we placed at the end of last week and the orders shipped today. So there is inventory direct from Meraki. ... View more

MRA on the expressway is the way to go, but it only supports 7800/8800 series phones. Jabber is also supported, so you can deploy jabber as a full client or soft phone only mode. ... View more

Is this in beta yet? ... View more