SPARC: How to Perform a Custom JumpStart Installation

1. Check Table 3-1 to make sure the system to be installed is set up for a custom JumpStart installation.

   Table 3-1 SPARC: Setting Up a System for a Custom JumpStart Installation: Task Map

   	Task			Description		For Instructions, Go To
   	Back up existing Solaris 1.x (SunOS 4.x) files			If the system has a previous Solaris 1.x (SunOS 4.x) release installed, some Solaris 1.x files can be converted or merged into the Solaris files. You can use begin and finish scripts to do this.		Solaris Transition Guide
   	Check if the system is supported			Check the hardware documentation to see if the system is supported for Solaris 7.		SMCC Hardware Platform Guide
   	Decide how to upgrade the system if it has a previous version of Solaris installed			If the system has a previous Solaris release installed, you need to determine how to upgrade the system. Make sure you know what to do before and after you upgrade a system; this will help you set up your profiles, begin scripts, and finish scripts.		Chapter 4, Upgrading a System
   	Check if the system has enough disk space for the Solaris software			Optional. There are many considerations when planning disk space, such as deciding which software group you want to install.		Appendix A, Planning Disk Space
   	Preconfigure system configuration information			Optional. You can use the sysidcfg file or the name service to preconfigure installation information (for example, locale) for a system, so you won't be prompted to supply the information during the installation.		Chapter 6, Preconfiguring System Configuration Information
   	Prepare system for custom Jumpstart installation			You need to do some initial setup work before you can install a system using custom JumpStart.		Chapter 8, Preparing Custom JumpStart Installations
   	Set up the system to install over the network			For network installations only. To install a system from a remote Solaris CD image, you need to set up the system to boot and install from an install server or boot server.		Chapter 7, Preparing to Install Solaris Software Over the Network

2. If the system is part of a network, make sure an Ethernet connector or similar network adapter is plugged into your system.

3. If you are installing a system connected through a tip line, make sure that your window display is at least 80 columns wide and 24 rows long.

   Otherwise, the character installation interface displays improperly. You can use the stty command to determine the current dimensions of your tip window.

4. If you are using the system's CD-ROM drive to install the Solaris software on the system, insert the Solaris CD-ROM into the system's CD-ROM drive.

5. If you are using a profile diskette to perform a custom JumpStart installation, insert the profile diskette into the system's diskette drive.

6. Boot the system.

   If the System Is...	Then ...
   New, out-of-the-box	Turn the system on.
   Existing	If you are installing from an install server on the network, get the system to the ok prompt and type: ok boot net - install (A space is required before and after the dash.) If you are installing from the system's local CD-ROM drive, get the system to the ok prompt and type: ok boot cdrom - install (A space is required before and after the dash.) Note - For systems with older EEPROMs, replace cdrom with sd(0,6,2) to boot from the system's CD-ROM.

   If you have any problems from this point, go to Chapter 5, Troubleshooting.

   ---

   Note -

   For more information about getting the system to the ok prompt, see the System Administration Guide, Volume I.

   ---

7. Wait for booting to complete.

   After you enter the boot command, the system checks various hardware and system components. This lasts for several minutes.

8. If prompted, provide information about the system.

   After booting, the Solaris installation program may prompt you to provide configuration information about the system. If you have preconfigured all the system configuration information, go to the next step.

9. Wait as the Solaris software installs on the system.

   After the installation is finished, a log of how the Solaris software was installed on the system is saved to a file, as shown in Table 3-2.

   Table 3-2 Installation Log Locations

   If the System Was Installed Using The ...	Then the Log Is Saved To ...
   Initial installation option	Before the system reboots: /a/var/sadm/system/logs/install_log After the system reboots: /var/sadm/system/logs/install_log
   Upgrade option	Before the system reboots: /a/var/sadm/system/logs/upgrade_log After the system reboots: /var/sadm/system/logs/upgrade_log

10. If the system's profile allocated space for diskless clients or AutoClient systems, use Solstice Host Manager to complete the setup of those clients.