Well, sort of. The idea is to have the kickstart be fully remote and
non-interactive, so going up there to physically disconnect one of the
interfaces doesn't really solve the problem, since I could just as
easily go up there to put a static IP into the dialog box. I just want
to avoid going up there at all.
Unfortunately, the network architecture here is a little strange, and it
precludes me from supplying a DHCP address for eth1 like I do for eth0.
It has to do with the DHCP server's eth1 (same physical segment as the
node's eth1) having two VLANs attached to it with separate static IP
addresses and custom MTUs. So, without being able to attach the eth1
address to at least one of those VLAN numbers, and set the MTU, all
before the ks.cfg file is retrieved, there doesn't seem to be a way of
using DHCP for my solution. Unfortunately, as I said before, this
network architecture is out of my control, so I just have to figure it out.
Some of our nodes have Platform Rocks on them, though, and they somehow
do the very thing I'm trying. I can't figure out how they do it,
though. If anyone can point me the right direction for that
investigation, that'd be great too.
Thanks,
Lloyd
Harry Mills wrote:
Hi,
If you only have one interface physically connected to the network (eth0) then try this:
linux ks=nfs:nfs_server:/path/to/ks.cfg ksdevice=link
This will get ks to use the interface which has a link.
Not sure if that is what you are looking for but I have to set up boxes with 3 nics - only one of which is connected to a network - works well for me.
Regards
Harry
On Thu, 25 Aug, Lloyd T Brown wrote:
Hey all.
Admittedly, I'm new to this whole kickstart thing, but I can't seem to
find an answer to my question anywhere else. For reasons that are out
of my control, I can't provide a DHCP address to the eth1 interface on
the node I'm trying to install. I don't need the eth1 interface to
perform the installation, so I'd like disable it using a kernel
parameter so that the step of configuring the eth1 interface during
kickstart (before it retrieves the ks.cfg over the network) is
non-interactive. This is the last thing I need to do to make my
configuration fully non-interactive and fully remote. Essentially I
need something like this, although I'm making up the parameters:
linux ks=nfs:nfs_server:/path/to/ks.cfg ksdevice=eth0 disable_eth1
Alternatively if someone has a way to specify a static address as a
kernel parameter, that'd be okay too.
Anyone have any ideas?
Thanks,
Lloyd Brown
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list
