ISE shows successful wireless authentications and almost no session updates afterward. The controller is not sending RADIUS accounting to ISE. What does that missing integration break?
Select an answer to reveal the explanation.
Short Explanation
ISE heard the door open and then nothing. Your controller is not sending accounting, so the session record never gets the updates that follow authentication. Accounting is not how you aim an antenna.
Full Explanation
RADIUS accounting tells ISE what happened after the initial accept: session start, updates, and stop. If the controller authenticates against ISE and never sends accounting, ISE shows successes and then almost no session updates. The missing integration is that accounting stream. The RF channel plan is an RRM job on the wireless side. It is not calculated from accounting packets, and a quiet accounting log does not retune radios. Access-point images are transferred over the controller-to-access-point path. They are not packed inside RADIUS accounting. Antenna aim is a mount. ISE does not set it, and the accounting interval is not a mechanical tilt. Exam caveat: accounting uses the same device entry and secret as authentication in a typical build, and it still has to be enabled on the controller's server definition. A working authentication test does not prove accounting is on. Operational check: enable accounting to ISE, join a test client, and confirm ISE shows a session start and later updates for that client.