Daemon trasmitting from different IP's makes no boot a Intel Boot Agent

[Angel_17]

I have a PXE daemon running on a HP-UX Service Guard Cluster.
The problem is that sometimes the daemon trasmits to the Intel Boot Agent Client with it's node IP, and sometimes with it's packet (floating) IP.
I suppose the client wants only the packets coming from the floating IP, not from the node IP.

How can I force my daemon to trasmit only using the packet (floating) IP?

Thanks to everybody.

[Florian Heigl (new acc)]

Can't You bind the PXE daemon to a specific IP, alas the package IP?


Florian

[Angel_17]

No Florian, I cannot modify the daemon. It's untouchable.

I must explain better the problem. The daemon ALWAYS transmit towards the client with the node IP.
I need to force that daemon to use the floating IP INSTEAD, because that is the address declared in the bootptab (you don't know which node will provide the service).

Anyway, is there any document explaining the differences between the node IP and the floating IP (in terms of programming, configuration...) on Service Guard?