New Omada Setup - Unable to Get Client Logging Functioning
I'm in the process of testing out Omada as a possible replacement for our current setup. So far I've got two EAP670's on the network, adopted by the software controller, and serving clients. Things are looking good, but I can't seem to get client logging to function at all.
If I go to my Site->Logs->Events the only thing that shows up are the AP Device events. Drilling into the client tab just shows "No entry in table". I've hit "Expand" and tried select all on the "Type", but despite there being clients on the network that are coming online, going offline, roaming, etc, the table just always shows blank.
At the global level, I've made sure that Client's History Data is toggled on. I've enabled remote logging and client data collection at the site level and confirmed that my syslog server recieves data from both the controller and the APs (although, interestingly, no data about client connect connect/disconnect/roam events seems to be transmitted). I've gone as far as taking my initial linux install of the software controller offline and setting everything up from scratch on the Windows client but it's the same results.
I feel like I'm missing something simple here. Can anyone provide some insight?
Thanks