Question 680
During an independent network handover at the Fox River branch of Fjord City Library, the monitored service is public records archive for clients in 172.20.54.0/24; incident reference is DC-9249. The on-duty analyst documents this symptom before proposing any configuration: Guest devices use a separate SSID but can still discover and contact each other directly on the same client VLAN. The branch requires an auditable explanation, a narrowly staged change, and a rollback plan that preserves its working services. Which ongoing operational check is most relevant to recognizing recurrence of this failure?
Answer and explanations
Monitor SSID-to-VLAN drift and unexpected address pools per WLAN. The observed condition is: During an independent network handover at the Fox River branch of Fjord City Library, the monitored service is public records archive for clients in 172.20.54.0/24; incident reference is DC-9249. This alternative addresses a different issue (ssid to service vlan binding). The decisive distinction is: Run periodic peer-isolation tests and alert on guest east-west sessions.
This alternative addresses a different issue (roaming continuity). The option would address: Measure roam duration, voice loss and failed reauthentication during client movement. The scenario instead reports: During an independent network handover at the Fox River branch of Fjord City Library, the monitored service is public records archive for clients in 172.20.54.0/24; incident reference is DC-9249.
Monitor AP tunnel resets and controller heartbeat loss. This alternative addresses a different issue (capwap control path). The reported case is: During an independent network handover at the Fox River branch of Fjord City Library, the monitored service is public records archive for clients in 172.20.54.0/24; incident reference is DC-9249. The decisive distinction is: Run periodic peer-isolation tests and alert on guest east-west sessions.
During an independent network handover at the Fox River branch of Fjord City Library, the monitored service is public records archive for clients in 172.20.54.0/24; incident reference is DC-9249. That points to this explanation: Run periodic peer-isolation tests and alert on guest east-west sessions.