I told you 😅 ... View more

There are many different standards in the industry for varying distances and fiber types. While Cisco Meraki strives to support the most common IEEE802.3 standards, if you are in need of a standard that Cisco Meraki does not carry a certified option for, you will need to use a non-Meraki part. If you have problems using the uncertified part with a Cisco Meraki product, please contact Cisco Meraki support. Though we do not officially support non-Meraki parts, many are still compatible and Support will do their best to ensure all the requirements are met for checking non-Meraki SFP connectivity and viability. For more information on compatible and supported SFP modules, check our SFP and Stacking Accessories document. ... View more

Cisco Meraki switches and security appliances with SFP interfaces allow both Cisco Meraki-branded and 3rd party optics. Our products do not lock out optics that have been detected as non-Meraki parts. However, please note that in most cases only Meraki-branded accessories have been certified to work with Cisco Meraki products. For any exceptions please see the section below labeled: Are other Cisco SFP/SFP+ parts certified to work with Cisco Meraki products? ... View more

Well, I have been using It with no Meraki and It has been working well.   But, as I suggested, make a wish for Meraki. ... View more

Or request a new feature for Meraki. 😉 ... View more

Unfortunately, it is not possible, but you can use it in auto-negotiate. mode with other devices that are not Meraki that will work without any problem. ... View more

On MX, you can access the local device status page and set It manually:    On switch, you can force 1Gb full duplex.   ... View more

@StuartClarke, I just confirmed It with Meraki support and they confirmed that It is possible to enable it on vMX. ... View more

What type of license are you using? per-device co-termination?   In co-termination, you just need to remove the old AP from the network and then add the new AP to the network and the license will automatically be linked to it. In the per-device do an undo assign on the old AP to assign to the new AP.     ... View more

Just remember that you have to contact the support to enable this feature.     ... View more

Probably yes, but I recommend you to read this article first:   https://documentation.meraki.com/Architectures_and_Best_Practices/Auto_VPN_Hub_Deployment_Recommendations ... View more

Try this without being connected to any network (wifi, etc).  Did you get an IP address when connecting to the management port? ... View more

You can try It, but to be honest I have never needed to configure It on my switches.   https://documentation.meraki.com/MS/Other_Topics/QoS_(Quality_of_Service) ... View more

Have you tried to enable the default traffic shaping rules?     ... View more

You need to generate a key:     ... View more

I know that the documentation does not indicate that management communication is always through Uplink.   But if we think about the logic of the other firewalls, we have outgoing (Internet) and incoming (LAN) traffic. In the case of MX, WAN interfaces are used for outgoing traffic. 😉 ... View more

Maybe this?     https://documentation.meraki.com/SM/Profiles_and_Settings/Certificates_Payload_(Pushing_Certificates) ... View more

Same here, but after clicking on device status and then back to the switch list, It worked as expected. ... View more

MX84 Meraki cloud communications would go through the Watchguard ; so Internet 1 and 2 would only be used for AutoVPN ?   Nope, The MX will use the WAN interfaces to communicate with Meraki Cloud. ... View more

Note: the keyword default route, means that a source-based default route, will not force all traffic to a configured next hop. It will only forward traffic for destinations that are unknown in its routing table. Note: This option cannot be configured if utilizing a single VLAN Use Case A simple use case is segmentation. With Source-based default routing, a default route per VLAN can be configured, (for example, Guest VLAN) with a next-hop as another MX security appliance over Meraki AutoVPN or a gateway device on the LAN. ... View more

Well, I don't know if It is the best option, but you can create a Source-based default route.   LAN source based default route - The next hop of a LAN source-based default route is on the LAN side of the MX security appliance. The next-hop IP is known to the security appliance on the LAN side either by a VLAN or a static route.    https://documentation.meraki.com/MX/Networks_and_Routing/Source_Based_Default_Routing ... View more

Try with API v1 instead v0:   https://developer.cisco.com/meraki/api-latest/#!get-network-sm-devices ... View more