Displaying 20 results from an estimated 10000 matches similar to: "kickstart question with 2 network cards"
2011 Jul 22
3
kickstart ksdevice in centos6
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
2015 Feb 25
2
Kickstart with multiple eth devices
-----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
2017 Apr 18
2
anaconda/kickstart: bonding device not created as expected
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
2008 Apr 25
2
PXE / Kickstart / nfs ....
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
2008 Feb 05
4
Kickstart stops with dialog about which networking device - how to avoid
Using a kickstart file that stops with a curses dialog "You have multiple
network devices on this system. Which one do you want to install through?"
The machine being configured with PXEboot has two ethernet interfaces. What's
missing from the network entries below? I'd like this install to proceed
without asking which ethernet interface.
PXE begins the install with DHCP, so
2012 Dec 07
2
Questions on making a kickstart cfg
So I took the anaconda cfg, commented out the partition/disk pieces and
ran it off my repo server and it almost worked.
Little things like not including things I had done on network setup. No
first boot.... :)
So now I am reading up on building a kickstart cfg
http://wiki.centos.org/TipsAndTricks/KickStart
http://www.centos.org/docs/5/html/5.2/Installation_Guide/s1-kickstart2-howuse.html
2013 Mar 18
1
CentOS 6.4 kickstart bonding
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
2015 Feb 23
7
Kickstart with multiple eth devices
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
2010 Jan 05
2
bind & kickstart
Anyone know what's up w/ trying to install bind through kickstart?
I am trying all variations of group installs, individual package
installs and it just won't install, it either fails on the libs, the
chroot pkg or whatever?
2015 Jun 25
1
Possible bug in kickstart
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
2015 Feb 26
2
Kickstart with multiple eth devices
On Thu, 26 Feb 2015 13:42:57 -0600, Ashley M. Kirchner <ashley at pcraft.com>
wrote:
> And after picking this back up this morning .... still no dice. I have
> now
> blacklisted the one module that would enumerate the add-in ethernet port
> so
> that is no longer an issue during the kickstart process, however the
> following is now happening:
>
> - kickstart
2017 Nov 01
6
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
2006 Aug 12
3
Problems with x86_64 kickstart
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
2008 Aug 16
0
kickstart and 5.2 x86_64 giving errors.
When I use my kickstart file (which works on 5.1 x86_64) with 5.2 I get
the following error.
I put my kickstart file at the end.
Do I have something incomaptible in the file?
jerry
--------------------------------------
Traceback (most recent call first):
File "/usr/lib/anaconda/network.py", line 341, in lookupHostname
ret = isys.pumpNetDevice(dev.get('device'),
2008 Sep 27
2
Why i can't configure network and hostname with this kickstart file?
Hi, all.
I use this kickstart file to install CentOS 5.2 (both i386 and x86_64),
but i can't config NICs and hostname during installation, what's wrong
with it?
Thanks very much.
----<- kickstart file ----<----
# System authorization information
#auth --useshadow --enablemd5
# System keyboard
#keyboard us
# System language
#lang en_US
# Installation logging level
#logging
2017 Nov 01
2
Kickstart ksdevice question
----- 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
2006 Dec 25
2
Kickstart Questions
Hi,
We dont run DHCP in our environment where I build our servers, is it
required to get a first IP address to hit my kickstart server running on
my xandros debian laptop? Just been a couple years since I last did some
kickstart builds and I dont have system-config-kickstart running on a
machine here in my home lab.
I can turn on DHCP on my linux laptop perhaps, but just wanted to check
in
2008 Mar 29
1
Open VPN connection problem on Virtual Box
Hi All,
I am working on a mystery. I am using
openvpn-2.1_beta7-gui-1.0.3-install on all
the computers in question. All computers
are running XP-Pro-SP2. (Mine is running
in a virtual window -- details below.)
This configuration works perfectly from my office.
I use it to call five facilities:
remote aa.bb.cc.dd
port 5030
proto udp
dev tap
ifconfig 192.168.240.30 255.255.255.0
secret
2008 Feb 06
2
kickstart %post not executed
Hi all,
I am trying to automate the provisioning of a few VM, dom0 CentOS5 - domU
CentOS4.5, the installation goes well but it completely ignores the %post
bit in the kickstart:
# Kickstart file for a generic VM
install
url --url http://server/mrepo/centos4-x86_64/disc1
cmdline
skipx
reboot
# Partition information
.....
# General system config
bootloader --location=mbr
keyboard uk
lang
2017 Nov 03
1
Kickstart ksdevice question
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