08-20-2019 03:42 PM - edited 07-05-2021 10:53 AM
I was wondering if there is a method to keep capwap APs from joining any mobility express controller or locking them down to a subnet? I'm standing up another mobility express network on a separate subnet for another building and I noticed other APs joining the new installation rather than staying connected to there "designated controller". I have removed the DNS entries and was hoping Dhcp option 43 would force the join or even election of a new controller in the subnet. That does not seem to work as I have previously configured APs joining the new network instead of staying put.
Any suggestion s would be great.
Thanks
Mark
Solved! Go to Solution.
08-20-2019 11:10 PM
On the existing AP's on the WLC you should go to their high availability tab and only enter the primary controller name and IP being your current controller.
If your AP's of the existing installation are of a certain type and the mobility express AP's are from another type, then you could utilize option 43 in combination of vendor class identifiers to only give out option 43 to a certain type of AP's.
There are examples on the internet but I haven't done anything like it.
08-20-2019 09:53 PM
No its not a good idea!
Best case would be to implement single wireless solution in whole network not multiple.
Simply designate one as Master and maybe one or two as backup. The rest will then simply connect to the Master while booting.
Regards
Dont forget to rate helpful posts