Ignite-ux and dhcp server linux (109 Views)
Reply
Advisor
uxbeginner22
Posts: 36
Registered: ‎11-25-2013
Message 1 of 2 (109 Views)

Ignite-ux and dhcp server linux

My configuration

dhcp linux machine(running slackware 14.1) 192.168.0.2

rx2620 ignite server 192.168.0.16

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: 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: /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

 

#boot
allow bootp;
use-host-decl-names on;
next-server 192.168.0.2;
filename "/pxelinux.0";
#hpuxboot ignite
group {
  host hpux3 {
        hardware ethernet 92:1d:c3:d4:f5:56;
        fixed-address 192.168.0.18;
        next-server 192.168.0.16;
        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



Please use plain text.
Honored Contributor
Matti_Kurkela
Posts: 6,271
Registered: ‎12-02-2001
Message 2 of 2 (71 Views)

Re: Ignite-ux and dhcp server linux

group {
  host hpux3 {
        hardware ethernet 92:1d:c3:d4:f5:56;
        fixed-address 192.168.0.18;
        next-server 192.168.0.16; <----------------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 192.168.0.16. 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.

MK
Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation