How to Ignite client on different subnet without a HP server to use for boot helper

[Tim Adamson_1]

Its been a while since I was in the forum, but work has been hectic to say the least.

I have an 11i Ignite server (B.4.3.x) for building 11i clients. I can successfully install a new 11i client on same subnet. How can I build an 11i client on a different subnet if I don't have another HP-UX server on that subnet to use as a boot helper? In other words, can I use something else as the boot helper (eg, the switch by getting it to forward the request)? If so, how is it done?

The Ignite-UX manual says you have to use a boot helper and install the "Ignite-UX minimum core functionality onto the helper system" which implies another HP-UX server on the same subnet. I don't have that luxury, and I have other subnets with the same problem.

Thanks in advance

[T G Manikandan]

Not sure about the present releases of ignite.worked on older releases

Without a boot helper/server you cannot accomplish the task.

[Tim Adamson_1]

I was sure the older releases of Ignite worked too.

And I know I can accomplish it by booting from a tape/CD and pointing to the Ignite server, but the client is in a remote location and I don't have access and don't want to use a tape/CD as I know it will get lost and that just adds more complexity that I can do without!

[Pete Randall]

Tim,

Sorry to say - I'm with TG on this one. Without a boot helper, it's not going to happen!


Pete

[Steven E. Protter]

Well,

You could put the two machines internal NIC cards on a private network, boot the client off of the private network. All you need is a hub at the right place, perhaps in the right wiring closet of the machines are not close physically.

Have the configuration set up to run the transfer on the larger, more public network. This would bypass the boot helper situation. I don't think a push would work, but I'm pretty sure I've done this with a pull.

SEP

[Jeff Schussele]

Hi,

There is one way.
You'd need to determine the MAC address of the built-in LAN on the client, create a dir on the Ignite server named to that address and copy the existing image dir you wish to use into that newly created dir. Then create a link named to the hostname you wish to use for that client to that newly created/loaded MAC-named dir. Cable the built-in NIC to the network. Then boot the install CD on the client, choose Ignite Install & point it to the Ignite server.

HTH,
Jeff

[Kurt Renner]

_IF_ the system has an existing HP-UX OS already on it, _AND_ you can bring that system up and enable networking on it, you can issue a "bootsys -v -w " and download the WINSTALL/INSTALL/VINSTALL kernel to the client. When the client boots this kernel, it will be visible to your Ignite-UX server in the GUI or TUI.

Of course.... if the system does not already have an OS, this does you no good. At that point your best bet would be to boot off the install CD, and point to your Ignite server from the initial screens of the installation interface given from the installation CD.

Good luck.