This affects DHCP and a number of older mac protocols. If you look carefully at the logs, here's what seems to happen client send dhcp request via broadcast to 0.0.0.0 switch sees that 0.0.0.0 and does not seem to run spanning tree on it dhcp server sees request, does an offer client tries to switch to the IP in the offer to send a confirm back to dhcp server switch sees new ip at that port, runs spanning tree all over again. clients response back to server is never seen, as it disappears in the spanning tree timeout. Since the client can't confirm, it never comes up. The full spanning tree can take anywhere from 15-30 seconds here. (2900's) We've simply turned spanning tree off - our configuration is simple enough and static enough we don't need it. In the past what we had done was just gone ahead and configured ports 1-22 or so as portfast, and left the last 1-2 ports alone, and used these one or two ports as uplink ports. On Wed, Jun 13, 2001 at 12:57:08PM -0700, yiping@xxxxxxxxxxxxxx wrote: > I had the same problem kickstarting machines connected with Cisco switches. > With default port settings, those ports takes 10-15 sec to become active. > > I think the real problem is that dhcp client times out too fast . If it > waited longer, a solution will eventually come back from dhcp server. I > don't see an option for program pump to change its time-out period though. > Perhap RedHat engineers can make it stay longer during kickstart. > > Yiping > > -----Original Message----- > From: Ajay Shekhawat [mailto:ajay@xxxxxxxxxxxxxxxxx] > Sent: Wednesday, June 13, 2001 12:33 PM > To: kickstart-list@xxxxxxxxxx > Subject: Re: 3COM 3c905C and Kickstart > > > On Wed, Jun 13, 2001 at 08:37:37AM -0700, Taylor, ForrestX wrote: > > What does your ks.cfg look like at the network configuration? > > > > I just fixed the problem. Here's what was going on: > > The machine was connected to a Cisco 3524XL. In the file > Documentation/networking/vortex.txt, there is a note about Cisco 6509 > switches having a problem with the 3COM card. On a whim I tried the > same fix for this port on the Cisco switch, and it worked. > The trick is to change the "spanning tree" parameter to "portfast" for that > port. > > Hope this helps anybody who is in the same situation! > > Ajay > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/kickstart-list > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/kickstart-list -- Hunter Matthews Unix / Network Administrator Office: BioScience 222/244 Duke Univ. Biology Department Key: F0F88438 / FFB5 34C0 B350 99A4 BB02 9779 A5DB 8B09 F0F8 8438 Never take candy from strangers. Especially on the internet.
