Hello,
I've inherited a medium sized campus Aruba install and I'm deploying a branch site with just a couple of AP's and a 7005 controller. I've noticed all of the Master/Local design guides are designed around campus implementations and don't discuss remote sites.
Would configuring the remote site controller as a Local controller and tying it back to the master at HQ be a proper deployment model, or are there disadvantages?
My initial plan was to configure the remote site controller as a standalone.
There are some limitations on the Instant OS, that affect my deployment, which is why I'm using a Mobility Controller for this site. The main things I'm trying to accomplish are as follows:
1. Local routing (I don't want traffic to tunnel back to HQ to route)
2. Survivability - Local clients will point to local auth servers, etc. so local operation will continue if the WAN link goes down.
My understanding is that I can do all of this with the master/local model and it will allow me to centralize configuration.
The one thing I'm somewhat confused about though is that I use the local DB for guest access. Would this be synced from the master to the local?
Is the only issue with a split that I wouldn't be able to make new configuration on the local until connectivity is restored?
Sorry for so many questions.
Thanks for your help!