new networkports - devices not seem to be present

Latest response

Hello

I have changed the mainboard with networkports onboard on a running HP DL360eGen8 Server with RHEL 6.5
Problem is now that the new networkports are not present in RHEL.
I changed in ifcfg-ethx the new MACs,created new uuid for the devices,deleted the 70-rules* file and run start_udev, rebooted...installed the new driver...but nothing helped.
What else can I do???

Thanks in advance.

Responses

folder /sys/class/net/ is empty...only ~lo is here. eth0 to eth3 folders are not created! any help?

I see you responded before I was done typing out that long response ;-) I'm not surprised that /sys/class/net is empty as the links in there are representative of the what the OS reports (which you can change using a number of methods). Please see my other response. Hopefully we can get you out of this method fairly quickly ;-)

Hey Felix,
The following approach is not very "scientific" and others may have a better way.. but I would do the following...

sed -i -e 's/^HWADDR/#HWADDR/g' /etc/sysconfig/network-scripts/ifcfg-e*
grep HWADDR /etc/sysconfig/network-scripts/ifcfg-e*

That will comment out the HWADDR values in your ifcfg-emX ifcfg-ethX and ifcfg-pXpY files and then you should restart the box. I have not had to modify UDEV rules for network devices since RHEL 5, which I am happy about ;-) You may have to make blank ifcfg- files (i.e. ifcfg-em1 ifcfg-em2) and just make sure for now that they say ONBOOT=yes, until you figure out the MAC address. Once you have restarted and you get the HWaddr values, I would put those in the ifcfg files.

You can find the MAC address using lspci also (which is bit involved)

[root@devstack ~]# lspci | grep -i net
01:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
01:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
01:00.2 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
01:00.3 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
03:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57781 Gigabit Ethernet PCIe (rev 10)
04:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8191SEvB Wireless LAN Controller (rev 10)
[root@devstack ~]# lspci -vv -s 01:00.0 | grep -i serial
    Capabilities: [140 v1] Device Serial Number a0-36-9f-ff-ff-1c-0d-2c
[root@devstack ~]# ifconfig eth0 | grep HW
eth0      Link encap:Ethernet  HWaddr A0:36:9F:1C:0D:2C

NOTE: in the serial number there are 2 additional "ff" values - I have NO idea why they are there. I am not always able to figure out a MAC address using this method.

Another place you could look (but I am not hopeful it would work in your situation is:

/sys/class/net

In that directory is more directories which are a symlink to the devices.

Please let me know what I need to clarify. I realize this was all over the place (again).

Hello

I tryed what you wrote...but at least it wrote me:

eth3: error fetching interface information: Device not found

any other ideas??

Do you have a new /etc/udev/rules.d/70-persistent-net.rules now?
Does the content look accurate? (i.e. are the correct MACs now present)
Are you expecting an ethX or emX interface? I believe that onboard devices should now show up as emX (BIOSDEVNAME should handle that)... and now I have another theory. I wonder if your box is new enough that the BIOSDEVNAME is not aware...

Please take a look at the following:
http://h20566.www2.hp.com/portal/site/hpsc/template.BINARYPORTLET/public/kb/docDisplay/resource.process/?spf_p.tpst=kbDocDisplay_ws_BI&spf_p.rid_kbDocDisplay=docDisplayResURL&javax.portlet.begCacheTok=com.vignette.cachetoken&spf_p.rst_kbDocDisplay=wsrp-resourceState%3DdocId%253Demr_na-c03231796-4%257CdocLocale%253D&javax.portlet.endCacheTok=com.vignette.cachetoken

The issue with using lspci is the inconsistent output. Notice the following: (one output has extra 'ff-ff' and the other added a '00-00-' to the beginning of the address.

[root@devstack net]# for DEV in `lspci | grep -i net | awk '{ print $1 }'`; do echo "$DEV `lspci -vv -s $DEV | grep Serial`"; done
01:00.0     Capabilities: [140 v1] Device Serial Number a0-36-9f-ff-ff-1c-0d-2c
01:00.1     Capabilities: [140 v1] Device Serial Number a0-36-9f-ff-ff-1c-0d-2c
01:00.2     Capabilities: [140 v1] Device Serial Number a0-36-9f-ff-ff-1c-0d-2c
01:00.3     Capabilities: [140 v1] Device Serial Number a0-36-9f-ff-ff-1c-0d-2c
03:00.0     Capabilities: [13c v1] Device Serial Number 00-00-bc-5f-f4-68-fc-fa


[root@devstack net]# ifconfig -a | grep HWadd | grep eth
eth0      Link encap:Ethernet  HWaddr A0:36:9F:1C:0D:2C  
eth1      Link encap:Ethernet  HWaddr A0:36:9F:1C:0D:2D  
eth2      Link encap:Ethernet  HWaddr A0:36:9F:1C:0D:2E  
eth3      Link encap:Ethernet  HWaddr A0:36:9F:1C:0D:2F  
eth4      Link encap:Ethernet  HWaddr BC:5F:F4:68:FC:FA

[root@devstack net]# cat /etc/udev/rules.d/70-persistent-net.rules 
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# PCI device 0x8086:0x1521 (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="a0:36:9f:1c:0d:2c", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x14e4:0x16b1 (tg3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="bc:5f:f4:68:fc:fa", ATTR{type}=="1", KERNEL=="eth*", NAME="eth4"

# PCI device 0x8086:0x1521 (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="a0:36:9f:1c:0d:2e", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x8086:0x1521 (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="a0:36:9f:1c:0d:2d", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x1521 (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="a0:36:9f:1c:0d:2f", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"

So - what do you get from
~~~
ifconfig -a
ls -l /sys/class/net
lspci | grep -i net

this file I have /etc/udev/rules.d/70-persistent-net.rules ... with the old entries and the new. as I read, I have to delete the old entries. I tried to re-create this file after booting, but it wasn't created new!

Via HP-iLO I can see the same MAC's of the Networkports, but one is missing...I have 0,1 and 3...number 2 is not available!!!

Anyway, the folder /sys/class/net is still empty...only lo is in there.

...

ifconfig -a = shows me the lo

ls -l /sys/class/net = total 0 1rwxrwxrwx 1 root root 0 May 26 16:20 lo -> ../../devices/virtual/net/lo

lspci | grep -i net = 02:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
... = 02:00.1 ...
... = 02:00.3 ...

...alright...thank you guys for helping...I solved it. I re-updated the firmware of the NIC on board. All 4 connectors are working now!

it took long that way...

crazy - I have had similar issues with HP gear. Be sure to check out that doc I linked earlier - that seemed to have quite a bit of good info (If you will be building a lot of servers).

Glad everything is working now.

thanks! yes, it is crazy, because in iLO the network adapters were visible (but only 3 of 4)...and in rhel no one! I think that was maybe a firmware problem. But I only tried to solve it on rhel. Now I know it better ;-)

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.