This chapter provides an example of setting up and installing Solaris software on both SPARC based and x86 based systems by using a custom JumpStart installation.Sample Site Setup Create an Install Server Create a Boot Server for Marketing Systems Create a JumpStart Directory Share the JumpStart Directory Create the Engineering Group's Profile Create the Marketing Group's Profile Update the rules File Validate the rules File Set Up Engineering Systems to Install From the Network Set Up Marketing Systems to Install From the Network Boot the Engineering Systems and Install Solaris Software Boot the Marketing Systems and Install Solaris Software Figure 7–1 shows the site setup for this example.

This illustration shows an install server on the engineering subnet and a boot server on the marketing subnet.

At this sample site, the conditions are as follows:SPARC: The engineering group is located on its own subnet. This group uses SPARCstation systems for software development. x86: The marketing group is located on its own subnet. This group uses x86 based systems for running word processors, spreadsheets, and other office productivity tools. The site uses NIS. The Ethernet addresses, IP addresses, and host names of the systems are preconfigured in the NIS maps. The subnet mask, date and time, and geographic region for the site are also preconfigured in the NIS maps.The peripheral devices for the marketing systems are preconfigured in the sysidcfg file. Both the engineering and marketing systems are to be installed with Solaris Express 5/07 software from the network. Because the groups need to install Solaris Express 5/07 software from the network, you make server-1 an install server for both groups. You use the setup_install_server1M command to copy the images to the server-1 local disk (in the /export/install directory). Copy the images from the either of the following media.Solaris Software CDs and the Solaris Languages CDs Solaris Operating System DVD You must copy the image from the disc to an empty directory, in these examples the sparc_11 directory and the x86_11 directory.Insert the Solaris Software for SPARC Platforms - 1 CD in the CD-ROM drive that is attached to server-1 and type the following commands:server-1# mkdir -p /export/install/sparc_11 server-1# cd /CD_mount_point/Solaris_11/Tools server-1# ./setup_install_server /export/install/sparc_11Insert the Solaris Software for SPARC Platforms - 2 CD in the CD-ROM drive that is attached to server-1 and type the following commands:server-1# cd /CD_mount_point/Solaris_11/Tools server-1# ./add_to_install_server /export/install/sparc_11Repeat the previous command for each Solaris Software you want to install.Insert the first SPARC: Solaris Languages for SPARC Platforms CD in the CD-ROM drive that is attached to server-1 and type the following commands:server-1# cd /CD_mount_point/Solaris_11/Tools server-1# ./add_to_install_server /export/install/sparc_11Repeat the previous command for each SPARC: Solaris Languages for SPARC Platforms CD you want to install. Insert the Solaris Software for x86 Platforms - 1 CD in the CD-ROM drive that is attached to server-1 and type the following commands:server-1# mkdir -p /export/install/x86_11 server-1# cd /CD_mount_point/Solaris_11/Tools server-1# ./setup_install_server /export/install/x86_11Insert the Solaris Software for x86 Platforms - 2 CD in the CD-ROM drive that is attached to server-1 and type the following commands:server-1# cd /CD_mount_point/Solaris_11/Tools server-1# ./add_to_install_server /export/install/x86_11Repeat the previous command for each Solaris Software you want to install.Insert the first Solaris Languages for x86 Platforms CD in the CD-ROM drive that is attached to server-1 and type the following commands:server-1# cd /CD_mount_point/Solaris_11/Tools server-1# ./add_to_install_server /export/install/x86_11Repeat the previous command for each Solaris Languages for x86 Platforms CD you want to install. Insert the Solaris Operating System for SPARC Platforms DVD in the DVD-ROM drive that is attached to server-1 and type the following commands:server-1# mkdir -p /export/install/sparc_11 server-1# cd /DVD_mount_point/Solaris_11/Tools server-1# ./setup_install_server /export/install/sparc_11 Insert the Solaris Operating System for x86 Platforms DVD in the DVD-ROM drive that is attached to server-1 and type the following commands:server-1# mkdir -p /export/install/x86_11 server-1# cd /DVD_mount_point/Solaris_11/Tools server-1# ./setup_install_server /export/install/x86_11 Systems cannot boot from an install server on a different subnet, so you make server-2 a boot server on the marketing group's subnet. You use the setup_install_server1M command to copy the boot software from the Solaris Operating System for x86 Platforms DVD or the Solaris Software for x86 Platforms - 1 CD. The boot software is copied to the server-2 local disk in the /export/boot directory.Choose the media and install the boot software to local disk.If you insert the Solaris Software for x86 Platforms - 1 CD in the CD-ROM drive that is attached to server-2, type the following command:server-2# cd /CD_mount_point/Solaris_11/Tools server-2# ./setup_install_server -b /export/boot If you insert the Solaris Operating System for x86 Platforms DVD in the DVD-ROM drive that is attached to server-2, type the following command:server-2# cd /DVD_mount_point/Solaris_11/Tools server-2# ./setup_install_server -b /export/boot In the setup_install_server command, b specifies that setup_install_server is to copy the boot information to the directory that is named /export/boot. Now that you have the install server and boot server set up, you create a JumpStart directory on server-1. You can use any system on the network. This directory holds files that are required for a custom JumpStart installation of Solaris software. You set up this directory by copying the sample directory from the Solaris Operating System DVD image or from the Solaris Software - 1 CD image that has been copied to /export/install: server-1# mkdir /jumpstart server-1# cp -r /export/install/sparc_11/Solaris_11/Misc/jumpstart_sample /jumpstart To make the rules file and profiles accessible to systems on the network, you share the /jumpstart directory.Use either the sharemgr utility or the share command as follows:Starting with the 5/07 Developer release, the sharemgr utility introduces the concept of share groups. See sharemgr Command in System Administration Guide: Network Services. Using the share command, edit the /etc/dfs/dfstab file by adding the following entry.# share -F nfs -o ro,anon=0 jumpstart_dir_pathFor example, the following entry shares the /jumpstart directory:# share -F nfs -o ro,anon=0 /jumpstartThen, type shareall and press Enter. Using the sharemgr utility, enter the following commands:# sharemgr add-share s /jumpstart default# sharemgr set P nfs S sys p ro="*" s /jumpstart default# sharemgr set P nfs p anon=0 s /jumpstart default For the engineering systems, you create a file that is named eng_prof in the /jumpstart directory. The eng_prof file contains the following entries, which define the Solaris Express 5/07 software to be installed on systems in the engineering group:install_type initial_install system_type standalone partitioning default cluster SUNWCprog filesys any 512 swapThe previous example profile specifies the following installation information.install_typeThe installation is to be treated as an initial installation, as opposed to an upgrade. system_typeThe engineering systems are standalone systems. partitioningThe JumpStart software uses default disk partitioning for installing Solaris software on the engineering systems. clusterThe Developer System Support software group is to be installed. filesysEach system in the engineering group is to have 512 Mbytes of swap space. For the marketing systems, you create a file that is named marketing_prof in the /jumpstart directory. The marketing_prof file contains the following entries, which define the Solaris Express 5/07 software to be installed on systems in the marketing group: install_type initial_install system_type standalone partitioning default cluster SUNWCuser package SUNWaudioThe previous example profile specifies the following installation information.install_typeThe installation is to be treated as an initial installation, as opposed to an upgrade. system_typeThe marketing systems are standalone systems. partitioningThe JumpStart software is to use default disk partitioning for installing Solaris on the marketing systems. clusterThe End User Solaris Software Group is to be installed. packageThe audio demo software package is to be added to each system. Now you must add rules to the rules file. The Solaris installation program uses the rules to select the correct installation (profile) for each system during a custom JumpStart installation. At this site, each department is located on its own subnet and has its own network address. The engineering department is located on subnet 255.222.43.0. The marketing department is located on 255.222.44.0. You can use this information to control how the engineering and marketing systems are installed with the Solaris Express 5/07 software. In the /jumpstart directory, you edit the rules file, delete all of the example rules, and add the following lines to the file:network 255.222.43.0 - eng_prof - network 255.222.44.0 - marketing_prof -Basically, these rules state that systems on the 255.222.43.0 network are to be installed with the Solaris Express 5/07 software by using the eng_prof profile. The systems on the 255.222.44.0 network are to be installed with the Solaris Express 5/07 software by using the marketing_prof profile.You can use the sample rules to use a network address to identify the systems to be installed with the Solaris Express 5/07 software by using eng_prof and marketing_prof, respectively. You can also use host names, memory size, or model type as the rule keyword. Table 8–1 contains a complete list of keywords you can use in a rules file. After the rules and profiles are set up, you run the check script to verify that the files are correct: server-1# cd /jumpstart server-1# ./checkIf the check script does not find any errors, the script creates the rules.ok file. After setting up the /jumpstart directory and files, you use the add_install_client command on the install server, server-1, to set up the engineering systems to install the Solaris software from the install server. server-1 is also the boot server for the engineering group's subnet.server-1# cd /export/install/sparc_11/Solaris_11/Tools server-1# ./add_install_client -c server-1:/jumpstart host-eng1 sun4u server-1# ./add_install_client -c server-1:/jumpstart host-eng2 sun4uIn the add_install_client command, the options that are used have the following meanings:cSpecifies the server (server-1) and path (/jumpstart) to the JumpStart directory. Use this option if you are using NFS.If you are not using NFS, you specify the path to the JumpStart directory by using the following commands:For SPARC based systems, specify the path in the boot command For x86 based systems, specify the path by editing the GRUB menu entry host-eng1The name of a system in the engineering group. host-eng2The name of another system in the engineering group. sun4uSpecifies the platform group of the systems that use server-1 as an install server. The platform group is for Ultra 5 systems. Next, you use the add_install_client command on the boot server (server-2). This command sets up the marketing systems to boot from the boot server and install the Solaris software from the install server (server-1):server-2# cd /marketing/boot-dir/Solaris_11/Tools server-2# ./add_install_client -s server-1:/export/install/x86_11 \ -c server-1:/jumpstart host-mkt1 i86pc server-2# ./add_install_client -s server-1:/export/install/x86_11 \ -c server-1:/jumpstart host-mkt2 i86pc server-2# ./add_install_client -d -s server-1:/export/install/x86_11 \ -c server-1:/jumpstart SUNW.i86pc i86pc server-2# ./add_install_client -c server-1:/jumpstart host-mkt1 sun4u server-2# ./add_install_client -c server-1:/jumpstart host-mkt2 sun4uIn the add_install_client command, the options that are used have the following meanings:-dSpecifies that the client is to use DHCP to obtain the network install parameters. This option is required for clients to use PXE network boot to boot from the network. d is optional for network boot clients that do not use PXE network boot. -sSpecifies the install server (server-1) and the path to the Solaris software (/export/install/x86_11). -cSpecifies the server (server-1) and path (/jumpstart) to the JumpStart directory. Use this option if you are using NFS.If you are not using NFS, you specify the path to the JumpStart directory by using the following commands:For SPARC based systems, specify the path in the boot command For x86 based systems, specify the path by editing the GRUB menu entry host-mkt1The name of a system in the marketing group. host-mkt2The name of another system in the marketing group. sun4uSpecifies the platform group of the systems that use server-1 as an install server. The platform group is for Ultra 5 systems. SUNW.i86pcThe DHCP class name for all Solaris x86 clients. If you want to configure all Solaris x86 DHCP clients with a single command, use this class name. i86pcSpecifies the platform group of the systems that use this boot server. The platform name represents x86 based systems. After setting up the servers and files, you can boot the engineering systems by using the following boot command at the ok (PROM) prompt of each system:ok boot net - installThe Solaris OS is automatically installed on the engineering group's systems. You can boot the system from one of the following: Solaris Software for x86 Platforms - 1 CD Solaris Operating System for x86 Platforms DVD The network by using PXE network boot Solaris software is automatically installed on the marketing group's systems.