06-01-2016 04:13 AM - edited 07-05-2021 05:09 AM
what is the recommended design between HQ and Branch :-
1- we have WLC in both side (in HQ and Branch)
2- The WAN link between Branch and HQ is very good .
3- all internet traffic , Mail traffic , File sharing server , and any application must be go fro Branch to HQ .
4- Security server including ISE are in the HQ .
5- we need to unified all WLAN with security in Branch and HQ .
are we need auto anchor design or just configure WLAN on the Branch with the same parameters as HQ ?
also what is the limitation and consideration when using autoanchor , is this related to number of users and if this impact during rooming .
the WAN link speed is very good between Branch and HQ
06-01-2016 09:20 PM
are we need auto anchor design or just configure WLAN on the Branch with the same parameters as HQ ?
Auto Anchoring typically used for Guest wireless service. Let's say you have guest SSID in branch & HQ. You do not like guest traffic terminate on your branch & want them to assign IP block from HQ (typically in DMZ range). In that case you can use anchoring for that SSID.
I would do anchoring for such SSID and all other SSIDs configure HQ & BR in similar fashion as you have WLCs in both location.
HTH
Rasika
*** Pls rate all useful responses ***
06-02-2016 06:06 AM
Thank you Mr Rasika for your fast response ,
Could you please to verify that when we configure auto anchor the below actions occurred:-
1- Local Conversation between two clients on Branches must go through WAN link .
Regarding to rooming:-
1- What the type of roaming when client roaming between controllers on the branches
2-What the type of roaming when client roaming between two AP on the same controller.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide