The issue here may be systemd (I've seen/agree with the venting, this is another example). If you're getting non-eth names there's a program called biosdevname which may be deciding how to name NICs for you. If that's the case then then the <nn>-net.rules may be ineffective unless the following is added as kernel command line parameters:
net.ifnames=1 and biosdevname=0
I need to add big cautions here, my experience with this is on Ubuntu (where it's 70-net.rules) and a hardware platform which has 10 NICs. systemd/biosdevname... named the first six NICs 'ens...' and the last four 'eth...'. (<rant> I really do wish the developers would stop trying to decide what's best for us and leave control in our hands or at least provide documentation which is easily findable that allows us to take control back. </rant>). Web documentation at freedesktop.org says net.ifnames needs to be set to zero, I found just the opposite but if it doesn't work for you try both before giving up. I know where to set these parameters on Ubuntu but you'll have to find where on CentOS. Hope this helps.
----- Original Message -----
From: "Ricardo J. Barberis" <ricardo@xxxxxxxxxxxxx>
To: "CentOS mailing list" <centos@xxxxxxxxxx>
Sent: Monday, February 1, 2016 8:31:42 AM
Subject: Re: NICs order
El Lunes 01/02/2016, Daniel Ruiz Molina escribió:
> Hi,
>
> After installing CentOS 7 in a server with 2 NICs, system detects eth0
> and eth1 in reserve order. I would like to have eth1 as eth0 and eth0 as
> eth1. I have forced HWADDR attribute in
> /etc/sysconfig/network-scripts/ifcfg-etc{0,1}, but after rebooting,
> order is the same...
>
> How can I solve it?
>
> Thanks.
You could put the MAC addresses in /etc/udev/rules.d/60-net.rules, e.g.:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="11:22:33:aa:bb:cc", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="44:55:66:dd:ee:ff", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
But that never worked reliably for me, no matter what I tried.
In the end I had to use different names instead of eth0 and eth1, like:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="11:22:33:aa:bb:cc", ATTR{type}=="1", KERNEL=="eth*", NAME="nic0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="44:55:66:dd:ee:ff", ATTR{type}=="1", KERNEL=="eth*", NAME="nic1"
And also rename /etc/sysconfig/network-scripts/ifcfg-ethX to ifcfg-nicX and
modify them accordingly.
HTH,
--
Ricardo J. Barberis
Usuario Linux Nº 250625: http://counter.li.org/
Usuario LFS Nº 5121: http://www.linuxfromscratch.org/
Senior SysAdmin / IT Architect - www.DonWeb.com
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
Confidentiality Notice | This email and any included attachments may be privileged, confidential and/or otherwise protected from disclosure. Access to this email by anyone other than the intended recipient is unauthorized. If you believe you have received this email in error, please contact the sender immediately and delete all copies. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
