Kickstart doesn't work on 2+ NIC system with static IP's

Solution Verified - Updated -

Environment

  • Red Hat Enterprise Linux.
  • DHCP less network.
  • System with two nics, having second one connected to the LAN with access to kickstart server.

Issue

  • In a dhcp-less network kickstart hangs while gathering extra files.
  • Second nic is connected to the LAN that can reach kickstart server.
  • Kickstart defines network configuration for both nics as network --device=nic#.

Resolution

Root Cause

  • Anaconda needs access to the kickstart script.
  • ksdevice is used to define the network to use for kickstarting.
  • The procededure is as follows:
    • Anaconda configures ksdevice nic with commandline supplied arguments (ip, mask, gateway, dns) and then gathers kickstart file specified by ks=.
    • When anaconda reads the kickstart file, it finds network --device=nic1 and as no configuration is provided, it tries to use the one supplied on command line (which was configured for ksdevice), making nic1 misconfigured for routing default, etc, causing stage2 to be innacessible.

Diagnostic Steps

  • Check kickstart file for "network --device=nic#" lines on systems which require access to installation network on nic number greater than 1 (i.e. eth1 vs eth0)

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.