similar to: Network installation from CD

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

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

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

Hi, Has any one tried to merge a custom kernel into vmlinuz/initrd.img for Centos 5 kickstart? Or similar Linux distribution? I am rebuilding a custom kernel from stock kernel source to build some hardware modules into static form, so that the hardware detection sequence can be altered in a hard way. Quick examples are: tg3 drivers will be loaded before e1000, 3w-9xxx be loaded before

Hi all, First time here, so please be gentle! :) I'm trying to configure a system that will pxeboot and retrieve a kickstart file from a server based on that host's macaddress as part of my Edison project[0] however I'm having issues getting the dns lookup to work and I'm hoping you can help! My pxelinux.cfg/default file is as follows: ======================= default linux

Here is my script for post install if you want to try it. In order for the shuffling to not occur you do need to create the udev rules file somehow. I am not sure how mangled this will be in email but it is worth a try. It should run OK with nothing else. I have a better version in the works but the enhancements are mainly useful for Fedora 19-21. I did forget to say I also block

Hi, Is it possible to disable the clear screen when loading syslinux ? Since the IBM BIOS on xSeries systems shows the MAC address of the onboard NICs, I would like to have them on screen when people do a kickstart fro mthe prompt using eg: ksdevice=<MAC address> I personally think that the clear screen is unwanted in most cases since people can add that to the boot message (ctrl-L) if

Define out of order in this case just so I know for sure what you mean. What my solution does, or at least does reliably in my case, is make sure the interfaces are in the same order once installed as the install kernel saw them. It won't re-order them to be sequential based on bus, mac or driver. I am working on that but it will also include naming the devices based on the module

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

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

Greetings all, Is there currently any mechanism in pxelinux the would send a mac address of the pxe booted interface through to the linux kernel much like ipappend can send the ip address? Kickstarting a system with multiple interfaces can be troublesome. ksdevice is helpful but only in some circumstances such as forcing eth0, but that doesn't always work since probe order changes depending

Hi, Question number 3 :) I'd like to do something like this: display text.msg append text kssendmac ksdevice=eth1 ks=http://1.2.3.4/footprint/ default localboot label localboot localboot 0x80 label system?5 kernel vmlinuz append initrd=initrd.img ip=1.2.3.5 netmask=255.255.255.192 gateway=1.2.3.1 label system6 kernel vmlinuz append initrd=initrd.img ip=1.2.3.6

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

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'm looking for a tool that breaks a working system (in one or more ways) with the sole purpose to fix it again. The aim would be to use this tool for several debugging techniques sessions in our local LUG. When I was invited to speak at a local LUG I was wondering what was the best way to demonstrate some of the tools (and more importantly) the way to tackle a problem. And nothing

I have 3 machines, T60 thinkpad with e1000 NIC Dell PowerEdge 2950 with bnx2 NIC HP DL360 G4P with tg3 NIC All running xen 3.03 / 2.6.16.29-xen I have a netbootable image with 2.6.16.29-xenU. This image when it boots creates a vlan eth0.4002, and then tries to communicate on that interface to a central server. On the machines with e1000 an bnx2 NICs, this works fine. On the

On Mon, 13 Feb 2006, Omer Faruk Sen wrote: > Is it possible to embed more than one kickstart that will match the > installation interface's MAC address. What I want is to use boot system > using virtual CD (using iLO) to install multiple systems but matching > kickstart conf file will be used with the matching MAC address. I would look at creating special programs for syslinux

Thanks for that Jason but it didn't solve the problem. The system is still coming up with the interfaces shuffled. It seems to *always* want to use the added ethernet card as eth0. On Wed, Feb 25, 2015 at 1:37 PM, Jason Warr <jason at warr.net> wrote: > Starting back in RHEL/Cent 5 I found that the only way to make sure your > interface enumeration was consistent after install

Hi I am running a pxe diskless node in f13 and I have some proposals to make ovirt-early working in this version. nash is no more available (nash/mkinitrd is replaced by dracut), so this following command fails : "echo "network --device $DEVICE --bootproto dhcp" | nash" it makes the network configuration incomplete. I replace the linuxrc command by dhclient and it's

I totally agree with Luc Boudreau about this problem. On modern branded server they ALL use Broadcom chipset... I must admit that: a) lot of people are experiencing the problem but can tolerate it or b) someone already experienced this problem and solved it Lets'' approach the problem pragmatically... just start with a survey on the list. ... hope we solve this issue soon. Ivan