Hello All,
I have one CentOS 6 KVM virtualization server that I built around a year
ago (best I can tell it was in October 2012) at which time I would have
been installing 6.3 [0]. That particular install used the Consistent
Network Device Naming [1] conventions (PCIe NICs are p1p1, p1p2).
I started to build out a new KVM virt server (kickstarting a 6.4 install
now as compared to 6.3 back then) and the interface names are back to the
old ethX convention for the PCIe NICs. See below for my snippets from udev
persistent rules on the two hosts.
I'm working off of [older] Dell PowerEdge 2950 hardware that has dual
onboard Broadcom NICs and an additional Intel Dual GigE PCIe NIC.
** Did anyone but me notice this change/regression in network interface
naming?
** Does anyone know if or why a change was made from what 6.3 or earlier
apparently defaulted to?
This is by no means a major problem, but it did make me wonder what caused
or why there was a change. [Of course I can change interface names in the
udev rules if I chose to.]
Thanks for your feedback!
=================
Snippets:
# was 6.3 when initially installed, but has been updated to 6.4 since then
~]# cat /etc/*ele*
CentOS release 6.4 (Final)
CentOS release 6.4 (Final)
CentOS release 6.4 (Final)
cpe:/o:centos:linux:6:GA
~]# egrep -v '^$|^#' /etc/udev/rules.d/70-persistent-net.rules
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:22:19:xx:xx:xx", ATTR{type}=="1",
KERNEL=="eth*",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:22:19:xx:xx:xx", ATTR{type}=="1",
KERNEL=="eth*",
NAME="eth1"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:15:17:xx:xx:xx", ATTR{type}=="1",
KERNEL=="eth*",
NAME="p1p1"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:15:17:xx:xx:xx", ATTR{type}=="1",
KERNEL=="eth*",
NAME="p1p2"
~]# lspci | grep Ether
05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
Gigabit Ethernet (rev 12)
09:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
Gigabit Ethernet (rev 12)
0c:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet
Controller (rev 06)
0c:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet
Controller (rev 06)
# freshly installed 6.4
~]# cat /etc/*ele*
CentOS release 6.4 (Final)
CentOS release 6.4 (Final)
CentOS release 6.4 (Final)
cpe:/o:centos:linux:6:GA
~]# egrep -v '^$|^#' /etc/udev/rules.d/70-persistent-net.rules
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:22:19:xx:xx:xx", ATTR{type}=="1",
KERNEL=="eth*",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:15:17:xx:xx:xx", ATTR{type}=="1",
KERNEL=="eth*",
NAME="eth2"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:22:19:xx:xx:xx", ATTR{type}=="1",
KERNEL=="eth*",
NAME="eth1"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:15:17:xx:xx:xx", ATTR{type}=="1",
KERNEL=="eth*",
NAME="eth3"
~]# lspci | grep Ether
03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
Gigabit Ethernet (rev 12)
07:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
Gigabit Ethernet (rev 12)
08:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet
Controller (rev 06)
08:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet
Controller (rev 06)
[0] https://access.redhat.com/site/articles/3078
[1]
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/appe-Consistent_Network_Device_Naming.html
--
---~~.~~---
Mike
// SilverTip257 //
On 11/15/2013 01:50 PM, SilverTip257 wrote:> Hello All, > > I have one CentOS 6 KVM virtualization server that I built around a year > ago (best I can tell it was in October 2012) at which time I would have > been installing 6.3 [0]. That particular install used the Consistent > Network Device Naming [1] conventions (PCIe NICs are p1p1, p1p2). > > I started to build out a new KVM virt server (kickstarting a 6.4 install > now as compared to 6.3 back then) and the interface names are back to the > old ethX convention for the PCIe NICs. See below for my snippets from udev > persistent rules on the two hosts. > > I'm working off of [older] Dell PowerEdge 2950 hardware that has dual > onboard Broadcom NICs and an additional Intel Dual GigE PCIe NIC. > > ** Did anyone but me notice this change/regression in network interface > naming? > ** Does anyone know if or why a change was made from what 6.3 or earlier > apparently defaulted to? > > This is by no means a major problem, but it did make me wonder what caused > or why there was a change. [Of course I can change interface names in the > udev rules if I chose to.] > > Thanks for your feedback! > > =================> > Snippets: > > # was 6.3 when initially installed, but has been updated to 6.4 since then > ~]# cat /etc/*ele* > CentOS release 6.4 (Final) > CentOS release 6.4 (Final) > CentOS release 6.4 (Final) > cpe:/o:centos:linux:6:GA > ~]# egrep -v '^$|^#' /etc/udev/rules.d/70-persistent-net.rules > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:22:19:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", > NAME="eth0" > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:22:19:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", > NAME="eth1" > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:15:17:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", > NAME="p1p1" > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:15:17:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", > NAME="p1p2" > ~]# lspci | grep Ether > 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 > Gigabit Ethernet (rev 12) > 09:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 > Gigabit Ethernet (rev 12) > 0c:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet > Controller (rev 06) > 0c:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet > Controller (rev 06) > > # freshly installed 6.4 > ~]# cat /etc/*ele* > CentOS release 6.4 (Final) > CentOS release 6.4 (Final) > CentOS release 6.4 (Final) > cpe:/o:centos:linux:6:GA > ~]# egrep -v '^$|^#' /etc/udev/rules.d/70-persistent-net.rules > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:22:19:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", > NAME="eth0" > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:15:17:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", > NAME="eth2" > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:22:19:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", > NAME="eth1" > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:15:17:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", > NAME="eth3" > ~]# lspci | grep Ether > 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 > Gigabit Ethernet (rev 12) > 07:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 > Gigabit Ethernet (rev 12) > 08:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet > Controller (rev 06) > 08:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet > Controller (rev 06) > > > [0] https://access.redhat.com/site/articles/3078 > [1] > https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/appe-Consistent_Network_Device_Naming.html >Do you have the biosdevname package loaded? -- Stephen Clark *NetWolves* Director of Technology Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.clark at netwolves.com http://www.netwolves.com
On 11/15/2013 01:50 PM, SilverTip257 wrote:> Hello All, > > I have one CentOS 6 KVM virtualization server that I built around a year > ago (best I can tell it was in October 2012) at which time I would have > been installing 6.3 [0]. That particular install used the Consistent > Network Device Naming [1] conventions (PCIe NICs are p1p1, p1p2). > > I started to build out a new KVM virt server (kickstarting a 6.4 install > now as compared to 6.3 back then) and the interface names are back to the > old ethX convention for the PCIe NICs. See below for my snippets from udev > persistent rules on the two hosts. > > I''m working off of [older] Dell PowerEdge 2950 hardware that has dual > onboard Broadcom NICs and an additional Intel Dual GigE PCIe NIC. > > ** Did anyone but me notice this change/regression in network interface > naming? > ** Does anyone know if or why a change was made from what 6.3 or earlier > apparently defaulted to? > > This is by no means a major problem, but it did make me wonder what caused > or why there was a change. [Of course I can change interface names in the > udev rules if I chose to.] > > Thanks for your feedback! > > =================> > Snippets: > > # was 6.3 when initially installed, but has been updated to 6.4 since then > ~]# cat /etc/*ele* > CentOS release 6.4 (Final) > CentOS release 6.4 (Final) > CentOS release 6.4 (Final) > cpe:/o:centos:linux:6:GA > ~]# egrep -v ''^$|^#'' /etc/udev/rules.d/70-persistent-net.rules > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:22:19:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", > NAME="eth0" > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:22:19:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", > NAME="eth1" > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:15:17:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", > NAME="p1p1" > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:15:17:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", > NAME="p1p2" > ~]# lspci | grep Ether > 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 > Gigabit Ethernet (rev 12) > 09:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 > Gigabit Ethernet (rev 12) > 0c:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet > Controller (rev 06) > 0c:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet > Controller (rev 06) > > # freshly installed 6.4 > ~]# cat /etc/*ele* > CentOS release 6.4 (Final) > CentOS release 6.4 (Final) > CentOS release 6.4 (Final) > cpe:/o:centos:linux:6:GA > ~]# egrep -v ''^$|^#'' /etc/udev/rules.d/70-persistent-net.rules > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:22:19:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", > NAME="eth0" > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:15:17:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", > NAME="eth2" > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:22:19:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", > NAME="eth1" > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR{address}=="00:15:17:xx:xx:xx", ATTR{type}=="1", KERNEL=="eth*", > NAME="eth3" > ~]# lspci | grep Ether > 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 > Gigabit Ethernet (rev 12) > 07:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 > Gigabit Ethernet (rev 12) > 08:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet > Controller (rev 06) > 08:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet > Controller (rev 06) > > > [0] https://access.redhat.com/site/articles/3078 > [1] > https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/appe-Consistent_Network_Device_Naming.html >Do you have the biosdevname package loaded? -- Stephen Clark *NetWolves* Director of Technology Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.clark-HKs6b5iW9l2akBO8gow8eQ@public.gmane.org http://www.netwolves.com
On Fri, Nov 15, 2013 at 01:50:18PM -0500, SilverTip257 wrote:> Hello All, > > I have one CentOS 6 KVM virtualization server that I built around a year > ago (best I can tell it was in October 2012) at which time I would have > been installing 6.3 [0]. That particular install used the Consistent > Network Device Naming [1] conventions (PCIe NICs are p1p1, p1p2).This regression is a combo RedHat/Dell idea, IIRC. That may be why it's that way on a Dell machine. On Fedora, which usually shows what new regressions will be in RH, it's gotten harder to fix with each iteration. To make it worse, at least on Fedora (and again, many of their ideas, whether good or bad for servers, get into RedHat) has apparently now been intertwined with systemd. At first, one simply had to remove the biosdevnames rpm to fix it. Now, one has to do that, and also add, (in Fedora, with grub2) net.ifnames=0 to the kernel line. (Note that this was for Fedora 19, not sure if they at least removed biosdevnames in F20). To make it even more of a mess, (again, this is judging from Fedora, which is good to keep on hand to see what new decisions good and bad will be made by RH), I think biosdevnames gave it one name and then the whole systemd thing gave it another. So, it would boot up as say p12p but in /etc/sysconfig/network-scripts it would show up as ifcfg-p1p2p or something like that. (I'm making these names up, but that was the general idea.) Some people consider it a good thing, especially when moving drives between machines, but aside from it being something new, which isn't necessarily improved, it breaks various working scripts. Like you, I consider it a regression, but of course, that's only my opinion, and many experienced folks disagree, thinking it's a good thing--although I'm sure that even they would agree that they better figure out if biosdevname or something else will be handling it so that it is at least consistent. Actually, I think (but am not sure, that in VMs, even Fedora will use the eth0, eth1 system rather than the new naming scheme. Not just KVM, but also VirtualBox, VMware, and so on--that has been my experience with CentOS VMs at least. -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6