Issue with Aquiring DHCP

[Jeremy Silver]

Do you have multiple ethernet interfaces?  Linux and the BIOS do not always
agree on which is the 'first' ethernet port(and therefore eth0) in the
system.  On some systems I have to use the second (as labeled on the server
chassis) ethernet port for kickstart  as Linux see it as eth0, or specify
eth1 as the ksdevice to use the first ethernet port.

-----Original Message-----
From: kickstart-list-bounces at redhat.com
[mailto:kickstart-list-bounces at redhat.com] On Behalf Of Andy Ciordia
Sent: Monday, June 07, 2004 10:41 AM
To: Discussion list about Kickstart
Subject: Re: Issue with Aquiring DHCP


Brian Long wrote:
> Does your switch have spanning tree port-fast enabled?  This tells the
> switch to disable spanning tree calculations for that port.  If not
> configured and spanning tree is enabled on your network, the time it
> takes your link to come up could be 30+ seconds and that's too long
> for "loader" to acquire an IP.
>

Sorry for being a bit dense atm, are you saying spanning tree port-fast
should be enabled?  As well, it does aquire the first pass, through
PXE's asking DHCP for an address, that is resolved immediatly.  Its the
second DHCP request which is when the install engages that stalls.

Currently on out Catalyst 5000:

!
#spantree
#uplinkfast groups
set spantree uplinkfast disable
#backbonefast
set spantree backbonefast disable
#vlan 208
set spantree enable     208
set spantree fwddelay 15    208
set spantree hello    2     208
set spantree maxage   20    208
set spantree priority 32768 208



--
Andy Ciordia, Network Engineer
Planned Giving Design Center (www.pgdc.com)
10800-D Independence Pointe Pkwy, Matthews, NC 28105
Ph: (704)849-0731 x106  |  Fax: (770)456-5239
--


_______________________________________________
Kickstart-list mailing list
Kickstart-list at redhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list