Hello Managers,
I recieved many responses and will look into them in due course....
Attached are those responses with the original posting at the end of
this summary.
>
>The usual reasons are sub-standard cabling, violating FastFD
>rules by having a hub, or problems with auto-negitiating
>full-duplex. A somewhat less frequent reason is a broken network
>card or switch port. If you use good quality cabling, and lock
>both the switch and network card at FastFD, full-duplex 100Mbps
>works very well indeed under Tru64.
>
>/Serge.P
>
>
>It depends if you are connected straight to a switch or if oyu are
>connected to a hub. Only a 1 to 1 connection to a switch will allow you
>a full duplex connection. If you are connnected to a switch you don't
>share the line so you can send in both ways. If you are connected to a
>hub all the send en recieve wires all come together in the hub at 1
>point. This means that if you are sending while there is some other
>transmition going on .............. :).
>
>regards
>
>Udo de Boer
>
>Hi,
>
>I can't make any definitive statements about what the underlying cause
>of your problem is, but as you have discovered, it's a duplex mis-match.
>The symptoms you described are exactly what happens when the
>duplex at one end does not match the duplex at the other end. It's
>doesn't matter which is set to what, they need to match. Either your
>hub is set to full and the system is set to full OR your hub is set to
>half and the system is set to half.
>
>Now, you can only use full duplex if this is a point to point link. That
>means that it's just your system directly connected to a switch or
>router or another system. If your system goes to a standard repeater hub
>that is shared with other systems, you can NOT use full duplex
transmission.
>
>I personally don't trust auto-negotiation either. I've had problems at
>both the system and the hub end although newer versions of Tru64 seem to
>have gotten a lot better at this.
>
>So, assuming you're going to a real switch, I would look into manually
>setting the port to 100MB Full Duplex and then shut down your Alpha box
>and at the >>> prompt issue the command
>
>>>> set ewa0_mode fastfd
>
>Where ewa0 is the name of your network interface
>
>I hope this clears a few things up. If you need more specific assistance,
>let me know and include a little info about the network configuration.
>
>Mitch
>
>--
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> Compaq, the NonStop(TM) Internet Company
>Mitch Kulberg
>Systems and Network Administration Mitch.Kulberg_at_compaq.com
>Compaq Computer Corporation mok_at_unx.dec.com
>200 Route 9 North
>Manalapan, NJ 07726 732-577-6062
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
>It is because that at full duplex, the card in question can effectively
>run 200MBps. However, the switch/hub/port to which the card is
>connected must also be configured to run at the same speed, else there
>is autonegotiation for each packet send/receive. At half duplex, the
>card is capable of 100MBps. Which is what is usually configured anyway.
>
>--
>
> -- Narendra Ravi
>
>
>Network problems due to connection settings? Well, it hapens with some
>series of switches and some DEC Tulip cards. Usually firmware refresh of
>the switch takes some problems out. Not always, though.
>
>Nix.
>
>
>I have had a similar situation and traced it back to our switches not auto
>negotiating. We set them to 100 full also and had no further problems. I
>have heard though that some servers are supposed to run better at half-
>dunno why?
>
>Regards, John.
>
>
>what kind of network card have you installed. There are some older
>DE500-AA's around installed in Alpha boxes and they have a problem with
>auto-negotiation with a hub. Try DE500-BA and all is fine after that.
>
>regards
>
>Werner Hahling
>
>
>the tulip based drivers can't handle full-duplex. Watch your
>collision count and you will see. Although the tulip chips are
>fast, they have drawbacks. But the benefits outway the minor
>issues of not being able to sense full/half duplex.
>
>cheers
>rich
>
Original Post:--->
>
> Hello Managers,
> I haved experienced this as well. Does anybody out there know why?
> Regards,
> Leo
>
>>Thank you to everyone for helping out.. It seems that the trick is to set
>>the Dec to Half Duplex, even though this does not seem to be the best
>>solution it is the one that worked and is working very very well.. Crazy
>>but true! Thank you again for all your help!!
>>
>>David
>>
>>-----Original Message-----
>>From: Dave William Shapiro [mailto:shapiro_at_lvc.edu]
>>Sent: Saturday, 22 July 2000 02:02
>>To: tru64-unix-managers_at_ornl.gov
>>Subject: TRU64, IP/UDP
>>
>>
>>I am having a problem with a new Dec Alpha... When we first started the
>>install we had it running half duplex on a 10mg port and FTP worked
fine...
>>
>>Now we have it on its own 100mg port set at Full Duplex and 100mg rather
>>than auto nogotiating.
>>
>>Telnet works fine, however using FTP and RCP is horrible...
>>
>>A 1mg file took 11 min's and a small 12k file, yes they still do exist,
>>took close to 3min's.
>>
>>Please Help!
>>
>>Thank You!
>>
>>______________________________________
>>- -
>>- David William Shapiro -
>>- shapiro_at_lvc.edu -
>>- 717-867-6023 -
>>- -
>>- Unix/Windows System Admin -
>>- -
>>______________________________________
>>
>
___________________________________________________________
PRIVATE AND CONFIDENTIAL
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you are not the intended recipient you are hereby notified that any
dissemination, distribution or copying of this email is strictly prohibited.
If you have received this email in error please disregard the contents
of the email, delete the email and notify the author immediately.
Thank you.
Received on Mon Jul 24 2000 - 23:04:46 NZST