Quibank app: now on the App Store — free, works offline. Get the app ↗

Chapters0/30 ▾
  1. 1.Models, Media & Topologies0/5
    1. The OSI and TCP/IP models: layers, data units and devices
    2. Copper and fiber: categories, distances and connectors
    3. Installing cable: plenum ratings and Power over Ethernet
    4. Wireless basics: channels, bonding, antennas and identifiers
    5. Topologies and network types: domains, mesh, spine and leaf, SAN
  2. 2.IP Addressing, Subnetting & Routing0/5
    1. IPv4 subnetting with the block-size method
    2. Private, loopback and APIPA ranges, and traffic types
    3. How routers choose a path: prefix, distance, metric and summaries
    4. IPv6: shortening, address types, SLAAC and NAT64
    5. VLANs, inter-VLAN routing and NAT
  3. 3.Ports, Protocols & Services0/5
    1. Well-known ports: secure and cleartext pairs
    2. TCP and UDP: handshake, flow control and real-time traffic
    3. DNS and DHCP: transports, records, relays and reservations
    4. Time and monitoring protocols: NTP and SNMP
    5. Tunnels, IPsec and QoS markings
  4. 4.Network Operations0/5
    1. Network documentation and the device lifecycle
    2. Monitoring with baselines, SNMP and syslog
    3. Seeing traffic: flow data, TAPs, mirror ports and availability checks
    4. Disaster recovery and high availability
    5. Change management and configuration baselines
  5. 5.Network Security0/5
    1. Core security terms: CIA, risk vocabulary and zero trust
    2. Identity and access: AAA, 802.1X, RADIUS, TACACS+, MFA and RBAC
    3. Filtering and segmentation: ACLs, screened subnets and IDS
    4. Recognizing network attacks from their symptoms
    5. Hardening, wireless authentication and physical security
  6. 6.Network Troubleshooting0/5
    1. The troubleshooting methodology, step by step
    2. Cable faults, distance limits, PoE budgets and the right tester
    3. Reading interface counters and port states
    4. Addressing and service failures: masks, DHCP, duplicates, loops, ACLs, DNS
    5. Wireless and voice quality problems
Saved in this browser. Move it to another device →
← Network Operations

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 →