SCIENTIFIC-LINUX-USERS Archives

July 2014

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
Date:
Mon, 28 Jul 2014 17:34:31 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (51 lines)
On Mon, Jul 28, 2014 at 5:35 AM, SCHAER Frederic <[log in to unmask]> wrote:
>
> From time to time, we get reboot issues with some machines, and each time it
> looks like there are duplicated persistent rules for the Ethernet devices :
>
> cat /etc/udev/rules.d/70-persistent-net.rules
>
> # 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:0x1521 (igb) (custom name provided by external tool)
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> ATTR{address}=="84:8f:69:fb:c1:2a", ATTR{type}=="1", KERNEL=="eth*",
> NAME="em1"
>
> # PCI device 0x8086:0x1521 (igb) (custom name provided by external tool)
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> ATTR{address}=="84:8f:69:fb:c1:2b", ATTR{type}=="1", KERNEL=="eth*",
> NAME="em2"
>
> # PCI device 0x8086:0x1521 (igb) (custom name provided by external tool)
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> ATTR{address}=="84:8f:69:fb:c1:2a", ATTR{type}=="1", KERNEL=="eth*",
> NAME="eth0"
>
> # PCI device 0x8086:0x1521 (igb) (custom name provided by external tool)
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> ATTR{address}=="84:8f:69:fb:c1:2b", ATTR{type}=="1", KERNEL=="eth*",
> NAME="eth1"
>
> The second set of rules seem to overwrite the first one, and then we get
> issues with our network config.
>
> This does not happen on all nodes, just apparently to some random ones,
> sometimes.
>
> I’m wondering if some of you might have faced and solved that erratic thing
> already ?
>
> We want to keep the emX scheme for nodes which support it…

The emX names come from biosdevname (part of a base install):

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/appe-Consistent_Network_Device_Naming.html

You should be able to delete the last two rules, the ethX rules, for
your interfaces to use the emX names, unless you're using
"biosdevname=0" on the kernel cmdline.

ATOM RSS1 RSS2