Monitoring, Troubleshooting and Diagnostics
Monitoring, Troubleshooting and Diagnostics tests how you use ExtremeCloud IQ to find the cause of a user or device problem, not just where to look. Expect questions on dashboards, alarms, client and device detail, and diagnostic tools.
What to monitor
- Dashboards summarize network, device, and client health. Use them to spot scope: one client, one AP, one site, or the whole tenant.
- Alarms indicate conditions needing attention; events are the chronological record. Correlate the two before acting.
- Client detail views show association history, authentication results, IP address, VLAN, and roaming events.
- Device detail views show uptime, management connectivity, firmware, radio utilization, and neighbor information.
Diagnostic tools
- Ping and traceroute test reachability from the device or from the cloud where supported.
- Packet capture on an AP or switch port helps prove whether frames arrive and whether authentication completes.
- Spectrum analysis identifies interference and channel utilization problems on wireless.
- Tech-support or diagnostic bundles collect logs for escalation.
Worked example
A laptop associates but cannot reach the internet. Reasoning: first check the client detail timeline for association, authentication, and DHCP. If authentication succeeds but no IP appears, the problem is likely VLAN or DHCP, not Wi-Fi security. Check the AP's VLAN assignment and the switch uplink. If the client gets an IP but no traffic passes, use ping and packet capture to test the default gateway and DNS. Only then inspect RF; a strong signal with no DHCP is not an RF problem.
Traps that cost marks
- Starting with RF when the client timeline shows an authentication or DHCP failure.
- Comparing data from different time windows or time zones.
- Assuming packet capture is available on every license tier.
- Capturing on the wrong radio or interface and concluding nothing arrived.
- Treating an alarm as the root cause without checking the event sequence.