Ignite-ux and dhcp server Linux

I try to start a integrity vm machine using ignite-ux
and my usual dhcp server on linux.
Ip of server ignite is =192.168.0.16
Ip of dhcpd is = 192.168.0.2
Ip of client vm = 192.168.0.18
I try to boot from lan

Booting over the network
Loading.: lanboot

Client MAC Address: XXXXXXXXXX ..
Client IP Address: 192.168.0.18
Subnet Mask: 255.255.255.0
BOOTP Server IP Address: 192.168.0.16
DHCP Server IP Address: 192.168.0.2
Boot file name: /opt/ignite/boot/nbp.efi

Retrieving File Size.
Retrieving File (TFTP)./
PXE-E18: Timeout.  Server did not respond.
Load of lanboot failed: Not Found
Paused - press any key to continue 

On linux i configure dhcp

#boot
allow bootp;
use-host-decl-names on;
next-server 192.168.0.2;
filename "/pxelinux.0";
#hpuxboot ignite
group {
  host hpux3 {
        hardware ethernet XXXXXXXXX;
        fixed-address 192.168.0.18;
        next-server 192.168.0.16;
        filename "/opt/ignite/boot/nbp.efi";
}

and tftp

tftp  dgram   udp     wait    root    /usr/sbin/in.tftpd  in.tftpd 

What i miss?
if i try using -s /tftpboot or similar give me error code 2h
Intel pxe clients linux and tftp clients works fine

I haven't used DHCP for ignite, but i can recommend the workaround :wink:

Use bootptab on the ignite host, no DHCP at all.
BOOTP Server Setup for ignite | HP-UX Tips & Tricks Site

I use this in around 50 HPUX servers environment for root backups / restoring (from v1 to v3).

Ok i will do that
Thanks

Without dhcp it can take the address ip and don't start

---------- Post updated at 11:30 AM ---------- Previous update was at 11:22 AM ----------

I try this Configuring an Ignite Server to Boot Anonymous Itanium-Based Clients
but no work give me the same error pxe18 timeout

Well Ignite was written first for bootp and tftp... and so as far as I can remember when using it, you are to be in the same subnet as the server or have a server in every subnet where HP boxes are...
Is this the case?

I found the solution..is probably a bug

http://hpux.ch/images/1/15/Ignite-UX\_Admin_Guide.pdf

"PHNE_36209 or a superseding bootpd patch must be used to enable the configuration of Next Server response."

---------- Post updated at 11:45 AM ---------- Previous update was at 11:45 AM ----------

But there's a problem: is an old patche probably superseeded

---------- Post updated at 11:59 AM ---------- Previous update was at 11:45 AM ----------

Same subnet

---------- Post updated at 01:38 PM ---------- Previous update was at 11:59 AM ----------

SOLUTION FOUND!

I use a vmswitch on the same lan card of ignite server
must be on separate lan
for example
lan0: hosthp,ignite server
lan1:virtual switch on the same subnet of ignite server.