I've got 10.1.1 running in our lab, and one of the main things I'm testing is the WLC management capability.
I've hit a snag that a previously released PTF (10.01.017) doesn't seem to have fixed, although I may attempt a backup/re-install when time permits to prove this.
Scenario.
Main site has a WLC that controls all APs across the estate. By design, when you discover a WLC, all APs auto-discover as pingables in the same container. This is fine, as the app has no way of knowing what sites each AP or group therein applies to.
One then moves APs for site "B" into a site "B"'s container on the universe view. All is fine with the world until such time as the site has a power out or someone/something restarts the AP. As the AP gets it's address from DHCP, the original model goes red, and that AP then re-discovers back in the same container for site "A" alongside the WLC. PTF 10.01.017 should have fixed this but doesn't appear to have.
My query is this:
I need to deploy this monitoring solution for a customer that has around 180 or so sites, not all of them have APs but for the ones that do, they're all controlled by a WLC in the head office DC. When they have power outs etc. (which is frequent as they're construction material suppliers and there's a lot of brown-outs on some remote sites as they're quite off the beaten track) short of forcing our engineers to DHCP reserve every AP (and of course that only works on MAC address, so a like-for-like replacement should one fail will still have the problem of discovering in the wrong place with the old one still showing down) is there any other way that Spectrum can be told to check hostname/MAC etc. when it's "discovered" a new AP - which is essentially just an existing one on a different IP and to have it update the existing model WHATEVER the container, rather than just plopping it next to the WLC on the central site and marking the old one as down?