Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am using Redhat Enterprise Linux 6.3. I dont have any problem if RHEL shows ethx or either emx. This time the RHEL is showing the interfaces as emx. I am contineously watching that my em1 or em2 or em3 keep changing its names. For example when I reboot my Linux box the em1 shows Auto_em1 and sometime it come back to em1 after reboot. I got tense to watch it. same is with em2 and other NICs. How can I make the NICs name persistent.
# cat /etc/udev/rules.d/70-persistent-
70-persistent-cd.rules 70-persistent-net.rules # 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 0x14e4:0x1639 (bnx2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:24:e8:2e:ab:40", ATTR{type}=="1", KERNEL=="eth*", NAME="Auto_em1"
# PCI device 0x8086:0x105e (e1000e) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:15:17:95:38:b5", ATTR{type}=="1", KERNEL=="eth*", NAME="Auto_p1p2"
# PCI device 0x14e4:0x1659 (tg3) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:10:18:1c:51:ea", ATTR{type}=="1", KERNEL=="eth*", NAME="Auto_p3p1"
# PCI device 0x14e4:0x1639 (bnx2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:24:e8:2e:ab:42", ATTR{type}=="1", KERNEL=="eth*", NAME="Auto_em2"
# PCI device 0x14e4:0x1639 (bnx2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:24:e8:2e:ab:40", ATTR{type}=="1", KERNEL=="eth*", NAME="em1"
# PCI device 0x8086:0x105e (e1000e) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:15:17:95:38:b4", ATTR{type}=="1", KERNEL=="eth*", NAME="Auto_p1p1"
=============================
=============================
ONE THING I WOULD LIKE TO ADD HERE IS THAT IF I RUN THE ifconfig COMMAND I CAN ONLY SEE ONE ENTRY FOR em1, WHICH IS em1 BUT IN THE ABOVE COMMAND I CAN SEE TWO ENTRIES WHICH ARE em1 AND Auto_em1
1. how many eth NICs are actually installed (inc built-in to motherboard) ?
2. what files have you got in /etc/sysconfig/network-scripts ?
3. do the eth-ifcfg* files have NM_CONTROLLED=no or 'yes' ?
Personally I've got Centos 6.5 and always turn off Network Manager; always seems to cause more problems than it solves.
1. how many eth NICs are actually installed (inc built-in to motherboard) ?
2. what files have you got in /etc/sysconfig/network-scripts ?
3. do the eth-ifcfg* files have NM_CONTROLLED=no or 'yes' ?
Personally I've got Centos 6.5 and always turn off Network Manager; always seems to cause more problems than it solves.
Yup. You either always use the applet and let NM have all the interfaces, or you remove it and do everything yourself. There seems to be no way to "peacefully coexist".
First of all I am very thankful to all in giving reply to my query.
If I do chkconfig NetworkManager off and reboot the node. Will changing of em1 to Auto_em1 and again Auto_em1 to em1 will be stopped ?
OR
in parallel with above activity should I remove the file /etc/udev/rules.d/70-persistent-net.rules and reboot the node and makesure the em1 should be em1 and em2 should be em2 instead of Auto_em1 and Auto_em2 under the file /etc/udev/rules.d/70-persistent-net.rules ?
What should I do ? Should I do both activities or only first ?
======================================================================================
======================================================================================
In parallel I installed a new RHEL 6.3 and run the chkconfig NetworkMonitor off and reboot the node then I am not able to see the file ( /etc/udev/rules.d/70-persistent-net.rules). See the below for reference:
# pwd
/etc/udev/rules.d
# ls -l
total 48
-rwxr-xr-x. 1 root root 708 Mar 8 18:27 40-VxVM.rules
-r--r-----. 1 root root 187 Oct 22 02:21 45-disk_reservation.rules
-rw-r--r--. 1 root root 1652 Aug 25 2010 60-fprint-autosuspend.rules
-rw-r--r--. 1 root root 1060 Jun 29 2010 60-pcmcia.rules
-rw-r--r--. 1 root root 316 Apr 6 2012 60-raw.rules
-rwxr-xr-x. 1 root root 1066 Oct 23 17:43 60-vxca.rules
-rw-r--r--. 1 root root 1406 Mar 8 17:29 70-persistent-cd.rules
-rw-r--r--. 1 root root 320 May 9 2012 90-alsa.rules
-rw-r--r--. 1 root root 83 Apr 1 2011 90-hal.rules
-rw-r--r--. 1 root root 53 Oct 21 2011 91-drm-modeset.rules
-rw-r--r--. 1 root root 292 May 25 2012 98-kexec.rules
-rw-r--r--. 1 root root 54 Nov 3 2011 99-fuse.rules
But the same file exist on my LIVE node. See the result of my LIVE node
# pwd
/etc/udev/rules.d
# ls -l
total 52
-rwxr-xr-x 1 root root 708 Mar 5 18:02 40-VxVM.rules
-r--r----- 1 root root 187 Oct 22 02:21 45-disk_reservation.rules
-rw-r--r--. 1 root root 1652 Aug 25 2010 60-fprint-autosuspend.rules
-rw-r--r--. 1 root root 1060 Jun 29 2010 60-pcmcia.rules
-rw-r--r--. 1 root root 316 Apr 6 2012 60-raw.rules
-rwxr-xr-x 1 root root 1066 Oct 23 17:43 60-vxca.rules
-rw-r--r--. 1 root root 1406 Mar 5 12:21 70-persistent-cd.rules -rw-r--r-- 1 root root 1504 Mar 7 02:01 70-persistent-net.rules -rw-r--r--. 1 root root 320 May 9 2012 90-alsa.rules
-rw-r--r--. 1 root root 83 Apr 1 2011 90-hal.rules
-rw-r--r--. 1 root root 53 Oct 21 2011 91-drm-modeset.rules
-rw-r--r--. 1 root root 292 May 25 2012 98-kexec.rules
-rw-r--r--. 1 root root 54 Nov 3 2011 99-fuse.rules
# cat 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 0x14e4:0x1639 (bnx2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:24:e8:2e:ab:40", ATTR{type}=="1", KERNEL=="eth*", NAME="Auto_em1"
# PCI device 0x8086:0x105e (e1000e) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:15:17:95:38:b5", ATTR{type}=="1", KERNEL=="eth*", NAME="Auto_p1p2"
# PCI device 0x14e4:0x1659 (tg3) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:10:18:1c:51:ea", ATTR{type}=="1", KERNEL=="eth*", NAME="Auto_p3p1"
# PCI device 0x14e4:0x1639 (bnx2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:24:e8:2e:ab:42", ATTR{type}=="1", KERNEL=="eth*", NAME="Auto_em2"
# PCI device 0x14e4:0x1639 (bnx2) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:24:e8:2e:ab:40", ATTR{type}=="1", KERNEL=="eth*", NAME="em1"
# PCI device 0x8086:0x105e (e1000e) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:15:17:95:38:b4", ATTR{type}=="1", KERNEL=="eth*", NAME="Auto_p1p1"
That's really odd about the new install; check the other dir with the ifcfg-* files.
Assuming you've got NetworkManager (not monitor) turned off, try manually setting up one NIC and plugging it in and bringing it up.
That's really odd about the new install; check the other dir with the ifcfg-* files.
Whats odd ?
========================
Assuming you've got NetworkManager (not monitor) turned off, try manually setting up one NIC and plugging it in and bringing it up.
Yes the same I did and seems the problem resolved.
What could be the necessary things we need to configure manually in the ifcfg-em* file.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.