SEO

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.

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...

Per the documentation you are correct. But you can do this (I haven't
made it that far yet) by modifying the information on your boot media.

Basically you make a 'jumpstart on cd' system but instead of installing
from the cd itself the target system obtains it's profile information
from the remote location. I can see it is possible but was hoping
someone had already done the *hacking* of the /etc/rcS script in the
jumpstart system to do it.

Also, DHCP booting is only available in the more current boot proms and
I have a large array of systems (old & new) to deal with.

Some routers can be configured to forward RARP requests but this is not
standard (so not reliable).

Thanks.

In article <1118406252.449684.185530@g43g2000cwa.googlegroups .com>,
chadmjohn@gmail.com wrote:

> Per the documentation you are correct. But you can do this (I haven't
> made it that far yet) by modifying the information on your boot media.

So, how would this work on a bare metal machine?

>
> Basically you make a 'jumpstart on cd' system but instead of installing
> from the cd itself the target system obtains it's profile information
> from the remote location. I can see it is possible but was hoping
> someone had already done the *hacking* of the /etc/rcS script in the
> jumpstart system to do it.

This part of the install (the Solaris kernel install) shouldn't be a
problem. It's done via an NFS mount, so you don't need to do this.
Unless I'm missing something on what you're saying...

>
> Also, DHCP booting is only available in the more current boot proms and
> I have a large array of systems (old & new) to deal with.

Yep. That pretty much puts you into the RAPR camp.

>
> Some routers can be configured to forward RARP requests but this is not
> standard (so not reliable).
>
> Thanks.

From what I recall (before the days of DHCP Jumpstart), the bootstap
process is the following:

-> client bootprom issues rarp request to host
<- boot host returns ip address from boot host rarpd's
reading /etc/ethers or ethers map OR dhcp host returns
ip address and bootfile
-> client boot prom issues tftp request
<- boot host returns tftpd reading /tftpboot/IPADDR
(linked to inetboot for arch) OR bootfile dhcp host sent
-> client runs inetboot which issues whoami to boothost
or dhcp host to obtain boot parameters
<- boot or dhcp host returns bootparamd's hostname from /etc/hosts
or host map
-> client's inetboot issues getfile to host
<- boot host's bootparamd reads /etc/bootparams to
get client's root location if dhcp is not used
-> client's inetboot issues NFS mount of root filesystem
on responding host
-> client's inetboot opens and reads kernel of NFS mounted root

So the rarp/boot server has to be on the same segment as the client (or
the server is multi-homed). If you use dhcp, it can be anywhere on the
network, even across routers. The load server can be on another net
or can be on the same system as the boot server.

Configuration files:

/etc/hosts
/etc/ethers
/etc/dfs/dfstab (to serve the root filesystems)
/etc/bootparams
/tftpboot/IPADDR -> inetboot for specific architecture and OS


No matter what way you slice this, I think you're SOL without DHCP or a
multi-homed boot server. If you want to "roll your own" network boot,
great. But the sysadmin that replaces you will most likely scrap it and
curse your name and your children's children.

Good luck. You need it.

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

On Thu, 09 Jun 2005 10:44:44 -0700, chadmjohn 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.

You can't, afaik, so you can do image installs which requires a visit
to each host and an image of each architecture, or you can go out to Fry's
and buy a dozen of their $179.99 PCs, reload them with Linux and configure
them to be rarp servers, and hang one on each subnet.

Regards, Scott

Michael Vilain <vilain@spamcop.net> writes:

> 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.

In addition to using DHCP it may be necessary to configure the routers
in question to forward the DHCP UDP broadcasts to the DHCP server.

With Cisco's IOS this is done with the "helper-address" configuration
command. For JunOS you use the "bootp" statement in the [edit
forwarding-options helpers] hierarchy level.

--
David Magda <dmagda at ee.ryerson.ca>
Because the innovator has for enemies all those who have done well under
the old conditions, and lukewarm defenders in those who may do well
under the new. -- Niccolo Machiavelli, _The Prince_, Chapter VI

On 9 Jun 2005 10:44:44 -0700
chadmjohn@gmail.com wrote:

[snip]

use a solaris laptop as bootserver or some old box that is not used
anymore?




--
Barbie - Prayers are like junkmail for Jesus

I have seen things you lusers would not believe.
I've seen Sun monitors on fire off the side of the multimedia lab.
I've seen NTU lights glitter in the dark near the Mail Gate.
All these things will be lost in time, like the root partition last
week. Time to die.

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.
>

<snip>

Perhaps WAN Boot would do what you're looking for.

Overview
http://www.sun.com/software/whitepap...secure_wan.pdf

How to
http://docs.sun.com/app/docs/doc/817...kv4nh4g?a=view

--
Chris

In article <42b1d7c6$0$305$cc9e4d1f@news-text.dial.pipex.com>,
Chris Lawson <newsgroups@spamtrap.com> wrote:
>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.
>>
>
><snip>
>
>Perhaps WAN Boot would do what you're looking for.
>
>Overview
>http://www.sun.com/software/whitepap...secure_wan.pdf
>
>How to
>http://docs.sun.com/app/docs/doc/817...kv4nh4g?a=view
>
>--
>Chris


on sparc, what i do is put an ordinary solaris distribution
CD (the 1 of 2 CD, ie, the CD with the boot image on it)
and say:
boot cdrom - install nfs://<ipaddress>/tmp/Q/v440m.tar dhcp nowin

the ipaddress is the ip address of the jumpstart server.
we assume you can do nfs across subnets.
my dhcp server will give the machine its hostname and ip.
the v440m.tar is a tar file of the machine's profile,
rules.ok, sysidcfg, ....
it lives in /tmp/Q so i don't have to type so much.


or you can try a Begin script that mounts the
OS distribution under /cdrom.....


--
Jay Scott 512-835-3553 gl@arlut.utexas.edu
Head of Sun Support, Sr. Operating Systems Specialist
Applied Research Labs, Computer Science Div. S224
University of Texas at Austin

In article <dbjjrn$hcl$1@ns3.arlut.utexas.edu>,
gl@csdsun1.arlut.utexas.edu (Jay G. Scott) wrote:

> In article <42b1d7c6$0$305$cc9e4d1f@news-text.dial.pipex.com>,
> Chris Lawson <newsgroups@spamtrap.com> wrote:
> >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.
> >>
> >
> ><snip>
> >
> >Perhaps WAN Boot would do what you're looking for.
> >
> >Overview
> >http://www.sun.com/software/whitepap...secure_wan.pdf
> >
> >How to
> >http://docs.sun.com/app/docs/doc/817...kv4nh4g?a=view
> >
> >--
> >Chris
>
>
> on sparc, what i do is put an ordinary solaris distribution
> CD (the 1 of 2 CD, ie, the CD with the boot image on it)
> and say:
> boot cdrom - install nfs://<ipaddress>/tmp/Q/v440m.tar dhcp nowin
>
> the ipaddress is the ip address of the jumpstart server.
> we assume you can do nfs across subnets.
> my dhcp server will give the machine its hostname and ip.
> the v440m.tar is a tar file of the machine's profile,
> rules.ok, sysidcfg, ....
> it lives in /tmp/Q so i don't have to type so much.
>
>
> or you can try a Begin script that mounts the
> OS distribution under /cdrom.....

The OP wants to boot across nets with RAPR and only a single boot
server. He's been told he can't do that and needs to switch to DHCP to
boot across routers. AFAIK, you can't boot without a multihomed boot
server as the rarp/bootp protocol isn't routable (but dhcp is).

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