Softpanorama (slightly skeptical) Open Source Software Educational Society

May the source be with you, but remember the KISS principle ;-)

Solaris Jumpstart

The Jumpstart is pretty neat NFS-based installation process for Solaris available for both UltraSparc and x86. It provides flexible "unattended installation" allowing system administrators to categorize machines on their network and install different system components or even versions of OS based on the category to which a system belongs. It also provides the infrastructure to preserve installation information from one generation of sysadmins to another.

In its simplest form the Jumpstart process involves the following stages (RARP based IP address retrieval is OK for installation from "Jumpstart laptop" via crossover cable which is the classic way to use Jumpstart; if the images are somewhere on the the bootable CD/DVD is the way to go):

1. Admin issues the boot net - install command from the 'ok' prompt of the client
    
2. Client machine broadcasts a RARP request to the local subnet
    
3. The Boot Server responds via RARPD (in.rarpd) with the IP address in /etc/ethers (or the ethers NIS map depending on the ethers setting in /etc/nsswitch.conf ) matching the hostname listed for the client's MAC address in the server's /etc/ethers file
    
4. The client sends a tftp request for a bootimage.
    
5. On the boot server, the "inetd" daemon listens for and handles tftp requests. After receiving the tftp request it spawns the  in.tftpd daemon to handle this request. . The server starts in.tftp from inetd and sends the small net kernel image. This way the Jumpstart boot image is sent back to the client
    
6. Client downloads and boots the boot image
    
7. Client starts bootparams client and requests boot information from Boot Server:  boot image issues a hostconfig request  for boot parameters.
    
8. rpc.bootparams server on Boot Server responds to a hostconfig request with the NFS location of a Jumpstart directory, an install-root filesystem, and the location of sysidcfg directory. rpc.bootparamd is a server process that usually provides information from a bootparams database to diskless clients at boot time. Under Solaris rpc.bootparamd usually is started by the nfs.server init script if the directory /tftpboot exists.
    
9. Client NFS-mounts Boot Server's Jumpstart directory as its root filesystem. After that client NFS-mounts Install server's Jumpstart directory and launches Solaris install
    
10. Solaris install on the client begins "System Indentification" stage of install. You might recognize this stage as where the install program asks for host, network, locale, date and time information. Client NFS-mounts the sysidcfg directory it was given by the rpc.bootparams daemon on the Boot server.
     
11. Client reads host configuration information from the configuration  file named 'sysidcfg' inside the sysidcfg directory it has mounted. Client switched to interactive mode for any information not contained in this file
     
12. Client begins "System Install" stage of install. If you are familiar with CD installs of Solaris, you will recognize this stage as where the install program asks you to choose a partition layout for system and to choose a package cluster/and or individual software packages to install.
     
13. Client finds line matching it's own system architecture, hostname, IP address, etc. in 'rules.ok' text file in Install server's Jumpstart directory. From this line the Client retrieves the name of a begin-script, profile, and finish-script. The profile is a text file, the begin and finish scripts Bourne shell scripts. All three files are located in the Install server's Jumpstart directory
     
14. Client executes the begin-script, if any
     
15. Client partitions and formats its disks according to rules in its profile
     
16. Client installs software packages according to rules in its profile
     
17. Client installs any system patches found in the Install server's Jumpstart/Patches directory, if any. It installs these patches in date-wise order (that is to say according to their time-stamps) from oldest to newest
     
18. Client executes the finish scripts, if any. Note that we did not rebooted the computer yet, so available to us tools are limited. Usually it makes more sense to reboot the computer, connect to it using ssh and execute finish scripts at this point.
     
19. Client reboots

Among positive features:

1. Simplifies installations  and permits its automation
2. Faster and less tedious then CD-ROM installation as most answers can be preprogrammed and there is not need to change disks.
3. Allows unattended/automatic  installation with post-processing (for example, hardening using JASS)
4. Replication - creation of multiple identical or semi-identical systems across the enterprise

Among negative features:

• Pretty complex multistage process with the possibility of failure on many stages (flash archive is a simpler, more reliable method).  The majority of problems are usually connected with the boot server and it is prudent to try to avoid them.
  • Unless you use DHCP server Jumpstart boot server need to be on the same segment as the server for which you need to install the OS. This is due to the limitations of RARP.  RARP does not furnish a network mask to the client, limiting the boot server (tftp) to reside on the local network.  Also if the router is not configured to pass RARP broadcasts (default) then the client will never find it’s own IP address.
    • the usage of "Jumpstart laptop" is a classic way to resolve boo server problems
    •  Bootable CD or DVD is another neat way to compensate this weakness. See  Performing Network Installations Without a Local Boot Server -by John S. Howard

      In some instances, it might be necessary or advantageous to boot an installation client from local boot media, such as a CD or DVD, but have the Solaris product installed from a JumpStart (or installation) server. This article describes the system startup and installation processes for the Solaris Operating System and explains how to modify them to change the location from which the Solaris product is installed.

    • Sometimes one can use DHCP to avoid this problem.
       
• Transfer of large amount of information via NFS is slow if this is WAN not LAN. Here against flash installation from DVD beats Jumpstart hands down. "Jumpstart laptop" method also solves this problems pretty neatly.

Old News ;-)

[Sep 8, 2008] BigAdmin Description - Less Known Solaris Features - Jumpstart Enterprise Toolkit

Description: A sixteen part tutorial about the configuration of the Jumpstart Enterprise Toolkit (JET).

Jumpstart and Jet have several ways and means to do an automatic installation, thus making the live of the admin much easier after you´ve done the initial setup.

This tutorial will show you that this setup is really easy.

[Apr 2, 2007] BigAdmin Feature Article Using Solaris JumpStart With the Solaris 10 OS for x86-x64 Platforms

... Using Solaris JumpStart software on the Solaris 10 OS for x86/x64 platforms is essentially the same as on Solaris 10 OS for SPARC platforms. However, there are some subtle differences that need to be addressed for correct operation.

This document provides the steps and explanations necessary to set up a JumpStart server for the Solaris 10 OS on a Sun x86/x64 machine, along with configuring JumpStart for two or more clients.

As a general reference, refer to the Sun online document Using Custom JumpStart.

[Jan 7, 2007] BigAdmin Submitted Article UberJS A More Flexible Solaris JumpStart System by by John Dickerson and Brett Trotter, Iowa State University

Extracting the Slices from the CD (Creating a Work Space)
Modifying the Images
Modifying the JumpStart Scripts
uberjs-exec Script
Install Configuration Files on the CD
Configuration Files for All Options
The UberJS sysidcfg File on the JumpStart Server
Burning the CD-ROM
Creating an ISO Image
Credits
References
About the Authors
 

Installing the Solaris Operating System usually comes down to a choice between using CDs or JumpStart. Nobody wants to install more than a couple of machines using CDs and a generic configuration, so most administrators use Sun's Solaris JumpStart software if they want to customize their builds.

JumpStart is a powerful tool that makes unattended Solaris installs possible with fine-grained control over machine configurations, but it has a few shortcomings. JumpStart is fairly limited in booting flexibility, but is still very capable when it comes to machine profiles. JumpStart only works if the JumpStart boot server is on the same network segment as the machine you're installing, and before you can do a network build of a machine you have to configure the JumpStart server using Sun's add_install_client script. If you've made an error in one of the many JumpStart configuration files and you're down the hall from the server, you can burn through a lot of shoe leather because of a typo.

In the College of Engineering at Iowa State University, we wanted to make JumpStart a little easier. We install Sun boxes on many LANs where we can't afford a JumpStart server or it isn't practical to manage one. For a while we built our machines using JumpStart on an Intel laptop running Linux that we carried from building to building, but the setup time got to be a headache. We needed a solution that was portable, easy to use, and didn't require touching the JumpStart server for every new machine. We wanted to preserve JumpStart's ability to apply different build profiles from a central location, and we wanted unattended install capability.

We've developed a system we call UberJS (for Uber JumpStart). We modeled it after Red Hat's Kickstart so a person can boot a machine from CD, type a simple command and walk away. With some clever hacking of the JumpStart install scripts and a CD burner, we created a bootable JumpStart CD that handles the networking initialization usually provided by a JumpStart boot server, but still allows us to access build profiles in a remote JumpStart or Flash install repository. With the UberJS CD, we can jumpstart machines even when there is no JumpStart server on the LAN. What's more, we incorporated more general configuration files that give us more flexibility and spontaneity than Sun's JumpStart provides.

To understand UberJS, let's first review what happens during a typical JumpStart or Flash install. (Kevin Amorin provides an excellent summary of the process: Solaris JumpStart Automated Installation.)

When you boot a Sun box with boot net - install, it uses reverse ARP to get its IP address from a JumpStart boot server, which has that machine in its ethers list. Once its IP address is determined, the client sends a TFTP request to the server for a network boot kernel image. A symlink must be created in a TFTP directory on the server beforehand, linking the hex version of the IP address of the machine to the boot image for that specific hardware. The client boots and sends an rpc.bootparams request to the boot server that specifies which NFS servers the client is to use for Solaris install packages, sysidcfg (system configuration) settings, and the install profiles. The client then mounts the paths from the NFS servers, reads the sysidcfg settings, determines its build profile, and installs the packages. The rules.ok file on the install profile server tells the Sun installer what profile to use, and each profile dictates either JumpStart or Flash install, which packages to install, and what pre- and post-installation scripts to run (if any). As you might expect, getting this all working can be a little tricky.

UberJS gives us some key improvements over JumpStart:

• UberJS switches the Sun installer from a CD-ROM-based install to a network-based install soon after it starts. More aptly, it fools JumpStart into doing a network install by putting network mounts where it expects CD-ROM media. When combined with the network initialization code, this is the major change in UberJS.
• UberJS doesn't require a reverse ARP server on the network because it looks up the IP address from a file on the CD, uses DHCP, or simply prompts you for the machine's IP address at the start.
• There is no need to TFTP the boot image since the system boots from a Solaris installation CD.
• The UberJS networking setup is more automated with features such as router auto-discovery, so it's not necessary to manage separate sysidcfg files for each network segment.
• UberJS can either read a bootparams file that is burned on the CD or wget'd once the network comes up, which associates a client with a specific install and config server, or it can download a list of potential NFS server paths from an FTP server to give you a choice of install server mirrors.
• Even though you are initiating a CD-ROM install, you can still build according to specific machine profiles stored on a JumpStart install server.

Keep in mind that UberJS still assumes you have a JumpStart or Flashstart install repository available via NFS that includes predefined build profiles. We won't go into detail about how to set that up here. Use Kevin Amorin's page or JumpStart documentation from Sun for details.

All of our scripts and methods were developed using the Solaris 9 08/03 Release.

Here's a quick summary of what it takes to set up an UberJS build.

1. Extract the data from a Solaris 9 Install V1 CD and mount the slices for editing.
2. Add a script called uberjs-exec to the existing scripts. This script performs the essence of the behavior added by UberJS, including prompting you for inputs, setting up the network, downloading configuration files from an FTP server, and processing of UberJS-specific configuration files.
3. Modify Sun's rcS and sysidfind scripts. Normally, the rcS and sysidfind scripts do most of the network setup and location of server paths. We modify rcS to call uberjs-exec instead to handle the networking and server path mounting. We also add a mechanism to turn off the twirling dial since it interferes with screen prompts. sysidfind usually fetches the sysidcfg file from a network mount and copies it to the miniroot, but since uberjs-exec does all of the mounting and copying, we need to modify the sysidfind script to simply check to see if the file already exists.
4. Create a few configuration files and either copy them to the CD slices or to an accessible FTP server. The configuration files can be used either to hard code the paths to the JumpStart configuration files or to set up where those files can be downloaded at build time.
5. Make an ISO image out of the modified slices and burn a new CD.
6. Boot the client machine with boot cdrom - install.
7. Sit back and enjoy a hot beverage.

In case you want to cut to the chase, we created a script called mkuber that can automate the entire CD creation process for you. Simply place a Solaris 9 Install V1 CD in the drive and run the script. All that is left to do after the script runs is add any site-specific configuration files, as discussed below. mkuber is available on the UberJS web site. If you wish to perform the alterations manually and/or become more familiar with UberJS, the following methods will create a successful UberJS CD.

[Jan 28, 2006] BigAdmin Submitted Article Server Configuration for Solaris JumpStart Software by Mohammad Shafiuddin Sharif

Looks like a plagiarized from SA-299 (not timezone (US/Mountain) and directories used).

The Solaris 9 Operating System offers an automatic installation process, Solaris JumpStart software. The Solaris JumpStart procedure enables you to install the Solaris OS automatically and configure it differently, depending on the characteristics of client systems. These identifying characteristics are used to select the correct configuration for each client system.

The following tasks are required to configure a single JumpStart server to provide basic software installation services using the JumpStart procedures:

1. Spool the operating system image.
2. Edit the sysidcfg file.
3. Edit the profile and rules.
4. Run the check script.
5. Run the add_install_client script.
6. Boot the client.

Step #1

To spool the Solaris 9 boot and installation images to a local disk, complete the following steps:

Create a directory with at least 800 Mbytes of space available to hold the Solaris OS image. Usually the /export/install directory is used.

# mkdir /export/install

Insert the Solaris 9 Software 1 of 2 CD-ROM in the CD-ROM drive or the Solaris 9 DVD in the DVD drive.

Change the directory to the location of the setup_install_server script.

# cd /cdrom/cdrom0/s0/Solaris_9/Tools

Run the setup_install_server script to copy the Solaris 9 OS installation images to the local disk.

#./setup_install_server /export/install

When the setup_install_server script finishes, change the directory to root (/), and eject the CD-ROM or DVD.

#cd /
#eject cdrom

If you use CD-ROM media, insert the Solaris 9 Software 2 of 2 CD-ROM in the CD-ROM drive.

Change the directory to the location of the add_to_install_server script.

# cd /cdrom/cdrom0/Solaris_9/Tools

Run the add_to_install_server script to copy the remainder of the installation image to the local disk.

#./add_to_install_server /export/install

When add_to_install_server finishes, change the directory to root (/), and eject the CD-ROM.

# cd /
# eject cdrom

Step #2

The sysidcfg file keeps the various types of system information such as locale, time_zone, and so on, and supplies the information to the client at the booting time.

Create a directory to hold the sysidcfg file. Typically the /export/config directory holds the sysidcfg file.

# mkdir /export/config

Change the directory to /export/config, and create a file called sysidcfg using a text editor.

# cd /export/config
# vi sysidcfg

In the sysidcfg file, add the following lines. Substitute values that are appropriate for your systems, location, and network.

network-interface=primary {protocol-ipv6=no
				netmask=255.255.255.0}

security_policy=none
name_service=none
time_zone=US/Mountain
system_locale=en_us

Save the sysidcfg file, and exit your edit session.

Step #3

a. Rules

Create a directory to hold the rules file if this directory does not already exist. Usually, the /export/config directory holds the rules file.

# mkdir /export/config

Change the directory to /export/config, and create a file called rules using a text editor.

# cd /export/config
# vi rules

In the rules file, add the following line:

hostname client_name - profile1 -

For client_name, substitute the name of your JumpStart client. For example:

hostname	sun1	- profile   -

Save the rules file, and exit your edit session.

b. Profiles

Usually, the /export/config directory holds the profile file.

Change the directory to /export/config, and create a file called profile using a text editor.

# cd /export/config

# vi profile1

Add the following lines to the profile1 file:

install_type	initial_install
system_type	standalone
partitioning	explicit
filesys		c0t0d0s0	 free	/
filesys		c0t0d0s1	128	swap
cluster		SUNWCXall

Save the profile1 file, and exit your edit session.

Step #4

Before a JumpStart client can use a configuration provided by a JumpStart server, you must run the check script to produce a file called rules.ok. The check script validates the syntax of the rules file and the profile files. If the validation completes successfully, the check script creates the rules.ok file.

Change the directory to the location of the check script.

# cd /export/install/Solaris_9/Misc/JumpStart_sample

Copy the check script to the /export/config directory.

# cp check /export/config

Change the directory to /export/config, and run the check script.

# cd /export/config
#./check
Validating rules...
Validating profile profile1...
The custom JumpStart configuration is ok.

Step #5

a. Add a host entry.

Edit the /etc/ethers file, and add an entry for the JumpStart client.

#vi /etc/ethers 

00-C0-26-84-34-A1		sun1

Save and exit from the ethers file.

Edit the /etc/inet/hosts file, and add an entry for the JumpStart client.

#vi /etc/inet/hosts

192.168.1.1	sun1

Save and exit from the hosts file.

b. Add a client.

Change the directory to the location of the add_install_client script on the server.

# cd /export/install/Solaris_9/Tools

Run the add_install_client script, and specify server and client information as follows. (Note: The following line of code should all be entered on one line.)

#./add_install_client -c server_name:/export/config \
    -p server_name:/export/config client_name platform_group

For example:

#./add-install-client -c sun:/export/config -p sun:/export/config sun1 sun4u

Edit the /etc/dfs/dfstab file to add the following line:

#vi /etc/dfs/dfstab

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

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

Save and exit from the dfstab file.

Run the shareall command to share the /export/config and /export/install directories.

#shareall

Verify that the /export/config and /export/install directories are currently shared.

#share

Step #6

Booting the JumpStart Client

After the JumpStart server has been configured to provide all of the required services, you can initiate the installation process on the JumpStart client. To boot the JumpStart client, perform the following steps:

a. Bring the JumpStart client to run state 0.

# init 0

b. Boot the client to initiate the software installation using the JumpStart procedure.

ok boot net - install

docs.sun.com Solaris 9 Installation Guide

Jumpstart can be performed on a stanalone system. In this case floppy should contain rules and profiles and DVD-ROM should contain instllation media

After you validate the rules file and the profiles, you can begin a custom JumpStart installation. The JumpStart program reads the rules.ok file. Then, the JumpStart program searches for the first rule with defined system attributes that match the system on which the JumpStart program is attempting to install the Solaris software. If a match occurs, the JumpStart program uses the profile that is specified in the rule to install the Solaris software on the system.

Figure 22–1 illustrates how a custom JumpStart installation works on a standalone, non-networked system. The system administrator initiates the custom JumpStart installation on Pete's system. The JumpStart program accesses the rules files on the diskette in the system's diskette drive. The JumpStart program matches rule 2 to the system. rule 2 specifies that the JumpStart program use Pete's profile to install the Solaris software. The JumpStart program reads Pete's profile and installs the Solaris software, based on the instructions that the system administrator specified in Pete's profile.  

docs.sun.com Solaris 9 Installation Guide

A diskette that contains a JumpStart directory is called a profile diskette. A system that is not connected to the network does not have access to a profile server. As a result, you must create a JumpStart directory on a diskette if a system is not connected to a network. The system on which you create a profile diskette must have a diskette drive.

The JumpStart directory contains all of the essential custom JumpStart files, for example, the rules file, rules.ok file, and profiles. You must save the JumpStart directory in the root (/) directory of the profile diskette.

SPARC: To Create a Profile Diskette

This procedure assumes that the system is running Volume Manager. If you are not using Volume Manager to manage diskettes, CDs, and DVDs, refer to System Administration Guide: Basic Administration for detailed information about managing removable media without Volume Manager.

1. Log in as superuser on a SPARC system to which a diskette drive is attached.
2. Insert a blank diskette or a diskette that can be overwritten in the diskette drive.
3. Mount the diskette.

   # volcheck

4. Determine if the diskette contains a UNIX file system (UFS).

   Examine the contents of the file /etc/mnttab on the system for an entry such as the following:

   /vol/dev/diskette0/scrap  /floppy/scrap  ufs  suid,rw,largefiles,dev=1740008  927147040

   • If the entry exists, go to Step 7.
   • If the entry does not exist, go to the next step.
5. Format the diskette.

   ---

   Caution - Formatting erases all data on the diskette.

   ---

   # fdformat -U

6. Create a UFS on the diskette.

   # newfs /vol/dev/aliases/floppy0

7. Determine if you want to copy examples of custom JumpStart files to your JumpStart directory.
   • If no, go to Step 10.
   • If yes, use the following decision table to determine what to do next.

   Example Locations	Instructions
   The Solaris 9 SPARC Platform Edition DVD or the Solaris 9 Software 1 of 2 SPARC Platform Edition CD	Insert the Solaris 9 SPARC Platform Edition DVD or the Solaris 9 Software 1 of 2 SPARC Platform Edition CD into the server's CD-ROM drive. Volume Manager automatically mounts the CD.
   An image of the Solaris 9 SPARC Platform Edition DVD or the Solaris 9 Software 1 of 2 SPARC Platform Edition CD on a local disk	Change the directory to the location of the Solaris 9 SPARC Platform Edition DVD or the Solaris 9 Software 1 of 2 SPARC Platform Edition CD image. For example, type the following command: cd /export/install

    

8. Copy the example custom JumpStart files into the JumpStart directory on the profile diskette.

   # cp -r media_path/Solaris_9/Misc/jumpstart_sample/* jumpstart_dir_path

   media_path	The path to the CD, DVD, or image on the local disk
   jumpstart_dir_path	The path to the profile diskette where you want to place the example custom JumpStart files

   ---

   Note -

   You must place all custom JumpStart installation files in the root (/) directory on the diskette.

   ---

   For example, the following command copies the contents of jumpstart_sample on the Solaris 9 Software 1 of 2 SPARC Platform Edition CD to the root (/) directory on a profile diskette that is named scrap:

   cp -r /cdrom/sol_9_sparc/s0/Solaris_9/Misc/jumpstart_sample/* /floppy/scrap

9. Update the example JumpStart files on the profile diskette so that the files work in your environment.
10. Ensure that root owns the JumpStart directory and that permissions are set to 755.
11. Eject the diskette.

    # eject floppy

    You have completed the creation of a profile diskette. You can now update the rules file and create profiles on the profile diskette to perform custom JumpStart installations. To continue, go to “Creating the rules File”.

[PDF] Configuring JumpStart™ Servers to Provision Sun™ x86-64 Systems (February 2005)  -by Pierre Reynes
File Format: PDF/Adobe Acrobat - View as HTML

Organizations are constantly challenged to deploy systems throughout the enterprise with consistent and reliable configurations. Solaris JumpStart technology provides a mechanism for fully automating the Solaris Operating System (Solaris OS) installation process. With the ability to locate installation information over the network or from a local CD-ROM drive, and use customized profiles, JumpStart facilitates the rapid and consistent deployment of Solaris OS-based systems.

Many organizations have relied on UltraSPARC/Solaris platforms for years, and use JumpStart technology for operating system deployment. With the introduction of Sun x86-64 based systems, organizations are now seeking ways to use existing JumpStart servers to deploy the Solaris OS and Linux operating environment on Sun x86-64 based systems. This article describes how to modify existing JumpStart servers to support the deployment of the Solaris OS and Linux operating environment on Sun x86-64 based systems, as well as how to use standard Linux installation tools for configuring Sun x86-64 based systems.

Solaris 8 Jumpstart Setup-How-To By Scott D. Matott sXe scott_matott@uchicago.edu

I wrote this page to document how I built a jumpstart server for my group and to help others. Although it didn't take me long to build a jumpstart server, it did take a lot of internet searching, reading of Sun docs and some previous jumpstart experience to figure out what all the pieces were and how they fit together. My hope in writing this document and posting it on the web is to create a place where others can go to find out most of all they need to know to setup a jumpstart server, thus saving them some of the searching, reading and trouble that I had to endure.

Solaris x86 umpstart on VMware
1: Installation from local CD-Roms and Floppies. The automatic installation of
Solaris can be done using CD-Rom or DVD Media. In this case the JumpStart ...
jan.exss.de/en/vms_install_auto.html - 14k - Jan 9, 2006 - Cached - Similar pages

[PDF] Solaris Jumpstart Basics   by  Hal Pomeranz, Deer Run Associates
File Format: PDF/Adobe Acrobat - View as HTML
Sun's primary reference for Jumpstart configuration is the Solaris Advanced
Installation. Guide which may be found on the Web at ...
www.deer-run.com/~hal/jumpstart/Jumpstart.pdf - Similar pages

[Dec 30 2005] Creating a Customized Boot CD/DVD for the Solaris Operating System for x86 Platforms  by John Cecere, Dana Fagerstrom

This article explains the mechanics of the boot process on the Solaris Operating System for x86 platforms so that you understand what is needed to create a customized CD/DVD. It discusses both the hard disk and CD/DVD boot processes, and points out the differences between the two.

There are a number of practical applications for this topic, including:

• Jumpstart Software — The feature in Solaris that allows access to Solaris installation media and configuration rules over a network
• Diagnostics — The ability to create a bootable CD for the purpose of diagnosing system problems without accessing or modifying the copy of the operating system that is installed on the target system
• Restoration — The ability to create a bootable CD with tools that aid in the repair and restoration of a down system
• Diskless clients that cannot do PXE booting—PXE is a DHCP-based network-based installation technology similar to Solaris Jumpstart. Some older x86-based system are incapable of using PXE
• Canned Firewall—The creation of a bootable CD that starts Solaris on a system configured with multiple network interfaces. A preset ipf configuration is then used to establish a network firewall on that system.

This article begins by examining the layout of a hard disk in the x86 architecture and the components on it that are used for booting. It then describes the pieces that are unique to a CD boot. Finally, this article puts the pieces together and creates an image file that can be burned to CD.

Using Live Upgrade 2.0 With JumpStart Technology and Web Start Flash

• Article is provided courtesy of Prentice Hall PTR.
• Date: May 24, 2002.

[Apr 30, 2004] Building a Bootable DVD to Deploy a Solaris Flash Archive -by John S. Howard

This article provides techniques to augment a DVD-ROM-based installation with the services and behaviors typically provided by a JumpStart server. The techniques presented in this article can be used when you need to perform an automated installation of a Solaris Flash archive, but are unable to use a JumpStart server. This article describes a procedure to create a bootable installation DVD-ROM with a complete software stack on a DVD that you can use to perform a standardized and fully automated installation of the software stack from the DVD.

This article also examines the structure of a bootable Solaris OS DVD and provides information about modifying installation behaviors to perform an automated install of a Solaris Flash archive from a DVD.

[Nov 30, 2001] WebStart Flash by John S. Howard and Alex Noordergraaf

The Solaris Operating Environment Flash installation component extends JumpStart technology by adding a mechanism to create a system archive, a snapshot of an installed system, and installation of the Solaris Operating Environment from that archive. This article introduces the concepts and best practices for a Flash archive, describes the master machine, and suggested storage strategies, and provides a complete example of creating a Flash archive and installing a Web server with Flash.

[Sep 30 2003] Deploying the Solaris Operating Environment Using a Solaris Security Toolkit CD by Steven Spadaccini

The Solaris Security Toolkit is a collection of shell scripts combined to form a flexible and extensible framework for rapidly deploying hardened platforms running the Solaris Operating Environment. The Toolkit is, however, quite versatile and can be used for much more than just hardening a system. This article discusses how the Toolkit can be used to construct a bootable CD, based on Sun's JumpStart framework, for building and configuring new systems. This article is authored for intermediate and advanced system administrators.
 

JumpStart Architecture and Security Scripts for the Solaris Operating Environment - Part 3 (September 2000) by Alex Noordergraaf

This article is third in a three part series describing an automated toolkit for implementing the security modifications documented in earlier Sun BluePrints onLine articles. In conjuction with this final article the toolkit itself is being made freely available.
 

JumpStart Architecture and Security Scripts for the Solaris Operating Environment - Part 2 (August 2000) by Alex Noordergraaf

This article is part two of a three part series that presents the JumpStart Architecture and Security Scripts toolkit. We continue with an in-depth review of the configuration files, directories, and scripts used by the toolkit to enhance the security of Solaris Operating Environment systems. This series is a must read for anyone interested in upgrading the security of their site.
 

JumpStart Architecture and Security Scripts for the Solaris Operating Environment - Part 1 (July 2000) by Alex Noordergraaf

This article is part one of a three part series presenting the JumpStart Architecture and Security Scripts tool (Toolkit) for the Solaris Operating Environment. The Toolkit is a set of scripts which automatically harden and minimize Solaris Operating Environment systems. The modifications made are based on the recommendations made in the previously published Sun BluePrints OnLine security articles.

Recommended Links

---

In case of broken links please try to use Google search. If you find the page please notify us about new location

---

Solaris Jumpstart Automated Install  www.amorin.org/professional/jumpstart.php - 102k - Dec 16, 2005

Enterprise Rollouts with JumpStart  by Jason Heiss  also [PDF] Enterprise Rollouts with JumpStart

Solaris Jumpstart

• Solaris Jumpstart Server Install

Solaris Jumpstart Automated Install

Solaris Jumpstart Basics

Jumpstart Information and Related Links

BigAdmin Submitted Article- UberJS- A More Flexible Solaris ...

Setting Up a Solaris™ Operating Environment Install Server and the ...

Solaris Jumpstart

The UNIX Forums - Create a Solaris Jumpstart from iso

Solaris Jumpstart AFS install

Solaris jumpstart installation @ DESY

Jon's Configuring Solaris Jumpstart Without a Name Service Lab

Blueprints

[PDF] Configuring JumpStart™ Servers to Provision Sun™ x86-64 Systems (February 2005)  -by Pierre Reynes
File Format: PDF/Adobe Acrobat - View as HTML

Organizations are constantly challenged to deploy systems throughout the enterprise with consistent and reliable configurations. Solaris JumpStart technology provides a mechanism for fully automating the Solaris Operating System (Solaris OS) installation process. With the ability to locate installation information over the network or from a local CD-ROM drive, and use customized profiles, JumpStart facilitates the rapid and consistent deployment of Solaris OS-based systems.

Many organizations have relied on UltraSPARC/Solaris platforms for years, and use JumpStart technology for operating system deployment. With the introduction of Sun x86-64 based systems, organizations are now seeking ways to use existing JumpStart servers to deploy the Solaris OS and Linux operating environment on Sun x86-64 based systems. This article describes how to modify existing JumpStart servers to support the deployment of the Solaris OS and Linux operating environment on Sun x86-64 based systems, as well as how to use standard Linux installation tools for configuring Sun x86-64 based systems.

Creating a Customized Boot CD/DVD for the Solaris Operating System for x86 Platforms (December 2005)
-by John Cecere, Dana Fagerstrom

This article explains the mechanics of the boot process on the Solaris Operating System for x86 platforms so that you understand what is needed to create a customized CD/DVD. It discusses both the hard disk and CD/DVD boot processes, and points out the differences between the two.

There are a number of practical applications for this topic, including:

• Jumpstart Software — The feature in Solaris that allows access to Solaris installation media and configuration rules over a network
• Diagnostics — The ability to create a bootable CD for the purpose of diagnosing system problems without accessing or modifying the copy of the operating system that is installed on the target system
• Restoration — The ability to create a bootable CD with tools that aid in the repair and restoration of a down system
• Diskless clients that cannot do PXE booting—PXE is a DHCP-based network-based installation technology similar to Solaris Jumpstart. Some older x86-based system are incapable of using PXE
• Canned Firewall—The creation of a bootable CD that starts Solaris on a system configured with multiple network interfaces. A preset ipf configuration is then used to establish a network firewall on that system.

This article begins by examining the layout of a hard disk in the x86 architecture and the components on it that are used for booting. It then describes the pieces that are unique to a CD boot. Finally, this article puts the pieces together and creates an image file that can be burned to CD.

Performing Network Installations Without a Local Boot Server (May 2004)
-by John S. Howard
In some instances, it might be necessary or advantageous to boot an installation client from local boot media, such as a CD or DVD, but have the Solaris product installed from a JumpStart (or installation) server. This article describes the system startup and installation processes for the Solaris Operating System and explains how to modify them to change the location from which the Solaris product is installed.

Building a JumpStart Infrastructure (April 2001)
-by Alex Noordergraaf
This article discussed how the core JumpStart components interract. Recommendations on how to structure the JumpStart server are provided in addition to step by step instructions on how to get a basic automated JumpStart environment up and running as quickly as possible.

Customizing the JumpStart Boot Image Recovery (March 2001)
-by John S. Howard
This article includes techniques and recommendations for creating a recovery platform by augmenting the Solaris OE boot image (mini-root). This article will also examine the boot and installation processes by demonstrating how to adapt those processes for system recovery.

Building a Bootable JumpStart Installation CD-ROM (March 2001)
-by John S. Howard
This article presents an examination of the structure of a bootable Solaris Operating Environment (Solaris OE) CD-ROM and procedures for how to create a bootable JumpStart installation CD-ROM. This CD can be used to complete a standardized, hands-free Solaris OE installation in environments where the disk space or networking constraints do not allow for a JumpStart server.

JumpStart Mechanics: Using JumpStart Application for Hands- Free Installation of Unbundled Software - Part 2 Automatic Encapsulation of the Root Disk (June 2000)
-by John S. Howard
John provides procedures to fully automate the initial configuration of Sun Enterprise Volume Manager and automate encapsulation of the boot disk using JumpStart.

Setting Up a Solaris Operating Environment Install Server and the Solaris JumpStart Feature (December 1999)
-by Rob Snevely
A walkthrough on setting up an install server.

JumpStart: NIS and sysidcfg (October 1999)
-by Rob Snevely
How to use JumpStart technology to allows automation of the install process.

MR System for Rapid Recovery (January 2001)
-by John S. Howard
This article is an introduction to the MR system for rapid recovery. As the system uptime requirements have become more exacting, the length of time it takes to boot these larger and more complex systems has grown. By implementing MR on your JumpStart servers it may be possible to reduce the number of reboots required during a system recovery or service event. This minimization of reboots will speed recovery and service time as well as enable the system administrator to use datacenter tools during system recovery procedures.

Ethernet Autonegotiation Best Practices
-by Steve Hodnett and Jim Eggers
Issues related to network performance, delays, jumpstart problems and link failures due to incorrect ethernet link speed and duplex settings are becoming more common due to outdated Ethernet link policies adopted by many administrators. This is largely due to misunderstanding of Ethernet autonegotation standards and experiences with older ethernet drivers and switches.

This article details Sun's recommendation to leave Ethernet autonegotiation enabled (default) when connecting Solaris Operating System 100Mb and 1000Mb Ethernet NICs to switches and hubs that are IEEE 802.3 compliant. Customers are unnecessarily setting 100Mb and 1000Mb ethernet interfaces parameters in /etc/system and driver.conf, or using ndd, without fully understanding the possible ramifications and negative results.

Performing Network Installations Without a Local Boot Server -by John S. Howard
In some instances, it might be necessary or advantageous to boot an installation client from local boot media, such as a CD or DVD, but have the Solaris product installed from a JumpStart (or installation) server. This article describes the system startup and installation processes for the Solaris Operating System and explains how to modify them to change the location from which the Solaris product is installed.

Building a Bootable DVD to Deploy a Solaris Flash Archive
-by John S. Howard
This article provides techniques to augment a DVD-ROM-based installation with the services and behaviors typically provided by a JumpStart server. The techniques presented in this article can be used when you need to perform an automated installation of a Solaris Flash archive, but are unable to use a JumpStart server. This article describes a procedure to create a bootable installation DVD-ROM with a complete software stack on a DVD that you can use to perform a standardized and fully automated installation of the software stack from the DVD.

This article also examines the structure of a bootable Solaris OS DVD and provides information about modifying installation behaviors to perform an automated install of a Solaris Flash archive from a DVD.
 

Deploying the Solaris Operating Environment Using a Solaris Security Toolkit CD
-by Steven Spadaccini
The Solaris Security Toolkit is a collection of shell scripts combined to form a flexible and extensible framework for rapidly deploying hardened platforms running the Solaris Operating Environment. The Toolkit is, however, quite versatile and can be used for much more than just hardening a system. This article discusses how the Toolkit can be used to construct a bootable CD, based on Sun's JumpStart framework, for building and configuring new systems. This article is authored for intermediate and advanced system administrators.

Customizing JumpStart Framework for Installation and Recovery
-by John S. Howard and Alex Noordergraaf
Techniques to augment a CDROM-based installation with the services and behaviors provided by a JumpStart server are detailed in this article. These techniques are suitable to situations when a hands-free Solaris Operating Environment (Solaris OE) installation is necessary but when a JumpStart server cannot be used. This article is a chapter from the Sun BluePrints book, "JumpStart Technology: Effective Use in the Solaris Operating Environment", ISBN# 0-13-062154-4.

Using Live Upgrade 2.0 With JumpStart Technology and Web Start Flash
-by John S. Howard
In this final installment of his three-part series on Solaris Live Upgrade 2.0 (LU) technology, John S. Howard provides recommendations and techniques for integrating LU with the JumpStart software framework and the Solaris Web Start Flash software. The first two articles in this series can be found at: http://www.sun.combrowsesubject.html.

WebStart Flash
-by John S. Howard and Alex Noordergraaf
The Solaris Operating Environment Flash installation component extends JumpStart technology by adding a mechanism to create a system archive, a snapshot of an installed system, and installation of the Solaris Operating Environment from that archive. This article introduces the concepts and best practices for a Flash archive, describes the master machine, and suggested storage strategies, and provides a complete example of creating a Flash archive and installing a Web server with Flash.

Building a JumpStart Infrastructure
-by Alex Noordergraaf
This article discussed how the core JumpStart components interract. Recommendations on how to structure the JumpStart server are provided in addition to step by step instructions on how to get a basic automated JumpStart environment up and running as quickly as possible.

• Customizing the JumpStart Boot Image for Recovery
  -by John S. Howard
  This article includes techniques and recommendations for creating a recovery platform by augmenting the Solaris OE boot image (mini-root). This article will also examine the boot and installation processes by demonstrating how to adapt those processes for system recovery.
  
   
• Building a Bootable JumpStart Installation CD-ROM
  -by John S. Howard
  This article presents an examination of the structure of a bootable Solaris Operating Environment (Solaris OE) CD-ROM and procedures for how to create a bootable JumpStart installation CD-ROM. This CD can be used to complete a standardized, hands-free Solaris OE installation in environments where the disk space or networking constraints do not allow for a JumpStart server.
   
• Solaris 8 Additions to sysidcfg (March 2000)
  -by Rob Snevely
  Shows you how to do fully hands-off installations of the Solaris 8 Operating Environment. He also discusses how to use Jumpstart and sysidcfg to provide uniform Solaris Operating Environment installations and save you time.
   
• Setting Up a Solaris Operating Environment Install Server and the Solaris JumpStart Feature (December 1999)
  -by Rob Snevely
  A walkthrough on setting up an install server.
   
• JumpStart: NIS and sysidcfg (October 1999)
  -by Rob Snevely
  How to use JumpStart technology to allows automation of the install process.

MR System for Rapid Recovery
-by John S. Howard
This article is an introduction to the MR system for rapid recovery. As the system uptime requirements have become more exacting, the length of time it takes to boot these larger and more complex systems has grown. By implementing MR on your JumpStart servers it may be possible to reduce the number of reboots required during a system recovery or service event. This minimization of reboots will speed recovery and service time as well as enable the system administrator to use datacenter tools during system recovery procedures.

 JumpStart Architecture and Security Scripts for the Solaris Operating Environment - Part 1

 JumpStart Architecture and Security Scripts for the Solaris Operating Environment - Part 2

 JumpStart Architecture and Security Scripts for the Solaris Operating Environment - Part 3

Presentations

Introduction to Solaris JumpStart

JumpStart Disks

JumpStart Disk Implementation

System recovery using Jumpstart

[DOC] Restoring a Sun system using JumpStart technology

Linux-based Jumpstart Server

linux-jumpstart

Tips

Solaris Tips - Jumpstart

Etc

Solaris jumpstart installation @ DESY -- http://www.desy.de/~dirkw/jumpstart.html

http://www.cuug.ab.ca/~leblancj/labs/index.html
http://www.tcsa.org/auto_install/
http://www.netsys.com/sunmgr/1995-11/msg00045.html
http://www.sunmanagers.org/pipermail/sunmanagers/2001-January/000736.html
http://docs.ns.gatech.edu/admin/installation/install_jumpstart.html
http://www.rootprompt.org/article.php3?article=2276

www.sun.com/blueprints/0500/jsmech1.pdf  JumpStartTM Mechanics: Using JumpStart Application for Hands-Free Installation of Unbundled Software By John S. Howard

www.sun.com/blueprints/0600/jsmech2.pdf -- JumpStartTM Mechanics: Using JumpStart Application for Hands-Free Installation of Unbundled Software - Part 2 Automatic Encapsulation of the Root Disk

JumpStart Architecture and Security Scripts for the Solaris Operating Environment - Part 1-3: Updated for Toolkit
version 0.2" by Alex Noordergraaf and Glenn Brunette [3].

• www.sun.com/blueprints/0700/jssec.pdf
• www.sun.com/blueprints/0800/jssec2.pdf    
• www.sun.com/blueprints/0900/jssec3.pdf 
  

Installing Solaris with Jumpstart

Automating UNIX installations with HP Ignite and Solaris JumpStart -- slides

Linux as a Jumpstart Server (C) Copyright Scott Howard, 2002 scott ...

Last modified: November 08, 2008