Configuring Solaris Jumpstart Without a Name Service
This lab will illustrate a very simple Solaris Jumpstart configuration suitable for users who do not use a Name Service (such as NIS or NIS+).
In this lab, we will convert a single-board-domain Sun Sparc or Ultra host into a combination boot, configuration, and installation server, with one other unconfigured (PROM level) Sun Sparc or Ultra as a Jumpstart client.
Hosts running Solaris on Intel (x86) require significantly different Jumpstart configurations involving boot diskettes and other methods. Please consult Sun documentation for instructions.
This lab utilizes a Solaris 7 Server Installation CD. Be advised that different Solaris versions (and sub-versions) may have different absolute pathnames on their CD-ROMs, so be sure to adapt accordingly.
Once you are satisfied that your client and server are completely configured, booting them over remote locations of the subnet (i.e. different floors of a building) will now be completely automatic, no longer requiring your interaction. Note that you will need to be present at the client to perform the PROM boot command.
It is important to note that a Boot Server relies on Reverse Address Resolution Protocol (RARP) to facilitate the booting of the client. A RARP packet cannot traverse a router. Thus, the client will need to boot from a Boot Server on its own subnet (note that some LAN switches can transport a RARP packet between subnets). By contrast, the Configuration and Installation Servers (if separate from the Boot Server) can be located on any other subnet that the client has a route to.
While the OS is spooling:
We will now prepare the Jumpstart server with precise, custom instructions on how it will install the Solaris OS onto our Jumpstart client.
Transplanting A Root Password
Customizing the Server (cont.)
A Jumpstart Client could be served by three separate Jumpstart servers (boot, configuration, and installation). We will simplify this lab by instructing our client to access only one server for all three tasks. We must enter these instructions onto the boot server, which will be the first source of information for the new client when it boots.
When the Solaris OS software has completed spooling onto the Jumpstart server, we are ready to proceed:
cd /export/install/Solaris_2.7/ToolsRun the following command (note that it is one continous line, not two) and substitute appropriate information as needed:
./add_install_client -e 8:00:20:2C:97:70 -s homer:/export/install -c homer:/export/config -p homer:/export/config scully sun4uSyntax Example (one whole line, no line wraps): ./add_install_client -e [client's ethernet address] -s [server's /export/install directory] -c [server's /export/config directory] -p [server's /export/config directory] [client's hostname] [client's architecture]
Our Jumpstart server configuration is now complete. Proceed to the next section.
At this point, assuming all has gone as required on the server, we have only one step to perform on the client. Read this entire section before proceeding with the actual bootup command shown in the next section.
When the client is issued its proper boot command, it will broadcast its ethernet address onto our subnet in hexadecimal format. Our Jumpstart server will recognize the client's ethernet address and respond with all of our defined bootup and system parameters.
The client's screen will show a burst of memory activity indicated by rapidly added hexadecimal digits showing the transfer of critical data, such as the kernel.
After a device configuration period, the client will then start an OpenWindows session with a single, small window in the upper left corner of the bluish-gray screen. Jumpstart does not require any human intervention in any way, so do not enter any keystrokes on the booting client. There will be no need to enlarge this small window, as we will soon see.
The window will begin to inform us of the installation's progress. As this is happening, all of the client's hard drives specified in the Jumpstart files should begin to show activity as they are partitioned and file systems are created on them.
Eventually, the actual OS installation will begin, and a countdown of package descriptions will appear in the now-enlarged window as they are being installed.
When observing the client's Jumpstart bootup, it will be easy to correct most problems since the window will constantly be monitoring boot progress.
If the problem exists in our rules or sysidcfg files, the window will indicate which line and character it is unable to understand. We can thus go to the Jumpstart server and correct the difficulty.
Now that you have read the items above, begin the Jumpstart session on the client by running the following PROM command:
boot net - installCarefully observe all aspects of the client's behaviour, as described above.
If you have experienced any errors and have corrected them, restarting the client's Jumpstart bootup is unfortunately not as simple as running the command over again.
Copyright © 2002 by Jon C. LeBlanc.
This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0 or later (the latest version is presently available at http://www.opencontent.org/openpub/).
Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder.
Click Here to jump to my Custom Solaris System Administration Labs page.