You haven't given enough info for me to tell what type of card e0 is, but the quad card will certainly support autosensing. Try setting the mediatype to "auto" - it should then negotiate with the switch correctly. If e0 supports autonegotiation it will have only one socket - in which case you can do the same there.

If it doesn't work, open a call with NetApp support and supply more information - at least the switch details, sysconfig -v

Andrew Bond, UK Systems Engineer

At 06:46 pm 1/12/99 -0800, Jamie Lawrence wrote:

At 06:36 PM 1/12/99 -0800, Jerry Talkington wrote:

...

Jamie Lawrence wrote:

...

Hi -

I have a 720 with a quad card which never negotiates to full duplex with out 10/100 switch. The Solaris boxes on the same switch negotiate to FD just fine, and the 720 thinks FD is enabled, but the switch only ever negotiates to HD.

Has anyone seen this before?

Not sure I understand the question, those all seem to be at full duplex. As a general rule, setting the filer up to autonegotiate is a bad idea, since it will try to come up faster than the interface can negotiate a connection. I always recommend that people manually set both the filer (through the rc file) and the switch to whatever duplex they want to use.

Sorry - That message was poorly written. The filer thinks the interface is full duplex. The switch thinks it is half duplex. I am setting the interface manually in rc:

ifconfig e0 mediatype 100tx-fd `hostname`-e0 netmask 255.255.255.128 ifconfig e2a mediatype 100tx-fd `hostname`-e2a ifconfig e2b mediatype 100tx-fd `hostname`-e2b ifconfig e2c mediatype 100tx-fd `hostname`-e2c ifconfig e2d mediatype 100tx-fd `hostname`-e2d

This is an unmanaged switch, so forcing the speed is not an option, but I don't think the switch is faulty because the Sun machines behave as expected - both the machines and the switch declare a full duplex connection.

-j