Collision Domain and Broadcast Domain

Collision Domain and Broadcast Domain are two fundamental concepts in Ethernet network design and troubleshooting. A Collision Domain is the portion of a network where packet collisions can occur, while a Broadcast Domain is the portion where broadcast frames are flooded to all devices. Cisco switches separate Collision Domains but not Broadcast Domains (unless VLANs are used), whereas routers separate both. This article explains these concepts in detail, their behavior in Cisco switches and routers, and practical examples.

Collision DomainBroadcast DomainCisco Switch Router

~3 min read · Updated Apr 12, 2026

Introduction

In Ethernet networks, two key concepts are essential for understanding network performance and design: Collision Domain and Broadcast Domain. These concepts directly affect network efficiency, security, and scalability. Cisco devices such as switches and routers behave differently regarding these domains.

What is a Collision Domain?

A Collision Domain is a segment of the network where if two devices transmit data at the same time, a collision occurs. In old hub-based networks, all ports shared one single Collision Domain.

Main characteristics:

  • Occurs in Half-Duplex mode
  • Managed by CSMA/CD
  • Almost eliminated in modern Full-Duplex networks

What is a Broadcast Domain?

A Broadcast Domain is the portion of a network where broadcast frames (such as ARP requests) are flooded to all devices. Any device that receives a broadcast frame belongs to the same Broadcast Domain.

Cisco Switch Behavior

Cisco switches:

  • Create a separate Collision Domain for each port (micro-segmentation)
  • By default, all ports belong to one single Broadcast Domain
  • Can separate Broadcast Domains using VLANs

Example on a Switch

A 24-port switch without VLANs:

  • Number of Collision Domains = 24 (one per port)
  • Number of Broadcast Domains = 1

Cisco Router Behavior

Cisco routers:

  • Each interface creates its own Collision Domain and Broadcast Domain
  • Do not forward broadcast frames from one interface to another
  • Act as a natural boundary for Broadcast Domains

Example on a Router

A router with 3 active interfaces:

  • Number of Collision Domains = 3
  • Number of Broadcast Domains = 3

Comparison Table: Switch vs Router

DeviceCollision DomainBroadcast Domain
HubAll ports sharedAll ports shared
Switch (no VLAN)One per portAll ports shared
Switch with VLANOne per portOne per VLAN
RouterOne per interfaceOne per interface

Checking and Configuring in Cisco IOS

Viewing Collision and Broadcast Information

Switch# show interfaces GigabitEthernet0/1
Switch# show vlan brief

Creating VLAN to Separate Broadcast Domains

Switch(config)# vlan 10
Switch(config-vlan)# name Sales
Switch(config-vlan)# exit
Switch(config)# interface range Gi0/1 - 8
Switch(config-if-range)# switchport mode access
Switch(config-if-range)# switchport access vlan 10

Important Design Considerations

  • The more Collision Domains you have, the fewer collisions occur (this is why switches are better than hubs).
  • Smaller Broadcast Domains mean less unnecessary traffic and better network performance.
  • Routers and Layer 3 switches are the best tools for separating Broadcast Domains.
  • In large networks, use VLANs, VTP, and inter-VLAN routing.

Conclusion

Understanding Collision Domain and Broadcast Domain is essential for designing efficient and trouble-free networks. Switches separate Collision Domains per port and use VLANs to separate Broadcast Domains. Routers naturally separate both domains. Mastering these concepts helps you design better Cisco networks, troubleshoot effectively, and optimize performance.

Written & researched by Dr. Shahin Siami

Related Articles

SDN and SD-WAN Fundamentals: Separating the Control Plane from the Data Plane

Traditional networking, covered throughout most of this series, distributes intelligence across every individual device, each making its own independent forwarding decisions. Software-Defined Networking fundamentally changes this by centralizing that intelligence, and this article explains the control plane and data plane separation underlying SDN, covers how SD-WAN applies these principles specifically to wide area network connectivity, and explains the practical benefits this architectural shift provides.

Continue

Enterprise Network Architecture: The Three-Tier Design Model

Every technology covered so far in this series -- VLANs, routing protocols, redundancy protocols -- needs an overall architectural framework to be deployed coherently rather than as an ad hoc collection of features. This article explains the classic three-tier hierarchical design model, covers the distinct role each layer plays, explains the simplified two-tier collapsed core alternative, and discusses how these models extend into modern data center design.

Continue

Multicast Fundamentals: IGMP and PIM Explained

Sending the same video stream individually to a thousand viewers would waste enormous bandwidth, and multicast solves this by delivering a single stream efficiently to exactly the devices that actually want it. This article explains how multicast addressing differs from unicast and broadcast, covers IGMP as the protocol hosts use to join multicast groups, and walks through how PIM builds the distribution trees that carry multicast traffic efficiently through a network.

Continue

First Hop Redundancy Protocols: HSRP, VRRP, and GLBP Explained

Every host on a network relies on a single default gateway, and that gateway becoming a single point of failure would undermine the redundancy carefully built everywhere else in the network. This article explains why first hop redundancy matters, walks through HSRP's active/standby model, compares it against the open-standard VRRP, and covers GLBP's added ability to load-balance traffic across multiple routers simultaneously.

Continue

Route Redistribution: Exchanging Routes Between Different Routing Protocols

Real enterprise networks often run multiple routing protocols simultaneously, whether due to mergers, legacy equipment, or vendor requirements, and these protocols do not automatically share routes with each other. This article explains why redistribution becomes necessary, covers the critical metric mismatch problem between protocols, walks through configuring redistribution between OSPF and EIGRP, and covers the routing loop risks that make careful redistribution design essential.

Continue

BGP Fundamentals: The Protocol That Runs the Internet

Every interior routing protocol covered so far in this series operates within a single organization's network, but connecting separate organizations together across the internet requires an entirely different protocol built around policy rather than pure shortest-path calculation. This article explains what makes BGP a path-vector protocol, covers the distinction between eBGP and iBGP, walks through essential path attributes used for path selection, and covers basic BGP configuration and verification.

Continue