Port Aggregation/LACP, MTU, Jumbo Frames, and Interface Settings
Key Takeaways
- Link aggregation combines multiple physical links into one logical link for redundancy and load sharing.
- LACP dynamically negotiates link aggregation membership and helps avoid some manual bundling mistakes.
- All member links in a port channel should have compatible speed, duplex, VLAN, trunk, and MTU settings.
- MTU mismatches can cause intermittent or size-dependent connectivity problems.
- Jumbo frames require end-to-end support across the relevant path.
Port Aggregation, MTU, and Interface Settings
Switch implementation is not only VLAN assignment. Real deployments also require matching interface settings, redundancy choices, and frame-size compatibility.
Link Aggregation and LACP
Link aggregation combines multiple physical links into a logical bundle. The bundle may be called a port channel, EtherChannel, LAG, or bond depending on platform.
| Concept | Meaning |
|---|---|
| Link aggregation | Multiple physical links operate as one logical link |
| LACP | Standards-based negotiation for link aggregation |
| Static aggregation | Manual bundling without negotiation |
| Load sharing | Traffic distributed across member links based on hashing |
| Redundancy | Bundle can stay up if one member link fails |
Aggregation does not usually make one single flow use every link at once. Hashing commonly places a flow on one member link based on source and destination values. Many flows can use the aggregate capacity.
Port Channel Consistency
| Setting | Why it must match |
|---|---|
| Speed | Incompatible speeds can keep members out of the bundle |
| Duplex | Mismatch can cause errors or poor performance |
| Access/trunk mode | Bundle must behave as one logical interface |
| Allowed VLAN list | Trunk members must carry the same VLANs |
| Native VLAN | Untagged traffic must be consistent |
| MTU | Frame-size mismatch can drop larger frames |
| LACP mode | Both sides must negotiate compatible behavior |
Configure logical settings on the port channel when the platform expects it. A common PBQ clue is that one physical member has a different allowed VLAN list or MTU, causing it to be suspended.
MTU and Jumbo Frames
MTU is the maximum transmission unit for frames or packets on a link. Standard Ethernet payload MTU is commonly 1500 bytes. Jumbo frames are larger frames used in some data center, storage, backup, or virtualization networks.
| MTU topic | Exam clue |
|---|---|
| Standard MTU | Most general-purpose Ethernet networks |
| Jumbo frame | Larger-than-standard frame, often around 9000 bytes depending on platform |
| MTU mismatch | Small pings work but large transfers fail |
| Path MTU | Effective size across the whole path |
| Fragmentation or drop | Larger packets fail when DF behavior or device limits apply |
Jumbo frames must be supported end to end across the relevant path. Enabling jumbo frames on only one switch port does not help if the server, switch uplinks, router, firewall, or storage interface cannot handle the size.
Speed, Duplex, and Autonegotiation
| Setting | Good state | Bad clue |
|---|---|---|
| Speed | Matches peer or negotiates correctly | One side forced, other side auto with mismatch |
| Duplex | Full duplex on modern switched links | Late collisions or poor performance |
| Autonegotiation | Consistent policy on both sides | One side forced without matching peer |
| Error counters | Low or stable | CRC errors, runts, giants, drops |
| Interface status | Up/up for working link | Administratively down or err-disabled |
Duplex mismatch is less common with modern equipment than it once was, but Network+ still expects you to recognize symptoms such as poor throughput, collisions, and interface errors.
PBQ Guidance
| Requirement | Likely configuration |
|---|---|
| Redundant high-speed switch uplink | LACP port channel |
| Storage network using large frames | Jumbo MTU across all participating interfaces |
| One port channel member suspended | Compare speed, duplex, VLAN, trunk, MTU, and LACP mode |
| Small traffic works but backups fail | Investigate MTU and jumbo-frame consistency |
| Interface shows CRC errors | Check cable, transceiver, speed/duplex, and physical layer |
Common Traps
| Trap | Better reasoning |
|---|---|
| Expect aggregation to multiply one TCP flow by all links | Load sharing is usually flow-hash based |
| Enable jumbo frames only on the endpoint | All devices in the path must support the larger MTU |
| Mix access and trunk members in one bundle | Port channel members need consistent switching mode |
| Ignore physical errors during VLAN troubleshooting | Bad cabling or optics can mimic higher-layer issues |
| Force speed on one side and leave the other side inconsistent | Match policy on both ends |
Which protocol is commonly used to dynamically negotiate a link aggregation bundle?
Small pings work, but large file transfers across a storage VLAN fail after jumbo frames were enabled on only one switch. What is the likely issue?
Which settings should be consistent across port channel member links? Select two.
Select all that apply