ignite on new subnet

[richard bumgardner]

I've been igniting workstations successfully at our site for some time now on an xxx.xxx.249.xxx subnet with a subnet mask of 255.255.255.0. Recently, a new subnet xxx.xxx.229.xxx was added with a subnet mask of 255.255.255.192. These 2 subnets have different default gateways.
I set up a new /var/opt/ignite/INDEX clause referencing the different subnet mask and gateway for the new .229 subnet.
Ignites seem to go okay, but when I bring up the newly ignited subnet .229 boxes, /etc/resolv.conf, /etc/nsswitch.conf, and /etc/hosts aren't included in the image.
It is my understanding that these 3 files are altered and/or created by the ignite process.
The .249 subnet boxes still ignite fine. The only difference is in a file with the new network parameters in /var/opt/ignite/saved_cfgs/.
All other INDEX files are identical.
Any help would be most appreciated.
Tim

[Steven E. Protter]

Shalom,

You need an Ignite boot helper to help these system boot and connect to the main Ignite server on another subnet.

http://docs.hp.com/en/5992-5309/5992-5309.pdf

It is a topic in that link.

SEP