Original question:
========================================================================
On a brand new AS ES40(installed less than a month), we have a
DEGPA-SA giga ethernet NIC that looks like it isn't functioning.
Previously I received anwsers about whether drivers for it
were included in Tru64 4.0F(they are) and what to include
in my kernel config file(pseudo-device alt0) to build a proper
kernel for it.
I can see that that the system "sees" it when I boot up.
And the firmware knows that it's there. Yes, it has been defined
in /etc/rc.config.
However all attempts
at attaching this NIC and getting a link(yes, we have used different
crossover cables and yes, we have tested the interface to which it is
going to attach: another giga ethernet card on a Network Appliance
filer) have failed.
Anyone have any ideas about what's wrong other than the card is
bad?
I got the best answers from:
joe_at_meng.ucl.ac.uk "Joe Fletcher"
The tech support people have just pointed me at the man page (man alt) for the
card and suggested I turn off autonegotiation. I'll give this a go but
I think it needs to be done at console level so the card is functioning
fully before the system boots. The above symptoms could well be in keeping
with the card and the switch not sorting things out on power-up.
We have a DS20 on another site which has a DEGPA which appears to run fine
though it plugs into a Cabletron switch.
I'll keep you informed of whatever progress I make.
Cheers
Joe.
and from:
tpb_at_doctor.zk3.dec.com "Dr. Tom Blinn, 603-884-0646"
(from one of Dr. Tom's colleague's)
It's impossible to tell what's going on.
Perhaps the Network Appliance is not running in autonegotiation mode. If
they tried to lock down the speed/mode of the DEGPA on the Tru64 UNIX
side, they could confirm that (lan_config -ialt0 -a0).
Fiber cables are particularly sensitive (even more so with Gigabit
Ethernet). I have several cables that just will not work on any Gigabit
Ethernet adapter, but will work fine for ATM and FDDI.
------- End of Forwarded Message
So, you might try the lan_config trick, and you might make sure that you
have good cabling, and see if you can verify the support and settings on
the Network Appliance box (not that this will necessarily be easy to do).
Hope you get this working..
Tom
___________________________________________________________________
Karen Y. Byrd Suite 600
Systems Manager 3440 Market St.
Tech Sup. Philadelphia, PA 19104
Info. Ser. Div. Voice: 215/615-0659
UofP Health System Fax: 215/349-5846
byrd_at_mscf.med.upenn.edu
karen_at_mail.med.upenn.edu
Received on Tue Feb 01 2000 - 11:52:53 NZDT