Ignite-UX Installation Booting

Section III: Network boot helpers

The bootp protocol query UDP broadcast is not routable (cannot relay or forward). In view of this,

Ignite-UX provides you the ability to configure a boot helper. A boot helper is the supported

method for accessing an Ignite-UX server when it is located on a different subnet than the client.

By default, an Ignite-UX boot helper does not have enough information to point to the correct server

so you must modify the server line in the INSTALLFS that gets downloaded from the boot helper

using instl_adm as follows:

instl_adm –d

# instl_adm defaults:

# NOTE: Manual additions between the lines containing "instl_adm

defaults"

# and "end instl_adm defaults" will not be preserved.

server="10.0.0.2"

netmask[]="255.255.255.0"

route_gateway[0]="10.0.1.1"

route_destination[0]="default"

disable_dhcp=true

# end instl_adm defaults.

This INSTALLFS indicates that the Ignite-UX client was somewhere on the class C subnet based

upon the netmask 10.0.1.1, and must contact the Ignite-UX server at 10.0.0.2.

If the server line in the INSTALLFS does not match one of the IP addresses of the system that the

Ignite-UX server booted from, you are using a boot helper. The remainder of the network boot

process occurs transparently as the IP address the firmware used is immaterial to the kernel.

Once the client systems boots from the boot helper, it sends a DHCP request to attempt to obtain an

IP address. If the request does not succeed, Ignite-UX prompts for the IP address information to be

entered on the client console.

For more information regarding boot helpers, refer to the Ignite-UX Administration Guide.