Thanks Rasika
What i am trying to do is, break roaming where ever it is not required.
scenario 1
I have used WLAN profiles with the same SSID to break the l3 intra-controller roaming.
example:
with intra-controller roaming in effect:
wlc-1:
wlan profile name:test1
ssid: test
wlan id: 50
AP-Group-1
Wlan id: 50
Vlan 10
AP-Group-2
Wlan id: 50
Vlan 20
assume the client is connected first on an AP in AP-GROUP1, When the client roams to an AP in AP-GROUP2, the IP of the client will be maintained.
breaking the intra-controller roaming:
wlc-1:
wlan profile name:test1
ssid: test
wlan id: 50
wlan profile name: test2
ssid: test
wlan id: 51
AP-Group-1
Wlan id: 50
Vlan 10
AP-Group-2
Wlan id: 51
Vlan 20
assume the client is connected first on an AP in AP-GROUP1, When the client moves to an AP in AP-GROUP2, the IP of the client will change and it will be a new association to WLAN ID:51.
Scenario 2
if i want to break the inter-controller l2/l3 roaming, can i use the same solution as scenario 1? in my test, i learned it doesn't matter, i saw a normal L3 inter-controller roaming.
i know changing the mobility domain name can break l2/l3 roaming but i am checking if wlan profile has any use in breaking inter-controller roaming.
