On May 1, 2014, at 11:45 AM, Lamar Owen <lowen at pari.edu> wrote: > On 05/01/2014 10:56 AM, Steve Clark wrote: >> I feel for you then. I guess we have been lucky in the 6 or 7 hardware >> platforms we have used that the nics ( minimum 3, usually 4 or more ) >> have always stayed the same names in the same order. > That's actually an illusion. If the detection pulls it up in a > different order, then by MAC address it will get put in the old order, > at least with EL6. Here's a 'grep' excerpt showing the fun: > ++++++++++ > Apr 21 14:39:25 www kernel: udev: renamed network interface eth0 to rename2 > Apr 21 14:39:25 www kernel: udev: renamed network interface eth1 to rename3 > Apr 21 14:39:25 www kernel: udev: renamed network interface eth2 to eth0 > Apr 21 14:39:25 www kernel: udev: renamed network interface eth3 to eth1 > Apr 21 14:39:25 www kernel: udev: renamed network interface rename3 to eth3 > Apr 21 14:39:25 www kernel: udev: renamed network interface rename2 to eth2 > ++++++++++ Been there, done that. NM creates the opposite problem for places that have "lights out" data-centers without trusted (much) remote-hands support, however... when a vendor goes in and swaps a motherboard out of a flaky server... now it's looking for specific MAC addresses that don't exist anymore... and getting the average "on-site tech" from a vendor to give you MAC addresses prior to swapping the hardware that's 1000 miles away, is pretty hit-or-miss. IMHO. Really isn't NM's fault, and swapping out Ethernet cards (back when they were actual cards... ha...) never has been safe remotely... but I like picking on NM. :-) -- Nate Duehr denverpilot at me.com