<tt>kickstart-list-bounces@redhat.com wrote on 05/17/2007 08:46:19 AM: > On Thu, 2007-05-17 at 07:20 -0400, SSTinsley@upsfreight.com wrote: > > kickstart-list-bounces@redhat.com 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 </tt> <tt>While this may solve the problem (and I will try it if I have time), I think</tt> <tt>the thread shows that there is an issue. The fact that DHCP works fine during</tt> <tt>the PXE boot and download of the kernel and fails in Anaconda should be</tt> <tt>reason enough to a fix to be made. Make the DHCP operate consistently during the</tt> <tt>whole process.</tt> <tt>Thanks for your help</tt> <DIV> NOTE: THIS DOCUMENT MAY CONTAIN CONFIDENTIAL AND NONPUBLIC INFORMATION. IT IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL(S) OR ENTITY(IES) NAMED ABOVE, AND OTHERS SPECIFICALLY AUTHORIZED TO RECEIVE IT. If you are not the intended recipient of this document, you are notified that any review, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify me immediately by return email, delete the electronic message and destroy any printed copies. Thank you for your cooperation. </DIV>