I have a Dell server that has two built-in ethernet devices. When I kickstart the machine, they are correctly identified as eth0 and eth1 (correctly meaning they correspond to the physical device ports 1 and 2). I need a third one and want that to come up as eth2. After adding the hardware, kickstart now fails because for some reason it goes through a rename process where it makes the newly added card eth1 (or eth0, I forgot). Is there a way to stop this rename process so kickstart correctly uses the physical hardware the way they are, meaning physical port 1 eth0, port 2 = eth1, and the additional ethernet card then becomes eth2? Should I be using the device's MAC address when I set the 'network' option in the kickstart file? So instead of 'network --device=eth0' I make it 'network -device=aa;bb:cc:dd:eee:ff' ?
Correction to my own post: I know it's not kickstart that's doing the renaming, it's the kernel that's booting up the system. On Feb 23, 2015 4:34 PM, "Ashley M. Kirchner" <ashley at pcraft.com> wrote:> I have a Dell server that has two built-in ethernet devices. When I > kickstart the machine, they are correctly identified as eth0 and eth1 > (correctly meaning they correspond to the physical device ports 1 and 2). I > need a third one and want that to come up as eth2. After adding the > hardware, kickstart now fails because for some reason it goes through a > rename process where it makes the newly added card eth1 (or eth0, I > forgot). Is there a way to stop this rename process so kickstart correctly > uses the physical hardware the way they are, meaning physical port 1 > eth0, port 2 = eth1, and the additional ethernet card then becomes eth2? > > Should I be using the device's MAC address when I set the 'network' option > in the kickstart file? So instead of 'network --device=eth0' I make it > 'network -device=aa;bb:cc:dd:eee:ff' ? > >
On 02/23/2015 05:34 PM, Ashley M. Kirchner wrote:> I have a Dell server that has two built-in ethernet devices. When I > kickstart the machine, they are correctly identified as eth0 and eth1 > (correctly meaning they correspond to the physical device ports 1 and 2). I > need a third one and want that to come up as eth2. After adding the > hardware, kickstart now fails because for some reason it goes through a > rename process where it makes the newly added card eth1 (or eth0, I > forgot). Is there a way to stop this rename process so kickstart correctly > uses the physical hardware the way they are, meaning physical port 1 > eth0, port 2 = eth1, and the additional ethernet card then becomes eth2?What version of CentOS are you trying to install? I would expect that a recent version would use the biosdevname interface naming scheme on a Dell server. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/sec-Consistent_Network_Device_Naming_Using_biosdevname.html -- =======================================================================Ian Pilcher arequipeno at gmail.com -------- "I grew up before Mark Zuckerberg invented friendship" -------- ========================================================================
6.6-x86_64 ... Keep in mind this is happening during the kickstart process. What I'm seeing is this: When the system first comes on, PXE kicks in and port 2 (or eth1) gets an IP from the network's dhcp and is configured properly. PXE grabs the necessary files to start installation. However, as soon as it the install image is uncompressed it does a rename on the devices and what should be eth3 is now configured as either eth0 or eth1 (I forgot which one) and what *should* be eth1 is effectively no longer configured. At that point kickstart stops because it can no longer fetch the kickstart file. I have to physically remove the additional ethernet card for it to work properly. On Mon, Feb 23, 2015 at 5:48 PM, Ian Pilcher <arequipeno at gmail.com> wrote:> On 02/23/2015 05:34 PM, Ashley M. Kirchner wrote: > >> I have a Dell server that has two built-in ethernet devices. When I >> kickstart the machine, they are correctly identified as eth0 and eth1 >> (correctly meaning they correspond to the physical device ports 1 and 2). >> I >> need a third one and want that to come up as eth2. After adding the >> hardware, kickstart now fails because for some reason it goes through a >> rename process where it makes the newly added card eth1 (or eth0, I >> forgot). Is there a way to stop this rename process so kickstart correctly >> uses the physical hardware the way they are, meaning physical port 1 >> eth0, port 2 = eth1, and the additional ethernet card then becomes eth2? >> > > What version of CentOS are you trying to install? I would expect that a > recent version would use the biosdevname interface naming scheme on a > Dell server. > > https://access.redhat.com/documentation/en-US/Red_Hat_ > Enterprise_Linux/7/html/Networking_Guide/sec-Consistent_Network_Device_ > Naming_Using_biosdevname.html > -- > =======================================================================> Ian Pilcher arequipeno at gmail.com > -------- "I grew up before Mark Zuckerberg invented friendship" -------- > =======================================================================> > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > >
> On Feb 23, 2015, at 6:34 PM, Ashley M. Kirchner <ashley at pcraft.com> wrote: > > I have a Dell server that has two built-in ethernet devices. When I > kickstart the machine, they are correctly identified as eth0 and eth1 > (correctly meaning they correspond to the physical device ports 1 and 2). I > need a third one and want that to come up as eth2. After adding the > hardware, kickstart now fails because for some reason it goes through a > rename process where it makes the newly added card eth1 (or eth0, I > forgot). Is there a way to stop this rename process so kickstart correctly > uses the physical hardware the way they are, meaning physical port 1 > eth0, port 2 = eth1, and the additional ethernet card then becomes eth2? > > Should I be using the device's MAC address when I set the 'network' option > in the kickstart file? So instead of 'network --device=eth0' I make it > 'network -device=aa;bb:cc:dd:eee:ff' ? >kickstart has an option: ksdevice=bootif I think that'll let you accomplish what you are trying.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/02/15 08:16 PM, Steven Tardy wrote:> >> On Feb 23, 2015, at 6:34 PM, Ashley M. Kirchner >> <ashley at pcraft.com> wrote: >> >> I have a Dell server that has two built-in ethernet devices. When >> I kickstart the machine, they are correctly identified as eth0 >> and eth1 (correctly meaning they correspond to the physical >> device ports 1 and 2). I need a third one and want that to come >> up as eth2. After adding the hardware, kickstart now fails >> because for some reason it goes through a rename process where it >> makes the newly added card eth1 (or eth0, I forgot). Is there a >> way to stop this rename process so kickstart correctly uses the >> physical hardware the way they are, meaning physical port 1 = >> eth0, port 2 = eth1, and the additional ethernet card then >> becomes eth2? >> >> Should I be using the device's MAC address when I set the >> 'network' option in the kickstart file? So instead of 'network >> --device=eth0' I make it 'network -device=aa;bb:cc:dd:eee:ff' ? >> > > kickstart has an option: ksdevice=bootif > > I think that'll let you accomplish what you are trying.Totally unrelated, but this is the reason I love discussions like this getting into the archives. I had no idea this option existed and it just solved an annoying problems I've been trying to think how to solve for ages! In PXE's 'default'; LABEL new-node1 MENU LABEL ^1) New Node 1 - RHEL 6 KERNEL boot/rhel6/x86_64/vmlinuz IPAPPEND 2 APPEND initrd=boot/rhel6/x86_64/initrd.img ks=http://10.20.4.1/rhel6/x86_64/ks/pxe-ccrs-node2.ks ksdevice=bootif Then in kickstart; network --bootproto dhcp --onboot yes --hostname node1.example.com (not the lack of --device) With this, my nodes with 6 NICs reliably boot without asking the user to choose the NIC by MAC they want to install from. Thanks!! - -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJU7SnDAAoJECChztQA3mh0+dEQAMWM705Tc9fWr/ODiLDQNQHk 5todiurUcM72zPn3NCwiLTb/ZEXbnkL74Zy7qQPf8zzFryLIuldGMDIVIgVp5k3m LnkU9dW0zguXnCfde3gXJs8taYSAYA/ciwO9mE+M3V4+VU6TvzjPkVxKGkhTxjTL 5/DBz1N9V6IChRLbjcQbkHJD5gAPY0cloOoP6f0FC/k+Ojeo7oUibYQjVB8nDkwa cfxxJ2yYIjOkTBm7vQuLnHf64jR8siqN9Zw5gZuuTBfbK2gIuMw99Fg7/QAEe85h uQttjHloI1SfhYN4D5AuQzeXFXTUM3IIkRr4KzGCmKezGi4s+wDrhm4goNmsOuiH ruf80gDjW+PZADx2Q4GHPpCRe2sCyLXDFPdUrvooCLrInXFK1AmisLVNKJlGbRs3 2qIhO8PAGP8Kli/Dff7NZ5bfBZob2nbZ6CEG0Qv/UHHcNzrBdzMA0gdGsuOpwjSW oJjqtgu4jfXlNAkPZKIvUk1wYUhxAN/2AZ2kfriLOJCeT7QOxYawKXWTjhmcj/QM mZfJTDhebDtqR/WLgjlISQ/pzyKl+lUl0sV0+6FNM1pycPQSrv1yKAD9dMaDpUFA y0WU6MJ+nig6uIYVZ2W9DKGu7qJp6Ghdi+IcmqHFqu/XEnw2LuG0ox2D5NdEkbc9 Ulp4KQOLuU9gSwQKNrPh =YRky -----END PGP SIGNATURE-----
> I have a Dell server that has two built-in ethernet devices. When I > kickstart the machine, they are correctly identified as eth0 and eth1 > (correctly meaning they correspond to the physical device ports 1 and > 2). I > need a third one and want that to come up as eth2. After adding the > hardware, kickstart now fails because for some reason it goes through a > rename process where it makes the newly added card eth1 (or eth0, I > forgot). Is there a way to stop this rename process so kickstart > correctly > uses the physical hardware the way they are, meaning physical port 1 > eth0, port 2 = eth1, and the additional ethernet card then becomes > eth2? > > Should I be using the device's MAC address when I set the 'network' > option > in the kickstart file? So instead of 'network --device=eth0' I make it > 'network -device=aa;bb:cc:dd:eee:ff' ?ksdevice=aa;bb:cc:dd:ee:ff in your above example will ensure the device with that mac is the kickstart device.
On Thu, Feb 26, 2015 at 3:42 PM, Tom Brown <tom at eazyriders.no-ip.biz> wrote:> > ksdevice=aa;bb:cc:dd:ee:ff in your above example will ensure the device > with that mac is the kickstart device. > >Yeah, turned out bootif accomplishes the same thing, at least in my scenario. What happened afterwards though is different.