VMware ESXi and vSphere Cluster Management

CSMA/CD Explained: Ethernet Collision Detection in Half-Duplex Networks

Learn how CSMA/CD lets shared half-duplex Ethernet stations detect collisions, use backoff, and retransmit frames, plus how hubs, switches, and duplex mismatches affect troubleshooting.

CSMA/CD means Carrier Sense Multiple Access with Collision Detection. It is the traditional Ethernet method for coordinating access to a shared, half-duplex medium. Devices use it to decide when to transmit, recognize when simultaneous transmissions interfere, and retry affected frames.

CSMA/CD does not guarantee that collisions never occur. Instead, it provides a controlled way to detect collisions and recover from them. It was important when multiple Ethernet stations shared one cable or a hub-based segment. It is generally not used on ordinary modern switch-to-host links because those links normally operate in full duplex.

What the CSMA/CD Acronym Means

In this context, a station is an Ethernet interface that can transmit and receive frames. A collision occurs when two or more stations transmit on the same shared medium at overlapping times, causing their signals to interfere.

Where CSMA/CD Operates

CSMA/CD belongs to shared, half-duplex Ethernet. In half-duplex communication, a device cannot send and receive on the shared medium at the same time. Stations take turns using the medium, although their access decisions can occasionally overlap.

A collision domain is the portion of a network in which simultaneous Ethernet transmissions can interfere with one another. Every station in the same collision domain competes for the same transmission opportunity.

A repeater regenerates and forwards signals but does not separate collision domains. A hub is a multiport repeater: when it receives a signal on one port, it repeats that signal to its other ports. Consequently, all devices connected to a hub share one collision domain. A signal from one host reaches the other hosts, and a collision on the shared segment can affect every station.

By contrast, an Ethernet switch normally creates a separate collision domain for each physical port. A frame arriving on one port is forwarded based on its destination MAC address rather than being repeated indiscriminately to every port. Modern switch-to-host and switch-to-switch links also normally use full duplex.

The Normal CSMA/CD Transmission Sequence

A station with a frame to send follows a sequence similar to this:

1. Sense the carrier. The station checks whether another transmission is already present.
2. Defer if busy. If the medium is busy, the station waits until the current transmission finishes and the medium becomes idle.
3. Transmit if idle. If the medium appears idle, the station begins sending its frame.
4. Monitor while transmitting. The sender continues listening to the medium and compares what it observes with what it expects to transmit.
5. Complete the frame if there is no collision. If the required collision-detection interval passes without conflicting activity, transmission proceeds normally.

Why Collisions Can Still Occur

Carrier sensing cannot eliminate every collision because signals need time to propagate through the medium. Consider two hosts at different locations on the same shared segment:

1. Host A checks the medium and sees no signal at its location.
2. Host B checks the medium at nearly the same time and also sees no signal at its location.
3. Both hosts begin transmitting.
4. Their signals travel along the segment and eventually meet.
5. The overlapping signals corrupt the frames.

This is a consequence of propagation delay: a signal observed at one point has not necessarily reached every other point yet. The farther apart the stations are, the more important this timing issue becomes.

A collision is not the same as ordinary packet loss. Packet loss can result from congestion, a damaged frame, a failing interface, or a higher-layer timeout. A collision specifically means that overlapping transmissions interfered on a shared Ethernet medium. A duplex mismatch can produce collision-related counters and poor performance, but it is a configuration or link-mode problem rather than normal contention between correctly configured full-duplex peers.

Collision Handling: Jam Signals and Discarded Frames

When a transmitting station detects a collision, it stops sending the original frame. It then sends a jam signal. The jam signal makes the collision recognizable throughout the shared collision domain so that other stations do not mistake the damaged activity for a valid frame.

The frames involved in the collision are discarded. Ethernet does not repair the damaged frame at the collision point. The sending stations must attempt retransmission. Depending on the implementation and protocol stack, a failure after repeated attempts is exposed as an transmission error to an upper layer.

Binary Exponential Backoff

If every station retried immediately after a collision, the same stations could collide again repeatedly. CSMA/CD therefore uses a randomly selected waiting period.

Binary exponential backoff expands the possible delay range after successive collisions. After an initial collision, a station selects a random delay from a small range. If another collision occurs during the retry, the range grows. Continued collisions cause the range to grow again, reducing the probability that all competing stations choose the same retry time.

The delay is measured in slot times. The exact random-selection rules are defined by Ethernet behavior, but the important concept is that repeated contention causes a wider range of possible waits.

Ethernet limits the number of retransmission attempts. In traditional Ethernet, a frame is commonly abandoned after 16 attempts. When the retry limit is reached, the interface reports a transmission failure rather than retrying forever.

Ethernet Slot Time and Minimum Frame Size

Slot time is the interval used by Ethernet to allow a transmitting station to detect a worst-case collision on a valid shared segment. The traditional Ethernet slot time is 512 bit times.

The relationship between slot time and frame size is important. A standard Ethernet frame has a traditional minimum size of 64 bytes, not counting the preamble and start-of-frame delimiter. A sender must still be transmitting when a worst-case collision signal can return. The minimum frame size helps ensure that a collision is detected while transmission is in progress rather than after the sender has already finished.

An early collision is detected within the expected slot-time window. A late collision is detected after that normal window. Late collisions are not expected as ordinary contention on a correctly designed Ethernet segment and commonly point to a physical or duplex problem.

Half Duplex Versus Full Duplex

In full-duplex communication, a point-to-point Ethernet link has two independent directions: one for sending and one for receiving. Only two endpoints use the link, and each direction can operate concurrently. Because the transmitted signals do not compete on one shared path, there are no normal Ethernet collisions and CSMA/CD is unnecessary.

Hubs, Repeaters, and Switches

It is too broad to say that a switch can never be associated with collisions. A switch port deliberately configured for half duplex can still participate in CSMA/CD. A duplex mismatch can also create collision symptoms: one endpoint may operate at full duplex while the other operates at half duplex. The full-duplex side does not perform normal collision handling, while the half-duplex side may record collisions or late collisions.

Practical Example: Two Hosts Connected to a Hub

Imagine Hosts A, B, C, and D connected to a single hub. All four ports are part of one collision domain.

1. Hosts A and B each have a frame ready.
2. Because of propagation delay, both initially judge the medium to be idle.
3. Both hosts begin transmitting, and their signals interfere.
4. The transmitting hosts detect the collision and send a jam signal.
5. Both hosts stop sending their original frames.
6. Each host selects a random backoff delay.
7. After waiting, each host retries. Different delays make another simultaneous transmission less likely.

Some collisions are therefore normal on a busy, correctly functioning hub-based half-duplex segment. Excessive collisions, however, can reduce throughput and indicate excessive contention or a physical design problem.

Practical Example: A Host Connected to a Modern Switch

Now consider one endpoint connected directly to one switch port using full duplex. The endpoint and switch can send in both directions at once. Other switch ports do not share this physical transmission path, so the link has no normal Ethernet collision domain containing multiple competing transmitters.

CSMA/CD is not used on this link. If collision counters rise or performance is poor, investigate the negotiated duplex mode, cabling, interface errors, and possible duplex mismatch rather than assuming normal shared-medium contention.

Operational Relevance and Diagnostics

Collision counters should remain at zero on correctly operating full-duplex links. A nonzero counter on a modern connection deserves investigation, especially if it continues increasing.

On a legacy shared segment, occasional collisions can be expected. Excessive collisions may indicate:

• A hubbed or otherwise shared segment with heavy traffic.
• Excessive contention from multiple active stations.
• An oversized or invalid legacy Ethernet segment.
• A duplex mismatch between connected interfaces.
• A cabling or physical-layer fault.

Late collisions commonly warrant investigation rather than being treated as normal contention. Check duplex settings, cabling, interface statistics, and whether the topology violates applicable legacy Ethernet limits.

Cisco IOS Inspection Commands

Use the following commands to inspect an interface's speed, duplex mode, and error counters:

show interfaces <interface>

show interfaces status

Review the reported speed and duplex along with collision, late-collision, CRC, input-error, and output-error counters. Exact counter names and displayed fields vary by platform and software release.

Matching Link Configuration

Where supported, automatic negotiation at both ends is generally preferred. A basic Cisco IOS configuration is:

configure terminal
interface <interface>
speed auto
duplex auto

If static settings are required, configure compatible speed and duplex values at both endpoints. Never configure one side for full duplex and the other for half duplex unless the mismatch is intentional for a specific test.

Duplex Mismatch Investigation

Suppose a switch port is forced to full duplex while its connected legacy endpoint operates at half duplex. Common symptoms include poor throughput, intermittent connectivity, collision or late-collision counters on the half-duplex side, and frame errors or drops on the full-duplex side.

1. Use interface status and detailed interface counters to verify the speed and duplex reported at both ends.
2. Set both sides to auto-negotiate where appropriate, or match manually configured values.
3. Inspect the cable, connectors, and physical interface statistics.
4. Reset or record counters, then observe the link during a controlled test.
5. Verify that no unsupported shared-media topology remains in the path.

Exam-Relevant Summary

• CSMA/CD is an Ethernet access method for shared, half-duplex media.
• Carrier sense means listening before transmitting.
• Multiple access means multiple stations share one medium or collision domain.
• Collision detection means the sender monitors for conflicting activity while transmitting.
• A hub and repeater extend one collision domain; they do not separate it.
• A switch normally provides one collision domain per physical port.
• Full-duplex point-to-point Ethernet has no normal collisions and does not use CSMA/CD.
• After a collision, stations send a jam signal, discard the affected frames, wait using binary exponential backoff, and retry.
• The traditional Ethernet slot time is 512 bit times, and the minimum Ethernet frame size is 64 bytes.
• Late collisions are abnormal on a correctly operating link and often suggest duplex, cabling, or topology problems.

For a broader review, see CSMA/CD explained alongside related study of Ethernet switching, collision domains, and duplex troubleshooting.