On a cisco switch: First trace the Ethernet cable from the problem server to the port on the switch and note it down. Log into the switch and run something similar to this: --- enable configure terminal interface <INT_TYPE><PORT_NUM> switchport mode access spanning-tree portfast exit exit write memory exit --- where <INT_TYPE> is fastethernet for 10/100 mbps ports and gigabitethernet for 1000 mbps ports and <PORT_NUM> is the port number you wrote down. you will need something like '0/' directly in front of the port number typically on single switches and sometimes '1/0/'. on stacked switches and blade based switches the '1' in '1/0/' may need to be changed to reflect witch switch in the stack or which blade number in the blade chassis.
Your network admin should be able to explain or take care of this for you. HTH byron -----Original Message----- From: cobbler-boun...@lists.fedorahosted.org [mailto:cobbler-boun...@lists.fedorahosted.org] On Behalf Of Dan White Sent: Thursday, November 10, 2011 8:23 PM To: cobbler mailing list Subject: Re: Weird Kickstart Problem In Search of a Clue Where do I add this option ? On Nov 10, 2011, at 4:09 PM, antonio teixeira gomes jr wrote: > Hey Sr, > > I have had this problem a simple kickstart system before, and t was > related to reverse DNS resolution, in my case as it was a simple > environment I just used the option dns=nodns > > > From: bpe...@secureworks.com > > To: cobbler@lists.fedorahosted.org > > Subject: RE: Weird Kickstart Problem In Search of a Clue > > Date: Thu, 10 Nov 2011 20:37:15 +0000 > > > > I too have run into this issue. Just like Orion, the solution for me was > > 'spanning-tree portfast' on the switch port itself on our Cisco switches. > > The issue seems to be compounded by the fact that kickstart installs seem > > to insist on requesting a DHCP address 3 times during the install process. > > Which I think is why the install will sometimes progress further only to > > fail again at a later point. > > > > > > byron > > > > -----Original Message----- > > From: cobbler-boun...@lists.fedorahosted.org > > [mailto:cobbler-boun...@lists.fedorahosted.org] On Behalf Of Orion > > Poplawski > > Sent: Thursday, November 10, 2011 1:25 PM > > To: cobbler mailing list > > Subject: Re: Weird Kickstart Problem In Search of a Clue > > > > On 11/10/2011 09:47 AM, Dan White wrote: > > > I have set up a cobbler server to kickstart/build HP ProLiant > > > boxen of various flavors with RHEL5 > > > > > > I have a particularly stubborn DL380 G5 that refuses to be > > > PXE-booted/net-installed > > > > > > I suspect a FUBAR from the guy that manages the DNS/DHCP, but I need more > > > evidence. > > > > > > When it tries to PXE-boot, I get "PXE-E11: ARP Timeout" a few > > > times and then, maybe, it will proceed _______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler _______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
