eth0 and eth1 missing - Newbie

vl23 · 01-26-2014, 02:52 PM

Quote:

Originally Posted by LYC

Hi,

There is no ntwork connection. The connection is via KVM, hence, file can not x'fer out and has to use screen shot.

No hardware changes. The server is shifted from one rack to another rack.

more /etc/sysconfig/selinux
SELINUXTYPE=targeted

lshw -c net
bash: command not found

Refer to attachment for lspci output

grep, essential tool, use it.

$ dmesg | egrep -i "net|eth"
lspci -vvv | less
then hit / and type "net" to search for that paricular substring in the piped input.

Also what about that iLO, IIRC the HP ones had the offline diagnostic option?

LYC · 01-26-2014, 04:31 PM

Hi,

See attached.

LYC · 01-26-2014, 04:36 PM

Hi,

See attached.

vl23 · 01-26-2014, 05:23 PM

How many interfaces did this system have, because if it was only 2 they might've gotten renamed, check their MACs if you have the old ones, then use a udev rule to return the old names if you wish.
If you still have problems try using udevadm to rescan and see if your missing interfaces will get found, but if it is a hw issue due to the move I doubt it will happen.

LYC · 01-26-2014, 06:52 PM

It should has 4 network interface, eth0, eth1, eth2 and eth3.

Output of ifconfig -a only show eth2 and eth3 (refer to attachment)

#udevadm
bash: udevadm command not found

LYC · 01-26-2014, 07:00 PM

Hi,

Attachment is the output of dmesg | egrep -i "net|eth".

LYC · 01-27-2014, 12:37 AM

Hi,

The following is expected to show up in dmesg but did not:
:
Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection
:

Can advise how to go about it?

chantk · 01-27-2014, 08:52 AM

To see if e1000 is loaded:

Code:

lsmod | grep e1000

To load the module manually:

Code:

modprobe e1000

See if it complains.

P.S. No more .gif please. Post the plain text file.

vl23 · 01-27-2014, 11:33 AM

Quote:

Originally Posted by chantk

To see if e1000 is loaded:

Code:

lsmod | grep e1000

To load the module manually:

Code:

modprobe e1000

See if it complains.

P.S. No more .gif please. Post the plain text file.

I think that lspci should have detected the hardware even if it wasn't claimed/recognized, I'd say 80/20 it is a hardware issue.
Also for the 3rd time, what happened to those hw diagnostics from the iLO?

LYC · 01-27-2014, 04:18 PM

Hi,

No return for lsmod | grep e1000 until manually loaded as advised but eth0 using ifcomfig -a still to no avail.

Could you advise how to get hw diagnostic from iLO?