Bug 224122 - netowrk speed not set up according to manual settings
netowrk speed not set up according to manual settings
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: initscripts (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2007-01-24 03:49 EST by LENHOF
Modified: 2014-03-16 23:05 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-12-08 16:31:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description LENHOF 2007-01-24 03:49:16 EST
Description of problem:

Network Speed is not set up according to the option ETHTOOL_OPTS in

I've managed to make it work by adding a sleep before this option is applied in
the ifup script... Perhaps a little better mean is to move the 

[ -n "${LINKDELAY}" ] && /bin/sleep ${LINKDELAY} 

line before 

if [ -n "$ETHTOOL_OPTS" ] ; then
        /sbin/ethtool -s ${REALDEVICE} $ETHTOOL_OPTS

and add an information in the documentation to specify that if the speed is not
set up according to the speed specified, a recommandation is to add a LINK_DELAY

I think that for some network cards, the link is not set up quickly, so when the
speed is set up by ethtool, the network card is not completely up... And when it
is up, the speed is overrided by default settings

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Bill Nottingham 2007-01-24 14:13:29 EST
What options are you using?
Comment 2 LENHOF 2007-01-25 01:18:06 EST
ETHTOOL_OPTS="speed 100 duplex full autoneg off"

Comment 3 Bill Nottingham 2007-01-25 10:30:16 EST
CC'ing ethtool maintainer - I don't see why the effect would change with or
without a sleep.
Comment 4 LENHOF 2008-02-29 15:17:28 EST
The problem could be solved by setting the port to "PortFast" on the cisco
switch, I can not verify it right now. I think it could be on an FAQ somewhere...
Comment 5 Bill Nottingham 2008-12-08 16:31:37 EST
Given that this appears to be a switch issue, closing as not an initscripts bug.

Note You need to log in before you can comment on or make changes to this bug.