What often happens is that the autonegotiation fails. The end device thinks that full duplex was negotiated and the other sides thinks half. This causes many more problems than just working at half duplex. I always make sure that major server devices on my networks get locked down at full duplex. There are just too many problems with autonegotiation.
barry
On Tuesday, December 31, 2002, at 08:22 AM, Dan O'Brien wrote:
Dan O'Brien wrote:
Hello, We are having trouble with a Solaris client having slow read performance. Both the Filer, F630 running 5.3.6R2, and Solaris, Ultra 2 running 2.6, client are on 100BT networks coupled thru Linksys EF24G2 Fast Etherswitch. I looked at the obvious, all ethernet devices are in 100BT mode, running full duplex. SUNW,hme0: Using Internal Transceiver SUNW,hme0: 100 Mbps full-duplex Link Up slot 4: 10BaseT/100BaseTX Quad-Ethernet Controller e4a MAC Address: 00:c0:95:e0:2f:48 (100tx-fd-up)
Ok, I found something significant. The FD light on my Linksys was out for the Filer and the Sun. Curious since both claim to be FD. I pulled out my trusty laptop and tapped into the switch config panel s/w to check out each port setting and sure enough, the Linksys was setting the ports to HD. I turned off AutoNeg for each of the ports and within a second or two, they came back as FD.
Thanks for all your suggestions so far. The lesson here is don't believe everything that the systems are showing. The switch wasn't lying when the FD lights were out.
Happy New Year!
Cheers,
Dan O'Brien, dmobrien@lcsi.net Cell: 614-783-4859 Work: 614-476-8473 Home: 740-927-2178 Pataskala, OH