Runts & Collision 1

[tpeterson]

Can anone help me figure out why my Runts and Collision are so high? I was told that runts effect the collision, but it does not look that way under my report.<br><br>Single-col&nbsp;&nbsp;&nbsp;Multi-col&nbsp;&nbsp;&nbsp;Runts&nbsp;&nbsp;&nbsp;Port<br>112640&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;42473&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3/1<br>1611371&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;553003&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3/22<br>44027&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;9182&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;26855&nbsp;&nbsp;&nbsp;4/45<br>0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6035&nbsp;&nbsp;&nbsp;&nbsp;4/2<br>0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;6989&nbsp;&nbsp;&nbsp;&nbsp;4/3<br>804693&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;444800&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;65&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;65<br><br>Can anyone tell I'm running cat3 cable (in some places) on an ATM network? I know some of my cable is substandard but could I also be looking at a router config problem? <p> <br><a href=mailto: > </a><br><a href= > </a><br>This is going to hurt... Ouch! Yep! That will leave a Mark!

 

[state]

To answer your question, I need to ask a question. Your numbers are indeed high, but relative to what? What are the numbers (normal baseline) for total network/segment traffic?. In addition, how long has it been since you last cleared your counters? If they have been cleared recently, you can correct this issue by first looking at physical layer objects (cable type and length, NIC's, etc). Whatever is connected to port 4/45 is the culpret.<br><br>Collisions indicates the number of times the selected object has participated in or has detected a collision. A collision occurs when two or more nodes try to transmit on the same network simultaneously. Collisions are normal on an ethernet network, but a properly configured network should normally have less than a 2% collision rate.<br><br>With regards to runts, I assume you are refering to etherStatsUndersizePkts as defined in RFC 1757. These are frames with a frame size between 8 and 63 bytes with a valid CRC and no alignment errors. If this is the case, you may or may not have a problem. Depending on the type of equipment, the vendor maybe using nonstandard frames. These frames are interpreted as runts. However, runts may be caused by a malfunctioning interface.<br><br>In ATM all information to be transferred is packed into fixed-size slots called cells. These cells have a 48 byte information field and a 5 byte header. This 53 byte cell falls within the definition of a under size packet and may be counted as a runt. <br><br>My suggestion is compare the collected interface information with that of your normal (baseline) data to see if there has or has not been an increase in runts. If not then you have nothing to worry about. If so, start checking you physical layer objects or the interface itself. <br><br>I also noticed that ports 4/2 & 4/3 report low numbers. Are they ATM interfaces or something else? Without seeing your router configuration and network topology, there is no way to tell if this is a config issue.<br><br>Hope this helps.<br>Steve

 

[tpeterson]

Yes, that helps. I know I can't replace the cat 3 cables in the walls (it cost too much) which makes for major headaches when you go mixing cats 3 & 5 together. That's what happens when you under budget your self and run out of cat 5. Don't you just love the Army. So, I started looking at the ports and NIC's. I found almost all my ports and NIC's&nbsp;&nbsp;where set for Auto instead of hard coded to 10 or 100. <br><br>Thanks for your help state. <p> <br><a href=mailto: > </a><br><a href= > </a><br>This is going to hurt... Ouch! Yep! That will leave a Mark!