Campus Access Monitoring, Management, and Troubleshooting
This domain tests how you observe and fix the network: monitoring/management platforms, logging, and a structured troubleshooting method. Know the tool categories: centralized management for configuration and firmware, monitoring/analytics for client and RF health, syslog for events, SNMP for polling, and RADIUS/authentication logs for access issues. Understand that a single management plane should push consistent config to many devices.
Troubleshooting should be layered: physical/link (cable, PoE, interface state) → Layer 2 (VLAN, trunk, spanning tree, MAC learning) → Layer 3 (IP, ARP, routing, DHCP relay) → policy/security (auth role, ACL) → application. Ask "what changed?" and "how many users affected?" - one user points to client/auth; many users on one switch points to link/VLAN; many across a site points to gateway/routing/DHCP.
Traps: jumping to the wireless layer when the real fault is DHCP or VLAN; trusting a green dashboard without checking interface counters (errors, discards, PoE budget); ignoring time synchronization, which breaks log correlation; and forgetting that monitoring depends on correct SNMP credentials and syslog destinations. Also watch for questions that ask for the first step - usually verify the physical/link and interface state before deeper config.
Worked example: users on one floor cannot get addresses. Check the access switch interface state and VLAN membership, confirm the trunk allows the VLAN, verify the SVI is up, confirm the DHCP relay address and that the server has a matching scope, then check counters for errors. This ordered path isolates link, VLAN, gateway, and DHCP causes quickly instead of guessing.