Page 1 of 7

InfoPartner Document 1-61-216251-1

Document Audience: SPECTRUM
Document ID: 216251
Old Document ID: (formerly 49462)
Title: Solaris[TM] Operating System:Jumpstart with a Boot Server only utilizing Flash
Archive.
Copyright Notice: Copyright ? 2008 Sun Microsystems, Inc. All Rights Reserved
Update Date: Mon Jan 30 00:00:00 MST 2006

Solution Type Technical Instruction

Solution 216251 : Solaris[TM] Operating System:Jumpstart with a Boot Server only utilizing Flash
Archive.

Related Categories
n Home>Product>Software>Operating Systems

Steps to Follow

VQ5712J Internal ID use only.

Solaris[TM] Operating Environment software Jumpstart with a Boot Server

only utilizing Flash Archive.

The following procedures explains in detail how to create a Jumpstart boot

server only, and installing a Flash Archive via Jumpstart. This procedure
will save the administrator disk space by only installing a Jumpstart boot
image instead of a full image.

NOTES: To use the Flash Archive feature, you must be running a minimum
Solaris 8 4/01.

NOTE: In this document we will not be using a Name Service, we will be using
local /etc files. For this reason we will need to edit the /etc/nsswitch.conf
and put files first on 3 lines, hosts, ethers and bootparams.

Definition of Flash Archive: A Flash Archive is a mirrored image

of a system. You can take the mirrored image and fully install it
including patches, Veritas or Disksuite, 3rd party packages etc..,
the possibilities are endless. You can use this Flash Archive to
install on ANY system with a similar architecture. In other words, if
you create a Flash Archive of an Ultra10 (sun4u) you can use that
Archive on any sun4u system. One caveat to this is your Archive should
be entire distribution+OEM to cover different drivers that some
systems require. The following procedure is a very basic Flash Archive.
You can actually layer Flash Archives, exclude directories, and
many other options. Please refer to the Solaris 8 Advanced Installation
Guide, the Solaris 9 Installation Guide or the Solaris 10 Installation
Guide: Custom JumpStart and Advanced Installations for more detailed
information.

You can install Veritas, but not configure them. The Flash Archive does
not pass the configuration portion of these software packages properly.
You would need to configure Veritas after the Flash Archive installation.

https://spe.sun.com/info/control/DocumentSelectByType/doc=552/216251 6/18/2008
 Page 2 of 7

In Solaris 8 the above applies for Disksuite as well.

In Solaris 9 (and greater) SVM packages are already included in Solaris

and you can configure the system with SVM setup during Flash Archive
installation. See Solaris 9 Advanced Installation Guide.

On the Boot Server: (In this scenario, we will be using Solaris 8 7/01)

1) # cd /export; mkdir install

2) Insert the Solaris 8 7/01 cd 1 of 2

3) # cd /cdrom/sol_8_701_sparc/s0/Solaris_8/Tools

4) # ./setup_install_server -b /export/install

5) # cd /cdrom/sol_8_701_sparc/s0

6) # cp .cdtoc /export/install

7) Edit /etc/hosts and add IP address and hostname of the Client:

129.148.94.6 Clientname

8) Edit /etc/ethers and add ethernet address of the Client:

8:0:20:30:6:9a Clientname

9) mkdir /jumpstart

10) Create a Custom Jumpstart profile:

Edit/create /jumpstart/profile

install_type flash_install
archive_location nfs ip_address_of_Location_of_Archive:/export/archive_name
partitioning explicit
filesys c0t0d0s1 512 swap
filesys c0t0d0s0 free /

11) Share the /jumpstart directories:

Edit the /etc/dfs/dfstab

share -F nfs -o ro,anon=0 /jumpstart

NOTE: If this is the first entry in the /etc/dfs/dfstab, run:

# /etc/init.d/nfs.server start

12) # shareall

13) # dfshares (To verify share)

14) Create a sysidcfg file

# vi /jumpstart/sysidcfg

Example: (yours may differ)

system_locale=C

https://spe.sun.com/info/control/DocumentSelectByType/doc=552/216251 6/18/2008
 Page 3 of 7

timezone=US/Eastern
timeserver=129.148.94.5 <-- Server1 IP
network_interface=primary {netmask=255.255.255.0 protocol_ipv6=no}
terminal=dtterm
security_policy=NONE
name_service=NONE

NOTE: Whatever netmask you use, it must match in the following locations:
ifconfig -a
/jumpstart/sysidcfg
/etc/netmasks /export/install/Solaris_8/Tools/Boot/netmask

15) Create a rules.ok file:

vi /jumpstart/rules.ok

any - - profile -
# version=2 checksum=0

16) # cd /export/install/Solaris_8/Tools
# ./add_install_client -s bootservername:/export/install \
-c bootservername:/jumpstart -p bootservername:/jumpstart \
clientname sun4u

17) Choose a system to use to make the Flash Archive.

Whatever system you do choose should have the following:

Sol 8 4/01 (or greater) and entire distribution+OEM

All patches you would want installed

All packages you would want installed. For example: Veritas, Disksuite,
3rd party packages, any customizations etc....

18) Create the Flash Archive:

NOTE: The following command will copy your entire system contents to
/export/archive_name. You will need the space in /export to do this.

# /usr/sbin/flarcreate -n SunBlade100-archive -a "Archive creator name" -x \

/export/install /export/archive_name

Determining which filesystems will be included in the archive...

Determining the size of the archive...
<baton>
The archive will be approximately 723.87MB.
Creating the archive...
<baton>
1482390 blocks
Archive creation complete.

NOTE: The "-x /export/install" will exclude /export/install from the Archive,
which in our example is the image we are using for the purpose of
Jumpstart. More than likely you will not want this on all the systems
you are installing to, so we excluded it.

-n name

https://spe.sun.com/info/control/DocumentSelectByType/doc=552/216251 6/18/2008
 Page 4 of 7

This option is required if you are using flarcreate

for archive identification. The value of name is used
to identify the archive. It is also used as the value
of the content_name archive identification flag.

-a author
author is used to provide an author name for the
archive identification section. If you do not specify
-a, no author name is included in the identification
section.

-x exclude
Exclude the directory exclude from the archive. Note
that the exclude directory is assumed to be relative
to the alternate root specified using -R.

19) List information on the newly created Archive:

# /usr/sbin/flar -i /export/archive_name
archive_id=ae03f7e2299ea267c4ea1884860ca18e
files_archived_method=cpio
creation_date=20010122161629
creation_master=Sol8_U4
content_name=SunBlade100-archive
files_compressed_method=none
files_archived_size=758983680
content_author=Archive creater name
content_architectures=sun4u

20) Share your Archive on the system it resides on:

# vi /etc/dfs/dfstab

share -F nfs -o ro,anon=0 /export/archive_name

# shareall

21) On the client:

ok boot net - install

Internal Comments

CJN1SWK Internal ID use only.

michael.wahlberg@sun.com

Product

Solaris 8 Operating System

Solaris 9 Operating System
Solaris 10 Operating System

https://spe.sun.com/info/control/DocumentSelectByType/doc=552/216251 6/18/2008
 Page 5 of 7

Keywords

Jumpstart, flar, Flash Archive, Installation

Previously Published As

49462

Change History

KWQ2C1P Internal ID use only.

Date: 2006-01-30
User Name: 31620
Action: Approved
Comment: Verified Metadata - ok
Verified Keywords - ok
Verified still correct for audience - currently set to contract
Audience left at contract as per FvF http://kmo.central/howto/FvF.html
Checked review date - currently set to 2006-10-27
Checked for TM - no new ones needed
Publishing under the current publication rules of 18 Apr 2005:
Version: 3
Date: 2006-01-27
User Name: 31620
Action: Accept
Comment:
Version: 0
Date: 2006-01-27
User Name: 35543
Action: Approved
Comment: Made some additions regarding SVM during installation
Corrected a typo regarding /etc/netmasks
Doublechecked Document. Looks good now.
Perhaps need some more info in different handling
of shares in Solaris 10. This could be made later on.
Version: 0
Date: 2006-01-26
User Name: 35543
Action: Accept
Comment:
Version: 0
Date: 2006-01-26
User Name: 76877
Action: Approved
Comment: customer did not think this document applied to Solaris 9 since Solaris 8 was specif
Version: 0
Date: 2006-01-26
User Name: 76877
Action: Update Started

https://spe.sun.com/info/control/DocumentSelectByType/doc=552/216251 6/18/2008
 Page 6 of 7

Comment: customer confusion because only Solaris 8 is referenced. He did not think this docu
Version: 0
Date: 2004-12-29
User Name: 139313
Action: Update Canceled
Comment: *** Restored Published Content *** I don't have time to work on it.
I've filled a Kgap report to merge it with another Jumpstart Infodoc
Version: 0
Date: 2004-09-27
User Name: 139313
Action: Update Started
Comment: I'm going to merge it with ID 40820 since they're about the same topic
Version: 0
Date: 2004-09-27
User Name: 141597
Action: Update Canceled
Comment: *** Restored Published Content *** Failing time to work on it
Version: 0
Date: 2003-11-27
User Name: 141597
Action: Updated
Comment:
Version: 0
Date: 2003-05-20
User Name: Administrator
Action: Migration from KMSCreator
Comment: updated by : Robin Dole
comment : No comment
date : Dec 12, 2002

updated by : Robin Dole

comment : No comment
date : Dec 12, 2002

updated by : Michael Wahlberg

comment : Article created.
date : Dec 11, 2002

updated by : Michael Wahlberg

comment : No comment
date : Dec 11, 2002

updated by : Peter Wilk

comment : tested procedure and verified
date : Dec 11, 2002
Version: 0

Product_uuid

https://spe.sun.com/info/control/DocumentSelectByType/doc=552/216251 6/18/2008
 Page 7 of 7

a7a38948-2bd5-11d6-98ce-9d3ac1c0cfd7|Solaris 8 Operating System

4f82caac-36f3-11d6-866b-85f428ef944e|Solaris 9 Operating System
5005588c-36f3-11d6-9cec-fc96f718e113|Solaris 10 Operating System

Attachments

This solution has no attachment

This collection hosted on The Sun Partner Exchange Portal

Copyright (c) 1997 - 2008 Sun Microsystems, Inc

https://spe.sun.com/info/control/DocumentSelectByType/doc=552/216251 6/18/2008