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
