Wireless Guest anchor move to Datacentre (mobility group affected?)

[azthomson]

Hi,

Can someone please advise on the below in regards to moving of our WLC guest anchor:

We have 3 wireless controllers:

• 2 WLC hosting internal SSIDs (all APs registering to number 1)
• 1 WLC acting as anchor for guest network SSID and direct ports to firewall
• All WLC are on same management VLAN / IP address for mobility group
• All WLC are set for "Current CAPWAP Operating Mode Layer3"

Our internet has moved to the Datacentre, so i need to move the guest wireless anchor to the Datacentre for direct attachment to the firewall. 

This will mean:

• The guest WLC will now be on different management subnet (IP and VLAN)
• No firewall is present so all ports for mobility anchor should work

Prerequisites indicate that "All controllers must be configured for the same LWAPP transport mode (Layer 2 or Layer 3)." I have limited knowledge on CAPWAP and whether the new seperation in management subnet (from L2 to L3) will effect the mobility anchor and ability for guest network to function. Is the above current CAPWAP mode correct for implementation, or am i looking in the wrong controller area? My understanding is that CAPWAP is new LWAPP so since they are L3 set this should not be an issue?

Appreciate your assistance, please advise if you require more information?

Thank you

Aaron

[Rasika Nayanajith · Accepted solution]

Hi Aaron,

You should be fine with moving guest anchor WLC to different data centre (in different L3 domain). You can keep it in seperate mobility group as well.

To ensure guest service is working, you need to establish mobility peering between Anchor WLC & other foreign WLCs.

Refer this post for better understanding of how to configure those peering

https://mrncciew.com/2013/05/20/mobility-config-via-cli/

HTH

Rasika

*** Pls rate all useful responses ***

[azthomson]

For some reason I cant see Rasika's response but can in an update to my email. 

Rasika was correct, i completed the change yesterday so great timing, there were no issues with the mobility group as expected.

Thanks Rasika

Aaron