Thanks CJ, your input is always appreciated (and I tend to look for your comments specifically). However, let me share with you my logic behind the design.
My logic is this, if the IAPs are all set up in the same cluster, then the four are removed from wired connectivity and then powered up and reconnect as mesh points, everyone should "see" each other and based off of connection metrics set up their dynamic routing accordingly. I would think that the dynamic routing would see multiple portals, assign each a metric, and then use them accordingly.
Now, why would I think that? Well, Meraki (I know, the dreaded M word, but I spent several years deploying their gear back in the day) has been doing exactly that since at least 2007. AeroHive's OS also does this very thing for strong, redundant mesh networks (and it's something they actively advertise). So, Aruba being a superior product to both of these manufacturers, I figured this should not be a problem for Aruba's dynamic routing, but I wanted to put it out there since this would be my first Aruba mesh deployment (other than a single mesh bridge to my garage at home)
I do realize I will have some co-channel interference from my two portals is I am not careful, but overall throughput I am not too concerned about. The data kicked out by the sensor arrays is in kilobits and currently runs on an old Proxim WDS point-to-multipoint wireless A, 54 meg network, but the old MP-11s are dying and NEW replacements can no longer be purchased and are not supported as they are beyond EoL.
Make sense? Or do you honestly think this is something the Aruba mesh cannot do?
:-)