Key Terms
Exercises
14.1. Creating JumpStart Servers
In this exercise, you'll create a JumpStart boot server, install server, configuration server, configuration files, and configure a JumpStart client to automatically install the Solaris 10 operating environment across the network.
For this exercise, you'll need two systems connected on a network. One system will serve as the boot/install/configuration server, so it needs about 2.5GB of free disk space. The second system will be the client and will have the entire disk destroyed and the operating system reloaded.
Caution
Destructive Process This procedure destroys data on the disk. Be sure you have proper backups if you want to save any data on these systems.
Estimated time: 1 hour
1. | On the system that will be used as the boot and install server, log in as root.
| 2. | Edit the /etc/hosts file and make an entry for the JumpStart client.
| 3. | Create the boot server as follows:
- a. Insert the CD labeled Solaris 10 CD 1 and let vold automatically mount the CD.
- b. Change to the Tools directory on the CD as follows:
cd /cdrom/cdrom0/s0/Solaris_10/Tools
- c. Run the setup_install_server script and specify the location for the CD image. Be sure you have about 2.5GB of free space and the target directory is empty. In the following example, I'm using /export/install as the install directory:
./setup_install_server /export/install
| 4. | Add the additional software as follows:
- a. Eject the Solaris 10 CD 1 and put in the Solaris 10 CD 2. Let vold automatically mount the CD.
- b. Change to the Tools directory on the CD as follows:
cd /cdrom/cdrom0/Solaris_10/Tools
- c. Execute the add_to_install_server script as follows to copy the images from the CD to the /export/install directory:
./add_to_install_server /export/install
- d. Repeat the procedure with the remaining CDs.
| 5. | Now create the JumpStart configuration directory as follows:
| 6. | Add the following entry in the /etc/dfs/dfstab file for this directory to share it across the network:
share -F nfs -o ro,anon=0 /jumpstart
| 7. | Start the NFS server as follows if the nfsd daemon is not already running:
| 8. | In the /jumpstart directory, use the vi editor to create a class file named basic_class with the following entries:
#Specifies that the installation will be treated as \
an initial
#installation, as opposed to an upgrade.
install_type initial_install
#Specifies that the engineering systems are \
standalone systems.
system_type standalone
#Specifies that the JumpStart software uses default \
disk
#partitioning for installing Solaris software on the \
engineering
#systems.
partitioning default
#Specifies that the developer's software group will \
be
#installed
cluster SUNWCprog
#Specifies that each system in the engineering group\
will have 512
#Mbytes of swap space.
filesys any 512 swap
| 9. | In the /jumpstart directory, use the vi editor to create a rules file named rules with the following entry:
hostname sun1 - basic_class -
| 10. | Validate the class and rules files with the check and pfinstall commands as follows :
cd /jumpstart
/export/install/Solaris_10/Misc/jumpstart_sample/check
/usr/sbin/install.d/pfinstall -d -c /export/install basic_class
| 11. | Now set up the JumpStart client as follows:
cd /export/install/Solaris_10/Tools
./add_install_client -s <SERVERNAME>:/export/install \
-c <SERVERNAME>:/jumpstart -p <SERVERNAME>:/jumpstart -e <MAC ADDRESS>\
<CLIENTNAME> <PLATFORM>
Where SERVERNAME is the hostname of your boot/install server, MAC ADDRESS is your client's Ethernet address, CLIENTNAME is your client's hostname, and PLATFORM is your client's architecture (such as sun4u).
For example:
./add_install_client -s \ sparcserver:/export/install\
-c sparcserver:/jumpstart -p sparcserver:/jumpstart \
-e 8:0:20:21:49:24 sun1 sun4u
| 12. | Go to the client, turn on the power, and at the boot PROM, issue the following command:
The JumpStart installation executes .
|
Exam Questions
1. | Which of the following is a method to automatically install Solaris on a new SPARC system by inserting the Solaris Operating System CD-ROM in the drive and powering on the system?
| 2. | Which of the following is a method to automatically install groups of identical systems?
| 3. | Which of the following sets up an install server to provide the operating system to the client during a JumpStart installation?
| 4. | For a JumpStart installation, which of the following files should contain a rule for each group of systems that you want to install?
| 5. | For a JumpStart installation, which of the following servers is set up to answer RARP requests from clients?
| 6. | Which of the following is used as an alternative to setting up a configuration directory ?
| 7. | For a JumpStart installation, which of the following files contains the name of a finish script?
| 8. | Which of the following is a user-defined Bourne shell script, specified within the rules file?
| add_install_client script
| | | | | | |
| 9. | In JumpStart, which of the following files defines how to install the Solaris software on a system?
| 10. | Which of the following is used to test a JumpStart class file?
| 11. | When working with JumpStart, which of the following files is not used to provide information about clients?
| 12. | Which of the following is not a valid entry in the first field in the rules file ?
| 13. | Which of the following files is the JumpStart file that can use any name and still work properly?
| 14. | Which of the following scripts will update or create the rules.ok file?
| 15. | Which of the following supplies the operating system during a JumpStart installation?
| 16. | Which of the following contains the JumpStart directory and configuration files such as the class file and the rules file?
| 17. | Which of the following commands is issued on the install server to set up remote workstations to install Solaris from the install server?
| 18. | Which of the following commands sets up a system as a boot server only?
| 19. | Which of the following commands is used on a JumpStart client to start the installation?
| 20. | Which script copies additional packages within a product tree to the local disk on an existing install server?
| 21. | Which of the following class file keywords is valid ONLY for a Solaris Flash Install using JumpStart?
| 22. | Which of the following are required to be able to boot an x86 client using the PXE network boot and install method? (Choose 3)
| A system with more than 1 GB of physical memory
| | An x86 client with a system BIOS that supports the Intel Preboot Execution Environment specification
| | | | A server running either NIS or NIS+ naming service
| | |
| 23. | Which of the following symbols would you configure in a DHCP server to correctly specify the Hostname of the JumpStart Install server so that a PXE network client would be passed the correct configuration information at boot time?
|
Answers to Exam Questions
1. | A. JumpStart lets you automatically install the Solaris software on a SPARC-based system just by inserting the Solaris CD and powering on the system. You do not need to specify the boot command at the ok prompt. For more information, see the section "JumpStart." | 2. | A. The custom JumpStart method of installing the operating system provides a way to install groups of similar systems automatically and identically. For more information, see the section "JumpStart." | 3. | D. The setup_install_server script sets up an install server to provide the operating system to the client during a JumpStart installation. For more information, see the section "The Install Server." | 4. | B. The rules.ok file is a file that should contain a rule for each group of systems you want to install. For more information, see the section "The Rules File." | 5. | A. The boot server is set up to answer RARP requests from a JumpStart client. For more information, see the section "Setting Up the Boot Server." | 6. | C. A configuration disk is used as an alternate to setting up a configuration directory. For more information, see the section "Setting Up a Configuration Diskette." | 7. | C. The rules.ok file contains the name of a finish script. For more information, see the section "The Rules File." | 8. | D. A begin script is a user-defined Bourne shell script, located in the JumpStart configuration directory on the configuration server, specified within the rules file, that performs tasks before the Solaris software is installed on the system. For more information, see the section "begin and finish Scripts." | 9. | A. A class file is a text file that defines how to install the Solaris software on a system. For more information, see the section "Creating Class Files." | 10. | B. After you create a class file, you can use the pfinstall command to test it. For more information, see the section "Testing Class Files." | 11. | C. The sysidcfg, rules, and class files all provide information about the JumpStart client. The check script is used to validate the rules file. For more information, see the section "JumpStart." | 12. | D. any, hostname, and karch are all valid keywords that can be used in the rules file. For more information, see the section "The Rules File." | 13. | A. The class file can be named anything, but it should reflect the way in which it installs the Solaris software on a system. For more information, see the section "Creating Class Files." | 14. | B. The check script will update or create the rules.ok file. For more information, see the section "Validating the Rules File." | 15. | B. The install server supplies the operating system during a JumpStart installation. For more information, see the section "The Install Server." | 16. | D. The configuration server contains all the essential custom JumpStart configuration files, such as the rules file, the rules.ok file, the class file, the check script, and the optional begin and finish scripts. For more information, see the section "Configuration Server." | 17. | A. Use the add_install_client command on the install server to set up remote workstations to install Solaris from the install server. For more information, see the section "Setting Up Clients." | 18. | C. setup_install_server -b sets up a system as a boot server only. For more information, see the section "Setting Up the Boot Server." | 19. | A. boot net - install is used on a JumpStart client to start the installation. For more information, see the section "Starting Up the Clients." | 20. | B. The add_to_install_server script copies additional packages within a product tree to the local disk on an existing install server. For more information, see the section "The Install Server." | 21. | A. The archive_location option is a valid class file keyword that is only used when installing a Flash Archive using JumpStart. For more information, see the section "Creating Class Files." | 22. | B, C, and E. The requirements for a PXE network boot are that there is an install server, a configure DHCP server, and an x86 client that supports the Intel Preboot Execution Environment specification. For more information, see the section "Preboot Execution Environment." | 23. | B. The DHCP symbol SinstNM specifies the hostname of the JumpStart Install server. For more information, see the section "Configuring the DHCP Server." |
|