Firewall.cx Newsletter

Receive Free notification on new articles!
***************

Firewall.cx Forums

Community Forums

Facebook Fans

Show your support for Firewall.cx!

Social Media Channels

Facebook-icon LinkedIn-icon Twitter-icon  rssfeed-icon
advert-banner-routing
advert-banner-voice

System Login



Login With Facebook

More Articles

Who's Online

We have 105 guests online

Statistics

Members : 5872
Content : 790
Web Links : 12
Content View Hits : 102229534

Top Website Visitors

37.4%United States United States
16.8%India India
7.4%United Kingdom United Kingdom
5.7%Australia Australia
4.3%Canada Canada
3.4%Germany Germany

Today: 2067
Yesterday: 6821
This Week: 41479
Last Week: 46096
This Month: 118888
Last Month: 239064
Total: 3379612

Gold Cisco Lab Partners

logo-gfi



logo-datavision

Late Ethernet Collisions Print Email
Written by Administrator   
Friday, 27 May 2011 23:27
AddThis Social Bookmark Button

Introduction

Again, we are going to make use of a step-by-step example in order to fully understand how and why late collisions occur.


Late Collisions

Late collisions, on the other hand, are not normal and are usually the result of out of spec. cabling or a malfunctioning adapter. A late collision is defined as any collision that occurs after 512 bits of the frame have been transmitted.

In this discussion we will refer to the same network described in the discussion of early collisions, but with one modification: In this network, the network administrator has violated the maximum cable length (500 meters for 10BASE5 thick ethernet, 185 meters for 10BASE2 thin ethernet) by either adding too many repeaters in between Stations A and B or by laying too much wire between them.

The following is an outline of a late collision event caused by out of spec. cabling:

Station A, detecting that the wire has been idle for 9.6 microseconds, begins to transmit its data frame, beginning with the 64 bit preamble. Station A transmits 256 bits of its frame. If the cabling were in spec and Station B began to transmit, causing a collision, even if Stations A and B were on the farthest ends of the wire from each other the collision would be detected by station A before it could transmit its 512th bit. (Stage 1)

late-collision-1

 

Station A continues to transmit bits, and meanwhile, down at the other end of the wire, just before the electrical signal reaches Station B, Station B detects idle wire for 9.6 microseconds and begins to transmit. (Stage 2)

late-collision-2

 

A minute amount of time later, a collision occurs. (Stage 3) Station B, being extremely close to the collision, detects it first and begins transmitting a 32 bit jam signal.

late-collision-3

 

The collision begins to propagate down the wire towards Station A (Stage 4), followed by the 32 Bit Jam signal generated from Station B.

late-collision-4

 

But because the cabling was out of spec. by the time it gets to Station A, Station A has already finished transmitting and is no longer listening for collisions! (Stage 5) Station A is completely unaware that a collision has occurred!

late-collision-5

The reason that late collisions are a problem is that once the NIC misses the fact that a collision has occurred, recovery and retransmission are left to the upper layers and recovery time goes up drastically. While a NIC will typically recover and retransmit a frame in 2-3 milliseconds, it typically takes anywhere from 10 to 100 times that long for upper layers.

The other major cause of late collisions is a malfunctioning NIC. If a NIC malfunctions in such a manner that it is unable to detect that another station is talking, late (and early) collisions will occur.

 
Subscribe To Receive Free Article Updates!

SIMILAR TOPICS THAT MIGHT INTEREST