Ignite on a routed network

[Dennis Faust]

Does anyone have any hints or has anyone made ignite work through a router? Can
you give me some help, as I have to deal with this for over 600 clients and
want to endure when the network migrates from flat to routed that the ignite
process still works.

[Alan Riggs_1]

You need an ignite boot server on each subnet of your network for which you
wish to install clients. Basically, these boot servers are configured with the
IP of your Ignite server. Respond to the client boot requests (which are
broadcast messages on teh local subnet) and then forward the request through
the routers to the Ignite server.

[Dennis Faust]

Could the ignite boot server just be running on one of the clients? How much
overhead would it cause?


Sory for my ignorance but I'm a networking guy, not an HP-UX guy....

[Alan Riggs_1]

It is certainly possible ot configure an Ignite server for each subnet. If all
you need is a generic system install image, then the overhead (in disk space)
is not extreme. If you want to save multiple "golden images" obviousy, the
space requirements rise appropriately. Network overhead and install time will
be reduced by using local Ignite servers, though admin time will be increased
as you will need to install the product and configure the server for each
subnet.