This should be easy to answer (I hope).? We routinely kickstart boxes to use for managing our customers RADIUS/DHCP configurations (along with other things).? We've had a C7 kickstart in place since I built one in May and are finally starting to roll it out for new installations.? But, I'm curious as to what ksdevice= actually does. With the C6 we routinely used ksdevice=eth0 since we ship boxes with two NICs and knew interface 1 was always eth0.? With C7 comes the interface naming convention changes and that's where questions have arisen about that option.? It's been set as ksdevice=eno1 since I know these servers name the interfaces with the eno# convention (integrated dual-port).? A coworker of mine insists on setting it ksdevice=enp2s0 which doesn't seem to work like it should (though, it could be a fault netinstall image, I'm not sure yet).? In all honesty, we'd prefer to keep the eth# convention for C7 like C6. So, my question is, does setting ksdevice=eth0 dictate to the system the names of the interfaces?? Is that just a name for the install process and the kickstart script assigns names?? (We have the kickstart script setting them as eno1 and eno2, btw.) I've googled this to no end and haven't found a satisfactory answer.? So, I'm hoping someone with more KS experience than I can explain it. -- Mark Haney Network Engineer at NeoNova 919-460-3330 option 1 mark.haney at neonova.net www.neonova.net
Hello, ksdevice specifies which NIC to be used during the network install. The new naming conventions indeed make this more complicated than it needs to be. To go back to the old naming scheme (eth0, eth1 ...) just add this to boot parameters (kernel cmdline): biosdevname=0 net.ifnames=0 HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message -----> From: "Mark Haney" <mark.haney at neonova.net> > To: "CentOS mailing list" <centos at centos.org> > Sent: Wednesday, 1 November, 2017 12:45:45 > Subject: [CentOS] Kickstart ksdevice question> This should be easy to answer (I hope).? We routinely kickstart boxes to > use for managing our customers RADIUS/DHCP configurations (along with > other things).? We've had a C7 kickstart in place since I built one in > May and are finally starting to roll it out for new installations.? But, > I'm curious as to what ksdevice= actually does. > > With the C6 we routinely used ksdevice=eth0 since we ship boxes with two > NICs and knew interface 1 was always eth0.? With C7 comes the interface > naming convention changes and that's where questions have arisen about > that option.? It's been set as ksdevice=eno1 since I know these servers > name the interfaces with the eno# convention (integrated dual-port).? A > coworker of mine insists on setting it ksdevice=enp2s0 which doesn't > seem to work like it should (though, it could be a fault netinstall > image, I'm not sure yet).? In all honesty, we'd prefer to keep the eth# > convention for C7 like C6. > > So, my question is, does setting ksdevice=eth0 dictate to the system the > names of the interfaces?? Is that just a name for the install process > and the kickstart script assigns names?? (We have the kickstart script > setting them as eno1 and eno2, btw.) > > I've googled this to no end and haven't found a satisfactory answer. > So, I'm hoping someone with more KS experience than I can explain it. > > -- > Mark Haney > Network Engineer at NeoNova > 919-460-3330 option 1 > mark.haney at neonova.net > www.neonova.net > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos
Once upon a time, Mark Haney <mark.haney at neonova.net> said:> This should be easy to answer (I hope).? We routinely kickstart > boxes to use for managing our customers RADIUS/DHCP configurations > (along with other things).? We've had a C7 kickstart in place since > I built one in May and are finally starting to roll it out for new > installations.? But, I'm curious as to what ksdevice= actually does.It just sets the NIC that the installer tries to bring up to fetch a kickstart file from the network (and then the rest of a network install, if you don't override it in the kickstart). If you are PXE booting using pxelinux, add "ipappend 2" to your pxelinux.cfg stanza and "ksdevice=bootif" to the append line. With that, pxelinux will add the MAC address of the PXE NIC to the kernel command line, and the installer will pick that up and use the matching interface for the rest of the kickstart. -- Chris Adams <linux at cmadams.net>
Nux! wrote:> Hello, > > ksdevice specifies which NIC to be used during the network install. > > The new naming conventions indeed make this more complicated than it needs > to be. To go back to the old naming scheme (eth0, eth1 ...) just add this > to boot parameters (kernel cmdline): > biosdevname=0 net.ifnames=0Yes! Actually, the other admin I work with and I were just bitching about that a few minutes ago. I have no idea who thought the new enpxsyz was a "good idea", but for 99% of us, I look at the back of a system, and I want to know which one. the enxyz is significantly less than useful. Now, if only there were some tool, like there used to be HERD, to figure out on my supermicro which DIMM is complaining.... You'd think IMPI would do it, but nooooo.... mark> > HTH > Lucian > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > ----- Original Message ----- >> From: "Mark Haney" <mark.haney at neonova.net> >> To: "CentOS mailing list" <centos at centos.org> >> Sent: Wednesday, 1 November, 2017 12:45:45 >> Subject: [CentOS] Kickstart ksdevice question > >> This should be easy to answer (I hope).? We routinely kickstart boxes to >> use for managing our customers RADIUS/DHCP configurations (along with >> other things).? We've had a C7 kickstart in place since I built one in >> May and are finally starting to roll it out for new installations.? But, >> I'm curious as to what ksdevice= actually does. >> >> With the C6 we routinely used ksdevice=eth0 since we ship boxes with two >> NICs and knew interface 1 was always eth0.? With C7 comes the interface >> naming convention changes and that's where questions have arisen about >> that option.? It's been set as ksdevice=eno1 since I know these servers >> name the interfaces with the eno# convention (integrated dual-port).? A >> coworker of mine insists on setting it ksdevice=enp2s0 which doesn't >> seem to work like it should (though, it could be a fault netinstall >> image, I'm not sure yet).? In all honesty, we'd prefer to keep the eth# >> convention for C7 like C6. >> >> So, my question is, does setting ksdevice=eth0 dictate to the system the >> names of the interfaces?? Is that just a name for the install process >> and the kickstart script assigns names?? (We have the kickstart script >> setting them as eno1 and eno2, btw.) >> >> I've googled this to no end and haven't found a satisfactory answer. >> So, I'm hoping someone with more KS experience than I can explain it. >> >> -- >> Mark Haney >> Network Engineer at NeoNova >> 919-460-3330 option 1 >> mark.haney at neonova.net >> www.neonova.net >> >> _______________________________________________ >> CentOS mailing list >> CentOS at centos.org >> https://lists.centos.org/mailman/listinfo/centos > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >
On Wed, 2017-11-01 at 08:45 -0400, Mark Haney wrote:> This should be easy to answer (I hope). We routinely kickstart boxes > to > use for managing our customers RADIUS/DHCP configurations (along > with > other things). We've had a C7 kickstart in place since I built one > in > May and are finally starting to roll it out for new installations. > But, > I'm curious as to what ksdevice= actually does. >Strictly speaking it is depricated https://anaconda-installer.readthedocs.io/en/latest/boot-options.html#d eprecated-options Regards, Tris ************************************************************* This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify postmaster at bgfl.org The views expressed within this email are those of the individual, and not necessarily those of the organisation *************************************************************
Once upon a time, Tristan Hoar <TrisHoar at bgfl.org> said:> Strictly speaking it is depricated > https://anaconda-installer.readthedocs.io/en/latest/boot-options.html#d > eprecated-optionsYeah, looking at my kickstart setup, I don't actually specify it anymore because it is automatic. The important thing is adding the "ipappend 2" to the pxelinux stanza. -- Chris Adams <linux at cmadams.net>
On 11/01/2017 01:57 PM, Tristan Hoar wrote:> > Strictly speaking it is depricated > https://anaconda-installer.readthedocs.io/en/latest/boot-options.html#d > eprecated-options > > Regards, > > Tris >Okay, so it looks like I can simply change ksdevice=eth0? to bootdev=eth0, correct? -- Mark Haney Network Engineer at NeoNova 919-460-3330 option 1 mark.haney at neonova.net www.neonova.net
Reasonably Related Threads
- Kickstart ksdevice question
- Kickstart ksdevice question
- getting a CentOS6 VM on VMware ESXi platform to recognize a new disk device
- I Have Multiple Ips But Can Only Telnet to One Interface. Not the subinterface. How to Fix?
- Is there a way to detect/validate DHCP static IP assignment?