Port Aggregation/LACP, MTU, Jumbo Frames, and Interface Settings

CompTIA Network+ N10-009

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

Current Exam Facts and Applied Networking Judgment Official Domain Weights and an 8-12 Week Study Plan How to Use Labs, Practice, and PBQ Workflow Missed-Question Notebook and Final Readiness Metrics

2 Domain 1: Networking Concepts (23%)

OSI and TCP/IP Models with Device and Protocol Mapping Networking Appliances and Where They Operate Ports and Protocol Decision Table Traffic Types and Encapsulation Flow

3 Domain 1: Media, Connectors, Transceivers, and Network Architectures

Copper, Fiber, Coax, and DAC Media Connector and Transceiver Selection Network Topologies and Design Patterns Cloud and Virtual Networking Concepts

4 Domain 1: IP Addressing and Subnetting Mastery

IPv4 Classes, Private/Public, APIPA, and Loopback CIDR, VLSM, and Subnet Math IPv6 Address Types and Notation Routing Basics and Longest Prefix Match

5 Domain 2: Network Implementation - Routing

Static vs Dynamic Routing and Route Selection OSPF, EIGRP, and BGP Basics at Network+ Depth NAT/PAT, VIP/FHRP, and Subinterfaces Routing PBQs and Troubleshooting Route Table Clues

6 Domain 2: Network Implementation - Switching

VLANs, Access Ports, Trunks, and Native VLAN STP/RSTP Loop Prevention and Bridge Roles Port Aggregation/LACP, MTU, Jumbo Frames, and Interface Settings Switch Implementation PBQs and Common Misconfigurations

7 Domain 2: Network Implementation - Wireless and Physical Implementation

Wi-Fi Standards, Bands, and Channels SSID Security, Guest Networks, and Authentication Antennas, Coverage, Roaming, Interference, and Site Surveys Physical Installation Implications

8 Domain 2: Network Implementation - Services Implementation

DNS Record Types and Troubleshooting Cues DHCP, DHCPv6, SLAAC, Scopes, Leases, and Relay NTP, PTP, NTS, and Time-Sensitive Networking Service Implementation PBQs: DNS, DHCP, VLANs, and Firewall Direction

9 Domain 3 Part A: Network Operations Documentation and Governance

Physical, Logical, Rack, Cable, Wireless Diagrams, and IPAM Asset Inventory, Baselines, SLAs, SOPs, and Runbooks Change Management and Request Tracking Lifecycle, EOL, EOS, Decommissioning, and Configuration Management

10 Domain 3 Part B: Monitoring, Remote Access, and Resilience

SNMP, Flow, Syslog, Packet Capture, Log Aggregation, APIs, and Port Mirroring Baselines and Performance Metrics Remote Access, Management Paths, and Secure Admin Habits DR and HA Concepts: RPO, RTO, MTTR, MTBF, Sites, Failover, and Testing

11 Domain 4: Logical Security and Secure Access (14%)

Encryption in Transit, Encryption at Rest, PKI, and Certificates IAM, MFA, SSO, Directory Services, and AAA Authorization, Least Privilege, RBAC, Geofencing, and Time-Based Access VPNs and Secure Management Design

12 Domain 4: Segmentation, Risk, and Network Attacks (14%)

Segmentation for Guest, BYOD, IoT, IIoT, SCADA, ICS, and OT Risk, Compliance, Audit, Data Locality, PCI, and GDPR Network Attacks and Scenario Cues Attack-to-Mitigation PBQ Tables

13 Domain 4: Security Controls and Hardening (14%)

Firewalls, IDS, IPS, Security Zones, and Screened Subnets ACLs, Filtering, NAC, Hardening, and Key Management Deception Technologies and Physical Security Zero Trust, SASE, and Trusted or Untrusted Zone Decisions

14 Domain 5: Troubleshooting Methodology and Tools (24%)

Official Troubleshooting Methodology and Evidence Handling Command-Line Tools: ping, traceroute, nslookup, dig, ipconfig, ifconfig, ip, arp, netstat, ss, and route Packet, Protocol, and Wi-Fi Analyzers Choosing the Right Tool by Symptom PBQs

15 Domain 5: Physical, Interface, and Wireless Troubleshooting (24%)

Cable Issues: Type, Attenuation, Crosstalk, Termination, and TX/RX Interface Issues: Errors, Discards, Duplex, Speed, Port Status, and PoE Transceiver, Fiber, and Signal Strength Troubleshooting Wireless Troubleshooting: Interference, Channels, Roaming, RSSI/SNR, Security, and Captive Portals

16 Domain 5: Network Services, Switching, Routing, and Performance Troubleshooting (24%)

DHCP, DNS, NTP, and IP Addressing Issues VLAN, STP, Trunk, Native VLAN, and ACL Issues Routing, Default Gateway, Route Table, and NAT Issues Congestion, Latency, Jitter, Packet Loss, and Application Performance Clues

17 Performance-Based Question Labs

Subnetting and VLSM Design Lab VLAN, Trunk, Router-on-a-Stick, and Firewall Rule Lab Wireless Deployment and Troubleshooting Lab Monitoring, Log Triage, and Route or Service Troubleshooting Lab

18 High-Yield Reference and Final Study Plan

High-Yield Ports and Protocols Table Wi-Fi, Cabling, Connectors, and Transceivers Quick Table Acronyms and Command-Line Tool Quick Table Final 7-Day Review Plan and Readiness Checklist

19 Final Synthesis: Strategy, Remediation, and Readiness

Mixed-Set Decision Strategy for Qualifiers and Close Answers Missed-Question Remediation Notebook by Error Type Exam-Day Time Management and PBQ Order 100-Question Readiness Simulation Blueprint Mapped to N10-009 Weights

Port Aggregation/LACP, MTU, Jumbo Frames, and Interface Settings

Key Takeaways Explain This Topic AI

Link aggregation bundles multiple physical links into one logical link for redundancy and load sharing.

LACP (802.3ad) dynamically negotiates the bundle; static aggregation skips negotiation and is riskier.

Aggregation hashes each flow onto one member link - a single flow does not span all links.

Standard Ethernet MTU is 1500 bytes; jumbo frames (~9000 bytes) must be enabled end-to-end.

Port-channel members must match in speed, duplex, mode, VLANs, native VLAN, MTU, and LACP mode.

Last updated: June 2026

Beyond VLANs: Real Interface Settings

Switch implementation is more than assigning VLANs. Production links also need redundancy, matched physical settings, and consistent frame sizes. Network+ tests whether you can spot the one mismatched value that breaks a bundle or a transfer.

Link Aggregation and LACP

Link aggregation combines two or more physical links into one logical link, called a port channel , EtherChannel , LAG (Link Aggregation Group), or bond depending on the platform.

Concept Meaning
Link aggregation Many physical links act as one logical link
LACP (IEEE 802.3ad) Standards-based dynamic negotiation of the bundle
Static aggregation Manual bundling, no negotiation - mismatch risk
Load sharing Flows distributed by a hash of header values
Redundancy Bundle survives loss of a member link

Key exam point: Aggregating four 1 Gbps links gives 4 Gbps of aggregate capacity, but any single TCP flow is hashed onto one member and is still capped near 1 Gbps. Many flows are needed to use the full bundle. Watch for the trap that says "bond two links to double one backup's speed" - that is wrong.

Port-channel setting Why it must match across members
Speed Mismatched speed suspends the member
Duplex Mismatch causes errors and slow links
Access/trunk mode Bundle is one logical interface
Allowed VLAN list Trunk members must carry the same VLANs
Native VLAN Untagged traffic must be consistent
MTU Frame-size mismatch drops large frames
LACP mode (active/passive) At least one side must be active

MTU and Jumbo Frames

MTU (Maximum Transmission Unit) is the largest payload a link will carry in one frame. Standard Ethernet MTU is 1500 bytes . Jumbo frames raise this to about 9000 bytes and are used in storage, backup, and virtualization networks to cut per-frame overhead.

MTU topic Exam clue
Standard 1500 MTU General-purpose Ethernet
Jumbo ~9000 MTU Storage (iSCSI), backups, vMotion
MTU mismatch Small pings work, large transfers fail
Path MTU The smallest MTU along the whole path wins
DF bit + oversize Packet dropped instead of fragmented

Critical rule: jumbo frames must be enabled end to end - every NIC, switch port, uplink, router, and storage interface in the path. Enabling 9000-byte MTU on the server and one switch but leaving the uplink at 1500 produces the classic symptom: a 64-byte ping succeeds, but a large file copy or backup stalls or fails.

Worked example: After a storage team sets MTU 9000 on a host and its access port, ping -l 1472 -f (a 1500-byte frame with DF set) succeeds, while ping -l 8972 -f (a ~9000-byte frame) fails with "packet needs to be fragmented." That gap proves the path drops oversize frames somewhere - usually an uplink still at 1500.

Speed, Duplex, and Autonegotiation

Setting Healthy state Bad clue
Speed Negotiates or matches peer One side forced, other auto
Duplex Full duplex on switched links Late collisions, slow throughput
Autonegotiation Same policy both ends One forced, one auto = duplex mismatch
Error counters Low and stable CRC, runts, giants, drops rising
Interface status up/up admin down or err-disabled

A duplex mismatch (one side full, one side half) is the classic cause of a link that works but is painfully slow with late collisions and CRC errors. The fix is to set both sides the same way - usually autonegotiation on both.

Reading Interface Counters

Counter Likely cause
CRC errors Bad cable, connector, or transceiver; sometimes duplex mismatch
Runts Frames smaller than 64 bytes - collisions or faults
Giants Frames larger than allowed MTU - jumbo/MTU mismatch
Late collisions Duplex mismatch or cable too long
Drops / discards Congestion, buffer exhaustion, or policy
PBQ Decision Table

Requirement Likely configuration
Redundant high-speed uplink LACP port channel
Storage network, large frames Jumbo MTU on every interface in path
One member suspended Compare speed, duplex, VLANs, MTU, LACP mode
Small traffic OK, backups fail Check MTU/jumbo consistency end to end
CRC errors on a port Inspect cable, transceiver, duplex
Common Traps

Trap Better reasoning
One flow uses all bundled links Flows are hashed onto one member
Jumbo frames on only the endpoint Every device in the path must support it
Mix access + trunk members in one bundle Members need identical switching mode
Ignore physical errors during VLAN work Bad optics/cable mimic higher-layer faults
Force speed on one side only Match autonegotiation policy on both ends

When a member silently drops out of a port channel, dump the bundle summary and compare it line by line to a healthy member - the suspended link almost always differs in exactly one setting.