ID #1101

How to configure network for Colama RDE in preexist dns and dhcp in Windows.

MS Dhcp server (chainloading)

The Microsoft DHCP server is the default DHCP server on Microsoft Windows. It can be configured to support iPXE. It cannot easily be used to support some of the more advanced iPXE options; if you have the choice then you may find it easier to use ISC dhcpd.
The Microsoft DHCP server is configured using the DHCP MMC plug-in. Go to Start → Administrative Tools → DHCP:


PXE Chain Loading
To use PXE chainloading, you need to set up the Microsoft DHCP server to hand out undionly.kpxe to legacy PXE clients, and then hand out the “real” boot configuration only to iPXE clients. You can do this by telling the Microsoft DHCP server to use different configurations based on the DHCP user class.
First, define a user class for iPXE. Right-click on your DHCP server and choose Define User Classes:


Click on Add to add a new user class. Set the display name to iPXE, the description to iPXE clients, and the ID to iPXE:



Right-click on Server Options and choose Configure Options. Scroll down to option 067 Bootfile Name and set it to undionly.kpxe:

On the Advanced tab, select iPXE from the User class drop-down list. Scroll down to option 067 Bootfile Name and set it to http://COLAMA-server/infracc/app/d3i/endpoints/prepare_target:


If everything has worked, then you should see two settings for 067 Bootfile Name in your DHCP configuration: one containing undionly.kpxe and one containing http://COLAMA-server/infracc/app/d3i/endpoints/prepare_target:


This will ensure that the iPXE image (undionly.kpxe) is handed out only when the DHCP request comes from a legacy PXE client. Once iPXE has been loaded, the DHCP server will direct it to boot from http://COLAMA-server/infracc/app/d3i/endpoints/prepare_target. (You should replace http://COLAMA-server/infracc/app/d3i/endpoints/prepare_target with whatever you want iPXE to boot from.)
    To configure fusion server in preconfigured dnsmasq requires following things.

a) Assign static IP to COLAMA-server. To do that add following lines in /etc/network/interfaces file.
auto lo
iface lo inet loopback
#auto eth0
iface eth0 inet manual
auto br0
iface br0 inet static
       address <static ip of COLAMA server>
       netmask <mask used in network>
bridge_ports eth0
bridge_fd 9
bridge_hello 2
bridge_maxage 12
bridge_stp off


b) Add an static ip entry in DNS for fusion-server
open /etc/hosts file and following line in it.
<static-ip-of-COLAMA-server> COLAMA-server
NOTE: in above line is FQDN of COLAMA-server

c) Configure ipxe.
Create file /etc/dnsmasq.d/ipxe.conf and add following lines in it.
dhcp-boot=undionly.kpxe,fusion,<static IP of COLAMA server>
d) Restart dnsmasq service.
service dnsmasq restart
    ISC DHCPD (chainloading)

Tags: -

Related entries:

You can comment this FAQ