In article <1118339084.063662.314200@g47g2000cwa.googlegroups .com>,
chadmjohn@gmail.com wrote:

> I have a need to perform jumpstart installations across subnets and
> will not be able to provide a boot server at each subnet. I can create
> jumpstart on a bootable cd, which is essentially a portable (yet local
> to the installing client)jumpstart installation system or I can create
> profile diskettes to be used for the installation information.
>
> Both of these methods suffer from static data. Should I need to change
> anything in the JS installation I will then need to redistribute the JS
> CDs or Profile disks to all locations in order to guarantee they have
> the most recent data.
>
> I would like to be able to boot the system to be installed (not using a
> boot server) but retrieve all my information (sysidcfg, rules, profile)
> from the centralized JS system.
>
> How can I do this as the system has no knowledge of it's IP (or router)
> address at boot time? It is unable to retreive the miniroot without
> this information. We do not use DHCP for server IPs so the DHCP
> keyword to 'boot' is out of the question.

The only way I know how to do this via Jumpstart is the initial
bootstrap must be via DHCP. In order to use RARP, you _must_ use a
multi-homed bootserver on the local net. AFAIK, RARP isn't routeable,
but _maybe_ you could configure your routers to bridge the protocol.
Not sure if that can be done or if it's even desireable. The Solaris
kernel load is via NFS, which can cross segments.

So, unless you switch to DHCP, I think you're out of luck. You'll have
to setup a multi-homed system that runs bootparamd and rarpd.

--
DeeDee, don't press that button! DeeDee! NO! Dee...