A flow is a communication between two network nodes. In EtherChannel load balancing, every message in one flow uses the same physical link, preserving consistent forwarding. section 16.3
Apply these rules when interpreting flow-based EtherChannel forwarding:
- Treat each direction as a separate flow: PC1 to SRV1 differs from SRV1 to PC1. section 16.3
- Expect uneven link use; the switch hashes configured source and destination identifiers rather than guaranteeing equal distribution. section 16.3 section 16.5
- Use parameters such as src-dst-mac or src-dst-ip to determine how flows are identified. section 16.3
PC-to-server traffic
If PC1 communicates with SRV1, all messages from PC1 to SRV1 can use one EtherChannel link, while messages from SRV1 to PC1 can use another.

