List Info

Thread: RHEL 3 kickstart network retrieval issue
RHEL 3 kickstart network retrieval issue
user name
 2008-04-30 18:26:48 

  


  

    
I am having the wierdest issue with RHEL 3 network installs. 


 


When I boot with a RHEL 3 boot media, I use the following boot commandline:


 ;


linux ks=http://myhost/RHEL3.ks ksdevice=eth0 ip=<MYIP> netmask=&lt;MYNETMASK> gateway=&lt;MYGATEWAY> dns=<MYDNS>


 


Anaconda boots up but it fails at installing. I switch over to a terminal and it shows that anaconda has failed to retrieve the kickstart file from the network and also I see a no route to host error. Does not look like the network device is being set up correctly based upon the boot commandline parameters.



&nbsp;


 ;


To Troubleshoot to make sure it wasn't the kickstart file that was the problem, I stuck this same kickstart file as an embedded kickstart on the cd and it worked fine. So that doesn't get me anywhere and validates that my actual kickstart file doesn't have errors and can install an OS 




 


So, I try doing the same thing but with RHEL 4 media and a RHEL4 based kickstart using the boot commandline


 




linux ks=http://myhost/RHEL4.ks ksdevice=eth0 ip=<MYIP> netmask=&lt;MYNETMASK> gateway=&lt;MYGATEWAY> dns=<MYDNS>


 


Everything works fine using ;RHEL 4 and the command line stated right above.


 


&nbsp;


Are their known issues with setting network&nbsp;parameters at the command line with RHEL 3? 



  

  
  
   
     
    

  

    RE: RHEL 3 kickstart network retrieval
issue
  


  

     country flaguser name
United States		
     2008-04-30 19:07:14
  


  

    

  


  

    You may be running into the timeout issue when connected to 
Cisco (and probably other) switches.

 



use the ethtool option to set speed/duplex/auto-neg and use 
a delay if needed.&nbsp; You can find all these options in my presentation last 
year at Linuxworld


 




&nbsp;






From: kickstart-list-bouncesredhat.com 
[mailto:kickstart-list-bouncesredhat.com] On Behalf Of Brent 
Clements
Sent: Wednesday, April 30, 2008 4:27 PM
To: 
kickstart-listredhat.com
Subject: RHEL 3 kickstart network retrieval 
issue





I am having the wierdest issue with RHEL 3 network installs. 


 


When I boot with a RHEL 3 boot media, I use the following boot 
commandline:


&nbsp;


linux ks=http://myhost/RHEL3.ks 
ksdevice=eth0 ip=<MYIP> netmask=&lt;MYNETMASK> 
gateway=<MYGATEWAY> dns=<MYDNS>


 


Anaconda boots up but it fails at installing. I switch over to a terminal 
and it shows that anaconda has failed to retrieve the kickstart file from the 
network and also I see a no route to host error. Does not look like the network 
device is being set up correctly based upon the boot commandline 
parameters.


&nbsp;


 ;


To Troubleshoot to make sure it wasn't the kickstart file that was the 
problem, I stuck this same kickstart file as an embedded kickstart on the cd and 
it worked fine. So that doesn't get me anywhere and validates that 
my actual kickstart file doesn't have errors and can install an 
OS 


 


So, I try doing the same thing but with RHEL 4 media and a RHEL4 based 
kickstart using the boot commandline


 




linux ks=http://myhost/RHEL4.ks 
ksdevice=eth0 ip=<MYIP> netmask=&lt;MYNETMASK> 
gateway=<MYGATEWAY> dns=<MYDNS>


 


Everything works fine using ;RHEL 4 and the command line stated right 
above.



 


 


Are their known issues with setting network&nbsp;parameters at 
the command line with RHEL 3? 

  

  
  
   
     
    

  

    Re: RHEL 3 kickstart network retrieval
issue
  


  

     user name

     2008-04-30 19:14:07
  


  

    

  


  

    
I thought that as well before I submitted to the mailing list. Tried various eth settings including the standard troubleshooting ones that are out there but it did not work.


&nbsp;


I&#39;m goin to do some traffic sniffing to see what's going on.


&nbsp;




&nbsp;


On Wed, Apr 30, 2008 at 7:07 PM, Shabazian, Chip < Chip.Shabazianbankofamerica.com">Chip.Shabazianbankofamerica.com>; wrote:






You may be running into the timeout issue when connected to Cisco (and probably other) switches.


 



use the ethtool option to set speed/duplex/auto-neg and use a delay if needed.&nbsp; You can find all these options in my presentation last year at Linuxworld



 




&nbsp;






From:  kickstart-list-bouncesredhat.com" target="_blank">kickstart-list-bouncesredhat.com [mailto: kickstart-list-bouncesredhat.com" target="_blank">kickstart-list-bouncesredhat.com] On Behalf Of Brent Clements


Sent: Wednesday, April 30, 2008 4:27 PM
To:  kickstart-listredhat.com" target="_blank">kickstart-listredhat.com
Subject: RHEL 3 kickstart network retrieval issue













I am having the wierdest issue with RHEL 3 network installs. 


 


When I boot with a RHEL 3 boot media, I use the following boot commandline:


 ;


linux ks=http://myhost/RHEL3.ks ksdevice=eth0 ip=<MYIP> netmask=&lt;MYNETMASK> gateway=&lt;MYGATEWAY> dns=<MYDNS>


 


Anaconda boots up but it fails at installing. I switch over to a terminal and it shows that anaconda has failed to retrieve the kickstart file from the network and also I see a no route to host error. Does not look like the network device is being set up correctly based upon the boot commandline parameters.



&nbsp;


 ;


To Troubleshoot to make sure it wasn't the kickstart file that was the problem, I stuck this same kickstart file as an embedded kickstart on the cd and it worked fine. So that doesn't get me anywhere and validates that my actual kickstart file doesn't have errors and can install an OS 




 


So, I try doing the same thing but with RHEL 4 media and a RHEL4 based kickstart using the boot commandline


 




linux ks=http://myhost/RHEL4.ks ksdevice=eth0 ip=<MYIP> netmask=&lt;MYNETMASK> gateway=&lt;MYGATEWAY> dns=<MYDNS>


 


Everything works fine using ;RHEL 4 and the command line stated right above.


 


&nbsp;


Are their known issues with setting network&nbsp;parameters at the command line with RHEL 3? 

_______________________________________________
Kickstart-list mailing list
 Kickstart-listredhat.com">Kickstart-listredhat.com

https://www.redhat.com/mailman/listinfo/kickstart-list




  

  
  
   
     
    

  

    Re: RHEL 3 kickstart network retrieval
issue
  


  

     country flaguser name
United Kingdom		
     2008-05-01 05:28:57
  


  

    
> I am having the wierdest issue with RHEL 3 network
installs.
>  
> When I boot with a RHEL 3 boot media, I use the
following boot 
> commandline:
>  
> linux ks=http://myhost/RHEL3.ks
ksdevice=eth0 ip=<MYIP> 
> netmask=<MYNETMASK> gateway=<MYGATEWAY>
dns=<MYDNS>
>  
> Anaconda boots up but it fails at installing. I switch
over to a 
> terminal and it shows that anaconda has failed to
retrieve the 
> kickstart file from the network and also I see a no
route to host 
> error. Does not look like the network device is being
set up correctly 
> based upon the boot commandline parameters.
>  
>  
> To Troubleshoot to make sure it wasn't the kickstart
file that was the 
> problem, I stuck this same kickstart file as an
embedded kickstart on 
> the cd and it worked fine. So that doesn't get me
anywhere and 
> validates that my actual kickstart file doesn't have
errors and can 
> install an OS 
>  
> So, I try doing the same thing but with RHEL 4 media
and a RHEL4 based 
> kickstart using the boot commandline
>  
> linux ks=http://myhost/RHEL4.ks
ksdevice=eth0 ip=<MYIP> 
> netmask=<MYNETMASK> gateway=<MYGATEWAY>
dns=<MYDNS>
>  
> Everything works fine using RHEL 4 and the command line
stated right 
> above.
>  
>  
> Are their known issues with setting network parameters
at the command 
> line with RHEL 3?

is your required NIC driver in the RHEL 3 image? what
hardware are you 
using?


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




  


  

    
  

  
  
   
     
    

  

    Re: RHEL 3 kickstart network retrieval
issue
  


  

     user name

     2008-05-01 06:13:06
  


  

    

  


  

    
Try using ksdevice=bootif  this will work for both RHEL3 and RHEL4.


 


&nbsp;


&nbsp;


&nbsp;


&nbsp;


 ;


 


 


 



 




 



On 5/1/08, Tom Brown < tomng23.net">tomng23.net&gt; wrote:






I am having the wierdest issue with RHEL 3 network installs.
 When I boot with a RHEL 3 boot media, I use the following boot commandline:

 linux ks=http://myhost/RHEL3.ks ksdevice=eth0 ip=<MYIP> netmask=&lt;MYNETMASK> gateway=&lt;MYGATEWAY> dns=<MYDNS>

&nbsp;Anaconda boots up but it fails at installing. I switch over to a terminal and it shows that anaconda has failed to retrieve the kickstart file from the network and also I see a no route to host error. Does not look like the network device is being set up correctly based upon the boot commandline parameters.

 &nbsp;To Troubleshoot to make sure it wasn't the kickstart file that was the problem, I stuck this same kickstart file as an embedded kickstart on the cd and it worked fine. So that doesn't get me anywhere and validates that my actual kickstart file doesn't have errors and can install an OS  So, I try doing the same thing but with RHEL 4 media and a RHEL4 based kickstart using the boot commandline

 linux ks=http://myhost/RHEL4.ks ksdevice=eth0 ip=<MYIP> netmask=&lt;MYNETMASK> gateway=&lt;MYGATEWAY> dns=<MYDNS>

&nbsp;Everything works fine using RHEL 4 and the command line stated right above.
&nbsp; Are their known issues with setting network parameters at the command line with RHEL 3?

is your required NIC driver in the RHEL 3 image? what hardware are you using? 




_______________________________________________
Kickstart-list mailing list
redhat.com" target="_blank">Kickstart-listredhat.com

https://www.redhat.com/mailman/listinfo/kickstart-list









  

  
  
   
     
    






 [1-5]











   
 





about | contact  Other archives ( Real Estate discussion Medical topics )