Chapters0/30 ▾
Chapter 4 · Lesson 3 of 5
Seeing traffic: flow data, TAPs, mirror ports and availability checks
1 min read
Pick the monitoring method by the question you need answered and what you can afford to store.
- Flow data (such as IPFIX) keeps conversation metadata: addresses, ports, protocol, interface and packet and byte counts. It answers who talked to whom and how much, for top-talker and capacity work, without storing payloads.
- Full packet capture keeps whole frames, so it answers the most but costs the most storage.
- A port mirror (SPAN) uses switch resources and drops frames when the mirrored traffic exceeds the monitor port. A passive TAP copies the signal in hardware, adds no switch load and even passes frames with CRC errors.
- Availability monitoring only asks whether a device answered, and those results become uptime percentages for service-level reports. Performance monitoring asks how well a reachable device runs.
Example: to find last week's top bandwidth users without keeping terabytes, export flow records to a collector rather than capturing every packet on the core uplink.
Check yourself
1. For capacity planning, a team must identify which internal hosts consumed the most bandwidth over the past week, to which destinations and over which ports, using a method that does not require storing terabytes of traffic. Which monitoring method fits best?
2. A forensic analysis must see every frame crossing a heavily loaded 1 Gbps link, including frames with CRC errors, and must not add load to the switch or risk silently dropping traffic. Which capture method best meets these constraints?
Facts checked 2026-11-16 · Sources: CompTIA Network+ certification overview, RFC 5424: The Syslog Protocol, NIST SP 800-34 Rev. 1: Contingency Planning Guide for Federal Information Systems
CompTIA Network+ cheat sheet: every key fact on one page →