Ethernet Mastery · Hardware Packet Walk

One ARP broadcast.
Forty-seven egress ports.
What happens inside the switch?

Does a 48-port switch store 47 complete packets? Fly through the ASIC: watch one frame get parsed, buffered once, turned into dozens of tiny work items, and shot out of every eligible port, then try to break it with a congested port.

⚡ Animated ASIC pipeline🧠 Descriptors vs copies🎛 Memory calculator🔬 Clickable ARP bytes
1START HERE

What the switch actually needs to do

① Recognize ARP broadcast

Ethernet destination FF:FF:FF:FF:FF:FF means broadcast. EtherType 0x0806 identifies ARP (for an untagged Ethernet II frame).

② Find eligible ports

Flood within the frame's VLAN to eligible forwarding ports, excluding the ingress port. Membership, STP, ACLs, storm control and hardware state can change the final list.

③ Produce distinct wire transmissions

Every selected egress port must transmit the frame. A modern ASIC can replicate metadata or descriptors instead of copying the whole payload into memory for each port.

Memory showdown: copies vs descriptors

Drag the sliders

❌ Naive: one full copy per port

✅ Shared buffer: 1 payload + pointers

Key distinction: 47 outgoing transmissions do not necessarily mean 47 full packet copies are stored simultaneously. The lab below models a shared-memory ASIC that keeps packet data in a shared buffer while egress tasks reference it. Other ASICs replicate at different stages or add egress buffering. The 16-byte descriptor size and frame-byte accounting here are illustrative assumptions. Real ASICs may remove the FCS before buffering, allocate fixed-size buffer cells, and maintain additional metadata; these totals are not measured chip memory usage.
2INTERACTIVE ASIC LAB

Fly through the chip, one stage at a time

The default has 48 ports all in VLAN 10. Eth1 is the ingress port, so 47 others are eligible before any additional policy or forwarding restrictions. Change the setup, press Next stage or Play all, and watch the packet travel. At stage 6 try the congested port switch. To replay the transmission sequence from the beginning, use Reset; going back from the final stage does not undo completed transmissions.

Switch forwarding simulator

Stage 1 of 7
SWITCH ASIC Eth1INGRESS ParserMAC · EtherTypeVLAN 10dst = broadcast L2 lookuplearn src MACflood group– Shared buffer– Replicatemake workitems0descriptors Queues0 pending EGRESS PORTS ARP
47Eligible egress
0Transmissions done
0Remaining references
0Payload buffers in use
Amber = ingress · Blue = VLAN member · Purple = queued · Green = transmitted · Gray = ineligible · Red = congested. The smaller egress-port icons in the ASIC pipeline represent a sample of ports; the front panel and counters track the full selected port set.

Hardware event log

    Model, not a chip dump: buffer handle 0x9A73, descriptors, queue layout and the reference count are illustrative. Real ASICs may use cells, VOQs, multiple replication stages or per-egress storage.

    Why reference counts help

    In this teaching model, each pending egress task holds a reference. As transmissions finish the count falls. When the last task completes, the shared payload can be reclaimed. Try the congested-port switch: a slow egress can keep the shared payload allocated even after the other ports finish.

    Does it all happen simultaneously?

    Ports may transmit concurrently, but scheduling, output congestion, fabric bandwidth and buffer architecture matter. A congested port can retain an outstanding task while faster ports finish.

    3PACKET-LEVEL UNDERSTANDING

    Click the bytes of the ARP frame

    This is the actual 42-byte Ethernet + ARP request (the wire adds padding up to 60 bytes, plus the FCS). Pick a field, or click a byte.

    Illustrative ASIC metadata

    Ingress port : Eth1
    VLAN         : 10
    Src MAC      : AA:AA:AA:AA:AA:AA
    Dst MAC      : FF:FF:FF:FF:FF:FF
    EtherType    : 0x0806
    Buffer handle: 0x9A73
    Egress set   : VLAN10 - ingress
    Queue tasks  : one per eligible egress

    Unlike the Ethernet and ARP fields, this is internal metadata. There is no standardized on-wire “buffer ID”.

    What changes between egress copies?

    In this simple access-VLAN case the same ARP content leaves each eligible port. Hardware may still apply per-egress edits: adding or removing 802.1Q tags, ACL/QoS handling, or encapsulation. “All descriptors refer to one payload” is a memory-sharing idea, not a claim that every transmitted bit is always identical.

    4WHERE DOES THE COPY HAPPEN?

    Three common replication styles

    The lab shows one teaching model. Real switches differ in where replication occurs. Pick a style; the star marks the replication point.

    StatementVerdict
    Broadcast is usually handled in the ASIC fast path.Correct for ordinary forwarded traffic on modern hardware switches; special exceptions may punt or drop frames.
    47 egress ports means 47 simultaneous full copies in RAM.Not generally true. Shared-buffer architectures can replicate descriptors instead.
    Every switch uses one shared buffer, one global buffer ID and a reference counter.Not universal. Architecture depends on the ASIC and switch design.
    Reference count always starts at 47 and reaches zero one at a time.A useful model, not a guaranteed implementation detail.
    Every port always sends a broadcast.Incorrect: VLAN, ingress exclusion, port state, filtering and policies limit the eligible set.
    Packets are never copied anywhere in hardware.Too strong. Some designs create extra copies across ASICs, pipeline stages or egress buffers.
    Hardware-backed example: Cisco's Silicon One architecture describes a shared memory packet buffer, packet descriptors, replication into virtual output queues, and further transmit-side replication and queuing. That supports descriptor-level fan-out while showing why one diagram cannot describe every switch. See the references below.
    5CHECK YOUR UNDERSTANDING

    Can you think like the forwarding ASIC?

    Choose one answer per question, then check the explanations.

    6TECHNICAL REFERENCES

    Sources and scope

    This lesson intentionally teaches a conceptual shared-buffer switch. The references describe concrete hardware or forwarding models, not a claim that every vendor implements the exact buffer ID and counter shown.