Hi Justin,
A good question - I'm following this out of curiosity. Mesh is a bad idea in general though.
If lowered latency and interference are important, mesh is probably not the solution.
How well mesh will work will be dependent on how many clients you'll have connected to each node, the type of traffic, and the volume of traffic. If you're using mission critical low latency applications, scrap mesh. If you plan on 20-40 client devices per AP, scrap mesh.
Two mesh nodes for every one parent device is about as high as I'd want to go in a busy environment. The parent device only has so much airtime to distribute.
I am curious to know the official answer to your question though!
------------------------------
Ethan
------------------------------
Original Message:
Sent: 11-16-2021 05:15 AM
From: Justin Elopre
Subject: Aruba Instant ON - Mesh (Primary Controllers)
Hello Aruba team,
Is it possible to have multiple primary controllers in the same Mesh network? In an example scenario, I have two floors to accommodate.
Using full wireless Mesh, I wanted to cover each floor with its primary to avoid latency or interference and excess hops.
1st Floor = 3 units of Instant ON AP22
1 Parent Node = 2 Child Nodes
2nd Floor = 6 units of Instant ON AP22
1 Parent Node = 5 Child Nodes
Is this possible or any recommendations you may add?
Best regards,
------------------------------
Justin
------------------------------