e1000 still

Barsalou barjunk at attglobal.net
Sat Apr 2 21:35:47 UTC 2005


Although this is only a story with no technical backup, we have
experienced issues using a Cisco 2950 with some ethernet devices not
properly negotiating.

We have spanning tree in portfast mode AND turned trunk mode to access.
This is actually important with regard to OS X machines getting
connected.

The solution we have used is to put a hub/switch between the two devices
to make things work.  In our case, the device was a Tally printer.  

We didn't spend lots of time trying to determine the problem, but by
changing the connection from a 2950 to an older 1900 we were able to get
things to work.  So it is definitely something with that particular ASIC
or the way it was programmed.

Hopefully someone with great technical expertise than myself can clarify
for us.

Mike B.

On Wed, 2005-03-23 at 10:43 +0100, Jeroen Roodhart wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> |I don't believe there is a need to wait 30 or 45 seconds for spanning
> |tree calculations on the switch.  There is something much more subtle
> |going on here.  As I mentioned before, we've tried capturing traffic
> |with a passive analyzer between the box being built and the switch, and
> |just this change to the network connections allow the install to >proceed
> |normally (as does inserting a small 10/100 hub inline, or replacing the
> |gig switch with a 100Mb switch.)  It isn't about spanning tree
> |calculations on the switch, I think there is some sub-second change in
> |the characteristics of the negotiation or anaconda's network setup, >when
> |spanning tree is on or off, that make a difference.
> |
> |-Ed
> 
> I just want to support Ed here, this is the _exact_ behaviour that we
> experienced.
> 
> I really don't see the issue here. I you retry try when it fails, you
> just make the proces more fault tolerant (normal programming I think,
> especially [as said before] when you use UDP).
> 
> If it works in one go, you don't have any adverse effects (it's just as
> fast) and if it doesn't, it works with a short delay. What's the
> deal?
> 
> In the mean time, when we experience this behaviour again (seems to
> have dissapeared when going to FC3) I'll patch the code myself.
> 
> With kind regards,
> 
> Jeroen
> - --
> Jeroen Roodhart              University of Amsterdam
> jeroen at science.uva.nl        Faculty of Science / ICT-Group
> Systeem- en netwerkbeheer    Tel. 020 525 7203 / 06 51338165
> - --
> See http://www.science.uva.nl/~jeroen for openPGP public key
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.6 (GNU/Linux)
> 
> iD8DBQFCQToy37AP1zFtDU0RAtnwAJ9RipKbZxzWWSRsbyVW/I39B7sH6wCeN2BS
> VAu/Rj9aha/xl0m37IcUGSE=
> =TY1P
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list at redhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list
-- 
Barsalou <barjunk at attglobal.net>




More information about the Kickstart-list mailing list