[nsp] single-col, multi-col, 6509

[Church, Chuck]

Compare the number of single collisions to the total number of packets output.  If you're getting more than 1 collision per 100 packets output, it's probably overloaded.  Like the others mentioned, check for any duplex mismatches, or FCS errors on either side.  If it's not misconfigured, and the rate is exceeding 1% (1% is a ballpark figure, nothing cast in stone), might be time to upgrade the speed, change to full duplex on that link, or both.  Once it is full duplex, keep an eye on deferrals and drops, as they're both still possible and a sign of link overload.

Chuck Church
Lead Design Engineer
CCIE #8776, MCNE, MCSE
Wam!Net Government Services - Design & Implementation Team
13665 Dulles Technology Dr. Ste 250
Herndon, VA 20171
Office: 703-480-2569
Cell: 703-819-3495
cchurch at wamnetgov.com
PGP key: http://pgp.mit.edu:11371/pks/lookup?op=index&search=cchurch%40wamnetgov.com

> -----Original Message-----
> From: matthew zeier [mailto:mrz at intelenet.net]
> Sent: Monday, March 22, 2004 2:40 PM
> To: cisco-nsp at puck.nether.net
> Subject: [nsp] single-col, multi-col, 6509
> 
> 
> 
> I can't (easily) find from cisco's site what Single-Col and 
> Multi-Col mean.
> I do know that on this port each are increasing.
> 
> Port  Single-Col Multi-Coll
> ----- ---------- ----------
>  9/11     634745     100903
> 
> 
> --
> matthew zeier                        | "Nothing in life is to 
> be feared.
> InteleNet Communications, Inc.       |  It is only to be understood."
> (949) 784-7904                       |       - Marie Curie
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>