There are several guidelines that should be followed to ensure a successful mesh deployment:
Wireless client handling on a repeater
VLANs and other SSID settings like firewall and traffic shaping settings will be maintained on SSIDs that are served by repeater access points.
In general, it is desirable to have as many gateway access points as possible to maximize overall network performance and reliability. As a general guideline, it is recommended to plan for no more than two repeater access points attached to each gateway access point.
Maximum mesh hops
There will be a throughput reduction (~50% reduction) with each “hop” in a mesh. It is recommended that a mesh network be designed for no more than one mesh hop from the gateway to client device.
In order to ensure that there are multiple failover paths, it is recommended that each mesh access point has at least three strong “neighbors”, or other access points in the mesh that the access point can “see”. The Mesh Documentation gives an overview of the different monitoring tools available on the Meraki Dashboard, including an overview of the Neighbors Table.
The gateway access point may be configured to connect to a trunk port and trunk SSIDs to different VLANs. Repeaters will also serve SSIDs trunked on different VLANs. However, only one SSID & associated VLAN may be configured to bridge wired clients across a mesh link on a repeater access point's Ethernet port. A mixture of wired clients and Cisco Meraki access points attached to one MR repeater interface is not a supported deployment configuration. This is due to the auto detection mechanisms that Cisco Meraki access points use to infer when they should function as a gateway or a repeater.
Mesh wired access may be treated like a traditional point-to-point link with a router on the remote site. Access points may connected to a repeater with a Layer 3 router separating the broadcast domains. For further discussion on this design, see Extending the LAN with a Wireless Mesh Link documentation article.