| Title: | FDDI - The Next Generation |
| Moderator: | NETCAD::STEFANI |
| Created: | Thu Apr 27 1989 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2259 |
| Total number of notes: | 8590 |
If an ethernet workstation is directly connected to an FDDI-to-ethernet bridge, on a dedicated port of the bridge, (i.e. no other stations - just the bridge and the workstation) what would cause a relatively high number of collisions (25% of the packets) on that segment? Would this have to be hardware, or is it possible part of the bridge functionality has to do with this? (i.e. does the bridge generate collisions to hold-back ethernet traffic from a port if it is busy on other ports?) I've a customer with this situation, and we are trying to determine if the system-level problem he is experiencing (occassional NFS not-responding time-outs) are related to the high collision rate or not.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2225.1 | what's the load? | NETCAD::ROLKE | The FDDI Genome Project | Thu Feb 20 1997 09:48 | 13 |
You get a collision when the bridge and the workstation try to transmit at the same time. Generally this is a function of how much traffic you are trying to put on the ethernet segment from each end. This is a normal feature of classic half-duplex ethernet and not a "problem" until throughput starts to roll off as the offered load increases. A FullDuplex ethernet circuit reduces collisions to zero. As this is unrelated to FDDI you may get better answers in HUMANE::ETHERNET Regards, Chuck | |||||