ā04-18-2017 07:35 AM - edited ā07-05-2021 06:52 AM
Hello,
Having two guest anchors, would be possible to load balance the traffic of different SSIDs between them by assigning different priorities to each WLAN? For example, anchor 'A' active for WLAN 'A' with priority 1 while anchor 'B' active for WLAN 'B' with priority 1. Each anchor would backup their partner with lower priority of 3 for the other SSID.
Regards,
Solved! Go to Solution.
ā04-23-2017 04:48 AM
Priorities are meant to only have traffic sent to a controller that has the highest priority value. For example if you have two data centers and you only want traffic to be sent to the primary DC but still have the other as backup.
In your case in which you want to load balance traffic, you just leave it at default or set them to the same value and the algorithm will determine what anchor controller a client will be directed to.
-Scott
*** Please rate helpful posts ***
ā04-20-2017 03:06 AM
Any ideas out there?
ā04-20-2017 04:15 AM
There is no priority for anchor load balancing it is round robin
Should check with Escalation if this is in the road map , doable, it is that the selection of anchor is done post association and before entering the DHCP in the state machine .
ā04-20-2017 06:03 AM
I'm a bit confused because according to the documentation:
"You can configure a priority to the guest anchor when you configure a WLAN. Priority values range from 1 (high) to 3 (low) or primary, secondary or tertiary and defined priority is displayed with guest anchor. Only one priority value is allowed per anchor WLC. Selection of guest anchor is round-robin based on a single priority value"
Although the priority is configured per WLAN, if only a single priority is allowed per anchor, then it should be the same priority for all the WLANs, correct?
ā04-21-2017 07:35 PM
I totally missed this , you are right there is a priority in place and it got introduced in 8.1 release i was in pre-8.1 mindset
ā04-20-2017 01:40 PM
Are you sure ?
Because I implemented both solution, and round robin is only when you have the same priority.
If you have different priorities, for example WLC Anchor A with priority 1 and WLC Anchor B with priority 2, traffic will be tunneled to the WLC Anchor A and if this WLC goes down, the WLC B will handle the client traffic.
Alex-
ā04-23-2017 03:38 AM
I understand that approach and seems to be the only one valid. However, since the documentation states that the priority is configured at the WLAN level, I was wondering if we can play with those values and make both anchors active but for different SSIDs.
ā04-23-2017 04:48 AM
Priorities are meant to only have traffic sent to a controller that has the highest priority value. For example if you have two data centers and you only want traffic to be sent to the primary DC but still have the other as backup.
In your case in which you want to load balance traffic, you just leave it at default or set them to the same value and the algorithm will determine what anchor controller a client will be directed to.
-Scott
*** Please rate helpful posts ***
ā04-23-2017 11:54 PM
Thanks Scott.
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