Alteeve Wiki - User contributions [en-gb]

User:Rucus

2013-05-18T18:26:55Z

Rucus: Created page with "Test"

Test

Changing the ethX to Ethernet Device Mapping in EL6 and Fedora 12 to 14

2012-11-19T14:18:38Z

Rucus: /* 'udev' Configuration */

Changing the ethX to Ethernet Device Mapping in EL6 and Fedora 12 to 14

2012-11-19T14:16:10Z

Rucus: /* For the Impatient */

{{howto_header}}

{{note|1=This applies up to Fedora 14. Fedora 15 works quite differently now that it uses biosdevname. Please follow [[Changing Ethernet Device Names in EL7 and Fedora 15+|this tutorial]] for Fedora 15 and newer.}}

When you have two or more ethernet devices in one machine, the Fedora install may not install them in the order you want. This document will show you how to change the ethX to physical ethernet device mapping.

This is desirable in cases where specific network cards need to be used on specific networks, and you are interested in maintaining common ethX names across servers. A practical example is found in the [[2-Node Red Hat KVM Cluster Tutorial]].

= For the Impatient =

Assuming that NetworkManager is already removed. This example will swap eth0 and eth1.

<source lang="bash">
# Stop the network daemon
/etc/init.d/network stop
cd /etc/sysconfig/network-scripts
# Move your ifcfg files to the device names you desire
mv ifcfg-eth0 ifcfg-temp
mv ifcfg-eth1 ifcfg-eth0
mv ifcfg-temp ifcfg eth1
# Modify DEVICE lines to match new file names
vim /etc/sysconfig/network-scripts/ifcfg-eth*
# Make changes as needed
# Remove udev rules file
rm /etc/udev/rules.d/70-persistent-net.rules
start_udev
/etc/init.d/network start
</source>

Thanks for fenris02 and mutk

= Example =

I find it easier to follow instructions when I have an example to follow, so let me provide one here:

I've got the same hardware in the same configuration in both of my storage nodes. To keep things simple, I want to make sure that both nodes use the same ethX name for the network devices on each of the given networks.

== Desired Mapping ==

Let's assume that you want this:

* eth0
** MAC: 90:E6:BA:71:82:EA
* eth1
** MAC: 00:21:91:19:96:53
* eth2
** MAC: 00:0E:0C:59:46:E4

== Initial Mapping ==

When the Fedora install finished, you may have gotten this:

* eth0
** MAC: 00:21:91:19:96:53
* eth1
** MAC: 90:E6:BA:71:82:EA
* eth2
** MAC: 00:0E:0C:59:46:E4

== The Problem ==

In the above example, eth2 is where we want it, so we leave it alone. The problem is that eth0 and eth1 are reversed.

== The Fix ==

What we need to do is modify the DEVICE=... line in each ifcfg-ethX file to reflect the order we want.

To avoid confusion later on, we should also rename the files to reflect the new device names.

=== Stopping the Network ===

First, stop the network. This is important because if you change the MAC address mapping while the network is still up, the init.d script will fail to bring down the network devices and you will need to reboot for the changes to take effect.

<source lang="bash">
/etc/init.d/network stop
</source>

=== Interface Configuration ===

Go to the /etc/sysconfig/network-scripts/ directory and then use cat to see the contents of the ifcfg-eth* network configuration files:

<source lang="bash">
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
</source>
<source lang="text">
DEVICE="eth0"
HWADDR="00:21:91:19:96:53"
</source>
<source lang="bash">
cat ifcfg-eth1
</source>
<source lang="text">
DEVICE="eth1"
HWADDR="90:E6:BA:71:82:EA"
</source>
<source lang="bash">
cat ifcfg-eth2
</source>
<source lang="text">
DEVICE="eth2"
HWADDR="00:0E:0C:59:46:E4"
</source>

The important lines are the DEVICE=... and HWADDR=... lines. The rest of the lines will very likely differ from the output above. It is outside the scope of this tutorial to cover the various settings. For an exhaustive list of available options, please [http://docs.fedoraproject.org/en-US/Fedora/12/html/Deployment_Guide/s1-networkscripts-interfaces.html see the Fedora documentation].

First, change the file names to reflect the device order that you want. In this example we need to swap eth0 and eth1.

<source lang="bash">
cd /etc/sysconfig/network-scripts
mv ifcfg-eth0 ifcfg-temp
mv ifcfg-eth1 ifcfg-eth0
mv ifcfg-temp ifcfg-eth1
</source>

Using your editor of choice, open each file and change the DEVICE=... to match the new filename.

Here is the updated files with updated network settings:

<source lang="bash">
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
</source>
<source lang="text">
DEVICE="eth0"
HWADDR="90:E6:BA:71:82:EA"
</source>
<source lang="bash">
cat ifcfg-eth1
</source>
<source lang="text">
DEVICE="eth1"
HWADDR="00:21:91:19:96:53"
</source>
<source lang="bash">
cat ifcfg-eth2
</source>
<source lang="text">
DEVICE="eth2"
HWADDR="00:0E:0C:59:46:E4"
</source>

=== 'udev' Configuration ===

The user-space device manager, [http://en.wikipedia.org/wiki/Udev udev], maintains a list of configuration files that help ensure that hardware to /dev (software) mappings stay consistent, even when hardware is hot swapped or moved between physical connections. For networking hardware, this mapping is recorded in the 70-persistent-net.rules.

Here, all that needs to be done is for the NAME="..." entry to be changed to reflect what you want.

Note that the entries do not need to be in any particular order.

<source lang="bash">
cd /etc/udev/rules.d/
cat 70-persistent-net.rules
</source>
<source lang="text">
# 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:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:0c:59:46:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x1186:0x4b00 (sky2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:91:19:96:53", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="90:e6:ba:71:82:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
</source>

Make the changes and save the file. The file should now look like this:

<source lang="bash">
cat 70-persistent-net.rules
</source>
<source lang="text">
# 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 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="90:e6:ba:71:82:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x1186:0x4b00 (sky2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:91:19:96:53", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:0c:59:46:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
</source>

=== Making the Changes Take Effect ===

First, you need to reload udev so that it updates the mapping in memory. This is done using the start_udev program:

<source lang="bash">
start_udev
</source>
<source lang="text">
Starting udev: [ OK ]
</source>

With udev updated, the last step is to restart the network daemon:

<source lang="bash">
/etc/init.d/network start
</source>
<source lang="text">
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth1: [ OK ]
Bringing up interface eth2: [ OK ]
</source>

Done! use ifconfig to verify that the network cards are properly assigned to the specified ethX names.

== Caveat! ==

'''''NOTE''''': If you are using a vlan, the device facing the vlan '''can not''' have the '''HWADDR=...''' value set! Set the others and leave this commented out. Otherwise, because of how the vlan loads, the OS will not see the physical device and will fail to bring up the interface at all.

{{footer}}

Changing the ethX to Ethernet Device Mapping in EL6 and Fedora 12 to 14

2012-11-19T14:15:09Z

Rucus: /* For the Impatient */

{{howto_header}}

{{note|1=This applies up to Fedora 14. Fedora 15 works quite differently now that it uses biosdevname. Please follow [[Changing Ethernet Device Names in EL7 and Fedora 15+|this tutorial]] for Fedora 15 and newer.}}

When you have two or more ethernet devices in one machine, the Fedora install may not install them in the order you want. This document will show you how to change the ethX to physical ethernet device mapping.

This is desirable in cases where specific network cards need to be used on specific networks, and you are interested in maintaining common ethX names across servers. A practical example is found in the [[2-Node Red Hat KVM Cluster Tutorial]].

= For the Impatient =

Assuming that NetworkManager is already removed. This example will swap eth0 and eth1.

<source lang="bash">
# Stop the network daemon
/etc/init.d/network stop
cd /etc/sysconfig/network-scripts
# Move your ifcfg files to the device names you desire
mv ifcfg-eth0 ifcfg-temp
mv ifcfg-eth1 ifcfg-eth0
mv ifcfg-temp ifcfg eth1
# Modify DEVICE lines to match new file names
vim /etc/sysconfig/network-scripts/ifcfg-eth*
# Make changes as needed
# Remove udev rules file
rm /etc/udev/rules.d/70-persistent-net.rules
start_udev
/etc/init.d/network start
</source>

Thanks for fenris02 and mutk

= Example =

I find it easier to follow instructions when I have an example to follow, so let me provide one here:

I've got the same hardware in the same configuration in both of my storage nodes. To keep things simple, I want to make sure that both nodes use the same ethX name for the network devices on each of the given networks.

== Desired Mapping ==

Let's assume that you want this:

* eth0
** MAC: 90:E6:BA:71:82:EA
* eth1
** MAC: 00:21:91:19:96:53
* eth2
** MAC: 00:0E:0C:59:46:E4

== Initial Mapping ==

When the Fedora install finished, you may have gotten this:

* eth0
** MAC: 00:21:91:19:96:53
* eth1
** MAC: 90:E6:BA:71:82:EA
* eth2
** MAC: 00:0E:0C:59:46:E4

== The Problem ==

In the above example, eth2 is where we want it, so we leave it alone. The problem is that eth0 and eth1 are reversed.

== The Fix ==

What we need to do is modify the DEVICE=... line in each ifcfg-ethX file to reflect the order we want.

To avoid confusion later on, we should also rename the files to reflect the new device names.

=== Stopping the Network ===

First, stop the network. This is important because if you change the MAC address mapping while the network is still up, the init.d script will fail to bring down the network devices and you will need to reboot for the changes to take effect.

<source lang="bash">
/etc/init.d/network stop
</source>

=== Interface Configuration ===

Go to the /etc/sysconfig/network-scripts/ directory and then use cat to see the contents of the ifcfg-eth* network configuration files:

<source lang="bash">
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
</source>
<source lang="text">
DEVICE="eth0"
HWADDR="00:21:91:19:96:53"
</source>
<source lang="bash">
cat ifcfg-eth1
</source>
<source lang="text">
DEVICE="eth1"
HWADDR="90:E6:BA:71:82:EA"
</source>
<source lang="bash">
cat ifcfg-eth2
</source>
<source lang="text">
DEVICE="eth2"
HWADDR="00:0E:0C:59:46:E4"
</source>

The important lines are the DEVICE=... and HWADDR=... lines. The rest of the lines will very likely differ from the output above. It is outside the scope of this tutorial to cover the various settings. For an exhaustive list of available options, please [http://docs.fedoraproject.org/en-US/Fedora/12/html/Deployment_Guide/s1-networkscripts-interfaces.html see the Fedora documentation].

First, change the file names to reflect the device order that you want. In this example we need to swap eth0 and eth1.

<source lang="bash">
cd /etc/sysconfig/network-scripts
mv ifcfg-eth0 ifcfg-temp
mv ifcfg-eth1 ifcfg-eth0
mv ifcfg-temp ifcfg-eth1
</source>

Using your editor of choice, open each file and change the DEVICE=... to match the new filename.

Here is the updated files with updated network settings:

<source lang="bash">
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
</source>
<source lang="text">
DEVICE="eth0"
HWADDR="90:E6:BA:71:82:EA"
</source>
<source lang="bash">
cat ifcfg-eth1
</source>
<source lang="text">
DEVICE="eth1"
HWADDR="00:21:91:19:96:53"
</source>
<source lang="bash">
cat ifcfg-eth2
</source>
<source lang="text">
DEVICE="eth2"
HWADDR="00:0E:0C:59:46:E4"
</source>

=== 'udev' Configuration ===

The user-space device manager, [http://en.wikipedia.org/wiki/Udev udev], maintains a list of configuration files that help ensure that hardware to /dev (software) mappings stay consistent, even when hardware is hot swapped or moved between physical connections. For networking hardware, this mapping is recorded in the 70-persistent-net.rules.

Here, all that needs to be done is for the NAME="..." entry to be changed to reflect what you want.

Note that the entries do not need to be in any particular order.

<source lang="bash">
cd /etc/udev/rules.d/
cat 70-persistent-net.rules
</source>
<source lang="text">
# 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:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:0c:59:46:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x1186:0x4b00 (sky2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:91:19:96:53", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="90:e6:ba:71:82:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
</source>

Make the changes and save the file. The file should now look like this:

<source lang="bash">
cat 70-persistent-net.rules
</source>
<source lang="text">
# 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 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="90:e6:ba:71:82:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x1186:0x4b00 (sky2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:91:19:96:53", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:0c:59:46:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
</source>

=== Making the Changes Take Effect ===

First, you need to reload udev so that it updates the mapping in memory. This is done using the start_udev program:

<source lang="bash">
start_udev
</source>
<source lang="text">
Starting udev: [ OK ]
</source>

With udev updated, the last step is to restart the network daemon:

<source lang="bash">
/etc/init.d/network start
</source>
<source lang="text">
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth1: [ OK ]
Bringing up interface eth2: [ OK ]
</source>

Done! use ifconfig to verify that the network cards are properly assigned to the specified ethX names.

== Caveat! ==

'''''NOTE''''': If you are using a vlan, the device facing the vlan '''can not''' have the '''HWADDR=...''' value set! Set the others and leave this commented out. Otherwise, because of how the vlan loads, the OS will not see the physical device and will fail to bring up the interface at all.

{{footer}}

Changing the ethX to Ethernet Device Mapping in EL6 and Fedora 12 to 14

2012-11-19T14:13:58Z

Rucus: /* Interface Configuration */

{{howto_header}}

{{note|1=This applies up to Fedora 14. Fedora 15 works quite differently now that it uses biosdevname. Please follow [[Changing Ethernet Device Names in EL7 and Fedora 15+|this tutorial]] for Fedora 15 and newer.}}

When you have two or more ethernet devices in one machine, the Fedora install may not install them in the order you want. This document will show you how to change the ethX to physical ethernet device mapping.

This is desirable in cases where specific network cards need to be used on specific networks, and you are interested in maintaining common ethX names across servers. A practical example is found in the [[2-Node Red Hat KVM Cluster Tutorial]].

= For the Impatient =

Assuming that NetworkManager is already removed. This example will swap eth0 and eth1.

<source lang="bash">
# Stop the network daemon
/etc/init.d/network stop
cd /etc/sysconfig/network-scripts
# Move your ifcfg files to the device names you desire
cp ifcfg-eth0 ifcfg-temp
cp ifcfg-eth1 ifcfg-eth0
cp ifcfg-temp ifcfg eth1
rm ifcfg-temp
# Modify DEVICE lines to match new file names
vim /etc/sysconfig/network-scripts/ifcfg-eth*
# Make changes as needed
# Remove udev rules file
rm /etc/udev/rules.d/70-persistent-net.rules
start_udev
/etc/init.d/network start
</source>

Thanks for fenris02 and mutk

= Example =

I find it easier to follow instructions when I have an example to follow, so let me provide one here:

I've got the same hardware in the same configuration in both of my storage nodes. To keep things simple, I want to make sure that both nodes use the same ethX name for the network devices on each of the given networks.

== Desired Mapping ==

Let's assume that you want this:

* eth0
** MAC: 90:E6:BA:71:82:EA
* eth1
** MAC: 00:21:91:19:96:53
* eth2
** MAC: 00:0E:0C:59:46:E4

== Initial Mapping ==

When the Fedora install finished, you may have gotten this:

* eth0
** MAC: 00:21:91:19:96:53
* eth1
** MAC: 90:E6:BA:71:82:EA
* eth2
** MAC: 00:0E:0C:59:46:E4

== The Problem ==

In the above example, eth2 is where we want it, so we leave it alone. The problem is that eth0 and eth1 are reversed.

== The Fix ==

What we need to do is modify the DEVICE=... line in each ifcfg-ethX file to reflect the order we want.

To avoid confusion later on, we should also rename the files to reflect the new device names.

=== Stopping the Network ===

First, stop the network. This is important because if you change the MAC address mapping while the network is still up, the init.d script will fail to bring down the network devices and you will need to reboot for the changes to take effect.

<source lang="bash">
/etc/init.d/network stop
</source>

=== Interface Configuration ===

Go to the /etc/sysconfig/network-scripts/ directory and then use cat to see the contents of the ifcfg-eth* network configuration files:

<source lang="bash">
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
</source>
<source lang="text">
DEVICE="eth0"
HWADDR="00:21:91:19:96:53"
</source>
<source lang="bash">
cat ifcfg-eth1
</source>
<source lang="text">
DEVICE="eth1"
HWADDR="90:E6:BA:71:82:EA"
</source>
<source lang="bash">
cat ifcfg-eth2
</source>
<source lang="text">
DEVICE="eth2"
HWADDR="00:0E:0C:59:46:E4"
</source>

The important lines are the DEVICE=... and HWADDR=... lines. The rest of the lines will very likely differ from the output above. It is outside the scope of this tutorial to cover the various settings. For an exhaustive list of available options, please [http://docs.fedoraproject.org/en-US/Fedora/12/html/Deployment_Guide/s1-networkscripts-interfaces.html see the Fedora documentation].

First, change the file names to reflect the device order that you want. In this example we need to swap eth0 and eth1.

<source lang="bash">
cd /etc/sysconfig/network-scripts
mv ifcfg-eth0 ifcfg-temp
mv ifcfg-eth1 ifcfg-eth0
mv ifcfg-temp ifcfg-eth1
</source>

Using your editor of choice, open each file and change the DEVICE=... to match the new filename.

Here is the updated files with updated network settings:

<source lang="bash">
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
</source>
<source lang="text">
DEVICE="eth0"
HWADDR="90:E6:BA:71:82:EA"
</source>
<source lang="bash">
cat ifcfg-eth1
</source>
<source lang="text">
DEVICE="eth1"
HWADDR="00:21:91:19:96:53"
</source>
<source lang="bash">
cat ifcfg-eth2
</source>
<source lang="text">
DEVICE="eth2"
HWADDR="00:0E:0C:59:46:E4"
</source>

=== 'udev' Configuration ===

The user-space device manager, [http://en.wikipedia.org/wiki/Udev udev], maintains a list of configuration files that help ensure that hardware to /dev (software) mappings stay consistent, even when hardware is hot swapped or moved between physical connections. For networking hardware, this mapping is recorded in the 70-persistent-net.rules.

Here, all that needs to be done is for the NAME="..." entry to be changed to reflect what you want.

Note that the entries do not need to be in any particular order.

<source lang="bash">
cd /etc/udev/rules.d/
cat 70-persistent-net.rules
</source>
<source lang="text">
# 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:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:0c:59:46:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x1186:0x4b00 (sky2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:91:19:96:53", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="90:e6:ba:71:82:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
</source>

Make the changes and save the file. The file should now look like this:

<source lang="bash">
cat 70-persistent-net.rules
</source>
<source lang="text">
# 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 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="90:e6:ba:71:82:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x1186:0x4b00 (sky2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:91:19:96:53", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:0c:59:46:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
</source>

=== Making the Changes Take Effect ===

First, you need to reload udev so that it updates the mapping in memory. This is done using the start_udev program:

<source lang="bash">
start_udev
</source>
<source lang="text">
Starting udev: [ OK ]
</source>

With udev updated, the last step is to restart the network daemon:

<source lang="bash">
/etc/init.d/network start
</source>
<source lang="text">
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth1: [ OK ]
Bringing up interface eth2: [ OK ]
</source>

Done! use ifconfig to verify that the network cards are properly assigned to the specified ethX names.

== Caveat! ==

'''''NOTE''''': If you are using a vlan, the device facing the vlan '''can not''' have the '''HWADDR=...''' value set! Set the others and leave this commented out. Otherwise, because of how the vlan loads, the OS will not see the physical device and will fail to bring up the interface at all.

{{footer}}

Changing the ethX to Ethernet Device Mapping in EL6 and Fedora 12 to 14

2012-11-19T14:09:43Z

Rucus: /* Interface Configuration */

{{howto_header}}

{{note|1=This applies up to Fedora 14. Fedora 15 works quite differently now that it uses biosdevname. Please follow [[Changing Ethernet Device Names in EL7 and Fedora 15+|this tutorial]] for Fedora 15 and newer.}}

When you have two or more ethernet devices in one machine, the Fedora install may not install them in the order you want. This document will show you how to change the ethX to physical ethernet device mapping.

This is desirable in cases where specific network cards need to be used on specific networks, and you are interested in maintaining common ethX names across servers. A practical example is found in the [[2-Node Red Hat KVM Cluster Tutorial]].

= For the Impatient =

Assuming that NetworkManager is already removed. This example will swap eth0 and eth1.

<source lang="bash">
# Stop the network daemon
/etc/init.d/network stop
cd /etc/sysconfig/network-scripts
# Move your ifcfg files to the device names you desire
cp ifcfg-eth0 ifcfg-temp
cp ifcfg-eth1 ifcfg-eth0
cp ifcfg-temp ifcfg eth1
rm ifcfg-temp
# Modify DEVICE lines to match new file names
vim /etc/sysconfig/network-scripts/ifcfg-eth*
# Make changes as needed
# Remove udev rules file
rm /etc/udev/rules.d/70-persistent-net.rules
start_udev
/etc/init.d/network start
</source>

Thanks for fenris02 and mutk

= Example =

I find it easier to follow instructions when I have an example to follow, so let me provide one here:

I've got the same hardware in the same configuration in both of my storage nodes. To keep things simple, I want to make sure that both nodes use the same ethX name for the network devices on each of the given networks.

== Desired Mapping ==

Let's assume that you want this:

* eth0
** MAC: 90:E6:BA:71:82:EA
* eth1
** MAC: 00:21:91:19:96:53
* eth2
** MAC: 00:0E:0C:59:46:E4

== Initial Mapping ==

When the Fedora install finished, you may have gotten this:

* eth0
** MAC: 00:21:91:19:96:53
* eth1
** MAC: 90:E6:BA:71:82:EA
* eth2
** MAC: 00:0E:0C:59:46:E4

== The Problem ==

In the above example, eth2 is where we want it, so we leave it alone. The problem is that eth0 and eth1 are reversed.

== The Fix ==

What we need to do is modify the DEVICE=... line in each ifcfg-ethX file to reflect the order we want.

To avoid confusion later on, we should also rename the files to reflect the new device names.

=== Stopping the Network ===

First, stop the network. This is important because if you change the MAC address mapping while the network is still up, the init.d script will fail to bring down the network devices and you will need to reboot for the changes to take effect.

<source lang="bash">
/etc/init.d/network stop
</source>

=== Interface Configuration ===

Go to the /etc/sysconfig/network-scripts/ directory and then use cat to see the contents of the ifcfg-eth* network configuration files:

<source lang="bash">
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
</source>
<source lang="text">
DEVICE="eth0"
HWADDR="00:21:91:19:96:53"
ONBOOT="yes"
</source>
<source lang="bash">
cat ifcfg-eth1
</source>
<source lang="text">
DEVICE="eth1"
HWADDR="90:E6:BA:71:82:EA"
ONBOOT="yes"
</source>
<source lang="bash">
cat ifcfg-eth2
</source>
<source lang="text">
DEVICE="eth2"
HWADDR="00:0E:0C:59:46:E4"
ONBOOT="no"
</source>

The important lines are the DEVICE=... and HWADDR=... lines. The rest of the lines will very likely differ from the output above. It is outside the scope of this tutorial to cover the various settings. For an exhaustive list of available options, please [http://docs.fedoraproject.org/en-US/Fedora/12/html/Deployment_Guide/s1-networkscripts-interfaces.html see the Fedora documentation].

First, change the file names to reflect the device order that you want. In this example we need to swap eth0 and eth1.

<source lang="bash">
cd /etc/sysconfig/network-scripts
mv ifcfg-eth0 ifcfg-temp
mv ifcfg-eth1 ifcfg-eth0
mv ifcfg-temp ifcfg-eth1
</source>

Using your editor of choice, open each file and change the DEVICE=... to match the new filename.

Here is the updated files with updated network settings:

<source lang="bash">
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
</source>
<source lang="text">
DEVICE="eth0"
HWADDR="90:E6:BA:71:82:EA"
ONBOOT="yes"
</source>
<source lang="bash">
cat ifcfg-eth1
</source>
<source lang="text">
DEVICE="eth1"
HWADDR="00:21:91:19:96:53"
ONBOOT="yes"
</source>
<source lang="bash">
cat ifcfg-eth2
</source>
<source lang="text">
DEVICE="eth2"
HWADDR="00:0E:0C:59:46:E4"
ONBOOT="yes"
</source>

=== 'udev' Configuration ===

The user-space device manager, [http://en.wikipedia.org/wiki/Udev udev], maintains a list of configuration files that help ensure that hardware to /dev (software) mappings stay consistent, even when hardware is hot swapped or moved between physical connections. For networking hardware, this mapping is recorded in the 70-persistent-net.rules.

Here, all that needs to be done is for the NAME="..." entry to be changed to reflect what you want.

Note that the entries do not need to be in any particular order.

<source lang="bash">
cd /etc/udev/rules.d/
cat 70-persistent-net.rules
</source>
<source lang="text">
# 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:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:0c:59:46:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x1186:0x4b00 (sky2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:91:19:96:53", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="90:e6:ba:71:82:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
</source>

Make the changes and save the file. The file should now look like this:

<source lang="bash">
cat 70-persistent-net.rules
</source>
<source lang="text">
# 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 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="90:e6:ba:71:82:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x1186:0x4b00 (sky2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:91:19:96:53", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:0c:59:46:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
</source>

=== Making the Changes Take Effect ===

First, you need to reload udev so that it updates the mapping in memory. This is done using the start_udev program:

<source lang="bash">
start_udev
</source>
<source lang="text">
Starting udev: [ OK ]
</source>

With udev updated, the last step is to restart the network daemon:

<source lang="bash">
/etc/init.d/network start
</source>
<source lang="text">
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth1: [ OK ]
Bringing up interface eth2: [ OK ]
</source>

Done! use ifconfig to verify that the network cards are properly assigned to the specified ethX names.

== Caveat! ==

'''''NOTE''''': If you are using a vlan, the device facing the vlan '''can not''' have the '''HWADDR=...''' value set! Set the others and leave this commented out. Otherwise, because of how the vlan loads, the OS will not see the physical device and will fail to bring up the interface at all.

{{footer}}

Changing the ethX to Ethernet Device Mapping in EL6 and Fedora 12 to 14

2012-11-19T14:07:37Z

Rucus: /* Interface Configuration */

{{howto_header}}

{{note|1=This applies up to Fedora 14. Fedora 15 works quite differently now that it uses biosdevname. Please follow [[Changing Ethernet Device Names in EL7 and Fedora 15+|this tutorial]] for Fedora 15 and newer.}}

When you have two or more ethernet devices in one machine, the Fedora install may not install them in the order you want. This document will show you how to change the ethX to physical ethernet device mapping.

This is desirable in cases where specific network cards need to be used on specific networks, and you are interested in maintaining common ethX names across servers. A practical example is found in the [[2-Node Red Hat KVM Cluster Tutorial]].

= For the Impatient =

Assuming that NetworkManager is already removed. This example will swap eth0 and eth1.

<source lang="bash">
# Stop the network daemon
/etc/init.d/network stop
cd /etc/sysconfig/network-scripts
# Move your ifcfg files to the device names you desire
cp ifcfg-eth0 ifcfg-temp
cp ifcfg-eth1 ifcfg-eth0
cp ifcfg-temp ifcfg eth1
rm ifcfg-temp
# Modify DEVICE lines to match new file names
vim /etc/sysconfig/network-scripts/ifcfg-eth*
# Make changes as needed
# Remove udev rules file
rm /etc/udev/rules.d/70-persistent-net.rules
start_udev
/etc/init.d/network start
</source>

Thanks for fenris02 and mutk

= Example =

I find it easier to follow instructions when I have an example to follow, so let me provide one here:

I've got the same hardware in the same configuration in both of my storage nodes. To keep things simple, I want to make sure that both nodes use the same ethX name for the network devices on each of the given networks.

== Desired Mapping ==

Let's assume that you want this:

* eth0
** MAC: 90:E6:BA:71:82:EA
* eth1
** MAC: 00:21:91:19:96:53
* eth2
** MAC: 00:0E:0C:59:46:E4

== Initial Mapping ==

When the Fedora install finished, you may have gotten this:

* eth0
** MAC: 00:21:91:19:96:53
* eth1
** MAC: 90:E6:BA:71:82:EA
* eth2
** MAC: 00:0E:0C:59:46:E4

== The Problem ==

In the above example, eth2 is where we want it, so we leave it alone. The problem is that eth0 and eth1 are reversed.

== The Fix ==

What we need to do is modify the DEVICE=... line in each ifcfg-ethX file to reflect the order we want.

To avoid confusion later on, we should also rename the files to reflect the new device names.

=== Stopping the Network ===

First, stop the network. This is important because if you change the MAC address mapping while the network is still up, the init.d script will fail to bring down the network devices and you will need to reboot for the changes to take effect.

<source lang="bash">
/etc/init.d/network stop
</source>

=== Interface Configuration ===

Go to the /etc/sysconfig/network-scripts/ directory and then use cat to see the contents of the ifcfg-eth* network configuration files:

<source lang="bash">
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
</source>
<source lang="text">
DEVICE="eth0"
HWADDR="00:21:91:19:96:53"
ONBOOT="yes"
</source>
<source lang="bash">
cat ifcfg-eth1
</source>
<source lang="text">
DEVICE="eth1"
HWADDR="90:E6:BA:71:82:EA"
ONBOOT="yes"
</source>
<source lang="bash">
cat ifcfg-eth2
</source>
<source lang="text">
DEVICE="eth2"
HWADDR="00:0E:0C:59:46:E4"
ONBOOT="no"
</source>

The important lines are the DEVICE=... and HWADDR=... lines. The rest of the lines will very likely differ from the output above. It is outside the scope of this tutorial to cover the various settings. For an exhaustive list of available options, please [http://docs.fedoraproject.org/en-US/Fedora/12/html/Deployment_Guide/s1-networkscripts-interfaces.html see the Fedora documentation].

First, change the file names to reflect the device order that you want. In this example we need to swap eth0 and eth1.

Here is the updated files with updated network settings:

<source lang="bash">
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
</source>
<source lang="text">
DEVICE="eth0"
HWADDR="90:E6:BA:71:82:EA"
ONBOOT="yes"
</source>
<source lang="bash">
cat ifcfg-eth1
</source>
<source lang="text">
DEVICE="eth1"
HWADDR="00:21:91:19:96:53"
ONBOOT="yes"
</source>
<source lang="bash">
cat ifcfg-eth2
</source>
<source lang="text">
DEVICE="eth2"
HWADDR="00:0E:0C:59:46:E4"
ONBOOT="yes"
</source>

=== 'udev' Configuration ===

The user-space device manager, [http://en.wikipedia.org/wiki/Udev udev], maintains a list of configuration files that help ensure that hardware to /dev (software) mappings stay consistent, even when hardware is hot swapped or moved between physical connections. For networking hardware, this mapping is recorded in the 70-persistent-net.rules.

Here, all that needs to be done is for the NAME="..." entry to be changed to reflect what you want.

Note that the entries do not need to be in any particular order.

<source lang="bash">
cd /etc/udev/rules.d/
cat 70-persistent-net.rules
</source>
<source lang="text">
# 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:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:0c:59:46:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x1186:0x4b00 (sky2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:91:19:96:53", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="90:e6:ba:71:82:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
</source>

Make the changes and save the file. The file should now look like this:

<source lang="bash">
cat 70-persistent-net.rules
</source>
<source lang="text">
# 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 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="90:e6:ba:71:82:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x1186:0x4b00 (sky2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:91:19:96:53", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:0c:59:46:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
</source>

=== Making the Changes Take Effect ===

First, you need to reload udev so that it updates the mapping in memory. This is done using the start_udev program:

<source lang="bash">
start_udev
</source>
<source lang="text">
Starting udev: [ OK ]
</source>

With udev updated, the last step is to restart the network daemon:

<source lang="bash">
/etc/init.d/network start
</source>
<source lang="text">
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth1: [ OK ]
Bringing up interface eth2: [ OK ]
</source>

Done! use ifconfig to verify that the network cards are properly assigned to the specified ethX names.

== Caveat! ==

'''''NOTE''''': If you are using a vlan, the device facing the vlan '''can not''' have the '''HWADDR=...''' value set! Set the others and leave this commented out. Otherwise, because of how the vlan loads, the OS will not see the physical device and will fail to bring up the interface at all.

{{footer}}

Changing the ethX to Ethernet Device Mapping in EL6 and Fedora 12 to 14

2012-11-19T13:58:06Z

Rucus: /* The Fix */

{{howto_header}}

{{note|1=This applies up to Fedora 14. Fedora 15 works quite differently now that it uses biosdevname. Please follow [[Changing Ethernet Device Names in EL7 and Fedora 15+|this tutorial]] for Fedora 15 and newer.}}

When you have two or more ethernet devices in one machine, the Fedora install may not install them in the order you want. This document will show you how to change the ethX to physical ethernet device mapping.

This is desirable in cases where specific network cards need to be used on specific networks, and you are interested in maintaining common ethX names across servers. A practical example is found in the [[2-Node Red Hat KVM Cluster Tutorial]].

= For the Impatient =

Assuming that NetworkManager is already removed. This example will swap eth0 and eth1.

<source lang="bash">
# Stop the network daemon
/etc/init.d/network stop
cd /etc/sysconfig/network-scripts
# Move your ifcfg files to the device names you desire
cp ifcfg-eth0 ifcfg-temp
cp ifcfg-eth1 ifcfg-eth0
cp ifcfg-temp ifcfg eth1
rm ifcfg-temp
# Modify DEVICE lines to match new file names
vim /etc/sysconfig/network-scripts/ifcfg-eth*
# Make changes as needed
# Remove udev rules file
rm /etc/udev/rules.d/70-persistent-net.rules
start_udev
/etc/init.d/network start
</source>

Thanks for fenris02 and mutk

= Example =

I find it easier to follow instructions when I have an example to follow, so let me provide one here:

I've got the same hardware in the same configuration in both of my storage nodes. To keep things simple, I want to make sure that both nodes use the same ethX name for the network devices on each of the given networks.

== Desired Mapping ==

Let's assume that you want this:

* eth0
** MAC: 90:E6:BA:71:82:EA
* eth1
** MAC: 00:21:91:19:96:53
* eth2
** MAC: 00:0E:0C:59:46:E4

== Initial Mapping ==

When the Fedora install finished, you may have gotten this:

* eth0
** MAC: 00:21:91:19:96:53
* eth1
** MAC: 90:E6:BA:71:82:EA
* eth2
** MAC: 00:0E:0C:59:46:E4

== The Problem ==

In the above example, eth2 is where we want it, so we leave it alone. The problem is that eth0 and eth1 are reversed.

== The Fix ==

What we need to do is modify the DEVICE=... line in each ifcfg-ethX file to reflect the order we want.

To avoid confusion later on, we should also rename the files to reflect the new device names.

=== Stopping the Network ===

First, stop the network. This is important because if you change the MAC address mapping while the network is still up, the init.d script will fail to bring down the network devices and you will need to reboot for the changes to take effect.

<source lang="bash">
/etc/init.d/network stop
</source>

=== Interface Configuration ===

Go to the /etc/sysconfig/network-scripts/ directory and then use cat to see the contents of the ifcfg-eth* network configuration files:

<source lang="bash">
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
</source>
<source lang="text">
DEVICE="eth0"
HWADDR="00:21:91:19:96:53"
ONBOOT="yes"
</source>
<source lang="bash">
cat ifcfg-eth1
</source>
<source lang="text">
DEVICE="eth1"
DEFROUTE="yes"
HWADDR="90:E6:BA:71:82:EA"
ONBOOT="yes"
</source>
<source lang="bash">
cat ifcfg-eth2
</source>
<source lang="text">
DEVICE="eth2"
HWADDR="00:0E:0C:59:46:E4"
ONBOOT="no"
</source>

The important lines are the DEVICE=... and HWADDR=... lines. The rest of the lines will very likely differ from the output above, and most will likely be set to BOOTPROTO=static. One or more may also be set to ONBOOT=yes. It is outside the scope of this tutorial to cover the various settings

For an exhaustive list of available options, please [http://docs.fedoraproject.org/en-US/Fedora/12/html/Deployment_Guide/s1-networkscripts-interfaces.html see the Fedora documentation].

With networking stopped, all we need to do is remove the HWADDR=... lines. '''Personally''', I like to keep the network card name and the HWADDR=... entries in my files, but comment them out. If you wish to do the same, move them to the appropriate file. Further, I use this time to further configure each interface to the values I want. Do whatever is right for you.

Here is the updated files with updated network settings:

<source lang="bash">
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
</source>
<source lang="text">
# Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
#HWADDR=90:E6:BA:71:82:EA
DEVICE=eth0
BOOTPROTO=static
ONBOOT=yes
TYPE=Ethernet
IPADDR=192.168.1.71
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
DNS1=192.139.81.117
DNS2=192.139.81.1
DEFROUTE=yes
</source>
<source lang="bash">
cat ifcfg-eth1
</source>
<source lang="text">
# D-Link System Inc DGE-560T PCI Express Gigabit Ethernet Adapter
#HWADDR=00:21:91:19:96:53
DEVICE=eth1
BOOTPROTO=static
ONBOOT=yes
TYPE=Ethernet
IPADDR=10.0.0.71
NETMASK=255.255.255.0
</source>
<source lang="bash">
cat ifcfg-eth2
</source>
<source lang="text">
# Intel Corporation 82540EM Gigabit Ethernet Controller
#HWADDR=00:0E:0C:59:46:E4
DEVICE=eth2
ONBOOT=yes
BOOTPROTO=static
TYPE=Ethernet
IPADDR=10.0.1.71
NETMASK=255.255.255.0
</source>

=== 'udev' Configuration ===

The user-space device manager, [http://en.wikipedia.org/wiki/Udev udev], maintains a list of configuration files that help ensure that hardware to /dev (software) mappings stay consistent, even when hardware is hot swapped or moved between physical connections. For networking hardware, this mapping is recorded in the 70-persistent-net.rules.

Here, all that needs to be done is for the NAME="..." entry to be changed to reflect what you want.

Note that the entries do not need to be in any particular order.

<source lang="bash">
cd /etc/udev/rules.d/
cat 70-persistent-net.rules
</source>
<source lang="text">
# 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:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:0c:59:46:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x1186:0x4b00 (sky2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:91:19:96:53", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="90:e6:ba:71:82:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
</source>

Make the changes and save the file. The file should now look like this:

<source lang="bash">
cat 70-persistent-net.rules
</source>
<source lang="text">
# 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 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="90:e6:ba:71:82:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x1186:0x4b00 (sky2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:91:19:96:53", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:0c:59:46:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
</source>

=== Making the Changes Take Effect ===

First, you need to reload udev so that it updates the mapping in memory. This is done using the start_udev program:

<source lang="bash">
start_udev
</source>
<source lang="text">
Starting udev: [ OK ]
</source>

With udev updated, the last step is to restart the network daemon:

<source lang="bash">
/etc/init.d/network start
</source>
<source lang="text">
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth1: [ OK ]
Bringing up interface eth2: [ OK ]
</source>

Done! use ifconfig to verify that the network cards are properly assigned to the specified ethX names.

== Caveat! ==

'''''NOTE''''': If you are using a vlan, the device facing the vlan '''can not''' have the '''HWADDR=...''' value set! Set the others and leave this commented out. Otherwise, because of how the vlan loads, the OS will not see the physical device and will fail to bring up the interface at all.

{{footer}}

Changing the ethX to Ethernet Device Mapping in EL6 and Fedora 12 to 14

2012-11-19T13:48:56Z

Rucus: /* Initial Mapping */

{{howto_header}}

{{note|1=This applies up to Fedora 14. Fedora 15 works quite differently now that it uses biosdevname. Please follow [[Changing Ethernet Device Names in EL7 and Fedora 15+|this tutorial]] for Fedora 15 and newer.}}

When you have two or more ethernet devices in one machine, the Fedora install may not install them in the order you want. This document will show you how to change the ethX to physical ethernet device mapping.

This is desirable in cases where specific network cards need to be used on specific networks, and you are interested in maintaining common ethX names across servers. A practical example is found in the [[2-Node Red Hat KVM Cluster Tutorial]].

= For the Impatient =

Assuming that NetworkManager is already removed. This example will swap eth0 and eth1.

<source lang="bash">
# Stop the network daemon
/etc/init.d/network stop
cd /etc/sysconfig/network-scripts
# Move your ifcfg files to the device names you desire
cp ifcfg-eth0 ifcfg-temp
cp ifcfg-eth1 ifcfg-eth0
cp ifcfg-temp ifcfg eth1
rm ifcfg-temp
# Modify DEVICE lines to match new file names
vim /etc/sysconfig/network-scripts/ifcfg-eth*
# Make changes as needed
# Remove udev rules file
rm /etc/udev/rules.d/70-persistent-net.rules
start_udev
/etc/init.d/network start
</source>

Thanks for fenris02 and mutk

= Example =

I find it easier to follow instructions when I have an example to follow, so let me provide one here:

I've got the same hardware in the same configuration in both of my storage nodes. To keep things simple, I want to make sure that both nodes use the same ethX name for the network devices on each of the given networks.

== Desired Mapping ==

Let's assume that you want this:

* eth0
** MAC: 90:E6:BA:71:82:EA
* eth1
** MAC: 00:21:91:19:96:53
* eth2
** MAC: 00:0E:0C:59:46:E4

== Initial Mapping ==

When the Fedora install finished, you may have gotten this:

* eth0
** MAC: 00:21:91:19:96:53
* eth1
** MAC: 90:E6:BA:71:82:EA
* eth2
** MAC: 00:0E:0C:59:46:E4

== The Problem ==

In the above example, eth2 is where we want it, so we leave it alone. The problem is that eth0 and eth1 are reversed.

== The Fix ==

Traditionally, the ethX to physical ethernet device was linked via the HWADDR=... argument in each NIC's ifcfg-ethX configuration file. With the introduction of [http://en.wikipedia.org/wiki/Udev udev], the HWADDR=... is no longer needed. Instead, this mapping is now made in the 70-persistent-net.rules udev configuration file.

So the trick then is to remove or comment-out the HWADDR=... argument in each NIC's ifcfg-ethX configuration file, then, change the NAME="ethX" in the udev configuration file to match the MAC address you want.

=== Stopping the Network ===

First, stop the network. This is important because if you change the MAC address to ethX mapping while the network is still up, the init.d script will fail to bring down the network devices and you will need to reboot for the changes to take effect.

<source lang="bash">
/etc/init.d/network stop
</source>

=== Interface Configuration ===

Go to the /etc/sysconfig/network-scripts/ directory and then use cat to see the contents of the ifcfg-eth* network configuration files:

<source lang="bash">
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
</source>
<source lang="text">
# D-Link System Inc DGE-560T PCI Express Gigabit Ethernet Adapter
DEVICE=eth0
BOOTPROTO=dhcp
DHCPCLASS=
HWADDR=00:21:91:19:96:53
ONBOOT=yes
DHCP_HOSTNAME=an-node01.alteeve.com
</source>
<source lang="bash">
cat ifcfg-eth1
</source>
<source lang="text">
# Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
DEVICE=eth1
BOOTPROTO=dhcp
DEFROUTE=yes
HWADDR=90:E6:BA:71:82:EA
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
ONBOOT=yes
OPTIONS=layer2=1
PEERDNS=yes
PEERROUTES=yes
TYPE=Ethernet
UUID=9c92fad9-6ecb-3e6c-eb4d-8a47c6f50c04
DHCP_HOSTNAME=an-node01.alteeve.com
</source>
<source lang="bash">
cat ifcfg-eth2
</source>
<source lang="text">
# Intel Corporation 82540EM Gigabit Ethernet Controller
DEVICE=eth2
HWADDR=00:0E:0C:59:46:E4
ONBOOT=no
</source>

The important lines are the DEVICE=... and HWADDR=... lines. The rest of the lines will very likely differ from the output above, and most will likely be set to BOOTPROTO=static. One or more may also be set to ONBOOT=yes. It is outside the scope of this tutorial to cover the various settings

For an exhaustive list of available options, please [http://docs.fedoraproject.org/en-US/Fedora/12/html/Deployment_Guide/s1-networkscripts-interfaces.html see the Fedora documentation].

With networking stopped, all we need to do is remove the HWADDR=... lines. '''Personally''', I like to keep the network card name and the HWADDR=... entries in my files, but comment them out. If you wish to do the same, move them to the appropriate file. Further, I use this time to further configure each interface to the values I want. Do whatever is right for you.

Here is the updated files with updated network settings:

<source lang="bash">
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
</source>
<source lang="text">
# Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
#HWADDR=90:E6:BA:71:82:EA
DEVICE=eth0
BOOTPROTO=static
ONBOOT=yes
TYPE=Ethernet
IPADDR=192.168.1.71
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
DNS1=192.139.81.117
DNS2=192.139.81.1
DEFROUTE=yes
</source>
<source lang="bash">
cat ifcfg-eth1
</source>
<source lang="text">
# D-Link System Inc DGE-560T PCI Express Gigabit Ethernet Adapter
#HWADDR=00:21:91:19:96:53
DEVICE=eth1
BOOTPROTO=static
ONBOOT=yes
TYPE=Ethernet
IPADDR=10.0.0.71
NETMASK=255.255.255.0
</source>
<source lang="bash">
cat ifcfg-eth2
</source>
<source lang="text">
# Intel Corporation 82540EM Gigabit Ethernet Controller
#HWADDR=00:0E:0C:59:46:E4
DEVICE=eth2
ONBOOT=yes
BOOTPROTO=static
TYPE=Ethernet
IPADDR=10.0.1.71
NETMASK=255.255.255.0
</source>

=== 'udev' Configuration ===

The user-space device manager, [http://en.wikipedia.org/wiki/Udev udev], maintains a list of configuration files that help ensure that hardware to /dev (software) mappings stay consistent, even when hardware is hot swapped or moved between physical connections. For networking hardware, this mapping is recorded in the 70-persistent-net.rules.

Here, all that needs to be done is for the NAME="..." entry to be changed to reflect what you want.

Note that the entries do not need to be in any particular order.

<source lang="bash">
cd /etc/udev/rules.d/
cat 70-persistent-net.rules
</source>
<source lang="text">
# 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:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:0c:59:46:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x1186:0x4b00 (sky2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:91:19:96:53", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="90:e6:ba:71:82:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
</source>

Make the changes and save the file. The file should now look like this:

<source lang="bash">
cat 70-persistent-net.rules
</source>
<source lang="text">
# 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 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="90:e6:ba:71:82:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x1186:0x4b00 (sky2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:91:19:96:53", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:0c:59:46:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
</source>

=== Making the Changes Take Effect ===

First, you need to reload udev so that it updates the mapping in memory. This is done using the start_udev program:

<source lang="bash">
start_udev
</source>
<source lang="text">
Starting udev: [ OK ]
</source>

With udev updated, the last step is to restart the network daemon:

<source lang="bash">
/etc/init.d/network start
</source>
<source lang="text">
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth1: [ OK ]
Bringing up interface eth2: [ OK ]
</source>

Done! use ifconfig to verify that the network cards are properly assigned to the specified ethX names.

== Caveat! ==

'''''NOTE''''': If you are using a vlan, the device facing the vlan '''can not''' have the '''HWADDR=...''' value set! Set the others and leave this commented out. Otherwise, because of how the vlan loads, the OS will not see the physical device and will fail to bring up the interface at all.

{{footer}}

Changing the ethX to Ethernet Device Mapping in EL6 and Fedora 12 to 14

2012-11-19T13:47:43Z

Rucus: /* Desired Mapping */

{{howto_header}}

{{note|1=This applies up to Fedora 14. Fedora 15 works quite differently now that it uses biosdevname. Please follow [[Changing Ethernet Device Names in EL7 and Fedora 15+|this tutorial]] for Fedora 15 and newer.}}

When you have two or more ethernet devices in one machine, the Fedora install may not install them in the order you want. This document will show you how to change the ethX to physical ethernet device mapping.

This is desirable in cases where specific network cards need to be used on specific networks, and you are interested in maintaining common ethX names across servers. A practical example is found in the [[2-Node Red Hat KVM Cluster Tutorial]].

= For the Impatient =

Assuming that NetworkManager is already removed. This example will swap eth0 and eth1.

<source lang="bash">
# Stop the network daemon
/etc/init.d/network stop
cd /etc/sysconfig/network-scripts
# Move your ifcfg files to the device names you desire
cp ifcfg-eth0 ifcfg-temp
cp ifcfg-eth1 ifcfg-eth0
cp ifcfg-temp ifcfg eth1
rm ifcfg-temp
# Modify DEVICE lines to match new file names
vim /etc/sysconfig/network-scripts/ifcfg-eth*
# Make changes as needed
# Remove udev rules file
rm /etc/udev/rules.d/70-persistent-net.rules
start_udev
/etc/init.d/network start
</source>

Thanks for fenris02 and mutk

= Example =

I find it easier to follow instructions when I have an example to follow, so let me provide one here:

I've got the same hardware in the same configuration in both of my storage nodes. To keep things simple, I want to make sure that both nodes use the same ethX name for the network devices on each of the given networks.

== Desired Mapping ==

Let's assume that you want this:

* eth0
** MAC: 90:E6:BA:71:82:EA
* eth1
** MAC: 00:21:91:19:96:53
* eth2
** MAC: 00:0E:0C:59:46:E4

== Initial Mapping ==

When the Fedora install finished, you may have gotten this:

* eth0
** Type: # D-Link System Inc DGE-560T PCI Express Gigabit Ethernet Adapter
** MAC: 00:21:91:19:96:53
* eth1
** Type: # Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
** MAC: 90:E6:BA:71:82:EA
* eth2
** Type: # Intel Corporation 82540EM Gigabit Ethernet Controller
** MAC: 00:0E:0C:59:46:E4

== The Problem ==

In the above example, eth2 is where we want it, so we leave it alone. The problem is that eth0 and eth1 are reversed.

== The Fix ==

Traditionally, the ethX to physical ethernet device was linked via the HWADDR=... argument in each NIC's ifcfg-ethX configuration file. With the introduction of [http://en.wikipedia.org/wiki/Udev udev], the HWADDR=... is no longer needed. Instead, this mapping is now made in the 70-persistent-net.rules udev configuration file.

So the trick then is to remove or comment-out the HWADDR=... argument in each NIC's ifcfg-ethX configuration file, then, change the NAME="ethX" in the udev configuration file to match the MAC address you want.

=== Stopping the Network ===

First, stop the network. This is important because if you change the MAC address to ethX mapping while the network is still up, the init.d script will fail to bring down the network devices and you will need to reboot for the changes to take effect.

<source lang="bash">
/etc/init.d/network stop
</source>

=== Interface Configuration ===

Go to the /etc/sysconfig/network-scripts/ directory and then use cat to see the contents of the ifcfg-eth* network configuration files:

<source lang="bash">
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
</source>
<source lang="text">
# D-Link System Inc DGE-560T PCI Express Gigabit Ethernet Adapter
DEVICE=eth0
BOOTPROTO=dhcp
DHCPCLASS=
HWADDR=00:21:91:19:96:53
ONBOOT=yes
DHCP_HOSTNAME=an-node01.alteeve.com
</source>
<source lang="bash">
cat ifcfg-eth1
</source>
<source lang="text">
# Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
DEVICE=eth1
BOOTPROTO=dhcp
DEFROUTE=yes
HWADDR=90:E6:BA:71:82:EA
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
ONBOOT=yes
OPTIONS=layer2=1
PEERDNS=yes
PEERROUTES=yes
TYPE=Ethernet
UUID=9c92fad9-6ecb-3e6c-eb4d-8a47c6f50c04
DHCP_HOSTNAME=an-node01.alteeve.com
</source>
<source lang="bash">
cat ifcfg-eth2
</source>
<source lang="text">
# Intel Corporation 82540EM Gigabit Ethernet Controller
DEVICE=eth2
HWADDR=00:0E:0C:59:46:E4
ONBOOT=no
</source>

The important lines are the DEVICE=... and HWADDR=... lines. The rest of the lines will very likely differ from the output above, and most will likely be set to BOOTPROTO=static. One or more may also be set to ONBOOT=yes. It is outside the scope of this tutorial to cover the various settings

For an exhaustive list of available options, please [http://docs.fedoraproject.org/en-US/Fedora/12/html/Deployment_Guide/s1-networkscripts-interfaces.html see the Fedora documentation].

With networking stopped, all we need to do is remove the HWADDR=... lines. '''Personally''', I like to keep the network card name and the HWADDR=... entries in my files, but comment them out. If you wish to do the same, move them to the appropriate file. Further, I use this time to further configure each interface to the values I want. Do whatever is right for you.

Here is the updated files with updated network settings:

<source lang="bash">
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
</source>
<source lang="text">
# Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
#HWADDR=90:E6:BA:71:82:EA
DEVICE=eth0
BOOTPROTO=static
ONBOOT=yes
TYPE=Ethernet
IPADDR=192.168.1.71
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
DNS1=192.139.81.117
DNS2=192.139.81.1
DEFROUTE=yes
</source>
<source lang="bash">
cat ifcfg-eth1
</source>
<source lang="text">
# D-Link System Inc DGE-560T PCI Express Gigabit Ethernet Adapter
#HWADDR=00:21:91:19:96:53
DEVICE=eth1
BOOTPROTO=static
ONBOOT=yes
TYPE=Ethernet
IPADDR=10.0.0.71
NETMASK=255.255.255.0
</source>
<source lang="bash">
cat ifcfg-eth2
</source>
<source lang="text">
# Intel Corporation 82540EM Gigabit Ethernet Controller
#HWADDR=00:0E:0C:59:46:E4
DEVICE=eth2
ONBOOT=yes
BOOTPROTO=static
TYPE=Ethernet
IPADDR=10.0.1.71
NETMASK=255.255.255.0
</source>

=== 'udev' Configuration ===

The user-space device manager, [http://en.wikipedia.org/wiki/Udev udev], maintains a list of configuration files that help ensure that hardware to /dev (software) mappings stay consistent, even when hardware is hot swapped or moved between physical connections. For networking hardware, this mapping is recorded in the 70-persistent-net.rules.

Here, all that needs to be done is for the NAME="..." entry to be changed to reflect what you want.

Note that the entries do not need to be in any particular order.

<source lang="bash">
cd /etc/udev/rules.d/
cat 70-persistent-net.rules
</source>
<source lang="text">
# 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:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:0c:59:46:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x1186:0x4b00 (sky2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:91:19:96:53", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="90:e6:ba:71:82:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
</source>

Make the changes and save the file. The file should now look like this:

<source lang="bash">
cat 70-persistent-net.rules
</source>
<source lang="text">
# 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 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="90:e6:ba:71:82:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x1186:0x4b00 (sky2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:91:19:96:53", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:0c:59:46:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
</source>

=== Making the Changes Take Effect ===

First, you need to reload udev so that it updates the mapping in memory. This is done using the start_udev program:

<source lang="bash">
start_udev
</source>
<source lang="text">
Starting udev: [ OK ]
</source>

With udev updated, the last step is to restart the network daemon:

<source lang="bash">
/etc/init.d/network start
</source>
<source lang="text">
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth1: [ OK ]
Bringing up interface eth2: [ OK ]
</source>

Done! use ifconfig to verify that the network cards are properly assigned to the specified ethX names.

== Caveat! ==

'''''NOTE''''': If you are using a vlan, the device facing the vlan '''can not''' have the '''HWADDR=...''' value set! Set the others and leave this commented out. Otherwise, because of how the vlan loads, the OS will not see the physical device and will fail to bring up the interface at all.

{{footer}}

Changing the ethX to Ethernet Device Mapping in EL6 and Fedora 12 to 14

2012-11-19T13:43:46Z

Rucus: /* For the Impatient */

{{howto_header}}

{{note|1=This applies up to Fedora 14. Fedora 15 works quite differently now that it uses biosdevname. Please follow [[Changing Ethernet Device Names in EL7 and Fedora 15+|this tutorial]] for Fedora 15 and newer.}}

When you have two or more ethernet devices in one machine, the Fedora install may not install them in the order you want. This document will show you how to change the ethX to physical ethernet device mapping.

This is desirable in cases where specific network cards need to be used on specific networks, and you are interested in maintaining common ethX names across servers. A practical example is found in the [[2-Node Red Hat KVM Cluster Tutorial]].

= For the Impatient =

Assuming that NetworkManager is already removed. This example will swap eth0 and eth1.

<source lang="bash">
# Stop the network daemon
/etc/init.d/network stop
cd /etc/sysconfig/network-scripts
# Move your ifcfg files to the device names you desire
cp ifcfg-eth0 ifcfg-temp
cp ifcfg-eth1 ifcfg-eth0
cp ifcfg-temp ifcfg eth1
rm ifcfg-temp
# Modify DEVICE lines to match new file names
vim /etc/sysconfig/network-scripts/ifcfg-eth*
# Make changes as needed
# Remove udev rules file
rm /etc/udev/rules.d/70-persistent-net.rules
start_udev
/etc/init.d/network start
</source>

Thanks for fenris02 and mutk

= Example =

I find it easier to follow instructions when I have an example to follow, so let me provide one here:

I've got the same hardware in the same configuration in both of my storage nodes. To keep things simple, I want to make sure that both nodes use the same ethX name for the network devices on each of the given networks.

== Desired Mapping ==

Let's assume that you want this:

* eth0
** Type: # Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
** MAC: 90:E6:BA:71:82:EA
* eth1
** Type: # D-Link System Inc DGE-560T PCI Express Gigabit Ethernet Adapter
** MAC: 00:21:91:19:96:53
* eth2
** Type: # Intel Corporation 82540EM Gigabit Ethernet Controller
** MAC: 00:0E:0C:59:46:E4

== Initial Mapping ==

When the Fedora install finished, you may have gotten this:

* eth0
** Type: # D-Link System Inc DGE-560T PCI Express Gigabit Ethernet Adapter
** MAC: 00:21:91:19:96:53
* eth1
** Type: # Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
** MAC: 90:E6:BA:71:82:EA
* eth2
** Type: # Intel Corporation 82540EM Gigabit Ethernet Controller
** MAC: 00:0E:0C:59:46:E4

== The Problem ==

In the above example, eth2 is where we want it, so we leave it alone. The problem is that eth0 and eth1 are reversed.

== The Fix ==

Traditionally, the ethX to physical ethernet device was linked via the HWADDR=... argument in each NIC's ifcfg-ethX configuration file. With the introduction of [http://en.wikipedia.org/wiki/Udev udev], the HWADDR=... is no longer needed. Instead, this mapping is now made in the 70-persistent-net.rules udev configuration file.

So the trick then is to remove or comment-out the HWADDR=... argument in each NIC's ifcfg-ethX configuration file, then, change the NAME="ethX" in the udev configuration file to match the MAC address you want.

=== Stopping the Network ===

First, stop the network. This is important because if you change the MAC address to ethX mapping while the network is still up, the init.d script will fail to bring down the network devices and you will need to reboot for the changes to take effect.

<source lang="bash">
/etc/init.d/network stop
</source>

=== Interface Configuration ===

Go to the /etc/sysconfig/network-scripts/ directory and then use cat to see the contents of the ifcfg-eth* network configuration files:

<source lang="bash">
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
</source>
<source lang="text">
# D-Link System Inc DGE-560T PCI Express Gigabit Ethernet Adapter
DEVICE=eth0
BOOTPROTO=dhcp
DHCPCLASS=
HWADDR=00:21:91:19:96:53
ONBOOT=yes
DHCP_HOSTNAME=an-node01.alteeve.com
</source>
<source lang="bash">
cat ifcfg-eth1
</source>
<source lang="text">
# Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
DEVICE=eth1
BOOTPROTO=dhcp
DEFROUTE=yes
HWADDR=90:E6:BA:71:82:EA
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
ONBOOT=yes
OPTIONS=layer2=1
PEERDNS=yes
PEERROUTES=yes
TYPE=Ethernet
UUID=9c92fad9-6ecb-3e6c-eb4d-8a47c6f50c04
DHCP_HOSTNAME=an-node01.alteeve.com
</source>
<source lang="bash">
cat ifcfg-eth2
</source>
<source lang="text">
# Intel Corporation 82540EM Gigabit Ethernet Controller
DEVICE=eth2
HWADDR=00:0E:0C:59:46:E4
ONBOOT=no
</source>

The important lines are the DEVICE=... and HWADDR=... lines. The rest of the lines will very likely differ from the output above, and most will likely be set to BOOTPROTO=static. One or more may also be set to ONBOOT=yes. It is outside the scope of this tutorial to cover the various settings

For an exhaustive list of available options, please [http://docs.fedoraproject.org/en-US/Fedora/12/html/Deployment_Guide/s1-networkscripts-interfaces.html see the Fedora documentation].

With networking stopped, all we need to do is remove the HWADDR=... lines. '''Personally''', I like to keep the network card name and the HWADDR=... entries in my files, but comment them out. If you wish to do the same, move them to the appropriate file. Further, I use this time to further configure each interface to the values I want. Do whatever is right for you.

Here is the updated files with updated network settings:

<source lang="bash">
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
</source>
<source lang="text">
# Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
#HWADDR=90:E6:BA:71:82:EA
DEVICE=eth0
BOOTPROTO=static
ONBOOT=yes
TYPE=Ethernet
IPADDR=192.168.1.71
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
DNS1=192.139.81.117
DNS2=192.139.81.1
DEFROUTE=yes
</source>
<source lang="bash">
cat ifcfg-eth1
</source>
<source lang="text">
# D-Link System Inc DGE-560T PCI Express Gigabit Ethernet Adapter
#HWADDR=00:21:91:19:96:53
DEVICE=eth1
BOOTPROTO=static
ONBOOT=yes
TYPE=Ethernet
IPADDR=10.0.0.71
NETMASK=255.255.255.0
</source>
<source lang="bash">
cat ifcfg-eth2
</source>
<source lang="text">
# Intel Corporation 82540EM Gigabit Ethernet Controller
#HWADDR=00:0E:0C:59:46:E4
DEVICE=eth2
ONBOOT=yes
BOOTPROTO=static
TYPE=Ethernet
IPADDR=10.0.1.71
NETMASK=255.255.255.0
</source>

=== 'udev' Configuration ===

The user-space device manager, [http://en.wikipedia.org/wiki/Udev udev], maintains a list of configuration files that help ensure that hardware to /dev (software) mappings stay consistent, even when hardware is hot swapped or moved between physical connections. For networking hardware, this mapping is recorded in the 70-persistent-net.rules.

Here, all that needs to be done is for the NAME="..." entry to be changed to reflect what you want.

Note that the entries do not need to be in any particular order.

<source lang="bash">
cd /etc/udev/rules.d/
cat 70-persistent-net.rules
</source>
<source lang="text">
# 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:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:0c:59:46:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x1186:0x4b00 (sky2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:91:19:96:53", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="90:e6:ba:71:82:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
</source>

Make the changes and save the file. The file should now look like this:

<source lang="bash">
cat 70-persistent-net.rules
</source>
<source lang="text">
# 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 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="90:e6:ba:71:82:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x1186:0x4b00 (sky2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:91:19:96:53", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:0c:59:46:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
</source>

=== Making the Changes Take Effect ===

First, you need to reload udev so that it updates the mapping in memory. This is done using the start_udev program:

<source lang="bash">
start_udev
</source>
<source lang="text">
Starting udev: [ OK ]
</source>

With udev updated, the last step is to restart the network daemon:

<source lang="bash">
/etc/init.d/network start
</source>
<source lang="text">
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth1: [ OK ]
Bringing up interface eth2: [ OK ]
</source>

Done! use ifconfig to verify that the network cards are properly assigned to the specified ethX names.

== Caveat! ==

'''''NOTE''''': If you are using a vlan, the device facing the vlan '''can not''' have the '''HWADDR=...''' value set! Set the others and leave this commented out. Otherwise, because of how the vlan loads, the OS will not see the physical device and will fail to bring up the interface at all.

{{footer}}

Changing the ethX to Ethernet Device Mapping in EL6 and Fedora 12 to 14

2012-11-19T13:33:16Z

Rucus: /* For the Impatient */

{{howto_header}}

{{note|1=This applies up to Fedora 14. Fedora 15 works quite differently now that it uses biosdevname. Please follow [[Changing Ethernet Device Names in EL7 and Fedora 15+|this tutorial]] for Fedora 15 and newer.}}

When you have two or more ethernet devices in one machine, the Fedora install may not install them in the order you want. This document will show you how to change the ethX to physical ethernet device mapping.

This is desirable in cases where specific network cards need to be used on specific networks, and you are interested in maintaining common ethX names across servers. A practical example is found in the [[2-Node Red Hat KVM Cluster Tutorial]].

= For the Impatient =

Assuming that NetworkManager is already removed. This example will swap eth0 and eth1.

<source lang="bash">
#Stop the network daemon
/etc/init.d/network stop
cd /etc/sysconfig/network-scripts
#Move your ifcfg files to the device names you desire
cp ifcfg-eth0 ifcfg-temp
cp ifcfg-eth1 ifcfg-eth0
cp ifcfg-temp ifcfg eth1
rm ifcfg-temp
#Modify DEVICE lines to match new file names
vim /etc/sysconfig/network-scripts/ifcfg-eth*
# Make changes as needed
#Remove udev rules file
rm /etc/udev/rules.d/70-persistent-net.rules
start_udev
/etc/init.d/network start
</source>

Thanks for fenris02 and mutk

= Example =

I find it easier to follow instructions when I have an example to follow, so let me provide one here:

I've got the same hardware in the same configuration in both of my storage nodes. To keep things simple, I want to make sure that both nodes use the same ethX name for the network devices on each of the given networks.

== Desired Mapping ==

Let's assume that you want this:

* eth0
** Type: # Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
** MAC: 90:E6:BA:71:82:EA
* eth1
** Type: # D-Link System Inc DGE-560T PCI Express Gigabit Ethernet Adapter
** MAC: 00:21:91:19:96:53
* eth2
** Type: # Intel Corporation 82540EM Gigabit Ethernet Controller
** MAC: 00:0E:0C:59:46:E4

== Initial Mapping ==

When the Fedora install finished, you may have gotten this:

* eth0
** Type: # D-Link System Inc DGE-560T PCI Express Gigabit Ethernet Adapter
** MAC: 00:21:91:19:96:53
* eth1
** Type: # Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
** MAC: 90:E6:BA:71:82:EA
* eth2
** Type: # Intel Corporation 82540EM Gigabit Ethernet Controller
** MAC: 00:0E:0C:59:46:E4

== The Problem ==

In the above example, eth2 is where we want it, so we leave it alone. The problem is that eth0 and eth1 are reversed.

== The Fix ==

Traditionally, the ethX to physical ethernet device was linked via the HWADDR=... argument in each NIC's ifcfg-ethX configuration file. With the introduction of [http://en.wikipedia.org/wiki/Udev udev], the HWADDR=... is no longer needed. Instead, this mapping is now made in the 70-persistent-net.rules udev configuration file.

So the trick then is to remove or comment-out the HWADDR=... argument in each NIC's ifcfg-ethX configuration file, then, change the NAME="ethX" in the udev configuration file to match the MAC address you want.

=== Stopping the Network ===

First, stop the network. This is important because if you change the MAC address to ethX mapping while the network is still up, the init.d script will fail to bring down the network devices and you will need to reboot for the changes to take effect.

<source lang="bash">
/etc/init.d/network stop
</source>

=== Interface Configuration ===

Go to the /etc/sysconfig/network-scripts/ directory and then use cat to see the contents of the ifcfg-eth* network configuration files:

<source lang="bash">
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
</source>
<source lang="text">
# D-Link System Inc DGE-560T PCI Express Gigabit Ethernet Adapter
DEVICE=eth0
BOOTPROTO=dhcp
DHCPCLASS=
HWADDR=00:21:91:19:96:53
ONBOOT=yes
DHCP_HOSTNAME=an-node01.alteeve.com
</source>
<source lang="bash">
cat ifcfg-eth1
</source>
<source lang="text">
# Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
DEVICE=eth1
BOOTPROTO=dhcp
DEFROUTE=yes
HWADDR=90:E6:BA:71:82:EA
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
ONBOOT=yes
OPTIONS=layer2=1
PEERDNS=yes
PEERROUTES=yes
TYPE=Ethernet
UUID=9c92fad9-6ecb-3e6c-eb4d-8a47c6f50c04
DHCP_HOSTNAME=an-node01.alteeve.com
</source>
<source lang="bash">
cat ifcfg-eth2
</source>
<source lang="text">
# Intel Corporation 82540EM Gigabit Ethernet Controller
DEVICE=eth2
HWADDR=00:0E:0C:59:46:E4
ONBOOT=no
</source>

The important lines are the DEVICE=... and HWADDR=... lines. The rest of the lines will very likely differ from the output above, and most will likely be set to BOOTPROTO=static. One or more may also be set to ONBOOT=yes. It is outside the scope of this tutorial to cover the various settings

For an exhaustive list of available options, please [http://docs.fedoraproject.org/en-US/Fedora/12/html/Deployment_Guide/s1-networkscripts-interfaces.html see the Fedora documentation].

With networking stopped, all we need to do is remove the HWADDR=... lines. '''Personally''', I like to keep the network card name and the HWADDR=... entries in my files, but comment them out. If you wish to do the same, move them to the appropriate file. Further, I use this time to further configure each interface to the values I want. Do whatever is right for you.

Here is the updated files with updated network settings:

<source lang="bash">
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
</source>
<source lang="text">
# Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
#HWADDR=90:E6:BA:71:82:EA
DEVICE=eth0
BOOTPROTO=static
ONBOOT=yes
TYPE=Ethernet
IPADDR=192.168.1.71
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
DNS1=192.139.81.117
DNS2=192.139.81.1
DEFROUTE=yes
</source>
<source lang="bash">
cat ifcfg-eth1
</source>
<source lang="text">
# D-Link System Inc DGE-560T PCI Express Gigabit Ethernet Adapter
#HWADDR=00:21:91:19:96:53
DEVICE=eth1
BOOTPROTO=static
ONBOOT=yes
TYPE=Ethernet
IPADDR=10.0.0.71
NETMASK=255.255.255.0
</source>
<source lang="bash">
cat ifcfg-eth2
</source>
<source lang="text">
# Intel Corporation 82540EM Gigabit Ethernet Controller
#HWADDR=00:0E:0C:59:46:E4
DEVICE=eth2
ONBOOT=yes
BOOTPROTO=static
TYPE=Ethernet
IPADDR=10.0.1.71
NETMASK=255.255.255.0
</source>

=== 'udev' Configuration ===

The user-space device manager, [http://en.wikipedia.org/wiki/Udev udev], maintains a list of configuration files that help ensure that hardware to /dev (software) mappings stay consistent, even when hardware is hot swapped or moved between physical connections. For networking hardware, this mapping is recorded in the 70-persistent-net.rules.

Here, all that needs to be done is for the NAME="..." entry to be changed to reflect what you want.

Note that the entries do not need to be in any particular order.

<source lang="bash">
cd /etc/udev/rules.d/
cat 70-persistent-net.rules
</source>
<source lang="text">
# 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:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:0c:59:46:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x1186:0x4b00 (sky2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:91:19:96:53", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="90:e6:ba:71:82:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
</source>

Make the changes and save the file. The file should now look like this:

<source lang="bash">
cat 70-persistent-net.rules
</source>
<source lang="text">
# 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 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="90:e6:ba:71:82:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x1186:0x4b00 (sky2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:91:19:96:53", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:0c:59:46:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
</source>

=== Making the Changes Take Effect ===

First, you need to reload udev so that it updates the mapping in memory. This is done using the start_udev program:

<source lang="bash">
start_udev
</source>
<source lang="text">
Starting udev: [ OK ]
</source>

With udev updated, the last step is to restart the network daemon:

<source lang="bash">
/etc/init.d/network start
</source>
<source lang="text">
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth1: [ OK ]
Bringing up interface eth2: [ OK ]
</source>

Done! use ifconfig to verify that the network cards are properly assigned to the specified ethX names.

== Caveat! ==

'''''NOTE''''': If you are using a vlan, the device facing the vlan '''can not''' have the '''HWADDR=...''' value set! Set the others and leave this commented out. Otherwise, because of how the vlan loads, the OS will not see the physical device and will fail to bring up the interface at all.

{{footer}}

Changing the ethX to Ethernet Device Mapping in EL6 and Fedora 12 to 14

2012-11-19T13:32:27Z

Rucus: /* For the Impatient */

{{howto_header}}

{{note|1=This applies up to Fedora 14. Fedora 15 works quite differently now that it uses biosdevname. Please follow [[Changing Ethernet Device Names in EL7 and Fedora 15+|this tutorial]] for Fedora 15 and newer.}}

When you have two or more ethernet devices in one machine, the Fedora install may not install them in the order you want. This document will show you how to change the ethX to physical ethernet device mapping.

This is desirable in cases where specific network cards need to be used on specific networks, and you are interested in maintaining common ethX names across servers. A practical example is found in the [[2-Node Red Hat KVM Cluster Tutorial]].

= For the Impatient =

Assuming that NetworkManager is already removed.

<source lang="bash">
#Stop the network daemon
/etc/init.d/network stop
cd /etc/sysconfig/network-scripts
#Move your ifcfg files to the device names you desire
cp ifcfg-eth0 ifcfg-temp
cp ifcfg-eth1 ifcfg-eth0
cp ifcfg-temp ifcfg eth1
rm ifcfg-temp
#Modify DEVICE lines to match new file names
vim /etc/sysconfig/network-scripts/ifcfg-eth*
# Make changes as needed
#Remove udev rules file
rm /etc/udev/rules.d/70-persistent-net.rules
start_udev
/etc/init.d/network start
</source>

Thanks for fenris02 and mutk

= Example =

I find it easier to follow instructions when I have an example to follow, so let me provide one here:

I've got the same hardware in the same configuration in both of my storage nodes. To keep things simple, I want to make sure that both nodes use the same ethX name for the network devices on each of the given networks.

== Desired Mapping ==

Let's assume that you want this:

* eth0
** Type: # Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
** MAC: 90:E6:BA:71:82:EA
* eth1
** Type: # D-Link System Inc DGE-560T PCI Express Gigabit Ethernet Adapter
** MAC: 00:21:91:19:96:53
* eth2
** Type: # Intel Corporation 82540EM Gigabit Ethernet Controller
** MAC: 00:0E:0C:59:46:E4

== Initial Mapping ==

When the Fedora install finished, you may have gotten this:

* eth0
** Type: # D-Link System Inc DGE-560T PCI Express Gigabit Ethernet Adapter
** MAC: 00:21:91:19:96:53
* eth1
** Type: # Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
** MAC: 90:E6:BA:71:82:EA
* eth2
** Type: # Intel Corporation 82540EM Gigabit Ethernet Controller
** MAC: 00:0E:0C:59:46:E4

== The Problem ==

In the above example, eth2 is where we want it, so we leave it alone. The problem is that eth0 and eth1 are reversed.

== The Fix ==

Traditionally, the ethX to physical ethernet device was linked via the HWADDR=... argument in each NIC's ifcfg-ethX configuration file. With the introduction of [http://en.wikipedia.org/wiki/Udev udev], the HWADDR=... is no longer needed. Instead, this mapping is now made in the 70-persistent-net.rules udev configuration file.

So the trick then is to remove or comment-out the HWADDR=... argument in each NIC's ifcfg-ethX configuration file, then, change the NAME="ethX" in the udev configuration file to match the MAC address you want.

=== Stopping the Network ===

First, stop the network. This is important because if you change the MAC address to ethX mapping while the network is still up, the init.d script will fail to bring down the network devices and you will need to reboot for the changes to take effect.

<source lang="bash">
/etc/init.d/network stop
</source>

=== Interface Configuration ===

Go to the /etc/sysconfig/network-scripts/ directory and then use cat to see the contents of the ifcfg-eth* network configuration files:

<source lang="bash">
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
</source>
<source lang="text">
# D-Link System Inc DGE-560T PCI Express Gigabit Ethernet Adapter
DEVICE=eth0
BOOTPROTO=dhcp
DHCPCLASS=
HWADDR=00:21:91:19:96:53
ONBOOT=yes
DHCP_HOSTNAME=an-node01.alteeve.com
</source>
<source lang="bash">
cat ifcfg-eth1
</source>
<source lang="text">
# Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
DEVICE=eth1
BOOTPROTO=dhcp
DEFROUTE=yes
HWADDR=90:E6:BA:71:82:EA
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
ONBOOT=yes
OPTIONS=layer2=1
PEERDNS=yes
PEERROUTES=yes
TYPE=Ethernet
UUID=9c92fad9-6ecb-3e6c-eb4d-8a47c6f50c04
DHCP_HOSTNAME=an-node01.alteeve.com
</source>
<source lang="bash">
cat ifcfg-eth2
</source>
<source lang="text">
# Intel Corporation 82540EM Gigabit Ethernet Controller
DEVICE=eth2
HWADDR=00:0E:0C:59:46:E4
ONBOOT=no
</source>

The important lines are the DEVICE=... and HWADDR=... lines. The rest of the lines will very likely differ from the output above, and most will likely be set to BOOTPROTO=static. One or more may also be set to ONBOOT=yes. It is outside the scope of this tutorial to cover the various settings

For an exhaustive list of available options, please [http://docs.fedoraproject.org/en-US/Fedora/12/html/Deployment_Guide/s1-networkscripts-interfaces.html see the Fedora documentation].

With networking stopped, all we need to do is remove the HWADDR=... lines. '''Personally''', I like to keep the network card name and the HWADDR=... entries in my files, but comment them out. If you wish to do the same, move them to the appropriate file. Further, I use this time to further configure each interface to the values I want. Do whatever is right for you.

Here is the updated files with updated network settings:

<source lang="bash">
cd /etc/sysconfig/network-scripts
cat ifcfg-eth0
</source>
<source lang="text">
# Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
#HWADDR=90:E6:BA:71:82:EA
DEVICE=eth0
BOOTPROTO=static
ONBOOT=yes
TYPE=Ethernet
IPADDR=192.168.1.71
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
DNS1=192.139.81.117
DNS2=192.139.81.1
DEFROUTE=yes
</source>
<source lang="bash">
cat ifcfg-eth1
</source>
<source lang="text">
# D-Link System Inc DGE-560T PCI Express Gigabit Ethernet Adapter
#HWADDR=00:21:91:19:96:53
DEVICE=eth1
BOOTPROTO=static
ONBOOT=yes
TYPE=Ethernet
IPADDR=10.0.0.71
NETMASK=255.255.255.0
</source>
<source lang="bash">
cat ifcfg-eth2
</source>
<source lang="text">
# Intel Corporation 82540EM Gigabit Ethernet Controller
#HWADDR=00:0E:0C:59:46:E4
DEVICE=eth2
ONBOOT=yes
BOOTPROTO=static
TYPE=Ethernet
IPADDR=10.0.1.71
NETMASK=255.255.255.0
</source>

=== 'udev' Configuration ===

The user-space device manager, [http://en.wikipedia.org/wiki/Udev udev], maintains a list of configuration files that help ensure that hardware to /dev (software) mappings stay consistent, even when hardware is hot swapped or moved between physical connections. For networking hardware, this mapping is recorded in the 70-persistent-net.rules.

Here, all that needs to be done is for the NAME="..." entry to be changed to reflect what you want.

Note that the entries do not need to be in any particular order.

<source lang="bash">
cd /etc/udev/rules.d/
cat 70-persistent-net.rules
</source>
<source lang="text">
# 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:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:0c:59:46:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x1186:0x4b00 (sky2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:91:19:96:53", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="90:e6:ba:71:82:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
</source>

Make the changes and save the file. The file should now look like this:

<source lang="bash">
cat 70-persistent-net.rules
</source>
<source lang="text">
# 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 0x10ec:0x8168 (r8169) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="90:e6:ba:71:82:ea", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x1186:0x4b00 (sky2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:21:91:19:96:53", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x100e (e1000) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:0c:59:46:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
</source>

=== Making the Changes Take Effect ===

First, you need to reload udev so that it updates the mapping in memory. This is done using the start_udev program:

<source lang="bash">
start_udev
</source>
<source lang="text">
Starting udev: [ OK ]
</source>

With udev updated, the last step is to restart the network daemon:

<source lang="bash">
/etc/init.d/network start
</source>
<source lang="text">
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth1: [ OK ]
Bringing up interface eth2: [ OK ]
</source>

Done! use ifconfig to verify that the network cards are properly assigned to the specified ethX names.

== Caveat! ==

'''''NOTE''''': If you are using a vlan, the device facing the vlan '''can not''' have the '''HWADDR=...''' value set! Set the others and leave this commented out. Otherwise, because of how the vlan loads, the OS will not see the physical device and will fail to bring up the interface at all.

{{footer}}

TNAP v1.1.4

2010-04-16T15:52:15Z

Rucus: /* TNAP v1.1.4 */

{{na_v1.1.4_header}}

TNAP; The Node Assassin Protocol is the protocol that defines how commands are to be passed to a Node Assassin device and what output to expect in return. Generally, you will use [[telnet]] to connect to a Node Assassin.

= TNAP v1.1.4 =

TNAP works by listening for a connection on [[TCP]] port 238 on [[IP]] 192.168.1.66 by default. Both the port and the IP are configurable. Once connected, it uses a very simple protocol.

There are two types of calls:
* [[#Queries|Queries]]
* [[#Commands|Commands]]

== Queries ==

Any message starting with 00:x are '''query commands'''. That is, the integer represented by '''x''' is interpreted to be a specific information request. Currently, two queries are supported:
* [[#00:0 - Node Status|00:0]] - Node states query
* [[#00:1 - NA Information|00:1]] - Node Assassin query

All queries and commands terminate with a final EOM on a new line. Any programs accessing a Node Assassin must watch for this message and, not finding it, treat any messages as incomplete and corrupt.

=== 00:0 - Node Status ===

To request the state of all supported nodes, send:
<source lang="text">
00:0
</source>

This will generate a message such as:
<source lang="text">
Node states:
- Node Count: 04
- Node 01: P0 R0 F1
- Node 02: P0 R0 F1
- Node 03: P1 R1 F0
- Node 04: P0 R0 F0
End Message.
</source>

The status is broken down into three values:
* Power: P[0|1]
* Reset: R[0|1]
* Feed: F[0|1].

For the power and reset buttons, a value of 0 indicates that the related switch switch is open. If it is set to 1, the switch is closed (the indicated button is "pressed").

For the Feed value, 0 indicates that there is no power coming from the node's feed and thus, the node is "off" or disconnected. If the feed is 1, then power is detected from the node and the node is known to be "on".

Quick reference table:
{|style="width: 600px; border-top: 1px dotted #7f7f7f; border-left: 1px dotted #7f7f7f;"
|-
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: center"|'''Type'''
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: center"|'''Code'''
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: center"|0
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: center"|1
|-
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: center"|Power Switch
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: center"|P
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: center"|Open
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: center"|Closed
|-
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: center"|Reset Switch
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: center"|R
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: center"|Open
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: center"|Closed
|-
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: center"|Power Feed
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: center"|F
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: center"|Node is On
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: center"|Node is Off/disconnected
|}

=== 00:1 - NA Information ===

This query requests information on the node assassin device itself and is called via:

<source lang="text">
00:1
</source>

This will generate a message such as:
<source lang="text">
Node info:
- Node Name: ..... Motoko
- Port Count: .... 04
- NAOS Version: .. v1.1.4.4
- Serial Number: . PR0002
- Build Date: .... 2010-04-03
- MAC address: ... 02:00:00:FF:F0:AA
- IP address: .... 192.168.1.66
- Subnet Mask: ... 255.255.255.0
- Default Gateway: 192.168.1.1
EOM
</source>

The above information is from the internal NAOS, not from the configuration file.

== Commands ==

Commands are always given in the form: XX:Y where:
* XX is the two-digit, zero-padded node number between 01 and max node.
* Y is the single-digit command being issues.

=== XX:0 - Release ===

XX:0

Release the fence on the node if one exists. Specifically, both power and reset switches are opened.

=== XX:1 - Fence ===

XX:1

Fence the specified node. Specifically;
# The state is checked.
## If the node is already fenced, the fence is momentarily released so that it can be re-applied.
# The reset switch is closed for one second to immediately disable the node.
# The reset switch is opened for one second.
## Some machines will not respond to the power button if the reset button is simultaneously pressed.
# The power switch is closed.
## After five seconds the node's power feed is checked. If the feed is still high, NA waits another 25 seconds and checks again. If the feed is still high, an error is generated.
# The reset switch is closed.
## At this point, both power and reset are closed, disabling the node's front-panel switches preventing accidental booting of the node before the fence is released.

=== XX:2 - Boot or Graceful Power Off ===

XX:2

This will close the power switch for one second and then re-open it. If the node was off, this should initiate a boot. If the node was on, this should initiate shutdown via [[ACPI]]. The power feed is checked prior to the one second fence and the returned message reflects whether the node is being booted or shut down.

=== XX:3 - Force Power Off ===

XX:3

This is essentially the same as XX:1 except the node is not locked at the end of the fence process. This will close the power switch. After five seconds the node's power feed is checked. If the feed is still high, NA waits another 25 seconds and checks again. If the feed is still high, an error is generated. Regardless of success or failure, the fence is removed.

{{footer}}

Node Assassin v1.1.4

2010-04-16T15:46:52Z

Rucus:

{{na_header}}

{|style="width: 100%; align: center;"
|-
|colspan="2"|[[Image:na_artsy_view.jpg]]
|}

'''-=] '''''Paradise by the node assassin light''''' [=-'''

[[Image:an_cluster_logo_01.jpg|thumb|300px|right|The AN!Cluster unnamed assassin.]]

= About =

'''Node Assassin''' is an open hardware, open source [[cluster fence]] device.

It is 100% compatible with the [[RedHat]]/[[CentOS]] cluster management suite.

= Download =

All downloads include all files needed to build your own Node Assassin from commodity parts.

{|style="width: 95%; border-top: 1px dotted #7f7f7f; border-left: 1px dotted #7f7f7f;"
|-
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: center; font-weight: bold;" colspan="3"|''Downloads''
|-
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: center; font-weight: bold;" nowrap="nowrap"|Source
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: left;" nowrap="nowrap"|[http://nodeassassin.org/files/node_assassin/node_assassin-1.1.4-1.tar.gz node_assassin-1.1.4-1.tar.gz]
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: left;"|Contains all files and programs needed to build a Node Assassin, load it's NAOS and install it's fence agent. Simply run the 'install' script from the root of the directory created by extracting the tarball.
|-
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: center; font-weight: bold;" nowrap="nowrap"| Minimal 
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: left;" nowrap="nowrap"|[http://nodeassassin.org/files/node_assassin/node_assassin-1.1.4-1.tar.gz node_assassin-1.1.4_minimal.tar.gz]
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: left;"|Same as the full source, but without the build images and files and does not have the Arduino IDE or BSchV3 programs. Substantially smaller download.
|-
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: center; font-weight: bold;" nowrap="nowrap"|RPM
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: left;" nowrap="nowrap"|[http://nodeassassin.org/files/node_assassin/node_assassin-1.1.4-1.noarch.rpm node_assassin-1.1.4-1.noarch.rpm]
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: left;"|Architecture independent RPM wrapper for the source file.
|-
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: center; font-weight: bold;" nowrap="nowrap"|SRPM
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: left;" nowrap="nowrap"|[http://nodeassassin.org/files/node_assassin/node_assassin-1.1.4-1.noarch.srpm node_assassin-1.1.4-1.noarch.srpm]
|style="border-bottom: 1px dotted #7f7f7f; border-right: 1px dotted #7f7f7f; text-align: left;"|Architecture independent Source RPM wrapper for the source file.
|}

= Node Assassin =

[[Image:current_na.jpg|thumb|400px|right|'''Apr. 03, 2010''': The current Node Assassin; v1.1.4 Prototype A.]]

There are four major sections:

* [[#Building your own Node Assassin|Building your own Node Assassin]]
* [[#NAOS; The Node Assassin Operating System|NAOS; The Node Assassin Operating System]]
* [[#The NA Fence Agent|The NA Fence Agent]]
* [[#TNAP; The Node Assassin Protocol|TNAP; The Node Assassin Protocol]]

== Building your own Node Assassin ==

At this time, the commercial, pre-built Node Assassin is still in development. In order to get a Node Assassin now, you will need to build your own.

If you live in a big city, then your local electronics hobby shop should have everything you need. If you don't, then you can either order the parts from an online supplier or, if you wish, you can buy a kit with everything you need from us.

* [[Building a Node Assassin v1.1.4]]

== NAOS; The Node Assassin Operating System ==

NAOS is the Arduino-based sketch that operates the Node Assassin. You will need to edit the source file naos_v1.1.4.4.c file to match your environment and then load it into your Node Assassin. Everything you need to know can be found in the link below:

* [[NAOS v1.1.4.x]]

== The NA Fence Agent ==

This is the FenceAgentAPI compatible fence agent for Node Assassin devices. It is a [[perl]] program consisting of three files;
* /sbin/fence_na - The core agent called by the fenced daemon.
* /etc/fence_na/fence_na.lib - The library containing the shared functions used by the core program.
* /etc/fence_na/fence_na.conf - This is the common configuration file for your Node Assassin(s). It must be updated to match your environment in order to work.

All the details, including the source code, can be found in the following article:

* [[Node Assassin Fence Agent v1.1.4]]

== TNAP; The Node Assassin Protocol ==

Node Assassins are accessed and controlled over [[telnet]] using a custom protocol called TNAP. For day-to-day clustering, you do not need to worry about the protocol as the fence agent handles the communication for you behind the scenes. If you would like to know the details though, or would like to help improving the protocol, all the details are in the following article.

* [[TNAP v1.1.4]]

{{na_footer}}