Trouble with RHN Provisioning/Kickstart

Latest response

Is there a correct way to handle multiple NICs in the RHN kickstart/provisioning?

 

Under Kickstart > Profiles > Kickstart Details > Advanced Options

I have my network stuff for setting a static IP on eth0, but when I tried to provision the system, during the kickstart it asked for the network details.  I think this is because the system has two NICs, eth0 and eth1.

 

Kickstart network line that it was provisioned with:

network --onboot yes --device eth0 --bootproto static --ip 192.168.1.2 --netmask 255.255.255.0 --gateway 192.168.1.1 --nameserver 192.168.1.1 --hostname hostname.domainname

 

After having to specify the network settings during boot, the resulting anaconda-ks.cfg file has two lines:

network --onboot yes --device eth0 --bootproto static --ip 192.168.1.2 --netmask 255.255.255.0 --gateway 192.168.1.1 --nameserver 192.168.1.1 --hostname hostname.domainname

network --onboot no --device eth1 --noipv4 --noipv6 --hostname hostname.domainname

 

How do I resolve this so it doesn't prompt for the network info and works with the line it is given?

 

network --onboot yes --device eth0 --bootproto static --ip 160.129.39.199 --netmask 255.255.255.224 --gateway 160.129.39.193 --nameserver 160.129.6.22 --hostname queso.mc.vanderbilt.edu
network --onboot no --device eth1 --noipv4 --noipv6 --hostname queso.mc.vanderbilt.edu

 

network --onboot yes --device eth0 --bootproto static --ip 160.129.39.199 --netmask 255.255.255.224 --gateway 160.129.39.193 --nameserver 160.129.6.22 --hostname queso.mc.vanderbilt.edu
network --onboot no --device eth1 --noipv4 --noipv6 --hostname queso.mc.vanderbilt.edu

Responses