HPE 9000 and HPE e3000 Servers
cancel
Showing results for 
Search instead for 
Did you mean: 

Ignite_UX Server and Boot Helpers

 
Jerry Sommerville_2
Frequent Advisor

Ignite_UX Server and Boot Helpers

Should the boot helpers have a different list of IPS (local to their subnet) from the Ignite server (which is on a different subnet). Asked another way, should the list of IPs available to clients for booting be on the same subnet as the server or should they be IPs for the remote subnet?
3 REPLIES 3
Sameer_Nirmal
Honored Contributor

Re: Ignite_UX Server and Boot Helpers

If the clients are not in the same subnet as the Ignite-UX server and clients needs to be booted from the network, then a boot helper needs to be installed. This boot helper must be on a HP-UX system within the subnet of the Ignite-UX clients.

If the clients are on the same subnet as that of Ignite-UX server , the boot helper is not required.
Dave Unverhau_1
Honored Contributor

Re: Ignite_UX Server and Boot Helpers

Jerry,

I know the language in the Ignite manual is a little confusing. Here's the issue: Bootp protocol cannot traverse subnets, so the client using bootp must have an address in the same subnet as the server it's booting from (in the case of multiple subnets, this is the boot helper).

So, to answer the question concisely, the list of client addresses configured into the boot helper must be within the same subnet as the address of the helper.

(Note that these are temporary client addresses and you will want to replace the client address with a permanent one later in the ignite process, so that this temporary address will be available for another client when needed.)

Best Regards,

Dave
Romans 8:28
Jerry Sommerville_2
Frequent Advisor

Re: Ignite_UX Server and Boot Helpers

Thanks Dave. As I understand it, the list of IPs on the boot helper is in fact a different list of IPs (for that subnet). The list of IPs on the Ignite Server itself is for the subnet the server resides on. Thanks so much. points assigned. :-)