Re: kickstart dhcp issues

[Sir June <sir_june@xxxxxxxxx>]

alright. i guess i have another minor issue.  still with DHCP.
Our  LAN's DHCP is handled by Microsft 2003 server. :((   with /21 for DHCP range  (192.168.10.x -> 192.168.17.x)


My query is,  can I run a Redhat DHCP on the same LAN segment?  How do i make sure that only my new-server will get IP from Redhat DHCP via PXE and no other clients will get any from Redhat DHCP.  or shall i say,  all other machines will get DHCP from the Windows DHCP , and only the server I want to install Redhat will get IP from the Redhat DHCP.

thanks in advance.

Sirjune

---

From: "CHU, STEPHEN H" <sc1680@xxxxxxx>
To: Sir June <sir_june@xxxxxxxxx>
Sent: Tuesday, January 31, 2012 10:22 AM
Subject: RE: kickstart dhcp issues

Sirjune,

 

Try ksdevice=link or ksdevice=bootif. Those worked for me every time.

 

Steve

 

From: Sir June [mailto:sir_june@xxxxxxxxx]
Sent: Tuesday, January 31, 2012 10:17 AM
To: Discussion list about Kickstart
Subject: Re: kickstart dhcp issues

 

I thank you all for the comments, solutions and suggestions.
as of yesterday,  I was able to install  RHEL5.5 via kickstart using  linux ks=http://192.168xxx.xxx/redhat/ks.cfg  dhcptimeout=500

although it still asks me as to which ethernet to use, (eth0..eth5). it continues afterwards.  I tried specifying ksdevice=eth0 and noipv6  but the installation wont proceed and keeps on coming back to the ipv4 and ipv6 selections.
I will try all the suggestions & options mentioned here.

thanks,
Sirjune
 

---

From: Angus Clarke <angus.clarke@xxxxxxxxx>
To: Discussion list about Kickstart <kickstart-list@xxxxxxxxxx>
Sent: Monday, January 30, 2012 3:13 PM
Subject: Re: kickstart dhcp issues

 

Perhaps - I didn't read the Dell solution as specifying MAC addresses is sufficient and already available, at least for my requirements (Ethernet interfaces)

All the best
~Angus

On 30 January 2012 20:06, Kaj Niemi <kajtzu@xxxxxxx> wrote:

I think this is what the dell naming scheme was designed to prevent… :-)

 

 

 

Kaj

 

On Jan 30, 2012, at 18:36, Angus Clarke wrote:

I notice that without specifying the device MAC address in the config files you are concerned with, and then later adding additional NICs on the PCIe bus - results in the PCIe NICs preceding the onboard NICs (eth0 changes to represent the NIC on the lowest PCIe bus.)

HP DL380 G7 and RHEL5.2 x86_64

 

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

 

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

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