Hi Mike,   Meraki itself doesn't provide the CAD renderings for our products. However, if you are looking for dimensions of our devices i would direct you to our library of datasheets that contains this information. ... View more

You're not the first to see this, sadly. It has been reported to our ui development team and they are actively investigating it. Hopefully it will be resolved soon. If you're still seeing the issue tomorrow consider opening a support case for more traditional updates. ... View more

The above statement is correct. While device ownership can be transferred between end customers, licensing can not. See the following link from meraki documentation explaining the guidelines regarding this. https://documentation.meraki.com/zGeneral_Administration/Inventory_and_Devices/Cisco_Meraki_Devices_purchased_Second_Hand ... View more

Hi EJN,   For that kind of discussion we would ask that you engage your account representative here at meraki. They have the most visibility when it comes to the roadmap and planned features. You can find your account reps information from your meraki dashboard in the "help" > "get help" section towards the bottom of the page. ... View more

Hi PeterJames,   I spoke with some of our SM experts here at meraki and wanted to share some important information. Firstly, that the iOS app should never get minimized while in single app mode. If you see this happening there may be an issue with the mode along with other components. Additionally, there is no way for meraki systems manager to run the clean up utility mentioned. If you are seeing this behavior please reach out to meraki support (support@meraki.net) for more in-depth troubleshooting and diagnosis. ... View more

Hi nst1,   You may be running into an instance of a missing return route back to the new interfaces on the MS350 from the other routers. The best way to troubleshoot would be to gather packet captures from the switch ports as the ping/traffic is attempting to pass. With the captures you should be able to track where the 350 is sending the traffic and follow it through the rest of your network. If you require any assistance please do not hesitate to open a case with our support team by contacting support@meraki.net ... View more

Hi Priesty,   The MV development team is always working towards new products and features. At this time we are not prepared to announce anything but we ask that you follow our blog at https://meraki.cisco.com/blog/ and keep an eye on the "announcements" portal of your meraki dashboard. If theres a feature you would like to see put on our roadmap please use the "make a wish" portal of your dashboard so our team is made aware of it! ... View more

Hi CiscoUser,   I will attempt to address your questions below:   In regards to the 1st question. Currently, the API call you referenced is the correct API for port information. At the moment there are no alternatives.   as for the 2nd, there are currently no API calls that will provide the in/out octet count in the manner an SNMP get would provide.   Our API systems are always growing, we recommend that any feature requests for additional API functionality be submitted through the "make a wish" window located on the bottom right corner of any dashboard page. ... View more

Hi hosokawaw,   Generally its not recommended that the "heartbeat" cable between a warm spare pair of MX devices be a direct link. Recommendations can be found in the link below, a switch which has connections to both MX LAN segments is preferred. https://documentation.meraki.com/MX/Deployment_Guides/MX_Warm_Spare_-_High_Availability_Pair#Recommended_Topologies ... View more