NETWORKS · SWITCHING · INTERMEDIÁRIO

LACP and Link Aggregation

IEEE 802.1AX link aggregation, member selection, hashing, resiliency and troubleshooting.

01 · OVERVIEW

What this topic solves

IEEE 802.1AX link aggregation, member selection, hashing, resiliency and troubleshooting.

Core concepts: lacp, lag, etherchannel, bonding, mlag, hash.

02 · MENTAL MODEL

Follow state and packet path

Validate the Layer 2 domain, VLAN/bridge-domain, MAC learning, port state, loops, MTU and counters before changing configuration.

Input → classification/state → decision → table → next-hop/output → counters

03 · DESIGN

Design before configuration

Define the failure domain and expected convergence behavior.
Document addressing, identifiers, timers, MTU and policy boundaries.
Prefer explicit, observable state over assumptions.
Plan rollback and out-of-band access before risky changes.

Operational examples

Commands and verification

Command syntax varies by platform and software release. The examples below come from the existing portal content and must be validated against the target platform documentation before production use.

Camadas do diagnóstico:
PHY up
  ↓
LACPDU TX/RX
  ↓
Actor/Partner coerentes
  ↓
Membro selecionado/synchronized
  ↓
Collecting/Distributing
  ↓
Tráfego realmente balanceado

Exemplo conceitual:
hash(src-ip, dst-ip, src-port, dst-port)
              ↓
       membro 1, 2, 3 ou 4

Mesmo fluxo → mesmo membro (normalmente)
Muitos fluxos → melhor distribuição estatística

04 · TROUBLESHOOTING

Evidence-driven workflow

Define source, destination, time window and exact symptom.
Establish the expected healthy state and compare it with the observed state.
Inspect counters, tables, logs and packet captures before resets.
Test one hypothesis at a time and prefer reversible changes.
Repeat the original test after correction and check side effects.

05 · STANDARDS

IEEE 802.1AX

Use the current standard/RFC and the documentation for the exact software release being operated. Vendor syntax is an implementation detail; protocol behavior should be understood independently.

06 · LAB

Prove the behavior in a controlled topology

Build the smallest topology that reproduces the mechanism, capture control and data traffic, introduce one deliberate failure and diagnose it before applying the fix.

07 · CONTINUE