Issues with using kickstart to program more than 1 NIC on boot

Issues related to configuring your network
ugatorf
Posts: 5
Joined: 2017/04/15 02:01:00

Re: Issues with using kickstart to program more than 1 NIC on boot

Post by ugatorf » 2017/04/18 13:34:54

Well, ens is missing because with the system-config-kickstart tool, you actually specify your own interface name. I chose eth0 and 1, but I could have just as easily typed eth0 and ens4, which is what CentOS defaults to during both a manual and an automatic install.

I will need to look into the script some more. I am new to kickstart and I haven't had much of a chance to work with postinstall scripts.

User avatar
jlehtone
Posts: 4523
Joined: 2007/12/11 08:17:33
Location: Finland

Re: Issues with using kickstart to program more than 1 NIC on boot

Post by jlehtone » 2017/04/18 14:03:15

If one can name interfaces, then I would use descriptive names like "data" and "man". No digits.

If the auto-generated eth/ens names depend on hypervisor device model, and names are different, then why the two interfaces do use different models?

hunter86_bg
Posts: 2019
Joined: 2015/02/17 15:14:33
Location: Bulgaria
Contact:

Re: Issues with using kickstart to program more than 1 NIC on boot

Post by hunter86_bg » 2017/04/18 16:59:54

As per the discussion in RHEL forum , you need to pass the following kernel parameter in the VM's grub line

Code: Select all

net.ifnames=0 
in order to disable the new naming convention.That's what this postinstall script (in my previous message) should do. Then the kernel will name the first device eth0 , second eth1 and so on in order they are defined in the VM's configuration. I haven't tried it , but it's worth trying.

Post Reply