Originally Posted by swanyjim
awesome thanks for the reply.
I have added it to the the config in that section. However the machine does boot over the network and begins the install(look for the init image and such) then when it moves on durring the text portion of the install is when it hangs. Would it still matter at that point?
Personally I don't see the point of using fixed-address statements unless of course you're using DHCP to assign permanent IPs to the device, which I assume is why you're using it.
Anyway, if it gets beyond the PXE boot screen and goes into Anaconda to try and begin the kickstart process but doesn't proceed beyond network autoconfiguration the most likely problems are:
1. There are two or more ethernet devices in the server and anaconda is detecting a different ethernet device as eth0 versus whatever the PXE boot process detected first. If you're in an environment where you're constrained to a single ethernet drop per server, then try specifying the kickstart ethernet interface; e.g.,
... or ksdevice=eth1
... or ksdevice=eth2
then change your Kickstart file:
network --device eth1 ...
I'd suggest having multiple menu option lines for each ethX interface and kickstart file that specifies individual different ethernet ports.
2. If you happen to be using Cisco switches enable portfast on all non-trunking ports. Portfast will speed up the DHCP process greatly on Cisco switches.