One scanner shows high retries on a radio where every other client looks clean. An engineer opens a building-wide syslog and cannot see the scanner's retries. Which view has them?
Select an answer to reveal the explanation.
Short Explanation
Everyone else on that radio is fine, so you want the one scanner's numbers, not a log of the whole building. Open the per-client radio stats. A splash-page log does not count retries.
Full Explanation
Retries for one client are counted in that client's radio statistics. This scanner is the only one suffering, and a building-wide syslog does not contain those counters, which is why the engineer cannot see them there. The syslog is the wrong view, not a secret copy of the retry counter. A guest portal log records portal events. A retry is not a failed splash page. RADIUS accounting records session start and stop. It does not count air retries as authentication failures. One client shows high retries and the others on the same radio do not. The per-client stats are the view. A building-wide syslog will not isolate it. Check one live client after the change and leave the rest of the floor alone until that client matches the result you expected. Exam caveat: high retries on one client can still be that client's driver or a dead spot only it sits in. The stat tells you the scanner is struggling. A walk to its location tells you why. Operational check: open the scanner's radio stats, confirm the retries are there, and compare them with a clean client on the same radio.