Hi,
I have a small dilemma at one of mys customers sites.
They have a Cisco vWLC 5508 appliance in VMWare. This is all working fine. This system only can run Flex Connect mode so am currenly breaking out the SSIDs / VLANs at the edge switching that the APs connect to.
The is now a need to use both the CAPWAP control and data tunnels over an IPSEC VPN to be able to have multiple SSIDs at theses remote sites.
Now I decided that the easiest way for this is to use a spare WLC 2504 controller for this small number of APs scattered over these WAN sites.
Thinking harder about this, effectively could have two WLCs (the VMware vWLC 5508 and the small 2504) sitting on the same subnet. I now worry that the APs that connect to the vWLC5508, may end up attempting to join the 2504 if the APs can do a Layer 2 broadcast and end up joining to the 2504. This would not be good.
My option here is to put the 2504 management interface in another VLAN so that it cannot see the broadcasts from the APs that should talk to the 5508. I will use DHCP option 43 to tell the remote APs connecting in via WAN / IPSEC tunnels to see the 2504. In this case I only need L3 discovery.
I have looked around the web looking for WLC commands to tell the WLC to only accept CAPWAP Layer 3 join requests. I couldn't find any.
Anyone know if this can be done or not?
I want to keep the remote sites away from the corporate 5508 WLC as it can't do the CAPWAP control and data tunnels. I guess this is due to CPU overheads for tunneling inside a VM. RRM and other stuff is not so resource hungry I guess.
Cheers and thanks in anticipation of an answer,
Simon
