When a controller or map is assigned to a virtual domain, the access points associated with the controller or map are automatically assigned as well. Access points can also be assigned manually (separate from the controller or map) to a virtual domain.
Let me give a bit of backround. We use a WISM2 as a "Flexconnect" AP service. All AP's are out in School Districts and register back to our WISM2. We used WCS to setup Domains on a "per District" basis and Assigned JUST the AP'sthey needed. We also gave them conditional rights to the controller to create Guest users etc. This worked well as the user just needed to login and he had rights to his domain, saw domain assigned APs, and had full management of their Infrasturcture.
Now, when I assign the controller into the Domain, the user see's every AP. Like they are a member of Root Domain.
We are excited to announce the Second refresh of 17.6.2 EFT/Beta Program for PRODUCTION deployments.
This release is the second qualified EFT/Beta Image and is BU supported.
After previous 17.6.1 CCO, this p...
Listen: https://smarturl.it/CCRS8E33 Follow us: https://twitter.com/ciscochampion The goal for stadium and large venue Wi-Fi is to deliver an exceptional, fast, and reliable wireless experiences to tens of thousands of fan...
We are pleased to announce the immediate availability of the IOS-XE release 17.6.1 for the Catalyst Wireless Controllers. The new code is now posted on the CCO and can be found at this link:
This version now introduces experimental new feature, "Upgrade Advisor, targeted to one of common case generators: what are the supported versions and how to upgrade my current controllers and APs
It supports both AireOS and IOS-XE, covering since ...
Thank you for the overwhelming response to the First and Second EFT refresh of 8.10MR6!
We are excited to announce the third refresh of 8.10 MR6 EFT Program for PRODUCTION deployments.
While the CCO release of 8.10MR6 is just a few we...