Hi @RobAce You can use the following API's to move the Meraki Nodes from one network to another within the same organization. https://developer.cisco.com/meraki/api-v1/remove-network-devices/ https://developer.cisco.com/meraki/api-v1/claim-network-devices/ ... View more

Hi @JFer   I would recommend you to put both ends on auto. Secondly, make sure the cable is good (Bypass the patch panel if any and directly have the AP connected to the switchport). Lastly, try another switch port. Alternatively, can also try to connect another test device using same cabling to same switchport to verify if the issue subsides. If the problem continues, contact our support hotline/open a case for further troubleshooting. ... View more

Hi @Ash24   Looks like others have already posted answers. Unfortunately, the functionality of the port cannot be changed (i.e. from LAN to WAN). Hence, you would need to purchase SFP's for WAN uplinks on MX250.   For your reference, I have attached a KB here: Small-Form Factor Pluggable (SFP) and Stacking Accessories ... View more

Hi @Phill2    Yes, this was a known issue. Although, our development team have confirmed the issue has been resolved.    In case, if you're still facing issues, I would recommend you reaching out to our support for further troubleshooting. ... View more

Hi @EdgeFarming    If traffic is still being allowed from VLAN 10 to VLAN 15, it is possible these are flows existed prior to creating this rule. I would suggest rebooting your MX appliance to end these current flows and check again. Please navigate to Security & SD-WAN > Appliance status > Tools > Firewall logging tool, to check if a flow from VLAN 10 to VLAN 15 is allowed or blocked if you would like to test this live.   I've attached a KB below on utilizing the "Firewall logging" tool from the tools page for reference: https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/Firewall_Logging#Quick_Start_Guide ... View more

Hi @Fabrice1  It looks like you are running into an unexpected behavior which has been identified by the development team and they are already working towards a fix.  I would recommend you to call into our support hotline/open a case, so that our engineers can apply a workaround on the backend and also attach your case to the known issue and notify you once it has been resolved. ... View more

Hi @JGill,   In case you are still facing issues with the GET API call not returning all the elements, I would recommend you to call into our support hotline/open a case, so that our engineers can help you troubleshoot the issue. ... View more

Hi @Shubh3738 Yes, there was an outage reported. Although, Documentation is back up and running again.   ... View more

Hi Vishal,   Yes, that is correct. Meraki MS classic switches (excluding MS390) are unable to ping their own Layer 3 Interface. KB: https://documentation.meraki.com/MS/Layer_3_Switching/MS_Layer_3_Switching_and_Routing#Pings_Destined_for_a_Layer_3_Interface ... View more

MG51E does support 5G. The firmware which introduced support for 5G band n77 was MG 3.101. Although, the latest stable firmware version for the MG51E is MG 3.212. ... View more

It looks like you are running into an unexpected behavior which has been identified by the development team and they are already working towards a fix.  I would recommend you to call into our support hotline/open a case, so that our engineers can attach your case to the known issue and notify you once it has been resolved. ... View more