similar to: Kickstart with a VLAN interface

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

On 18/04/2017 15:54, Frank Thommen wrote: > 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

I've searched around but haven't found a definitive answer yet, is it possible to kickstart from a tagged VLAN? I found this bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=431915 But I can't find out how far the vlan support goes. I haven't found anything about it in any kickstart docs. I have two tagged vlans: Vlan 100 - server subnet Vlan 101 - backup subnet From

Hello! I would like to use the new bonding feature of kickstart in release 6.4. My setup is one bonding interface (bond0) with two (eth0, eth1) ethernet cards. I am using two VLANs on bonding interface so I have no IP for bond0 but have IPs for bond0.1 and bond0.2. If I create config by hand it works. Now I would like to convert my kickstart file using the new bonding feature. The kickstart

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

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

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

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

Nope, it doesn't add it to the kernel boot parameters. That was the first thing I checked. As for the bootproto ... DUH. I didn't check that. :) That being solved, yeah it's not bringing up the add-in card now when it boots up. On Thu, Feb 26, 2015 at 12:50 PM, Jason Warr <jason at warr.net> wrote: > > > On Thu, 26 Feb 2015 13:42:57 -0600, Ashley M. Kirchner

hello all, I have been trying to set-up bridged network with VLAN and not able to succeed as many tutorials address only single NIC. I am trying to setup 2 guests (backtrack instance) each guest has NIC1 and NIC2. following is snippet for guest1 I am not able to get 192.168.0.2 address back on guest eth0. VIRT-MANAGER GUI : guest1-lan details radio button left side panel NIC1

Hi, I encountered a problem when creating a VLAN interface according to the Red_Hat_Enterprise_Linux-7-Networking_Guide. I configuered the parent interface ifcfg-eno1 as follows: DEVICE=eno1 TYPE=Ethernet BOOTPROTO=none ONBOOT=yes And I created a new file named ifcfg-eno1.5, the content is: DEVICE=eno1.5 BOOTPROTO=none ONBOOT=yes IPADDR=192.168.81.3 PREFIX=24

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 completes successfully using the machine's physical port 2 (or eth1) which is on a subnet with DHCP - when the system reboots, it

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

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

Hi all, I use CentOS5.x + Xen in production for virtualization. I use it with bridged vlan networks and bonding (active-backup) like that: eth0 eth1 | | ------- | bond0-------bond0.10---------bond0.12 ... | | | | vlanbr10 vlanbr12 dom0 | | ------------- -------------- | |

If the vlan kernel argument is provided, then it is used during networking auto-configuration. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- scripts/ovirt-config-networking | 56 ++++++++++++++++++++++++++++++++------ scripts/ovirt-early | 7 ++++- 2 files changed, 53 insertions(+), 10 deletions(-) diff --git a/scripts/ovirt-config-networking

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

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'),

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

I am using kickstart to automate installs. working nicely. I now have a box with 2 NIC cards and I am getting prompted for which nick to use. I have a line like: network --device eth0 --bootproto dhcp --hostname tmp.msgnet.com in my kickstart. This line does not seem to be enough to say install with eth0 even though there may be an eth1. How do I tell kickstart to not prompt for which network