biosdevname ethN_rename issues on 5.7 (SOLVED)

Mikael Fridh mfridh at marinsoftware.com
Mon Jan 23 18:34:15 CST 2012


I found some of our systems end up with the following names, 
note the ethN_rename:

2: em1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 qlen 1000
3: em2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 qlen 1000
4: em3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
5: em4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
6: p1p1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
7: eth1_rename: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
8: p1p3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
9: eth3_rename: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 00:1b:21:cc:2d:1d brd ff:ff:ff:ff:ff:ff

the em* is bnx2
the p1p* are igb

01:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
01:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
02:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
07:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
07:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
08:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)
08:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)

System is R710.
CentOS 5.7, kernel 2.6.18-274.el5

So, while writing this email, I actually found a fix for this issue, so FYI
for anyone else experiencing the same:
Remove any alias eth* entries from modprobe.conf !

Background:
In the %post section of a kickstart a script takes care of 
everything to install biosdevname if the server is a centos 5 and configure
all files in sysconfig/network-scripts/ifcfg-emN and pNpN but I found that in
/etc/modprobe.conf there's the following after a kickstart:
alias eth0 igb
alias eth1 igb
alias eth2 igb
alias eth3 igb
alias eth4 bnx2
alias eth5 bnx2
alias eth6 bnx2
alias eth7 bnx2
alias scsi_hostadapter megaraid_sas

And by commenting out the aliases I got it to consistantly do the right
thing on the intel nics:
#alias eth0 igb
#alias eth1 igb
#alias eth2 igb
#alias eth3 igb

# modprobe -r igb; modprobe igb; ip link
36: p1p1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
37: p1p2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
38: p1p3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
39: p1p4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000

When there are alias entries in modprobe.conf you're sometimes left with
seemingly random devices ending up named as ethN_rename.

So I tried removing all alias eth* from modprobe.conf and restart networking
and drivers completely:
# service network stop; modprobe -r igb; modprobe -r bnx2; modprobe bnx2; modprobe igb; service network start

Things work fine now it seems so I guess I will update the kickstart %post 
script to clear out all aliases from modprobe.conf from now on.

-- 
Mikael Fridh             / www.marinsoftware.com
Sysadmin, Operations    / Regus, 8th Floor
Marin Software         / Mäster Samuelsgatan 60
Cell: +46-708-174-200 / 111 21 Stockholm



More information about the Linux-PowerEdge mailing list