Looks like this case was just resolved with the solution below
The issue(s) here are two-fold:
1) WAE devices are supposed to be configured to forward their Flow Monitoring information to the ADA Console and it's the job of the Monitor to do the data processing. But since the WAE Flow data is forwarded to the ADA Console one *should* expect the WAE device to re-appear (as "Not Assigned") after being deleted until the WAE device is configured to no longer forward to the ADA Console.
2) According to the database provided it appears that one of the customer's WAE devices changed the Interface through which it was forwarding its Flow Monitoring data. And when the there appeard a WAE device with the same hostname and IP but a different MAC address, ADA got confused and couldn't associate the new Source (WAE device) with a Collector because another Source (WAE device with old MAC) was already associated with the Collector.
Example screen shots attached.
The workaround to correct this issue is to:
* Log into ADA as admin
* Select 'Administration' tab
* Select "Show me" Data Monitoring -> Monitoring Devices
* In the WAN Optimization Device List, open the "Select Source Set:" dropdown box and select the Monitor where the problem WAE devices are associated. -- ?ZA-ZATNAG001?
1) Sort by IP Address
2) Look for and DELETE ALL entries with 2 or more of the same IP (I believe there should only be 1 dup, 10.38.100.20)
3) Now DELETE all the remaining WAE devices marked as "Not Assigned" (I believe there should only be 3 remaining)
* And wait approximately 5 minutes for any of the deleted WAE devices to re-broadcast, and once the device appears again, you should now be able to properly assign the WAE device to the desired Monitor.
Note: actual fix to avoid this situation in the future will be applied to top-of-tree. No binary fix can be created for ADA 9.2.