similar to: Kickstart ksdevice question

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

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

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

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

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

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

I have a line in my kickstart file (ksdevice) # Network information network --bootproto=dhcp --device=eth0 --onboot=on # Default network to boot ksdevice=eth0 # Auto reboot (to being next install faze) reboot However its still poping up and asking me eth0 or eth1 for install? Has this operation changed? Thanks, Jerry

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

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

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. -- Chris Adams <linux at cmadams.net>

I'm under a bit of a crunch here, so any immediate help would be appreciated. We kickstart our customer boxes and have started migrating to CentOS 7. We're running Radiator 4.6 1 (I know, but bear with me) and we just deployed our first radius box to a customer to be turned up today. (I know, I know. I had no idea it wasn't being tested sooner than this.) I was brought in

We have a couple of CentOS 7 boxes that were built before I was hired to clean up the kickstart script used for C7 boxes. We had a couple of rpm packages that were pre-C7 that were used and setup the old SysV Init way using ntsysv and chkconfig on these boxes. (I finally fixed that in the newer scripts.) These are out in the field and I'm having to deal with them as they are. One thing

Hi, kickstarting fails due to problems with host resolution, even though the network seems to be properly configured through DHCP. eno1 and eno2 are both attached to the network, but only eno1 gets an IP via DHCP. Still `curl` cannot resolve the mirror host and the kickstart host during dracut-initqueue: rdsosreport.txt ------------------------------------------------ [...] [ 14.780428]

I have successfully set up a very nice kickstart install with the i386 version of CentOS 4.3 and it works great. I am using a custom kickstart script and the kernel and initrd from disc1/images. But when I try to duplicate this for a 64 bit setup (changing paths in my tftp server, ks.cfg, etc to point to the 64 bit stuff) it successfully tftp's everything just as it should (tethereal

Hi all, I've got an issue with C6's dhcpd custom logging that I cannot figure out. Hopefully someone has an idea, or has seen a similar issue. We have dhcpd logging to /var/log/messages a custom header (DHCPUSER:) with MAC, IP and Circuit-ID. I'll not bore you with the guts, so here's the beginning of that line in dhcpd.conf: if exists agent.circuit-id { log (info,

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

I can't seem to find anything clear on this, but is the C7 version of BIND 9.9 built with Request Rate Limiting? -- Mark Haney Network Engineer at NeoNova 919-460-3330 option 1 mark.haney at neonova.net www.neonova.net

I know this is for CentOS stuff, but I'm at a loss on how to build a script that does what I need it to do.? It's probably really logically simple, I'm just not seeing it.? Hopefully someone will take pity on me and at least give me a big hint. I have a file with two columns 'email' and 'total' like this: me at example.com 20 me at example.com 40 you at domain.com