[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: pxe deployment



Certainly.

Here's our dhcp.conf -

[root plague:/tmp]# cat /etc/dhcpd.conf 
# Deploy Kickstart Server DHCPd.conf

ddns-update-style ad-hoc;

default-lease-time 600;
max-lease-time 7200;

option subnet-mask 255.255.255.0;

option broadcast-address 10.20.11.255;

option routers 10.20.11.1;

option domain-name-servers 10.20.11.2;

#host deploy1 {
#       hardware ethernet 0:e0:81:21:d8:a4;
#       fixed-address 10.20.11.100;
#       filename "/var/www/html/kickstart/deploy.ks";
#}

allow bootp;
allow booting;

# Definition of PXE-specific options
# Code 1: Multicast IP address of boot file server
# Code 2: UDP port that client should monitor for MTFTP responses
# Code 3: UDP port that MTFTP servers are using to listen for MTFTP requests
# Code 4: Number of seconds a client must listen for activity before trying
#         to start a new MTFTP transfer
# Code 5: Number of seconds a client must listen before trying to restart
#         a MTFTP transfer

option space PXE;
option PXE.mtftp-ip               code 1 = ip-address;  
option PXE.mtftp-cport            code 2 = unsigned integer 16;
option PXE.mtftp-sport            code 3 = unsigned integer 16;
option PXE.mtftp-tmout            code 4 = unsigned integer 8;
option PXE.mtftp-delay            code 5 = unsigned integer 8;
option PXE.discovery-control      code 6 = unsigned integer 8;
option PXE.discovery-mcast-addr   code 7 = ip-address;

class "pxeclients" {
    match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";
    option vendor-class-identifier "PXEClient";
    vendor-option-space PXE;

    # At least one of the vendor-specific PXE options must be set in
    # order for the client boot ROMs to realize that we are a PXE-compliant
    # server.  We set the MCAST IP address to 0.0.0.0 to tell the boot ROM
    # that we can't provide multicast TFTP (address 0.0.0.0 means no
    # address).

    option PXE.mtftp-ip 0.0.0.0;

    # This is the name of the file the boot ROMs should download.
    filename "pxelinux.0";

    # This is the name of the server they should get it from.
    next-server 10.20.11.2;
}

option mask-supplier    false;  # Don't respond to ICMP Mask req

subnet 10.20.11.0 netmask 255.255.255.0 {
        range 10.20.11.100 10.20.11.150;
}

-----Original Message-----
From: Stephen Mah [mailto:steve mah oracle com] 
Sent: Monday, June 20, 2005 10:13 AM
To: Discussion list about Kickstart
Subject: pxe deployment


All,

Is it possible for a unix based dhcp server to pass information to a 
client about tftp/pxe server information during bootup. We don't 
administer the dhcp servers, and I wanna do some inital research before 
approaching that group.

-regards
steve

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


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]