PXE-E21 error when LAN-Booting VM Guest

[noldi]

Hello,

I have setup a VM Host that is an Ignite-UX Server for it's VM
Guests and I'm trying to boot the VMs from it.
I've added the guests to /etc/bootptab as described in
http://h71028.www7.hp.com/ERC/downloads/c00589728.pdf
but I'm constantly getting this error:

"CLIENT MAC ADDR: AA 55 43 0E AA 27
CLIENT IP: 172.18.8.164 MASK: 255.255.255.0
DHCP IP: 172.18.8.160 PROXY IP: 172.18.8.57
GATEWAY IP: 172.18.8.1

Next Device (BIOS/EFI)

PXE-E21: Remote boot cancelled.
Load of LAN0 failed: Not Found
Paused - press any key to continue"

The DHCP IP Address is the one from the Ignite-
Server, although I don't know where the PROXY
IP-Address comes from.

I used to successfully Ignite-boot VM Guests before in a
similar environment, but this time I can't seem to
get it to work.

Has anybody an idea what could be wrong here?

Thanks & best Regards,

Arnold

[Steven E. Protter]

Shalom Arnold,

I wasn't aware Ignite supported PXE boot.

What Ignite does support is a boot on the same subnet as the Ignite server (or through a boot helper) through the systems built-in lan card only.

If you can't meet that criteria then you might not be able to install via Ignite this way.

SEP

[noldi]

Hello Steve,

as you can see, both the Ignite Server and
the VM Guest is on the very same subnet.

Booting Integrity Servers via LAN seems
to go with PXE, this is also the case
with IVMs.

What I'm suspecting is that other bootp/dhcp servers
could be interfering . . .

Regards,

Arnold

[Sameer_Nirmal]

I would second your suspect.

It seems that the PXE client is trying to boot from the PROXY server which PXE client would take as a proxy DHCP server ( port 4011 ). You might want to verify the PROXY IP from the network guy.

I guess it seems, the PXE client might have contacted the Ignite server (VM host , verify the syslog on the VM host) but it didn't receive enought information from it. Hence it tried to get more information through port 4011 which is responded by the proxy DHCP server. Obviously, the proxy DHCP would cancel the boot request of the PXR client as an invalid/absurd request.

Just wondering if you have enabled bootpd and tftpd on the VM host?

Other option which could tried out is using dbprofile.

[noldi]

Hello,

there was an Altiris Server on the same LAN that was interfering with us. Disabling that one solved the VM Guest boot problems and the VMs are installing now.

Even the direct boot approach with "dbconfig" did not help so we are now looking into the possibility to reduce the scope of the Altiris Services and exlude our HP-UX IP-Range in order to reduce future conflicts.

Thanks & best Regards,

Arnold