On Thu, 2007-05-17 at 07:20 -0400, SSTinsley@xxxxxxxxxxxxxx wrote: > kickstart-list-bounces@xxxxxxxxxx wrote on 05/16/2007 08:28:48 PM: > > The reason you can get an IP and PXEboot is because the NIC is up > for > > more than 30 seconds, which gives the switch time to negotiate with > the > > NIC and turn up the port. When anaconda starts, it recycles the NIC > (to > > load the driver). If you have portfast issues, anaconda will > timeout > > before your switch makes the port live. > > > > Ananacoda will also recycle the NIC one more time after it gets the > > ks.cfg, but that one never causes portfast timeout issues. > > > > I here what your saying. I took your suggestion to the network guys > and they confirmed the > switch is configured correctly. So short of calling them liars, I am > pretty much at a > standstill and have to go with the ks.cfg on CDROM. you may want to add "nicdelay=40 linksleep=30" to you kernel command line. I didn't see that in any of your posts so I thought I'd mention it. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=189795 Note: you can add these to your ifcfg-eth0 conf file as well # No portfast, wait 30s LINKDELAY=30 # DISABLE stupid ZeroConf address NOZEROCONF=1 I've been on this list for a long time and been quite mostly but this is a long thread and I thought I would hop in share my thoughts with the rest of the Internet as well :) I'm not calling your networking team a liar, but in the same effect, you appear to be experiencing an issue where linkdelay and nicdelay my come in handy for you (works for both static and dhcp) -- - Kevin Landreth - RHCE - Sr. Systems Architect - The Planet (https://www.theplanet.com)
Attachment:
signature.asc
Description: This is a digitally signed message part
