similar to: kickstart ksdevice in centos6

-----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

On Fri, 3 Nov 2017, Mark Haney wrote: > On 11/01/2017 05:02 PM, James A. Peltier wrote: >> Leaving ksdevice= off the command line will prompt you for the location of >> the kickstart file and the device you want to use to kickstart >> > Well, things just got weird with this.? The first couple of times I included > the biosdevname etc, on the command line with

----- On 1 Nov, 2017, at 13:07, Chris Adams linux at cmadams.net wrote: | Once upon a time, Mark Haney <mark.haney at neonova.net> said: |> On 11/01/2017 03:25 PM, Chris Adams wrote: |> >Once upon a time, Mark Haney <mark.haney at neonova.net> said: |> >>Okay, so it looks like I can simply change ksdevice=eth0? to |> >>bootdev=eth0, correct? |> >I

Hi, I am currently struggling with the right way to configure a bonding device via kickstart (via PXE). I am installing servers which have "eno" network interfaces. Instead of the expected bonding device with two active slaves (bonding mode is balance-alb), I get a bonding device with only one active slave and an independent, non-bonded network device. Also the bonding device

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

On 11/01/2017 03:25 PM, Chris Adams wrote: > Once upon a time, Mark Haney <mark.haney at neonova.net> said: >> Okay, so it looks like I can simply change ksdevice=eth0? to >> bootdev=eth0, correct? > I believe you can just leave both off (IIRC for CentOS 6 as well) if you > add "ipappend 2" to the pxelinux stanza. > I probably should have clarified that

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=0 Yes! Actually, the other admin I work with and I were just

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

Hi all, Someone played with kickstart bonding with centos 6.4 ? CentOS 6.4, as upstream now support ifcae bonding in kickstart network section. I've an issue with configuring a second bonding iface in kicstart on CentOS 6.4. The first bonding (bond0) works as espected but the second is not configured during installation. I've a 6 nic server (two for "puclic" network, two for

Hello All, I seem to have run into a bug with the new --bridgeslaves=<INTERFACE> option. It would seem that if I tell the bridge device to use a virtual interface (like bond0) rather than a physical interface (em1/em2) that kickstart completely barfs on it. I have provided my network section below which works fine as long as i don't enable all the bridge content. When the

Hi, I'm kickstarting a vm in ESXi 5.1. ks.cfg is on floppy, install media is ISO file. This works great as long as I don't add an additional repo, in our case it is vmware tools on one of our webservers. If I add the repo line, anaconda asks then for the used network card and indeed, switching to console the interfaces are still unconfigured. Chosing eth0 in gui continues the

hello there, I wonder if you could help me: I am trying to install 50 diskless servers using PXE / kickstart, it all starts well, DHCP server issues a dynamic address, tftp issues the kickstart file, the client starts reading the KS file but at some point anaconda brings up an unhandled exception related to Python when reading Comps.xml?? What is really unsettling is the fact that if I plug

Starting back in RHEL/Cent 5 I found that the only way to make sure your interface enumeration was consistent after install with what you had during install was to create a udev rules file using the mac addresses as the key. It is easy to run a short script in postinstall to create it based on how anaconda has seen them. In order for this to work on Cent 6 you have to set biosdevname=0

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

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

Ok, so some of this now works, but I'm still having problems. With the bootif option, the system now correctly configures and uses the same interface to get its kickstart file. However, when the system is done and boots up, the interfaces are still messed up. So this is what I have in the kickstart file: # On-Board Port 1 with public IP configuration network --noipv6 --onboot yes --bootproto

<overly trimmed> On 02/25/2015 01:56 PM, Ashley M. Kirchner wrote: > Ok, so some of this now works, but I'm still having problems. With the > bootif option, the system now correctly configures and uses the same > interface to get its kickstart file. However, when the system is done and > boots up, the interfaces are still messed up. So this is what I have in the >

On 11/01/2017 05:02 PM, James A. Peltier wrote: > Leaving ksdevice= off the command line will prompt you for the location of the kickstart file and the device you want to use to kickstart > Well, things just got weird with this.? The first couple of times I included the biosdevname etc, on the command line with ksdevice=eth0 it worked perfectly.? Sometime yesterday (and I verified this a

How to use qemu with a network brdige The bridge should have dhcp Not nat

Once upon a time, Mark Haney <mark.haney at neonova.net> said: > On 11/01/2017 03:25 PM, Chris Adams wrote: > >Once upon a time, Mark Haney <mark.haney at neonova.net> said: > >>Okay, so it looks like I can simply change ksdevice=eth0? to > >>bootdev=eth0, correct? > >I believe you can just leave both off (IIRC for CentOS 6 as well) if you > >add