A store uses dashboard-managed access points and has no Catalyst 9800. A client was slow yesterday. Where is the first place to read that client's history?
Select an answer to reveal the explanation.
Short Explanation
This store does not have a campus controller to trace. The dashboard that runs those access points is where yesterday's client history lives. Your reload will not play the day back, because there is nothing to reload here.
Full Explanation
Dashboard-managed access points keep client history in the cloud dashboard: association, roaming, and usage for that store. A slow-client complaint from yesterday, with no Catalyst 9800 in the design, is looked up there. A radioactive trace is a Catalyst 9800 tool. This store has no 9800, so there is no trace to start, and a trace started elsewhere cannot see these access points. A controller reload does not replay a timeline. There is no controller to reload, and a reload would not restore yesterday's client experience even if one existed. An RF tag is a Catalyst radio-profile object. It is not an archive of client throughput, and this dashboard network is not using 9800 tags. Exam caveat: dashboard history still has a retention window. If the complaint is older than what the dashboard keeps, you will not reconstruct it from the access point. Operational check: open the client in the store's dashboard, set the window to yesterday, and read the connection events before you change the SSID.