|>Environment:
|>
|>Fully switched 10baseT environment using Cisco Catalyst 1900 switches
|>uplinking to a Cisco Catalyst5000 switch using Full Duplex 100baseTX.
|>We have several Ascend MAX4004s and USR TC hubs on the same Cat1900
|>switch that the PM3s are on.
|>
|>The Cat5000 uplinks to a cisco 7513 via multi-mode fiber into a
|>100baseFX PA in a vip2-20 card.
|>
|>All cabling is cat5 and is cat5 certified. It does not appear to be an
|>ethernet problem.
|
|It isn't clear to me from the above how many machines on each collision
|domain. Is it one machine per domain/port?
Correct. Each machine has its own switched port.
|>Here are the ether stats on some of our PM3s that are having problems:
|>
|>pm1.austin> sh nets
|>Name Ipkts Ierrs Opkts Oerrs Collis Resets Queue
|>ether0 40497473 204 40103900 0 316392 2 0
|>pm1.austin> ver
|>Livingston PortMaster PM-3 ComOS 3.5c6
|>System uptime is 9 days 3 hours 35 minutes
|
|There is a problem with the above machine. The Ierrs of 204 indicate a
|problem. The 2 resets, if not done by administrative resets by !root also
|indicate a problem. This machine does not appear to be on its own
|collision domain.
Can you give me an RMA number? This is the first PM3 in the hunt.
The above has a .3925% collision rate. How did you come to the
conclusion pm1.austin is not on its own collision domain?
|>pm2.austin> sh nets
|>Name Ipkts Ierrs Opkts Oerrs Collis Resets Queue
|>ether0 885613 0 900601 0 3945 0 0
|>pm2.austin> ver
|>Livingston PortMaster PM-3 ComOS 3.5.1b11
|>System uptime is 6 hours 51 minutes
|
|The above machine looks okay, collisions under 1 percent.
0.22% collision rate. About half the above, but this box probably has
half the load. Higher load will result in more collisions even in a
switched environment.
|
|>pm3.austin> sh nets
|>Name Ipkts Ierrs Opkts Oerrs Collis Resets Queue
|>ether0 15841913 0 16451627 0 89414 0 0
|>pm3.austin> ver
|>Livingston PortMaster PM-3 ComOS 3.5c6
|>System uptime is 8 days 3 hours 3 minutes
|
|The above machine looks okay, collisions under 1 percent.
|
|
|>isdn-1.austin> sh nets
|>Name Ipkts Ierrs Opkts Oerrs Collis Resets Queue
|>ether0 128011 0 45632 0 0 0 0
|>isdn-1.austin> ver
|>Livingston PortMaster PM-3 ComOS 3.5c6
|>System uptime is 13 hours 33 minutes
|
|The above machine is on an excellent network even given the short uptime.
|
|>isdn-2.austin> sh nets
|>Name Ipkts Ierrs Opkts Oerrs Collis Resets Queue
|>ether0 859378 0 925061 0 2101 0 0
|>isdn-2.austin> ver
|>Livingston PortMaster PM-3 ComOS 3.5.1b11
|>System uptime is 14 hours 1 minutes
|
|The above machine looks okay, collisions under 1 percent.
|
|
|I would be interested in the increase rate of collisions during the period
|of sluggish performance.
|
|I would also be interested in a comparison of ping times to all machines on
|the network at ten same time along with a diagram or map of what is
|connected where.
When the sluggish performance happens pings to other machines on the
same switch are < 1ms.
Jonah
Jonah Barron Yokubaitis | Texas' First X2 and K56flex
President | Internet Provider
Texas.Net | Austin|San Antonio|Houston
http://www.texas.net | Dallas|Fort Worth|Boerne
Making 56K affordable | Georgetown|Dripping Springs