[Cisco] Local vs Remote vs Late Collisions -- calling all experts

[Jose Straube]

Hi Kevork,

Here you have my 2 cents worth of thought.

"The question is :  Is the sending machine still transmitting for a
remote collision to occur? "

Yes, the 2 machines are still sending (within the first 64 octects)

"If not, then is it not a Late collision?" 

No, because it will be detected within the 64 octets. 

"Also, how can the sending machine know there was a remote collision ?
Does it get fragments of the collision back across the repeater with the
FCS not matching ?" 


Two scenarios: 
1)Let's assume machine A and machine B are separated by a repeater.

A ------ R ----xxx-- B

In here we see that the remote collision for A (represented by xxx) is
also a local collision for B. When B detects the collision it sends a
Jamming signal (which is repeated) that can be detected by A which will
in turn also send the Jamming signal.

2) Let's now assume 3 repeaters in the logical segment (worst case
scenario).

A ------ R ------ R ---xxx--- R ------ B


In this case the collision is remote to both sources. A or B can only
detect the collision by checking the FCS (which in any case will be
incorrect) of the received frame. In this case you could say that the
collision can also be seen as 'Late' collision due to the fact that the
FCS is at the end of the frame.


"and does that happen before the 64 bytes slot time is exhausted ?"

Please refer to the previous answer.


I hope it helps to clarify a bit.

Regards,
Straube

-----Original Message-----
From: Kevork Krozian [mailto:Kroset at novell1.fhc.vic.edu.au] 
Sent: Wednesday, 27 April 2005 2:07 PM
To: cisco at edulists.com.au
Subject: [Cisco] Local vs Remote vs Late Collisions -- calling all
experts

  Hi Folks,

        I am wondering if anyone can help me here. 
I am reading contradictory information about Collision types on
Ethernet.

 Local collisions look OK.  These happen during the first 64 bytes of
transmission ( also known as slot time ). There is an amplitude increase
on the local segment, and both Rx and Tx wires become active hence the
collision. The sending machine has to resend. No problems here.

 Remote Collsions . Happen on the other side of repeaters, which is does
not send back the amplitude increase or send back a signal on the Rx
wire. However, these must happen while the sending machine is still
transmitting the first 64 bytes which means it is still transmitting
when a remote collision occurs. See Slide 6.2.6 Semester 1. 
 The question is :  Is the sending machine still transmitting for a
remote collision to occur? If not, then is it not a Late collision ?
Also, how can the sending machine know there was a remote collision ?
Does it get fragments of the collision back across the repeater with the
FCS not matching ? and does that happen before the 64 bytes slot time is
exhausted ?

  Late Collisions :  These happen after the slot time is exhausted and
the sending machine does not know there was a collision. The higher
layers handle the error.

   I am happy to hear any and all suggestions


With thanks

   

Kevork Krozian
IT Manager , Forest Hill College
Mailing List(s) Creator and Administrator
http://www.edulists.com.au
k.krozian at fhc.vic.edu.au
Mobile: 0419 356 034


_______________________________________________
cisco mailing list
cisco at edulists.com.au
http://www.edulists.com.au/mailman/listinfo/cisco




Confidentiality and Privacy Statement

This message is intended only for the use of the individual or entity named above and may contain information that is confidential and privileged. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by telephone and destroy the original message. 
Box Hill Institute of TAFE is committed to protecting your privacy and the confidentiality and security of personal information provided by you to us. For further information visit www.bhtafe.edu.au or email privacy at bhtafe.edu.au.