VMware ESXi and vSphere Cluster Management
Broadcast Domains Explained
Learn how Ethernet broadcasts work, how switches, VLANs, and routers affect broadcast domains, and how to count and troubleshoot them.
A broadcast domain is the Layer 2 scope in which devices receive an Ethernet broadcast frame. In a typical LAN, this scope includes every device in the same Ethernet segment or VLAN. A broadcast is intended for every eligible host in that local scope, not for one specific destination.
Understanding broadcast domains helps explain ARP, VLAN segmentation, router boundaries, and why adding ordinary switches does not automatically divide a LAN.
What Is a Broadcast Domain?
An Ethernet broadcast is a frame addressed to every device on the local Ethernet broadcast domain. Ethernet identifies this destination with the all-ones MAC address:
FF:FF:FF:FF:FF:FFA broadcast domain therefore consists of the Layer 2-connected devices that can receive such a frame. If two hosts are in the same unsegmented VLAN, a broadcast sent by one can reach the other through the Layer 2 network.
A broadcast domain is related to, but not identical to, an IP subnet. A subnet is a Layer 3 addressing and routing concept, while a broadcast domain is a Layer 2 forwarding scope. In a common design, one routed VLAN is assigned one IP subnet, so one broadcast domain aligns with one IP subnet. However, the terms describe different properties and should not be treated as synonyms.
How Ethernet Broadcasts Behave
When a host creates a broadcast frame, it places FF:FF:FF:FF:FF:FF in the destination MAC address field. A Layer 2 switch recognizes the frame as a broadcast and floods it through the relevant ports in the same VLAN, except the port where the frame entered.
Every eligible device in that VLAN receives the frame and decides whether to process it. The switch does not send the broadcast into a different VLAN. It also does not normally send an ordinary Ethernet broadcast through a router interface.
ARP: A Common Broadcast Use Case
ARP, the Address Resolution Protocol, is used in IPv4 LANs to discover the MAC address associated with a local IPv4 address. A host needs a destination MAC address before it can send an IPv4 packet directly across Ethernet.
ARP for a Local Destination
Suppose Host A and Host B are on the same IP subnet. Host A does not yet know Host B's MAC address. Host A sends an ARP request as an Ethernet broadcast, asking which device owns Host B's IPv4 address.
- Host A sends the ARP request to
FF:FF:FF:FF:FF:FF. - The Layer 2 switch floods the request within the VLAN, excluding Host A's ingress port.
- Host B recognizes its own IPv4 address in the request and sends an ARP reply directly to Host A's MAC address.
- Host A can then send the IPv4 traffic in a unicast Ethernet frame.
ARP for a Remote Destination
If the destination is outside Host A's IP subnet, Host A does not broadcast an ARP request for the remote host. Instead, Host A determines that the destination is remote and ARPs for the MAC address of its default gateway.
The default gateway is the local router address used to reach remote IP networks. Host A sends the packet in an Ethernet frame addressed to the gateway's MAC address. The router receives the frame, removes the local Ethernet framing, routes the IP packet, and creates a new frame on the next network. It does not relay Host A's original Ethernet broadcast into the remote LAN.
How Common Devices Affect Broadcast Domains
| Device | Primary OSI layer | Forwards or floods Ethernet broadcasts | Creates a new broadcast domain by default | Key note |
|---|---|---|---|---|
| Hub | Layer 1 | Repeats the electrical signal to other ports | No | A hub does not inspect MAC addresses or divide broadcast scope. |
| Bridge | Layer 2 | Ordinarily forwards or floods broadcasts | No | It can filter some unicast traffic but remains in the same Layer 2 network. |
| Layer 2 switch | Layer 2 | Floods broadcasts within the VLAN | No | Adding ordinary switches does not create additional broadcast domains. |
| Router | Layer 3 | No, not for ordinary Layer 2 Ethernet broadcasts | Yes | Each routed interface connects to a separate attached Layer 2 segment. |
| Layer 3 switch | Layers 2 and 3 | Within each VLAN, but not across routed VLAN interfaces | Yes, when routing is configured between VLANs | It can switch locally and route between separate VLAN broadcast domains. |
| VLAN-enabled switch | Layer 2 | Within each individual VLAN | Yes, per configured VLAN | VLANs create logical Layer 2 networks on the same physical switch. |
Hubs, Bridges, and Layer 2 Switches
A hub is a Layer 1 device. It repeats incoming electrical signals to its other ports without making forwarding decisions. Broadcasts therefore reach all connected devices, and the hub does not divide the broadcast domain.
A bridge is a Layer 2 forwarding device. It can learn or filter MAC addresses for some unicast traffic, but it ordinarily forwards broadcasts throughout the connected Layer 2 network.
A Layer 2 switch is essentially a multiport bridge that learns source MAC addresses. It forwards known unicast frames selectively, but it floods broadcasts throughout the same VLAN. Connecting two ordinary switches therefore leaves the connected ports in one broadcast domain when they carry the same VLAN.
VLANs Change the Scope
A VLAN is a logical Layer 2 network on a switch. Each VLAN is normally a separate broadcast domain. For example, ports assigned to VLAN 10 and ports assigned to VLAN 20 can share one physical switch while remaining separate broadcast scopes.
A broadcast from VLAN 10 is flooded only to eligible VLAN 10 ports. It is not flooded into VLAN 20. Normal communication between the VLANs requires a Layer 3 device, such as a router or a Layer 3 switch, and each VLAN commonly uses a different IP subnet.
Routers as Broadcast-Domain Boundaries
A router forwards packets between different IP networks. It does not forward ordinary Layer 2 Ethernet broadcasts between its interfaces. Each router interface connects to a separate attached Layer 2 broadcast domain.
Routing can divide a large LAN into smaller broadcast scopes. ARP requests and similar local broadcasts remain on the interface's attached network instead of reaching every device connected to the router's other interfaces.
For example, if one router interface connects to a user LAN and three other interfaces connect to three additional LANs, the topology contains four broadcast domains: one for the user LAN and one for each additional routed LAN.
Broadcast Domains and Network Performance
Broadcasts are normal and useful. ARP, address discovery, and some service-discovery protocols depend on local broadcast behavior. The problem is not that every broadcast is automatically harmful; the concern is the size and activity level of the broadcast scope.
When a broadcast reaches many devices, it consumes bandwidth on the links that carry it. Each receiving host also needs to inspect and often process the frame, using CPU time and interrupt resources. A very large or noisy broadcast domain can therefore reduce scalability and make faults affect more devices.
Routed segmentation reduces the number of devices affected by each broadcast. VLANs can define smaller Layer 2 scopes, and routers or Layer 3 switches can provide controlled communication between them. This contains traffic and improves scalability, while still allowing designs to use broadcasts where they are appropriate.
Broadcast Domains Versus Collision Domains
A collision domain is the portion of an Ethernet network in which simultaneous transmissions could collide on shared or half-duplex media. A broadcast domain answers the question, “Who receives this Layer 2 broadcast?” A collision domain answers the question, “Which devices might contend for the same shared transmission medium?”
| Characteristic | Broadcast domain | Collision domain |
|---|---|---|
| What traffic defines it | Ethernet broadcast frames addressed to FF:FF:FF:FF:FF:FF | Shared or half-duplex transmission where simultaneous sends could collide |
| Typical boundaries | Routers and VLAN boundaries | Switch ports, bridges, and separate physical shared-media segments |
| Effect of a hub | Does not divide it | Creates one shared collision domain across the hub segment |
| Effect of a Layer 2 switch | Does not divide it when ports are in the same VLAN | Generally creates a separate collision domain per port in half-duplex Ethernet |
| Effect of a router | Divides broadcast domains at its interfaces | Separates the attached physical or Layer 2 segments |
| Relevance in full-duplex Ethernet | Still matters because broadcast scope remains a Layer 2 design concern | Modern full-duplex Ethernet does not experience CSMA/CD collisions |
CSMA/CD means Carrier Sense Multiple Access with Collision Detection. It was the legacy Ethernet access method for shared, half-duplex media. A host listened before transmitting and detected collisions when simultaneous transmissions occurred. Modern switched full-duplex Ethernet does not use CSMA/CD for normal operation, but broadcast-domain boundaries remain important.
How to Count Broadcast Domains in a Topology
- Locate every router interface or other Layer 3 routed boundary.
- Identify every VLAN. Separate VLANs are separate broadcast domains even if they exist on the same physical switch.
- Group hubs, bridges, and switch ports that are connected within the same unsegmented VLAN.
- Count one broadcast domain for each distinct Layer 2 segment attached to a routing interface.
- Do not count each switch port as a separate broadcast domain. A switch port is usually a separate collision domain, not a separate broadcast domain.
| Network area | Devices included | Boundary device or VLAN | Broadcast-domain count |
|---|---|---|---|
| Shared LAN containing hubs, bridge, and switch | PCs and Layer 2 devices connected within the same VLAN | Bounded by the router interface connected to this LAN | 1 |
| Each additional LAN connected to a distinct router interface | Devices in that interface's attached Layer 2 segment | The corresponding router interface | 1 per additional LAN |
| Total for one shared LAN plus three additional routed LANs | All four separate Layer 2 areas | Router interfaces | 4 |
Worked Topology Example
Imagine six PCs connected through two hubs, one bridge, and one Layer 2 switch. If these devices are all part of the same VLAN and the router connects that LAN to three other LAN segments, the hubs, bridge, and switch together form one broadcast domain. Each of the three other router-connected LANs forms another domain. The total is four broadcast domains.
Practical Examples
Single Switched LAN
Several PCs connect to one ordinary Layer 2 switch in the same VLAN. All PCs and those switch ports belong to one broadcast domain. When one PC sends an ARP request, the switch floods it to the other eligible ports in that VLAN. The fact that each PC uses a different physical switch port does not create separate broadcast domains.
Mixed Layer 2 Devices and a Router
Hubs, a bridge, and a Layer 2 switch can extend one Layer 2 network when they are connected without VLAN or routing boundaries. The router stops the broadcast at its interface. Each additional LAN attached to a different router interface is a separate broadcast domain.
Local and Remote ARP
When Host A communicates with a host on its own subnet, it broadcasts an ARP request for that destination host's IP address. When Host A communicates with a host on another subnet, it broadcasts an ARP request for the default gateway's IP address instead. The router then forwards the IP packet, but not the original Ethernet broadcast, into the remote LAN.
VLAN Segmentation
A switch can assign user ports to VLAN 10 and VLAN 20. These VLANs are separate broadcast domains even though they use the same physical switch. Broadcasts from VLAN 10 remain in VLAN 10, and broadcasts from VLAN 20 remain in VLAN 20. A router or Layer 3 switch is required for normal traffic between them.
Troubleshooting Broadcast-Domain Problems
One VLAN Can Reach Its Members but Not Another VLAN
If a host can reach devices in its own VLAN but not a device in another VLAN, first recognize that the VLANs are separate broadcast domains. Check that the host has the correct IP address, subnet mask, and default gateway, and verify that inter-VLAN routing exists.
Two Switches Were Assumed to Create Two Domains
Two Layer 2 switches remain one broadcast domain when their connected ports carry the same VLAN and no routed boundary exists. Inspect the VLAN assignments and the link between the switches rather than counting the switches themselves.
ARP Requests Repeat Without a Reply
If a host repeatedly ARPs for an address believed to be remote, verify the subnet mask and the host's routing decision. For a remote destination, the host should normally ARP for the default gateway, not for the remote host's MAC address. Also verify that the gateway address and local connectivity are correct.
Broadcasts Appear on Many Switch Ports
Broadcast flooding across many ports in the same VLAN is normal switching behavior. It is not automatically a switching failure. If the volume is excessive, investigate the source and consider smaller VLANs, routed segmentation, or broadcast-storm controls.
Summary
- A broadcast domain is the Layer 2 scope in which devices receive Ethernet broadcasts.
- The destination MAC address for an Ethernet broadcast is
FF:FF:FF:FF:FF:FF. - Hubs, bridges, and ordinary Layer 2 switches extend or forward broadcasts within the same Layer 2 network.
- A switch creates separate broadcast scopes only when VLAN separation is configured.
- Routers do not forward ordinary Layer 2 broadcasts between interfaces; each interface marks a broadcast-domain boundary.
- ARP requests stay local. For a remote destination, a host ARPs for the default gateway.
- Broadcast domains and collision domains are different concepts. A switch port can be its own collision domain without being its own broadcast domain.
- To count domains, find routed interfaces and VLAN boundaries, then group all same-VLAN Layer 2 connections between those boundaries.
For a related explanation, see Broadcast Domain Explained.