CSMA/CD Collision Backoff Ranges
|
Retry |
Range |
Max Number |
Max Wait Time |
|
1st |
0-1 |
(2^1)-1 |
51.2us |
|
2nd |
0-3 |
(2^2)-1 |
153.6us |
|
3rd |
0-7 |
(2^3)-1 |
358.4us |
|
4th |
0-15 |
(2^4)-1 |
768.0us |
|
5th |
0-31 |
(2^5)-1 |
1587.2us |
|
6th |
0-63 |
(2^6)-1 |
3225.6us |
|
7th |
0-127 |
(2^7)-1 |
6502.4us |
|
8th |
0-255 |
(2^8)-1 |
13056.0us |
|
9th |
0-511 |
(2^9)-1 |
26163.2us |
|
10th – 15th |
0-1023 |
(2^10)-1 |
52377.6us |
Cisco switches monitor various collision counters, as follows:
-
Single
-
Multiple
-
Late
-
Excessive
Of the four types, be wary of late and excessive collisions. Late collisions occur when two devices send data at the same time. Unlike single and multiple collisions, late collisions cause packets to be lost. Late collisions are usually indicative of the cable exceeding IEEE specifications. Cascading hubs (connecting two or more hubs to each other) can also cause the length of the collision domain to increase above specification. You can use a Time Delay Reflectometer (TDR) to detect cable fault and whether the cable is within the IEEE standard. Other factors that cause late collisions include mismatched duplex settings and bad transceivers. Example 1-1 shows the output from a switch that has detected a late collision on one of its ports.