liveBook · Manning

Information flow

As explained in Acing the CCNA Exam: Volume 1 Fundamentals and Protocols

A flow is a communication between two network nodes whose traffic can be assigned consistently to a physical link.

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.

How Acing the CCNA Exam: Volume 1 Fundamentals and Protocols covers it

How deep it goes
Defines directional flows, identifies MAC and IP parameters, and shows verification output without detailing hashing internals.
Examples
Uses PC1-to-SRV1 and reverse traffic, plus MAC-address and IP-address parameter tables and IOS command output.
What it assumes
Assumes only the idea of communicating network nodes and frames; distinguishes IP-carrying from non-IP frames.
What you can do after
Operate EtherChannel load balancing by configuring parameters and verifying them with show etherchannel load-balance.
How it connects
Connects flow with EtherChannel, load balancing, MAC addresses, and IP addresses.

Also explained in

Compare how 2 books explain information flow →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Acing the CCNA Exam: Volume 1 Fundamentals and Protocols. The section links point to the parts of the book it draws on.