6

I'm attempting to configure a machine with 3 NICs, the first two are built-in GbE controllers, the third is a 10GbE controller. Via NetworkManager, I've configured the 'first' GbE NIC (which at the time was eth0) to use a static IP address. The second GbE NIC will be configured on a separate private network and the 10GbE NIC is not being used right now.

When I reboot the machine, the ordering of eth0, eth1, eth2, etc appears to be random. Occasionally eth0 will pick up the static ip address, other times it is recognized as eth1 and grabs a DHCP address. In this case, I need to swap the cables before it reconfigures properly.

How can I control the ordering so that a particular physical NIC always comes up as eth0 or eth1 without changing next reboot?

3

The method still supported in RHEL 6 is via udev device rules.

There should be an automatically generated /etc/udev/rules.d/70-persistent-net.rules which forces consistent naming:

# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.

# PCI device 0x8086:0x10c9 (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:25:90:1d:d1:30", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x8086:0x10c9 (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:25:90:1d:d1:31", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

If not you can use a similar syntax with your own MAC addresses to force persistent device naming.

4

Maybe someone will find those informations useful: First of all in RHEL7 you dont need to reinstall your system to change interface naming convention.

Note: Boot params required:

a) With no parameters or net.ifnames=1 used, the names will use systemd Predictable Network Interface Names
b) With biosdevname=1 used, the names will be managed by udev (technically systemd-udev) using Consistent Network Device Naming
c) With net.ifnames=0 and biosdevname=0 both specified, traditional ("kernel names") ethX names will be used; if udev rules are also added they can rename the interfaces to anything except eth

Example:

Edit /etc/default/grub
append selected params eg.
biosdevname=0 net.ifnames=0
grub2-mkconfig -o /boot/grub2/grub.cfg

And in case of main topic: When you need to adjust order of all interfaces procedure is easy:

mv /etc/udev/rules.d/70-persistent-net.rules /root/ 
(New udev rules will be generated at next boot)

Adjust configuration files in
/etc/sysconfig/network-scripts/ifcfg-eth*
[Edit device name, connection name, HWADDR etc.] 

Reboot and then udev will generate rules basing on configuration files - if you did it properely.
4

The supported way to do this, for RHEL 6 and in the future, is consistent network device naming. This ensures that all interfaces get a meaningful name which is based on the hardware and remains the same throughout the life of the system (if you don't change the hardware, anyway, and usually even if you do).

(Note that in RHEL 7, a different naming format is used.)

To switch to it on RHEL 6, you need to reinstall the system, and when you install, you must pass the kernel command line option biosdevname=1 when starting the installation media, and every time you boot the system.

2

As suggested by RedHat documentation you can specify HWADDR=MAC-address parameter in your interface configuration file.

HWADDR=MAC-address where MAC-address is the hardware address of the Ethernet device in the form AA:BB:CC:DD:EE:FF. This directive must be used in machines containing more than one NIC to ensure that the interfaces are assigned the correct device names regardless of the configured load order for each NIC's module. This directive should not be used in conjunction with MACADDR.

0

As mentionned by HBruijn, the ordering in rhel6 is /etc/udev/rules.d/70-persistent-net.rules. This file is writen by /lib/udev/write_net_rules.

If for some reason you need an arbitrary and pre-determined ordering of your network interfaces, you may replace this script by your own one, to create the 70-persistent-net.rules file. This makes sure it won't be overwriten.

You may obtain device information to do so using

lspci | grep -i ethernet

to get the list of devices

ethtool -i ethx
ethtool -P ethx

to get the MAC-addr of each one (correlate PCI @ / MAC @).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.