SUMMARY: SUN: QFE0 Late Collisions

From: Cheryl Milburn <>
Date: Fri Sep 26 2003 - 12:59:31 EDT
Thank you all for the quick response.  I had about 20+ people respond very

It turns out I was setting the wrong device in the ndd command.  I was
using /dev/hme when I was having problems with qfe0.  I should have been
using /dev/qfe0.   The first command below sets the instance to my qfe0


ndd -set /dev/qfe instance 0
ndd -set /dev/qfe adv_100hdx_cap 0
ndd -set /dev/qfe adv_100fdx_cap 1
ndd -set /dev/qfe adv_10hdx_cap 0
ndd -set /dev/qfe adv_10fdx_cap 0
ndd -set /dev/qfe adv_autoneg_cap 0  (Do this last)

I also verified that the network switch my machine was plugged into was set
to 100 Full.


I have a E4500 with Solaris 2.6 on it.  I'm getting a lot of late
collisions errors:
Sep 26 08:50:47 db1-fe unix: SUNW,qfe0: late collision

There is a previous thread on this site that talks about this stating that
it was a full duplex mismatch, but it didn't say what steps were performed
to fix it.

I've tried changing the setting using ndd:
ndd -set /dev/hme adv_autoneg_cap 0
ndd -set /dev/hme adv_100hdx_cap 0
ndd -set /dev/hme adv_100fdx_cap 1

Long term, I'll change the /etc/system file, but this machine is a
production database server and I can't do a reboot for the changes to take
affect without a maintenance window.

Does anybody know how to change this setting on the fly?  Please help.

sunmanagers mailing list
sunmanagers mailing list
Received on Fri Sep 26 12:59:27 2003

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:20 EST