As @BlakeRichardson  said, I have seen similar situations where the device is not claimed in a network (but present in the organisation inventory).  In this situation, the MR44 is not a part of a network and , as a result, cannot download any specific configuration. Alternatively, there could be an issue with dashboard communication. Please raise a support ticket and we can investigate it further for you. KB for detailed reference: https://documentation.meraki.com/MR/MR_Installation_Guides/MR44_Installation_Guide  ... View more

Lets monitor this for a few days. If the switch behaves nice and normal throughout, we will know our issue is resolved 🙂  ... View more

If the switch is working fine in terms of traffic forwarding, it is possible that either it is not storing its own logs properly or (if the logs are stored correctly) they are not sent to the dashboard correctly. I would be very interested to see the behavior when we change the MASTER of a stack to a different stack member (something Meraki Support can check) or with a firmware change. But overall, I would raise a support ticket regarding this and call the support line via https://meraki.cisco.com/support/ to have an engineer check the internal configuration/logs of the device and verify this for you.   ... View more

While your reasons are genuine and the desired topology may work practically, it won't be officially supported on the Meraki end and if it comes down to troubleshooting it with a support personnel, they might ask you to revert back to ring topology. Again, as per my earlier answer, you will have to deploy it at your own risk 🙂   ... View more

I did some digging on this one. So Meraki uses a proprietary protocol using which different members of a stack communicate with each other. Going by the tradition and KB information, it is recommended to use a basic ring topology to connect the stack members. Although based on internal tests even non-ring topology (similar to one you shared in the picture) worked fine as a stack - however - this is not officially support by Meraki and should be used at your own risk. I hope this answers your question 🙂   ... View more

A single default gateway should work fine. Since you are doing routing on the MS225 stack, you will have to configure a static default route pointing towards a single IP address residing on the firewalls. Now if you are adding a redundant pair of firewalls, only one of them will be active/master at any given time which will be the owner of the IP that the switch stack is using as a gateway. There are some firewall vendors that use the (virtual IP/ virtual MAC) in their HA firewall setup (as @GreenMan  mentioned), in that case the gateway of the switches will point to the virtual IP that the HA firewall share.   As long as you have physical connectivity between the stack switches and both HA pair firewalls, STP will do it its magic and redundancy will take care of any failover scenarios.      ... View more