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.
Ethernet destination FF:FF:FF:FF:FF:FF means broadcast. EtherType 0x0806 identifies ARP (for an untagged Ethernet II frame).
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.
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.
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.
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.
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.
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.
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 egressUnlike the Ethernet and ARP fields, this is internal metadata. There is no standardized on-wire “buffer ID”.
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.
The lab shows one teaching model. Real switches differ in where replication occurs. Pick a style; the star marks the replication point.
| Statement | Verdict |
|---|---|
| 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. |
Choose one answer per question, then check the explanations.
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.