[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::etherworks

Title:EtherWORKS Notes Conference
Notice:WWW server at http://ftp.digital.com/pub/DEC/adapters/
Moderator:NETCAD::STEFANI
Created:Wed Sep 01 1993
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1318
Total number of notes:5673

1264.0. "DE500-AA TCPIP 25% collisions" by NETRIX::"[email protected]" (Sunny Spain) Thu Feb 20 1997 14:50

Hi, 

Can anyone help?
I've also posted this as a reply to Zav's note 200 on gvprod::prioris.

I have a customner who has several Prioris ZX running NT4.0sp2
Specifically one of our clients reported upto 50% frame collision rates on
Prioris ZX6000 servers, based on this I tested two DE500-AA (which use the
21140-AC chip) on this I made a mock-up using two two DE500-AA on Prioris XL
servers and (with a little help from my friends) analyzed the traffic,
results:-

NT4.0 with or without SP's, NT driver, v260 driver and v263 interim drivers.

Using NETBEUI........1-5% collision on a 60-70% LAN utilizacion...i.e very
good

Using TCPIP only (MS) 25% collisions on a 60-70% LAN utilizacion...i.e NOT
VERY GOOD At ALL.

Tests were carried out on a Isolated network using a DEC PortSwitch 900 and a
Hp Lan Analzser.

I have escalated this to Valbonne PCBU who have talked/submitted this to NPBU,
this was done last week 13/14 of Feb 97.

I don't know if this problem is common to DE500-XA or the 21142 chips used in
Prioris MX6000/HX6000 etc.

cheers John
[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name
DateLines
1264.1isn't this how ethernet works?NETCAD::ROLKEThe FDDI Genome ProjectFri Feb 21 1997 08:1919
>Using NETBEUI........1-5% collision on a 60-70% LAN utilizacion...i.e very
>good
>
>Using TCPIP only (MS) 25% collisions on a 60-70% LAN utilizacion...i.e NOT
>VERY GOOD At ALL.

Are you saying that the same machine, same driver, same adapter, same
network gives different collision rates for different protocols?

This narrows the problem down to the protocols.  There is nothing more
that the driver and adapter can do for you; they offer the protocol's
load to the network and collisions happen.

Do you have the numbers of packets transmitted by each station in the
NETBEUI and TCPIP cases?  This could be a clue as to why TCPIP has more
collisions.

Regards,
Chuck
1264.2More data + 3com OKNETRIX::"[email protected]"Sunny SpainFri Feb 21 1997 13:4136
Hi Chuck, thanks for the reply,

>Are you saying that the same machine, same driver, same adapter, same
>network gives different collision rates for different protocols?

Yep,  however the customer teested on Prioris ZX6200/4 and I tested with
Prioris XL590, same cards + the client also tested on another 4 DE-500-AA's he
has...same result. As regards to drivers NT4.0 native + v260 and v263 all gave
the same result.

>This narrows the problem down to the protocols.  There is nothing more
>that the driver and adapter can do for you; they offer the protocol's
>load to the network and collisions happen.

The client has a applied a work-around ...install 3COM 10/100 and collision
rate (under IP or Netbuie) drops to 1-5% !...so I don't think its a generic
Microsoft TCPIP problem, otherwise I hopew we would have heard.!

>Do you have the numbers of packets transmitted by each station in the
>NETBEUI and TCPIP cases?  This could be a clue as to why TCPIP has more
>collisions.

I'm not a LAN man but with a little help from my friends (NSIS) in the digital
offices we tested on an isolated LAN with a DEC Portswitch 900:-

Under Netbuie: 130000 packet txd/rxd with around 200-650 collisions
Under TCPIP:   130000 packets txd/rxd with around 29000 collisions

In both cases from server A to server B and vica versa we copied 53MB of data,
LAN utilizacion in both cases around the 60-70% mark.

I don't now have the servers to test on any more as there at ASLAN event but I
do have the cards.

Cheers John
[Posted by WWW Notes gateway]
1264.3Capture Effect in action?NETCAD::ROLKEThe FDDI Genome ProjectFri Feb 21 1997 15:4120
There are some notes about high collision rates on networks with 
few (say, two) nodes on them.

 See TURRIS::digital_unix note 3056.1 for pointers to discussons of
 the capture effect.
 
 See TURRIS::digital_unix note 373.7 for adjustments you might make to
 your tcpip stack to partially compensate for the effect.  This note
 has good explanations of what it is doing.
 
Does your driver have a "capture effect" kind of switch?  This might make
a difference if the ethernet chip can run a different backoff algorithm.

The reason the 3Com board works differently is probably because it leaves
a larger interpacket gap between frames.  This allows the second node to
start transmitting without a collision.

These are tough problems to solve!

Chuck
1264.4Thanks, will read up and testNETRIX::"[email protected]"Sunny SpainFri Feb 28 1997 03:499
Hi Chuck,

Thanks for the reply, I will read up on said articles and hopefully test at
the client site.

Yes there are only a couple of nodes on the particular ethernet segment.

Cheers John
[Posted by WWW Notes gateway]