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
Jerry Geis wrote:
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
Actually if I select eth0 and continue - I then get an error on screen about Unknown kickstart command ksdevice=eth0
jerry
On Fri, Jul 22, 2011 at 11:00:13AM -0400, Jerry Geis wrote:
Jerry Geis wrote:
I have a line in my kickstart file (ksdevice) ... ksdevice=eth0 ..
Actually if I select eth0 and continue - I then get an error on screen about Unknown kickstart command ksdevice=eth0
ksdevice is on the boot command line, not in the kickstart file
/usr/share/doc/anaconda-*/kickstart-docs.txt:
On Fri, 22 Jul 2011, Jerry Geis wrote:
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?
I use ksdevice= as a boot option (e.g., in the APPEND section of syslinux or pxelinux config).
On 7/22/2011 11:04 AM, Paul Heinlein wrote:
On Fri, 22 Jul 2011, Jerry Geis wrote:
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?
I use ksdevice= as a boot option (e.g., in the APPEND section of syslinux or pxelinux config).
How do you know which device is going to be eth0 at that point?
On Fri, 22 Jul 2011, Les Mikesell wrote:
I use ksdevice= as a boot option (e.g., in the APPEND section of syslinux or pxelinux config).
How do you know which device is going to be eth0 at that point?
That's a great question. Sadly, my answer is somewhat idiosyncratic and less likely to be of use in larger environments.
In our small-office environment, I rarely kickstart a new server until after I've booted it into a rescue environment. The initial boot allows me to inventory the MACs (for dhcp), adjust IPMI network settings, check for driver issues, and double-check to ensure that the hardware matches the order. (I've only had one case where a vendor shipped less RAM than we'd purchased, but I'm glad I identified the problem before I wrote any data to the hard drives.)
It's during the MAC inventory that I identify eth0, eth1, ... I've never had a case where the order in the initial boot environment didn't match the kickstart environment.
On 7/22/2011 12:15 PM, Paul Heinlein wrote:
On Fri, 22 Jul 2011, Les Mikesell wrote:
I use ksdevice= as a boot option (e.g., in the APPEND section of syslinux or pxelinux config).
How do you know which device is going to be eth0 at that point?
That's a great question. Sadly, my answer is somewhat idiosyncratic and less likely to be of use in larger environments.
In our small-office environment, I rarely kickstart a new server until after I've booted it into a rescue environment. The initial boot allows me to inventory the MACs (for dhcp), adjust IPMI network settings, check for driver issues, and double-check to ensure that the hardware matches the order. (I've only had one case where a vendor shipped less RAM than we'd purchased, but I'm glad I identified the problem before I wrote any data to the hard drives.)
I use ocsinventory-ng for this, but it doesn't report until everything including the agent is installed and on the right network.
It's during the MAC inventory that I identify eth0, eth1, ... I've never had a case where the order in the initial boot environment didn't match the kickstart environment.
I think nics that use the same driver or at least sets on the same card are detected in the same order. Ours tend to have at least a pair of Broadcomm and one or more pairs of Intels and the pairs tend to flip randomly until they are nailed down with a HWADDR= entry in the ifcfg-eth? file which must rename them after kernel detection.
-- Les Mikesell lesmikesell@gmail.com
On Fri, Jul 22, 2011 at 10:57 AM, Jerry Geis geisj@pagestation.com wrote:
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?
"ksdevice=..." shouldn't be in the kickstart file but on the installer's kernel line if you're cd-booting or on the append line if you're pxe-booting.
-
Jerry Geis -
Les Mikesell -
Paul Heinlein -
Tom H -
Tru Huynh