Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Version-Release number of selected component (if applicable):
initscripts-9.03.23-1.el6.x86_64
How reproducible:
Always.
Steps to Reproduce:
1. boot system
2. or run ifup command
3.
Actual results:
See below
Expected results:
Would like dhcp configured eth0 to start on boot.
Additional info:
On Red Hat 6.0 and 6.1 using dhcp on boot fails with:
Determining IP information for eth0... failed; no link present. Check cable?
I was hoping that rhel6.1 was going to fix but it did not. The same
system works fine with Red Hat 5.x.
Using a static IP in ifcfg-eth0 works. Using NetworkManager works as
long as 'NETWORKWAIT=yes" option is added to /etc/sysconfig/network else
NetworkManager fails.
Running "ifup eth0" with a dhcp configuration fails the first time.
Running "ifup eth0" a second time works.
NetworkManager manger service is turned off, daemon not running.
Client configured to use dhcp only, here is the ifcfg-eth0 settings:
DEVICE="eth0"
ONBOOT="yes"
TYPE="Ethernet"
HWADDR="00:01:6C:8F:D4:04"
BOOTPROTO="dhcp"
IPV6INIT="yes"
MTU="1500"
NM_CONTROLLED="no"
The intefrace was turned off with "ifdown eth0", then I try
to bring it up:
# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:01:6C:8F:D4:04
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:222500 errors:0 dropped:0 overruns:0 frame:0
TX packets:21468 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:27699281 (26.4 MiB) TX bytes:2074947 (1.9 MiB)
Interrupt:16 Memory:d8080000-d80a0000
# ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: pumbag
Wake-on: g
Current message level: 0x00000001 (1)
Link detected: no
# ifup eth0
Determining IP information for eth0... failed; no link present. Check cable?
# ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: off
Supports Wake-on: pumbag
Wake-on: g
Current message level: 0x00000001 (1)
Link detected: yes
Note that the link is now detected and the second time ifup is
run the interface comes up:
# ifup eth0
Determining IP information for eth0... done.
#ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:01:6C:8F:D4:04
inet addr:152.2.130.183 Bcast:152.2.143.255 Mask:255.255.240.0
inet6 addr: fe80::201:6cff:fe8f:d404/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:227430 errors:0 dropped:0 overruns:0 frame:0
TX packets:21708 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:28125605 (26.8 MiB) TX bytes:2097733 (2.0 MiB)
Interrupt:16 Memory:d8080000-d80a0000
first ifup eth0 /var/log/messages:
----------------------------------
Jun 28 09:04:03 tophat kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun 28 09:04:10 tophat kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Jun 28 09:04:10 tophat kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Note it takes 7 seconds for the link to become ready. Here is the card info:
# lspci | grep Ethernet
02:00.0 Ethernet controller: Intel Corporation 82573E Gigabit Ethernet Controller (Copper) (rev 03)
The check_link_down function in /etc/sysconfig/network-scripts/network-fucntions
is failing when called by /etc/sysconfig/network-scripts/ifup-eth. I cannot
figure out why.
The "ethtool --test eth0 online" and offline tests pass fine. The system
works fine once the interface is running. Thanks for any help.
I will have to investigate our switch configuration. I have managed
many rhel 3,4,5 systems and never had to use a LINKDELAY. I added
LINKDELAY=10 to /etc/sysconfig/network-scripts/ifcfg-eth0 and
that fixed. The LINKDELAY option is not mentioned in the
rhel6.x install, release or deployment guides. I did see
it in the knowledge base. Thanks for you quick response.
I guess you can close.
The machine having the problem is dual boot with ubuntu 10.04, it took 5 seconds
for the interface to come up using "ip link set eth0 down" and then watching
the syslog after running "ip link set eth0 up" in ubuntu. So a slower driver
may be the case. Using NetworkManager with the NETWORKWAIT=yes and dhcp is
probably the best choice. Thanks.
Description of problem: Version-Release number of selected component (if applicable): initscripts-9.03.23-1.el6.x86_64 How reproducible: Always. Steps to Reproduce: 1. boot system 2. or run ifup command 3. Actual results: See below Expected results: Would like dhcp configured eth0 to start on boot. Additional info: On Red Hat 6.0 and 6.1 using dhcp on boot fails with: Determining IP information for eth0... failed; no link present. Check cable? I was hoping that rhel6.1 was going to fix but it did not. The same system works fine with Red Hat 5.x. Using a static IP in ifcfg-eth0 works. Using NetworkManager works as long as 'NETWORKWAIT=yes" option is added to /etc/sysconfig/network else NetworkManager fails. Running "ifup eth0" with a dhcp configuration fails the first time. Running "ifup eth0" a second time works. NetworkManager manger service is turned off, daemon not running. Client configured to use dhcp only, here is the ifcfg-eth0 settings: DEVICE="eth0" ONBOOT="yes" TYPE="Ethernet" HWADDR="00:01:6C:8F:D4:04" BOOTPROTO="dhcp" IPV6INIT="yes" MTU="1500" NM_CONTROLLED="no" The intefrace was turned off with "ifdown eth0", then I try to bring it up: # ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:01:6C:8F:D4:04 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:222500 errors:0 dropped:0 overruns:0 frame:0 TX packets:21468 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:27699281 (26.4 MiB) TX bytes:2074947 (1.9 MiB) Interrupt:16 Memory:d8080000-d80a0000 # ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: pumbag Wake-on: g Current message level: 0x00000001 (1) Link detected: no # ifup eth0 Determining IP information for eth0... failed; no link present. Check cable? # ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: off Supports Wake-on: pumbag Wake-on: g Current message level: 0x00000001 (1) Link detected: yes Note that the link is now detected and the second time ifup is run the interface comes up: # ifup eth0 Determining IP information for eth0... done. #ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:01:6C:8F:D4:04 inet addr:152.2.130.183 Bcast:152.2.143.255 Mask:255.255.240.0 inet6 addr: fe80::201:6cff:fe8f:d404/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:227430 errors:0 dropped:0 overruns:0 frame:0 TX packets:21708 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:28125605 (26.8 MiB) TX bytes:2097733 (2.0 MiB) Interrupt:16 Memory:d8080000-d80a0000 first ifup eth0 /var/log/messages: ---------------------------------- Jun 28 09:04:03 tophat kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Jun 28 09:04:10 tophat kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Jun 28 09:04:10 tophat kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Note it takes 7 seconds for the link to become ready. Here is the card info: # lspci | grep Ethernet 02:00.0 Ethernet controller: Intel Corporation 82573E Gigabit Ethernet Controller (Copper) (rev 03) The check_link_down function in /etc/sysconfig/network-scripts/network-fucntions is failing when called by /etc/sysconfig/network-scripts/ifup-eth. I cannot figure out why. The "ethtool --test eth0 online" and offline tests pass fine. The system works fine once the interface is running. Thanks for any help.