Meru Technical Note - What are the requirements for Meru Mesh design and implementation?

What are the requirements for Meru Mesh design and implementation?

KB Article Type: Design

Related Products: AP

Related Software Versions: Any

Keywords: Mesh, AP

The following restrictions apply to the design and implementation of Meru mesh networks. 

• Enterprise Mesh APs require L3 connectivity to the controller.
• Monitoring of backhaul links via SAM is not supported.
• A radio that is not actively used for mesh cannot be used for SAM purposes.
• Bridged mode is not supported for Enterprise Mesh—only tunneled mode is supported.
• Gateway and mesh APs support a maximum of 4 backhaul links.
• From the gateway (i.e., an AP physically connected to the network), a maximum of 3 hops is supported with no more than 16 APs per cloud.
• A maximum of 500 stations can be active on a mesh cloud at any given time.
• Minimum channel separation guidelines are to use non-overlapping channels.
• Mesh operation on DFS channels is not recommended.
• Aggregation of multiple uplink connections is not supported.
• A single AP cannot be assigned to multiple different meshes