The question
A frame arrives bit by bit. The switch needs the destination MAC to decide where it goes, and that's in the first 6 bytes. Should it start sending straight away, or wait for the whole frame?
Where each mode starts forwarding
| Mode | Starts forwarding after | Latency | Bad frames |
|---|---|---|---|
| Store-and-forward | The whole frame, after checking the FCS | Highest; grows with frame size | Dropped: corrupt frames never leave the switch |
| Cut-through | The destination MAC | Lowest, constant | Forwarded: the error is found too late (counted, not stopped) |
| Fragment-free | The first 64 bytes | Low | Collision fragments dropped; other corruption forwarded |
Which is used where?
- Campus switches (for example most Cisco Catalyst models) use store-and-forward. The extra microseconds don't matter for users, and dropping corrupt frames keeps errors local.
- Data-centre switches (for example many Cisco Nexus models) often use cut-through where low, predictable latency matters, such as storage and trading networks.
- A switch must store-and-forward when the ports run at different speeds (e.g. 1 Gbps in, 10 Gbps out), or when it's congested and has to buffer anyway.
- Fragment-free mattered in the era of collisions; it's rare today.
Check yourself
Which mode drops a frame whose FCS is wrong before forwarding it?
Why must a switch store-and-forward from a 1 Gbps port to a 10 Gbps port?