Kick start - Tips for network interface selection

Kick start - Tips for network interface selection:

Use a specific network interface for kickstart:

When your system has more than one network interface anaconda asks you which one you'd like to use for the kickstart process. 
This decision can be made at boot time by adding the ksdevice paramter and setting it accordingly. 

1.ksdevice=eth?? - To run kickstart via eth0 simply add ksdevice=eth0 to the kernel command line.

2.ksdevice=link  -  second method is using ksdevice=link. In this case anaconda will use the first interface it finds that has a active link.

3.ksdevice=bootif -  third method works if you are doing PXE based installations. Then you add IPAPPEND 2 to the PXE configuration file and use ksdevice=bootif. In this case anaconda will use the interface that did the PXE boot (this does not necessarily needs to be the first one with a active link).

Within the kickstart config itself you need to define the network interfaces using the network statement. If you are using method 2 or 3 then you don't know which device actually will be used. If you don't specify a device for the network statement anaconda will configure the device used for the kickstart process and set it up according to your network statement.

Forcing kickstart to ask for network configuration

There is a undocumented option that enable a prompt asking for network configuration during the installation. At the network statement, put the query keyword at the --bootproto= networking configuration, as we see below:

network --device=eth0 --bootproto=query

And a dialog box will appear asking for IP addressing, as well the hostname configuration.

Post a Comment