Thanks Blakekrone for the clarification regarding this.

As each WLC eachs as there own "server"  is there a way to force all traffic from a centrally switch SSID over two controllers to only exit out of a single controller?

To clarify this we have a centrally switched SSID which terminates on the WLC1 in the image below which send that traffic to the firewall connected to a port on the WLC for filtering. We have a second WLC in another data centre which will in future be connected to a backup firewall however for the moment is there anyway to utilise this controller for AP management but force the traffic from a centrally switched SSID's subnet out of the interface on the WLC1?

Would a mobility anchor on the first controller allow this?

You can define mobility anchor as WLC1 on the ssid defined on WLC2 but make sure that you have the same ssid defined

on WLC1 with the same exact config except the WLAN id and interface.

IP address will be assigned to the clients throught the Anchor controller ( WLC1 ).

In genreal when you have moility anchor defined on certain WLAN on foreign and anchor controller, All L2 stuff is done on Foreign and L3 is handled on Anchor.

I hope this has been infromative for you.

Regrads

-----------------------------------------------

Pleaes make sure to rate ( flag ) correct answers

I do have a similar question on dhcp server scope but with redundant anchor controllers, I think it is nearly the same like with 2 internal controllers in the same local mobility group.

Do you know what happens if I divide one IP subnet to 2 scopes and a failover, e.g. controller reboot, happens ?

E.g. subnet 10.1.1.0/24, controller 1 dhcp-server-scope 10.1.1.3 - 10.1.1.127, controller 2 dhcp-server-scope 10.1.1.128 - 10.1.1.254 ?

Will the failover client hold it's ip address until lease expires ?

Will the failover client get a new ip address of the other scope on failover ?

Regards

Alois