---
title: Packet Switching Concepts
tags: Cisco IOS, networking, manual, reference, router, switch, technical
---

<header>
<h6>Packet Switching Concepts</h6>

> [toc]
</header>
---

# Frame Forwarding

### Learn and Forward
**The following two-step process is performed on every Ethernet frame that enters a switch:**

<dl class='step-list'>
<dt>Learn - Examining the Source <abbr title="Media Access Control">MAC</abbr> Address</dt>
<dd>
<br>
<ul>
<li>If the source MAC address does not exist in the MAC address table, the MAC address and incoming port number are added to the table.</li>
<li>If the source MAC address does exist, the switch updates the refresh timer for that entry. By default, most Ethernet switches keep an entry in the table for five minutes.</li>
<li>If the source MAC address exists in the table, but on a different port, the switch treats this as a new entry. The old entry is replaced using the same MAC address, but with the more current port number.</li>
<br>
</ul>
</dd>
<dt>Forward - Examining the Destination <abbr title="Media Access Control">MAC</abbr> Address</dt>
<dd><br>
<ul>
<li>If the destination MAC address is in the table, it will forward the frame out of the specified port.</li>
<li>If the destination MAC address is not in the table, the switch will forward the frame out of all ports except the incoming port. This is called an unknown unicast. If the destination MAC address is a <b>broadcast</b> or a <b>multicast</b> address, the frame is also flooded out all ports except the incoming port.</li>
</ul>
</dd>
</dl>

## Store-and-Forward Switching
This method makes a forwarding decision on a frame after it has received the entire frame and checked the frame for errors using a mathematical error-checking mechanism known as a cyclic redundancy check (CRC). Store-and-forward switching is Cisco’s primary LAN switching method.

* **Error checking** - After receiving the entire frame on the ingress port, the switch compares the frame check sequence (FCS) value in the last field of the datagram against its own FCS calculations. The FCS is an error checking process that helps to ensure that the frame is free of physical and data-link errors. If the frame is error-free, the switch forwards the frame. Otherwise, the frame is dropped.
* **Automatic buffering** - The ingress port buffering process used by store-and-forward switches provides the flexibility to support any mix of Ethernet speeds. For example, handling an incoming frame traveling into a 100 Mbps Ethernet port that must be sent out a 1 Gbps interface would require using the store-and-forward method. With any mismatch in speeds between the ingress and egress ports, the switch stores the entire frame in a buffer, computes the FCS check, forwards it to the egress port buffer and then sends it.

## Cut-Through Switching
This method begins the forwarding process after the destination MAC address of an incoming frame and the egress port have been determined.

While the **store-and-forward** switching method drops frames that do not pass the FCS check, the **cut-through** switching method does not perform an FCS check. This gives it the ability to perform rapid frame switching: the switch can make a forwarding decision as soon as it has looked up the destination MAC address of the frame in its MAC address table. The switch does not have to wait for the rest of the frame to enter the ingress port before making its forwarding decision.

The lower latency speed of cut-through switching makes it more appropriate for extremely demanding, high-performance computing (HPC) applications that require process-to-process latencies of 10 microseconds or less.

Because the cut-through switching method can forward frames with errors, this method can have a negative impact on bandwidth, clogging up the network with damaged and invalid frames.

**Fragment free** switching is a modified form of cut-through switching in which the switch only starts forwarding the frame after it has read the Type field. Fragment free switching provides better error checking than cut-through, with practically no increase in latency.

# Collision and Broadcast Domains

## Collision Domains
In legacy **hub-based** Ethernet segments, network devices competed for the shared medium. The network segments that share the same bandwidth between devices are known as **collision domains**. When two or more devices within the same collision domain try to communicate at the same time, a collision will occur.

If an Ethernet switch port is operating in **half-duplex**, each segment is in its own collision domain. If the switch port is connected to a device operating in half-duplex, such as a legacy hub, then the switch port will operate in half-duplex.

There are no collision domains when switch ports are operating in **full-duplex**.

## Broadcast Domains
A collection of interconnected switches forms a **single broadcast domain**. When two switches are connected together, the **size of the broadcast domain is increased**. Only a network layer device, such as a router, can divide a Layer 2 broadcast domain. **Routers are used to segment broadcast domains**, but will also segment a collision domain.

The Layer 2 broadcast domain is referred to as the **MAC broadcast domain**. The MAC broadcast domain consists of all devices on the LAN that receive broadcast frames from a host.

When a switch receives a broadcast frame, it forwards the frame out each of its ports, except the ingress port where the broadcast frame was received. Too many broadcasts and a heavy traffic load on a network can result in congestion, which slows down network performance.

---

*[LAN]: Local Area Network

---

{%hackmd 7PGmjAHeTXak2VUM3iw5Wg %}