RE: Unable toget any httprequests: Unable toretreive netstg2.imgfile

["Mukarram Syed" <muksyed@xxxxxxxxxxxx>]

Hi All,

 

Since I started this thread, let me finish it.

 

I got it to work.  Thanks to everyone in this list.  I couldn’t have done it without your help.

 

There were 3 problems:

 

1.                   Spanning Tree/portfast was not enabled on the switch ports.

2.                   I was working on Dell PE2950’s.  They have a Link Enumeration issue. NIC Port1 becomes eth1 and NIC port2 becomes eth0.

Hence, what I did was this in my default file:

 

label 1

  kernel ENT_LINUX_64/vmlinuz

  append nofb ks=http://171.67.39.130/ENT_LINUX_64/Enterprise/ks.cfg initrd=ENT_LINUX_64/initrd.img ramdisk_size=10000 lang= devfs=nomount ramdisk_size=9216 ksdevice=eth1 console=ttyS0,9600 ipappend 1

 

I changed ksdevice=link to ksdevice=eth1

 

3.       The third problem was I had to change the following link in my ks.cfg file to reflect eth1 instead of eth0

network --bootproto=dhcp --device=eth1

 

That was it

 

Thanks again.

 

-Mukarram.

 

 

---

From: kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of SSTinsley@xxxxxxxxxxxxxx
Sent: Thursday, May 17, 2007 10:32 AM
To: amm@xxxxxxxx; Discussion list about Kickstart
Subject: RE: Unable toget any httprequests: Unable toretreive netstg2.imgfile

 

kickstart-list-bounces@xxxxxxxxxx wrote on 05/17/2007 01:22:21 PM:

> SSTinsley@xxxxxxxxxxxxxx;
> Apologies if I've missed part of the thread, but
> does the hardware you are attempting to pxeboot/ks have more than one
> nic?
> Sometimes you need to put --dev=eth(N) as the install kernel might probe
> and set up the device in a different order than the bios...
>
> bios device 1 might show up as eth(N) to the installer...
>
> so you can get a ip via pxeboot, download installer, etc, but anaconda
> set's up eth0 as the other nic, so it times out...
> using --dev=eth(N) usually fixes this.
>


Yes these suggestions were made earlier and tried. I disabled the second NIC in the
BIOS and still had the problems.

NOTE: THIS DOCUMENT MAY CONTAIN CONFIDENTIAL AND NONPUBLIC INFORMATION. IT IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL(S) OR ENTITY(IES) NAMED ABOVE, AND OTHERS SPECIFICALLY AUTHORIZED TO RECEIVE IT. If you are not the intended recipient of this document, you are notified that any review, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify me immediately by return email, delete the electronic message and destroy any printed copies. Thank you for your cooperation.