Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
1Activity
0 of .
Results for:
No results containing your search query
P. 1
Jumpstart Documentation

Jumpstart Documentation

Ratings: (0)|Views: 69|Likes:
Published by anil_shenoy

More info:

Published by: anil_shenoy on Jan 22, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

01/22/2011

pdf

text

original

 
Solaris Jumpstart Automated Installation
COURTESY : http://amorin.org/professional/jumpstart.phpAbstract
This is an introduction to custom automated installation in a Solaris environment. It is anoverview of the necessary systems, services, and configurations needed for easy client integrationinto existing corporate environments. General pre and post install modifications will also bediscussed.
What is Jumpstart
The Jumpstart feature is an automatic installation process available in the Solaris operatingenvironment. It allows system administrators to categorize machines on their network andautomatically install systems based on the category to which a system belongs. 
Reasons to Automate
Simplifies installations
Speed - Faster then CD-ROM installation
Allows unattended installation
Replication - same systems across the enterpriseAll Solaris base installations require some basic configuration. With Jumpstart, Sun has enabled thesystem administrator to avoid repetitive tasks associated with bringing a sun system online.
Prerequisites
A boot server on the same ethernet segment
An install server with the Solaris OS
A Jumpstart configuration server that defines rules and profiles. 
Needed Services UseNFS (mountd nfsd)
Sharing Solaris OS Image Files
RarpIP address discoveryBootpHost and location of shared file systemsRpldServes X86 initial boot net kernel
 
TftpServes Solaris initial boot net kernelOverview
 
IMAGE
1. Client sends a RARP for its IP address2. The Boot Server responds via RARPD (in.rarpd) with the IP addressin
/etc/ethers
or the
ethers
NIS/NIS+ map depending on the
ethers
setting in
/etc/nsswitch.conf
3. The client sends a tftp request for a bootimage4. The server starts in.tftp from inetd and sends the small net kernelimage5. The client then sends out a bootp request6. The server responds with the clients entry from /etc/bootparams7. The client NFS mount it’s root partition from the install server8. The client then mounts the configuration server (/jumpstart) and runs“sysidtool”.9. It then mounts the install image and runs Suninstall to begin theinstall process.
Boot Server
The boot server is composed of rarpd (in.rarpd), bootp (in.bootparamd), and tftp (in.tftpd)servers for solaris systems and rplboot for x86 architecture. The Boot server must be on the client’slocal network due to the fact that rarp packets will not be forwarded across a router.
Server Files:
/etc/ethers Contains entry for install clients ethernet address
8:0:20:ab:cd:ef client_name
/etc/bootparams Contains NFS share parameters for installation & configurationclient_name root=boot_svr:/export/install/Solaris_2.6/Tools/Boot \
 
install=boot_svr:/export/install boottype=:in \sysid_config=boot_svr:/jumpstart \install_config=boot_svr:/jumpstart rootopts=:rsize=32768/tftpboot Houses the small net kernel used for bootstrapping
C0A8000B
C0A8000B.SUN4Uinetboot.SUN4U.Solaris_8-1rm.192.168.0.11tftpboot/rpldboot Used in x86 installs (tftpequivalent)192.168.0.12.glue.com 
192.168.0.12.hw.com192.168.0.12.inetbootgluecode.cominetboot.I86PC.Solaris_2.7-1rm.192.168.0.12smc.com
DesignInstall Server
The install server supplies the client with the Solaris OS. It is an NFS share with the Solarisinstall image. Any OS able to export NFS shares is able to serve as a Jumpstart Install Server.
Configuration Server
The configuration Sever is comprised of the rules file, profiles, and sysidcfg. It allows theadministrator to have available different custom jumpstart configurations based on rule sets. This isvery helpful when different groups within an organization require different system configurations.Below are examples of a profile. Profiles contain filesystem layout and packageinformation.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->