DHCP server not working for iPXE

[excessive]

The switch is BlackDiamond X8.
I’ve set dhcp server for our lab VLAN that I’m using for testing. The pool range and everything else works as intended.
I’ve configured options 66 and 67 to FOG server machine and that’s where it breaks. I’m getting:

Filename: undionly.kpxe
Could not start download: Operation not supported (http://ipxe.org/3c092003)

I can confirm that when using separate isc-dhcp server there’s no problem. But I’d like to utilize our switch.

Here’s snippet of my configuration:

VLAN "XXX_TEST":
    DHCP Address Range   : 192.168.xx.xx->192.168.xx.xx
    Netlogin Lease Timer : Not configured (Default = 10 seconds)
    DHCP Lease Timer     : 86400 seconds
    Default Gateway      : 192.168.xx.xx
    Primary DNS Server   : xx.xx.xx.xx
    DHCP Option Code  66 : ipaddress 192.168.xx.xx
    DHCP Option Code  67 : string "undionly.kpxe"
    Ports DHCP Enabled   : 1:21

[excessive]

Sorry, maybe I misunderstood you. 

Anyway, here’s everything that appeared in Wireshark.
 

0.0.0.0		    255.255.255.255	    DHCP	451	DHCP Discover
192.168.230.253	255.255.255.255	    DHCP	347	DHCP Offer
192.168.230.51	255.255.255.255	    DHCP	342	DHCP Offer
0.0.0.0		    255.255.255.255	    DHCP	463	DHCP Request  
192.168.230.51	255.255.255.255	    DHCP	342	DHCP ACK     
0.0.0.0		    255.255.255.255	    DHCP	342	DHCP Request 

The offer coming from 230.253 (which is my gateway interface on the switch) contains option 66 and 67. I’ve disabled the dhcp though!
Afterwards 230.51 provides the working Offer with no options.

[StephanH]

Check the other dhcp messages please

[excessive]

Frame 380: 342 bytes on wire (2736 bits), 342 bytes captured (2736 bits) on interface \Device\NPF_{4C63F991-A548-48B3-A772-5278B943AE7F}, id 0
Ethernet II, Src: e6:95:01:b5:0a:4e (e6:95:01:b5:0a:4e), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Internet Protocol Version 4, Src: 192.168.230.51, Dst: 255.255.255.255
User Datagram Protocol, Src Port: 67, Dst Port: 68
Dynamic Host Configuration Protocol (ACK)
    Message type: Boot Reply (2)
    Hardware type: Ethernet (0x01)
    Hardware address length: 6
    Hops: 0
    Transaction ID: 0x8790a21c
    Seconds elapsed: 18
    Bootp flags: 0x8000, Broadcast flag (Broadcast)
    Client IP address: 0.0.0.0
    Your (client) IP address: 192.168.230.20
    Next server IP address: 192.168.230.51
    Relay agent IP address: 0.0.0.0
    Client MAC address: 82:5d:c6:8a:7e:48 (82:5d:c6:8a:7e:48)
    Client hardware address padding: 00000000000000000000
    Server host name not given
    Boot file name: undionly.kpxe
    Magic cookie: DHCP
    Option: (53) DHCP Message Type (ACK)
    Option: (54) DHCP Server Identifier (192.168.230.51)
    Option: (51) IP Address Lease Time
    Option: (1) Subnet Mask (255.255.255.0)
    Option: (3) Router
    Option: (6) Domain Name Server
    Option: (15) Domain Name
    Option: (255) End
    Padding: 00000000000000000000000000000000

Apparently, the frames coming from isc-dhcp do not contain options 66 and 67, but have values for “Next server” and “Boot file name” which seems to be enough to boot iPXE.
I feel like I’m stuck.

[StephanH]

Try first do create a trace with wireshark for ISC to compare both options (66,67) for ICS and XOS.

[excessive]

So the question is what I can do about that? On the ISC dhcp there is that option “next-server” which explains itself. But how I can set it on our XOS?