Physical ties do not form correctly the expected aggregate.
Probable causes
- different LACP mode
- VLAN/port mode
- port channel
Verifications.
- Limit the impact. — Identify whether an endpoint, service, or whole site is affected.
- Collect evidence. — Keep the exact error message, timestamp, and associated logs.
- Test the simplest hypothesis first. — Compare the affected system with a known-good path.
- Correct the confirmed cause and validate the result. — Apply one controlled change at a time and retest.
Solutions.
- Correct the confirmed cause rather than the symptom.
- Document the change and its result.
- Establish monitoring if the fault can recur.
When to escalate?
Escalate if the impact expands, data are at risk, or remediation requires an irreversible change.
LACP negotiation focus
An interface that remains individual has not joined the expected aggregation. Compare both ends of the bundle instead of troubleshooting each physical link independently, because LACP requires compatible settings and a valid partner relationship.
What to verify
- Confirm LACP mode on both devices; at least one side should actively initiate negotiation.
- Check speed, duplex, MTU, VLAN or trunk configuration and the logical aggregation identifier for every member.
- Inspect actor and partner system IDs, keys and LACP state flags to find a member that belongs to a different bundle.
- Look for physical errors, excessive flaps or a link connected to the wrong switch or stack member.
Resolution path
Align the member configuration with the working links, remove stale aggregation membership if necessary, then re-add the interface to the correct port-channel or bond.
Validation
Confirm that the member changes from individual to collecting and distributing state, and verify traffic distribution across the bundle without packet loss.