Simpler Navigation coming for Servers and Operating Systems
Coming soon: a much simpler Servers and Operating Systems section of the Community. We will combine many of the older boards, and you won't have to click through so many levels to get at the information you need. If you are looking for an older board and do not find it, check the consolidated boards, as the posts are still there.
Showing results for 
Search instead for 
Did you mean: 

Ignite-ux and dhcp server linux

Trusted Contributor

Ignite-ux and dhcp server linux

My configuration

dhcp linux machine(running slackware 14.1)

rx2620 ignite server

I try to boot a virtual machine


Booting over the network
Loading.: LANBOOT

Client MAC Address: 92 1D C3 D4 F5 56 ..
Client IP Address:
Subnet Mask:
BOOTP Server IP Address:
DHCP Server IP Address:
Boot file name: /nbp.efi

Retrieving File Size..
PXE-E23: Client received TFTP error from server.
PXE-E98: Code: 2h  Access violation
Load of LANBOOT failed: Not Found
Paused - press any key to continue 

 If i change the path of nbp.efi give me timeout


Other file confs dhcp.conf


allow bootp;
use-host-decl-names on;
filename "/pxelinux.0";
#hpuxboot ignite
group {
  host hpux3 {
        hardware ethernet 92:1d:c3:d4:f5:56;
        filename "/nbp.efi";

 inetd.conf on linux


tftp  dgram   udp     wait    root    /usr/sbin/in.tftpd  in.tftpd -s /tftpboot

 Of course nbp.efi is present in tftpboot

Honored Contributor

Re: Ignite-ux and dhcp server linux

group {
  host hpux3 {
        hardware ethernet 92:1d:c3:d4:f5:56;
        next-server; <----------------this overrides the earlier next-server setting!!!
        filename "/nbp.efi";

 Your DHCP configuration says that the booting VM should try to load /nbp.efi from In other words, it is trying to load /nbp.efi from the rx2620 Ignite server, not from the Linux server.


You should modify the next-server setting to point to the Linux server if that is what you want.

Or if you want the Ignite server to provide the nbp.efi file, make sure that the file permissions on HP-UX are correct and pathname in the DHCP configuration matches the way the HP-UX tftpd actually presents the file.


Note that the configuration syntax of HP-UX tftpd is different from Linux in.tftpd. On HP-UX tftpd, if the client requests for "/nbp.efi", the tftpd daemon will look for ~tftp/nbp.efi,  /nbp.efi, or both, depending on configuration. See "man tftpd" on HP-UX for details.