AI Analytics shows onboarding success steady for weeks, then worse starting the hour a RADIUS change was made. RF health is unchanged. What is the comparison telling you?
Select an answer to reveal the explanation.
Short Explanation
The graph was calm until the hour you changed RADIUS, and the radios did not change with it. That lines the worse onboarding up with the RADIUS change. The comparison is a lead, not a channel edit.
Full Explanation
AI Analytics is useful when a baseline breaks at the same time as a known change. Onboarding was steady, then worse from the hour of the RADIUS change, and RF health did not move. The comparison says the RADIUS change is the lead to investigate. An onboarding drop is not always RF. Unchanged RF health is the evidence against that. The comparison does not push a channel change, and nothing in the stem says onboarding recovered. Analytics does not record every drop as a guest VLAN mismatch. This WLAN's symptom starts at the RADIUS change. Onboarding success fell in the window right after a RADIUS change and was steady before it. The analytics comparison points at that change. It does not itself roll the change back. Exam caveat: a matching clock is not proof. Confirm the change window in the RADIUS logs before you roll back, and look for a second change made in the same hour. Operational check: compare onboarding just before and just after the change, then test a client against the previous RADIUS policy if the logs agree.