• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 6111
  • Last Modified:

eth1 does not seem to be present, delaying initialization

I am running CentOS 5.3 on a IBM xSeries 360 with 3 NIC cards. If the 2nd NIC is not being used after an extended period of time, I am seeing that eth1 is disappearing after an extended period of time (eth2 isn't configured as of yet).

I tried to do '/etc/init.d/network restart', but I am getting the following message:

Shutting down interface eth0:                              [  OK  ]
Shutting down loopback interface:                          [  OK  ]
Bringing up loopback interface:                            [  OK  ]
Bringing up interface eth0:                                [  OK  ]
Bringing up interface eth1:  e100 device eth1 does not seem to be present, delaying initialization.  [FAILED]

But if I were to reboot the server, eth0 and eth1 come up fine.

I have included the output from lspci and snippets from the /var/log/messages and /etc/modprobe.conf for additional details.

/var/log/messages
=================
Apr 17 12:43:24 spacewalk dhcpd: DHCPOFFER on 10.1.0.10 to 00:0b:cd:a2:7e:b6 via eth1
Apr 17 12:43:24 spacewalk dhcpd: DHCPREQUEST for 10.1.0.10 (10.1.0.1) from 00:0b:cd:a2:7e:b6 via eth1
Apr 17 12:43:24 spacewalk dhcpd: DHCPACK on 10.1.0.10 to 00:0b:cd:a2:7e:b6 via eth1
Apr 17 12:43:47 spacewalk dhcpd: DHCPREQUEST for 10.1.0.10 from 00:0b:cd:a2:7e:b6 via eth1
Apr 17 12:43:47 spacewalk dhcpd: DHCPACK on 10.1.0.10 to 00:0b:cd:a2:7e:b6 via eth1
Apr 17 22:22:48 spacewalk dhcpd: DHCPREQUEST for 10.1.0.10 from 00:0b:cd:a2:7e:b6 via eth1
Apr 17 22:22:48 spacewalk dhcpd: DHCPACK on 10.1.0.10 to 00:0b:cd:a2:7e:b6 via eth1
Apr 18 02:01:38 spacewalk avahi-daemon[4348]: Interface eth1.IPv6 no longer relevant for mDNS.
Apr 18 02:01:38 spacewalk avahi-daemon[4348]: Leaving mDNS multicast group on interface eth1.IPv6 with address fe80::203:47ff:fedf:904.
Apr 18 02:01:38 spacewalk avahi-daemon[4348]: Interface eth1.IPv4 no longer relevant for mDNS.
Apr 18 02:01:38 spacewalk avahi-daemon[4348]: Leaving mDNS multicast group on interface eth1.IPv4 with address 10.1.0.1.
Apr 18 02:01:38 spacewalk dhcpd: receive_packet failed on eth1: Network is down
 
 
lspci output
============
00:00.0 Host bridge: IBM Winnipeg PCI-X Host Bridge (rev 02)
00:01.0 VGA compatible controller: S3 Inc. Savage 4 (rev 06)
00:02.0 Bridge: IBM Remote Supervisor Adapter (RSA)
00:03.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev 08)
00:04.0 SCSI storage controller: Adaptec AIC-7892P U160/m (rev 02)
00:06.0 Class 0808: IBM Unknown device 0246
00:0f.0 ISA bridge: Broadcom OSB4 South Bridge (rev 50)
00:0f.1 IDE interface: Broadcom OSB4 IDE Controller
00:0f.2 USB Controller: Broadcom OSB4/CSB5 OHCI USB Controller (rev 04)
01:00.0 Host bridge: IBM Winnipeg PCI-X Host Bridge (rev 02)
0a:00.0 Host bridge: IBM Winnipeg PCI-X Host Bridge (rev 02)
 
 
/etc/modprobe.conf
==================
alias eth0 e100
alias eth1 e100
alias scsi_hostadapter aic7xxx
alias eth2 e100

Open in new window

0
Michael Worsham
Asked:
Michael Worsham
  • 3
  • 2
1 Solution
 
Daniel McAllisterPresident, IT4SOHO, LLCCommented:
Sounds like your system is powering down the NIC card for inactivity -- any chance this is a BIOS (motherboard or NIC card) setting???

also, you might try the command: ifcfg eth1 up
...as a root user to re-up the eth1 card...

If you're connected to the same LAN (but perhaps different switches), you may want to look into bonding eth0 and eth1 so that each is being used (and thus, is not turned off)

There is a nice writeup on Linux bonding at
http://www.cyberciti.biz/howto/question/static/linux-ethernet-bonding-driver-howto.php

I hope this helps!

Dan
IT4SOHO
0
 
Michael WorshamInfrastructure / Solutions ArchitectAuthor Commented:
Bonding is not an option as I am trying to separate two networks (eth0 = 192.168.105.x, eth1 = 10.1.0.x).

---

Tried the 'ifcfg eth1 up' and got the following error/message:

Forwarding is ON or its state is unknown (4). OK, No RDISC.
/sbin/ifcfg: line 25: [: up: integer expression expected
/sbin/ifcfg: line 26: [: up: integer expression expected
/sbin/ifcfg: line 27: [: up: integer expression expected
/sbin/ifcfg: line 28: [: up: integer expression expected
SIOCGIFFLAGS: No such device
Error: cannot enable interface eth1.


If I do ifup eth1, I get the following message:

e100 device eth1 does not seem to be present, delaying initialization.
0
 
Michael WorshamInfrastructure / Solutions ArchitectAuthor Commented:
Just on a theory, I installed WakeOnLan (wol) for seeing if I could send 'magic packets' to the device to wake it up. Ethtool and ifconfig reports they no longer see the 2nd NIC card any longer as well.

Results are as follows....


[root@spacewalk ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Intel Corporation 82557/8/9/0/1 Ethernet Pro 100
DEVICE=eth0
BOOTPROTO=static
DHCPCLASS=
HWADDR=00:02:55:AC:3B:81
IPADDR=192.168.105.19
NETMASK=255.255.254.0
ONBOOT=yes
 
[root@spacewalk etc]# cat /etc/sysconfig/network-scripts/ifcfg-eth1
# Intel Corporation 82557/8/9/0/1 Ethernet Pro 100
DEVICE=eth1
BOOTPROTO=static
DHCPCLASS=
HWADDR=00:03:47:DF:09:04
IPADDR=10.1.0.1
NETMASK=255.255.255.0
ONBOOT=yes
ETHTOOL_OPTS="wol g"
 
[root@spacewalk etc]# wol 00:03:47:DF:09:04
Waking up 00:03:47:DF:09:04...
 
[root@spacewalk etc]# ifconfig 
eth0      Link encap:Ethernet  HWaddr 00:02:55:AC:3B:81  
          inet addr:192.168.105.19  Bcast:192.168.105.255  Mask:255.255.254.0
          inet6 addr: fe80::202:55ff:feac:3b81/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:135315 errors:52 dropped:0 overruns:0 frame:52
          TX packets:9451 errors:8 dropped:0 overruns:0 carrier:8
          collisions:0 txqueuelen:1000 
          RX bytes:10001586 (9.5 MiB)  TX bytes:1251301 (1.1 MiB)
 
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:728425 errors:0 dropped:0 overruns:0 frame:0
          TX packets:728425 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:88261146 (84.1 MiB)  TX bytes:88261146 (84.1 MiB)
 
[root@spacewalk etc]# ethtool eth0
Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
        Supports auto-negotiation: Yes
        Advertised link modes:  100baseT/Full 
        Advertised auto-negotiation: No
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: off
        Supports Wake-on: g
        Wake-on: g
        Current message level: 0x00000007 (7)
        Link detected: yes
 
[root@spacewalk etc]# ethtool eth1
Settings for eth1:
Cannot get device settings: No such device
Cannot get wake-on-lan settings: No such device
Cannot get message level: No such device
Cannot get link status: No such device
No data available
 
[root@spacewalk etc]# ifup eth1  
e100 device eth1 does not seem to be present, delaying initialization.

Open in new window

0
Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

 
Daniel McAllisterPresident, IT4SOHO, LLCCommented:
Have you examined the dmesg log and the system log? (perhaps grep them both with eth1 or a MAC address fragment)

It's beginning to look like your NIC may be simply failing, so Linux is unloading the driver.

Perhaps if you find the driver module (by looking in the dmesg log), you could manually re-load the module (insmod) and look closely at the system log file for potential errors.

Just a suggestion....

Dan
IT4SOHO

PS: Possible to replace the NIC?
0
 
Michael WorshamInfrastructure / Solutions ArchitectAuthor Commented:
The NIC was failing, so once it was replaced the problem went away.
0
 
DevynCommented:
There's a number of solutions to this error as it's only generic or miscellaneous error.  See this old post on a number of ways of solving these.

http://microdevsys.com/wp/device-eth0-does-not-seem-to-be-present-delaying-initialization-linux-networking/

Regards,
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now