There is a book written by Scott Haugdahl called Network Analysis and
Troubleshooting ISBN 0201433192
and he has a pretty good discussion on collisions, there are lots of factors
that go into the number (length of the segment, number of users, etc) but I
think that above 5% was where he'd start getting worried and that will have
a negative effect on throughput. I personally think that 0.1% is way too
low (cisco's numbers) but if you're trying to sell switches....
I took a quick look on google and ran into this -- a couple of guys on the
free BSD mailing list that say less than 50% was ok -- obviously I think
they spend too much time coding and not enough time making the network work.
http://lists.openresources.com/FreeBSD/freebsd-questions/msg05297.html
Joe
"E Joseph" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
| I would first like to thank everyone. I have been a
| member of this groups for several years now. I have
| never actually posted a question, generally I just
| absorb others questions. I realise there is no
| concrete answer on this, BUT how many collision on a
| shared media ethernet segment does it take before
| having a problem?? I was just invovled in a situation
| where we had a hub hanging off a hub connected to our
| 6509. The switchport error disabled and I had to
| track the devices down. I beleive you will always see
| some collisions in a shared ethernet environment???
| At what collision rate should you get worried??? How
| much does it take to shut a switch port down???
|
| Thanks,
| Ed
|
| __________________________________________________
| Do You Yahoo!?
| Yahoo! Calendar - Get organized for the holidays!
| http://calendar.yahoo.com/
|
| _________________________________
| FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
| Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
|
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]