wi-fi – Cisco WLC topology for a multi-site deployment

I’ve three bodily websites (geographic places) which can be linked collectively by way of IKE tunnels, and every web site is on a unique subnet. I need to deploy wi-fi entry factors throughout these websites with some SSIDs which can be comparable in nature/configuration and others which can be location-specific.

I might like to deploy a central WLC within the cloud or in a single location and have all the entry factors use that controller, so I can handle them centrally. Nonetheless, I would like to have the ability to entry sure native sources when the cloud or the site-to-site tunnels are down and the native WAPs cannot entry the WLC.

Because of this, I need to deploy native WLCs (embedded controller in an AP grasp). Nonetheless, on this situation configuring every one and synchronizing configuration modifications the place the configuration is analogous throughout the websites is cumbersome.

Is there a means to make use of the native WLCs (i.e., embedded) as as backups or secondaries and have a central WLC (standalone, bodily or digital) the place all configuration takes place?

This query is probably going just like the one right here: WLC geographical redundancy, besides the reply is probably going outdated, my topology/particulars could also be totally different, and importantly my query pertains to the Embedded Wi-fi Controllers present in fashionable Catalyst entry factors (and equal 9800-series bodily or digital standalone controller), versus mobility categorical or different legacy merchandise circa 2013.


Leave a Reply

Your email address will not be published.