Currently Thin AP are a sub-object of the controller they are on. However with Aruba one AP can be managed by several controllers in a cluster or backup configuration. This means that if it associates with its backup controller it will be 'up' on one controller, but 'down', or missing, on another.
Current processing is really bad.
Common Scenarios
ADS.RJLtest is on ControllerA with ControllerB as its backup
in the MIB it is present and up on Controller A, but missing on controller B
=> no alert for ADS.rjltest on controllerA (status is OK)
=> no alert for ADS.rjltest on controllerB (status is absent or 'missing')
If there is a network issue and controller A becomes unreachable from the AP then the AP will re-associate with controller B
in the MIB it is present and Down on Controller A, but present and UP on controller B
=> alert for ADS.rjltest on controllerA (status is DOWN)
=> no alert for ADS.rjltest on controllerB (status is OK)
When Controller A becomes reachable again
in the MIB it is present and UP on Controller A, and present and DOWN on controller B
=> no alert for ADS.rjltest on controllerA (status is OK)
=> alert for ADS.rjltest on controllerB (status is DOWN)
----
now, when things get really bad:
the default processing is to remove APS from controllers if they are no longer in the MIB.
if I perform a firmware upgrade, or reboot, controller A then
a) all of the AP failover to controllerB
b) all of the history of all of the clients on APs on controllerA is deleted