Kickstart network interface identification

Issues related to configuring your network
Post Reply
User avatar
invade
Posts: 5
Joined: 2020/02/26 14:26:51

Kickstart network interface identification

Post by invade » 2020/02/28 14:08:43

Hi.

I can see a number of other threads on this subject, but none as far as I can see that are identical to the issue we have.

We build systems via Kickstart using the netinstall / boot ISOs.

To date we've been stuck on CentOS 6 and this works fine. We boot to the ISO and then add the following boot options:

ks=https://{Host for the Kickstart file}/{Name of Kickstart file} ksdevice={Interface Name, eg. eth0} ip={IP Address} netmask={Net Mask} gateway={Gateway IP Address} dns={DNS IP Addresses (comma separated)}

We are now testing the same process with CentOS 8. In this version, the network options for a static IP address are:
inst.ks=https://{Host for the Kickstart file}/{Name of Kickstart file} ip=ip::gateway:netmask:hostname:interface:none nameserver={DNS IP Addresses (comma separated)}

(sourced from https://access.redhat.com/documentation ... tion/index)

The problem have is identifying the "interface" name to use in the boot option.

Initially I tried using the old naming convention, eth0, and also "link" but both of these resulted in the system booting to an emergency shell because it looks like the network interface doesn't get activated.

After a few attempts at this I eventually ran the "ip link" command from the emergency shell and got the predictable network interface name for the device, ens32, used this in the boot options and it worked OK.

So, my question is, how are we supposed to know what the "Predictable Network Interface Name" is in advance, so we can use it in the boot options?

I hope that made sense.

Thanks in advance.

User avatar
TrevorH
Forum Moderator
Posts: 28026
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Kickstart network interface identification

Post by TrevorH » 2020/02/28 16:12:00

You can turn it off if that makes a difference (in the FAQ, net.ifnames=0 biosdevname=0). Otherwise I've found no predictable way to predict the predictable name ;-)
CentOS 6 will die in November 2020 - migrate sooner rather than later!
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 is dead, do not use it.
Full time Geek, part time moderator. Use the FAQ Luke

User avatar
invade
Posts: 5
Joined: 2020/02/26 14:26:51

Re: Kickstart network interface identification

Post by invade » 2020/02/28 16:17:29

Thanks for the response.

Can you tell me which FAQ you are referring to as I cannot find anything.

User avatar
TrevorH
Forum Moderator
Posts: 28026
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Kickstart network interface identification

Post by TrevorH » 2020/02/28 22:38:16

CentOS 6 will die in November 2020 - migrate sooner rather than later!
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 is dead, do not use it.
Full time Geek, part time moderator. Use the FAQ Luke

User avatar
invade
Posts: 5
Joined: 2020/02/26 14:26:51

Re: Kickstart network interface identification

Post by invade » 2020/03/02 15:01:32

We skipped el7 and so had missed this FAQ.

I can confirm that the suggested options work as required. Many thanks.

This thread can now be closed.

Post Reply

Return to “CentOS 8 - Networking Support”