Not knowing much about the networking side of the equation, I assumed that
the problem was Tru64.
Thanks to:
"Serguei Patchkovskii" <patchkov_at_ucalgary.ca>
"Partin, Kevin S" <Kevin.Partin_at_SW.Boeing.com>
The problem is likely to be that the switch is expecting to see the
auto-negotiation sequence before FastFD. I talked to one of our network
technicians and sure-nuf, he confirmed that all ports on the Cisco are set
to auto-negotiate. So, auto-negotiate it is.
Thanks,
Allen Belk
| Allen Belk, Systems Manager
| Office of Technology Resources
| University of Southern Mississippi
| allen.belk_at_usm.edu 601.266.6013
----- Original Message -----
From: "Allen Belk" <allen.belk_at_usm.edu>
To: "tru64" <tru64-unix-managers_at_ornl.gov>
Sent: Monday, April 03, 2000 2:21 PM
Subject: Difference between auto-negotiate and FastFD
> Managers,
> I am running into a strange problem changing between FastFD and
> auto-negotiate for ewa0_mode on an AlphaServer DS10. The NIC is reported
as
> follows while booting.
>
> vmunix: tu1: DECchip 21143: Revision: 4.1
> vmunix: tu1: auto negotiation capable device
> vmunix: tu1 at pci0 slot 11
> vmunix: tu1: DEC TULIP (10/100) Ethernet Interface, hardware address:
>
> It is connected to a Cisco Catalyst 2900. When I set it to FastFD, the
> network comes to a halt. When I set it to auto-negotiate it operates
> flawlessly at 100BaseT: full duplex.
>
> Other than the obvious, what is the difference in these two settings?
>
> Thanks,
>
> Allen Belk
>
> | Allen Belk, Systems Manager
> | Office of Technology Resources
> | University of Southern Mississippi
> | allen.belk_at_usm.edu 601.266.6013
>
>
>
Received on Mon Apr 03 2000 - 20:49:35 NZST