Broadcom NIC delays prevent DHCP during Kickstart

[Kevin Kwast]

In my case, sure, spanning tree is on because every 5324 switch is
interconnected with at least one other, and I haven't used the web interface
to repeatedly set STP off for every port that is connected to a host.  Maybe
the command line offers a way to turn off STP for 21 or 22 ports at a time
on each switch?  I know that STP can cause delays after bringing up the
ethernet link on a port, but Intel NICs don't seem to have this problem.  Is
there a way to keep the ethernet link up between when the PXE boot uses it
and the kickstarting Linux kernel tries to DHCP?  Or add 30 seconds to the
amount of time it waits before it does the DHCP?  Thanks!

On 10/19/06, Mann, Andrew <amann at ea.com> wrote:
>
>
> > Is spanning tree enabled on the switch?
>
>   Is there a conflict with the Broadcom NICs and spanning tree?  We're
> using a Cisco 4500 series switch with spanning tree enabled.  2550s,
> 1750s, 1850s, and 1955 blades are able to quickly bring the NIC up and
> start communicating.  2650s and 2950s have about a 30-60 second delay
> between the time the NIC is enabled and communication succeeds.  After a
> reboot, we have to run through and restart NTP on each of these types of
> system since this delay causes the ntp startup to fail.  It's only been
> mildly annoying in the past, but getting rid of it would be nice :)
>
>
> Andrew
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20061019/d7a51040/attachment.htm