I have seen the *nice* usage pf summaries in this mailing list, so i'm
going to do tha same.
----------------------------------------------------------------------
my original question:
Hello managers.
I have a problem setting up the ethernet card of an AlphaServer 400
running DEC OSF 3.2C
Our technicians have put to work the local network just last friday.
Than I configured the ethernet card givin it the IP address 137.1.1.1
using ifconfig.
If I try pinging the local card it works as the same as it works pinging
the loopback.
But I can't ping any of the three PCs connected in the local network
(they can ping each others), nor they can ping the Station.
The card has three connectors: a thick-ethernet adapter, a BNC thin
ethernet adapter and an RJ-45 we are using.
Maybe we have to select the connector we are using? If so I have to move
some jumper on the card itself or to give some configuration command? Or
can the problem arise from some other source?
----------------------------------------------------------------------
I have resolved the problem setting, at the SRM prompt (>>>) the cable
type with the command:
>>> set ewa0_mode Twisted-Pair
thanks to
Lucio Chiappetti, Wanderley O. Mendes, Olle Eriksson, Herve DEMARTHE,
Guy Dallaire, Ryan R Ziegler, Patrick O'Brien, Arnaud Valeix, Regis
Rembado, Murthy Hebbar, Benoit Maillard.
A lot of people!
I report here in the following two answers I think contains some much
useful informations:
Herve DEMARTHE wrote:
...
Also beware of a potential problem in 3.2C :
This patch must be installed (it is included in 3.2D) :
Patch ID: OSF350-070
o Corrects a problem where under certain relatively rare conditions,
the DECchip 21040-AA and DECchip 21041-AA Ethernet devices would
corrupt a transmit packet. However, stations receiving the packet
would not notice the loss and/or corruption of the original data
because the Cyclic Redundancy Check (CRC) was computed during
transmission over the corrupted data.
o Fixes a problem where under heavy system/bus loads, the default
programming of the DECchip 21140-AA Fast Ethernet device (DE500)
resulted in excessive framing errors.
AND Murthy Hebbar wrote:
At the console prompt see if you have any settings for selecting the
ethernet type. "show" or "help" may be able to guide at the cosole
prompt. Does system say "no carrier" while booting up? If so
it is the problem with the cable or the selection of the ethernet type.
Also while booting system will tell you which interface it has selected
if it is auto detect. I think these messages are logged in to
/var/adm/messages also.
As a last trial you can check the netmask for that interface ( netstat
-rn). It should be same as netmasks on the other hosts in that network.
Try executing "setup" after logging in as root then use optin 1 to
configure your TCP/IP setup.
If you suspect the cable connecting to this particular host try
connecting the same cable to already working system and see if it works.
Another thing in some of the Alpha's I found is that the system needs
the network cable connected while booting. If you connect the network
cable after system boots network may not work.
I have worked on different models of Alpha but not this one.
Most of them are almost similar. Hope my theory will work!
bye and many thanks to all the people.
--
Sigismondo Boschi
net1701_at_comune.bologna.it
PhD student at the Physical Chemistry Department
Bologna University (Italy)
Received on Tue Sep 24 1996 - 13:09:51 NZST