This chapter provides step-by-step instructions about how to prepare the systems at your site from which and on which you intend to install the Solaris software by using the custom JumpStart installation method.Task Map: Preparing Custom JumpStart Installations Creating a Profile Server for Networked Systems Creating a Profile Diskette for Standalone Systems Creating the rules File Creating a Profile Testing a Profile Validating the rules File Task Description For Instructions Decide how to upgrade the system if a previous version of the Solaris software is installed on the system. If a previous release of Solaris is installed on the system, you need to determine how to upgrade the system. Ensure that you know what to do before and after you upgrade a system. Planning helps you to create your profiles, begin scripts, and finish scripts. Upgrade Planning in Solaris Express Installation Guide: Planning for Installation and Upgrade Create a JumpStart directory. On a serverIf you want to perform custom JumpStart installations on systems that are connected to a network, you must create a profile server. The profile server contains a JumpStart directory for the custom JumpStart files. Creating a Profile Server for Networked Systems On a disketteIf you want to perform custom JumpStart installations on systems that are not connected to a network, you must create a profile diskette. A profile diskette contains the custom JumpStart files. Creating a Profile Diskette for Standalone Systems Add rules to the rules file. After you decide how you want each group of systems or single systems to be installed, create a rule for each group that you want to install. Each rule distinguishes a group, based on one or more system attributes. The rule links each group to a profile. Creating the rules File Create a profile for every rule. A profile is a text file that defines how to install the Solaris software, for example, which software group to install on a system. Every rule specifies a profile to define how a system is to be installed with the Solaris software when the rule is matched. You usually create a different profile for every rule. However, the same profile can be used in more than one rule. Creating a Profile (Optional) Test the profiles. After you create a profile, use the pfinstall1M command to test the profile before you use the profile to install or upgrade a system. Testing a Profile Validate the rules file. The rules.ok file is a generated version of the rules file that the JumpStart program uses to match the system to be installed with a profile. You must use the check script to validate the rules file. Validating the rules File When setting up custom JumpStart installations for systems on the network, you need to create a directory on a server that is called a JumpStart directory. 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 server.The server that contains a JumpStart directory is called a profile server. A profile server can be the same system as an install server or a boot server, or the server can be a completely different server. A profile server can provide custom JumpStart files for different platforms. For example, an x86 server can provide custom JumpStart files for both SPARC based systems and x86 based systems. After you create a profile server, you must allow systems to access the server. For detailed instructions, see To Allow All Systems Access to the Profile Server. This procedure assumes that the system is running removable media services. If you have questions about removable media services that manage discs, refer to System Administration Guide: Devices and File Systems for detailed information. Locate the server on which you want to create the JumpStart directory. &suStepA;Create the JumpStart directory anywhere on the server.# mkdir -m 755 jumpstart_dir_pathIn the command, jumpstart_dir_path is the absolute path of the JumpStart directory.For example, the following command creates a directory that is called jumpstart in the root (/) directory and sets the permissions to 755:# mkdir -m 755 /jumpstart 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 Determine if you want to copy examples of custom JumpStart files to your JumpStart directory.If no, go to Step 8. If yes, use the following decision table to determine what to do next. Example Locations Instructions The Solaris Operating System DVD or the Solaris Software - 1 CD for your platform Insert the Solaris Operating System DVD or the Solaris Software - 1 CD into the server's CD-ROM drive.Removable media services automatically mounts the CD or DVD. An image of the Solaris Operating System DVD or the Solaris Software - 1 CD for your platform on a local disk Change directory to the location of the Solaris Operating System DVD or the Solaris Software - 1 image. For example, type the following command:cd /export/install Copy the example custom JumpStart files into the JumpStart directory on the profile server. # cp -r media_path/Solaris_11/Misc/jumpstart_sample/* jumpstart_dir_pathmedia_pathThe path to the CD, DVD, or image on the local disk jumpstart_dir_pathThe path on the profile server where you are placing the example custom JumpStart files For example, the following command copies the jumpstart_sample directory into the /jumpstart directory on the profile server:For SPARC based systems:cp -r /media/cdrom/s0/Solaris_11/Misc/jumpstart_sample/* /jumpstart For x86 based systems:cp -r /media/cdrom/Solaris_11/Misc/jumpstart_sample/* /jumpstart Update the example JumpStart files so that the files work in your environment. Ensure that root owns the JumpStart directory and that the permissions are set to 755. Allow systems on the network to access the profile server.For detailed instructions, see To Allow All Systems Access to the Profile Server. When you create a profile server, you must ensure that systems can access the JumpStart directory on the profile server during a custom JumpStart installation. Use one of the following ways to ensure access.Command or File Providing Access Instructions add_install_client command Each time that you add a system for network installation, use the c option with the add_install_client command to specify the profile server. If you are not using NFS, then you must use another means to provide access.For SPARC based systems, use the boot command For x86 based systems, edit the GRUB menu For DVD media, see Adding Systems to Be Installed From the Network With a DVD Image in Solaris Express Installation Guide: Network-Based Installations For CD media, see Adding Systems to Be Installed From the Network With a CD Image in Solaris Express Installation Guide: Network-Based Installations Specify the location of the JumpStart directory when you boot the system For SPARC based systems, use the boot command to boot the system. Specify the location of the JumpStart directory on the profile server when you boot the system. You must compress the custom JumpStart configuration files into one file. Then, save the compressed configuration file on an HTTP or HTTPS server. Creating a Compressed Configuration File Step 5 in To Perform an Installation or Upgrade With the Custom JumpStart Program For x86 based systems, specify the location of the JumpStart directory on the profile server when you boot the system by editing the boot entry on the GRUB menu. You must compress the custom JumpStart configuration files into one file. Then, save the compressed configuration file on an HTTP or HTTPS server. When you edit the GRUB menu entry, specify the location of the compressed file. Creating a Compressed Configuration File Performing a Custom JumpStart Installation by Editing the GRUB Boot Command /etc/bootparams file Add a wildcard in the /etc/bootparams file. To Allow All Systems Access to the Profile Server Use the following procedure only if you store network installation information in the following places: In the /etc/bootparams file. In the naming service bootparams database. To update the bootparams database, add the entry that is shown in Step 3. If you use the following procedure, the systems must be of the same type, such as all SPARC systems.Do not use this procedure under the following conditions:If you save the JumpStart directory on a diskette. If you specify the location of the profile server when you boot the system. If you have systems of different architectures, you must specify the location of the profile server when you boot the system If you have the above conditions, use the SPARC boot command or use the x86 GRUB menu.You also can store network installation information on a DHCP server.For SPARC based systems, you use the add_install_client command and the d option to specify that the custom JumpStart program use the DHCP server. Or you use the boot command with the dhcp option to specify that the custom JumpStart program use the DHCP server. For instructions about using this option, see Command Reference for the boot Command. For x86 based systems, you use dhcp in one of the following ways:If you use an install server, use the add_install_client command and the d option to specify that the custom JumpStart program use the DHCP server with PXE. You can edit the GRUB entry on the GRUB menu and add the dhcp option. For instructions about editing the GRUB entry, see Performing a Custom JumpStart Installation by Editing the GRUB Boot Command On the installation or boot server, log in as superuser. Use a text editor to open /etc/bootparams. Add this entry. * install_config=server:jumpstart_dir_path*A wildcard character that specifies that all systems have access serverThe host name of the profile server where the JumpStart directory is located jumpstart_dir_pathThe absolute path of the JumpStart directory For example, the following entry enables all systems to access the /jumpstart directory on the profile server that is named sherlock:* install_config=sherlock:/jumpstartUse of this procedure might produce the following error message when an installation client is booted: WARNING: getfile: RPC failed: error 5: (RPC Timed out).Booting From the Network, Error Messages contains details about this error message. All systems can now access the profile server. 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.See one of the following procedures:To Create a Profile Diskette To Create a Profile Diskette With GRUB This procedure assumes that the system is running removable media services. If you have questions about removable media services that manage discs, refer to System Administration Guide: Devices and File Systems for detailed information. Locate a SPARC based system to which a diskette drive is attached. &suStepA;Insert a blank diskette or a diskette that can be overwritten in the diskette drive. Mount the diskette. # volcheck 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 927147040If the entry exists, go to Step 7. If the entry does not exist, go to the next step. Create a UFS on the diskette.# newfs /vol/dev/aliases/floppy0 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 Operating System for SPARC Platforms DVD or the Solaris Software for SPARC Platforms - 1 CD Insert the Solaris Operating System for SPARC Platforms DVD or the Solaris Software for SPARC Platforms - 1 CD into the server's CD-ROM drive.Removable media services automatically mounts the CD or DVD. An image of the Solaris Operating System for SPARC Platforms DVD or the Solaris Software for SPARC Platforms - 1 CD on a local disk Change the directory to the location of the Solaris Operating System for SPARC Platforms DVD or the Solaris Software for SPARC Platforms - 1 CD image. For example, type the following command:cd /export/install Copy the example custom JumpStart files into the JumpStart directory on the profile diskette.# cp -r media_path/Solaris_11/Misc/jumpstart_sample/* jumpstart_dir_pathmedia_pathThe path to the CD, DVD, or image on the local disk jumpstart_dir_pathThe path to the profile diskette where you want to place the example custom JumpStart files 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 Software for SPARC Platforms - 1 CD to the root (/) directory on a profile diskette that is named scrap:cp -r /media/cdrom/s0/Solaris_11/Misc/jumpstart_sample/* /floppy/scrap Update the example JumpStart files on the profile diskette so that the files work in your environment. Ensure that root owns the JumpStart directory and that permissions are set to 755. Eject the diskette.# eject floppyYou 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. Use this procedure to create a profile diskette with GRUB. A GRUB menu is provided during the installation procedure that enables the boot process. The GRUB menu replaces the Solaris Device Configuration Assistant that might have been needed to boot a system in past releases.This procedure assumes that the system is running removable media services. If you have questions about removable media services that manage discs, refer to System Administration Guide: Devices and File Systems for detailed information. Locate an x86 based system to which a diskette drive is attached. &suStepA;Insert a blank diskette or a diskette that can be overwritten into the diskette drive. Mount the diskette. # volcheck Determine if you want to copy examples of custom JumpStart files to your JumpStart directory.If no, go to Step 8. If yes, use the following decision table to determine what to do next. Example Locations Instructions The Solaris Operating System for x86 Platforms DVD or the Solaris Software for x86 Platforms - 1 CD Insert the Solaris Operating System for x86 Platforms DVD or the Solaris Software for x86 Platforms - 1 CD into the server's CD-ROM drive.Removable media services automatically mounts the DVD or CD. An image of the Solaris Operating System for x86 Platforms DVD or the Solaris Software for x86 Platforms - 1 CD on a local disk Change directory to the location of the Solaris Operating System for x86 Platforms DVD or the Solaris Software for x86 Platforms - 1 CD image. For example, type the following:cd /export/install Copy the example custom JumpStart files into the JumpStart directory on the profile diskette. # cp -r media_path/Solaris_11/Misc/jumpstart_sample/* jumpstart_dir_pathmedia_pathThe path to the CD, DVD, or image on the local disk jumpstart_dir_pathThe path to the profile diskette where you want to place the example custom JumpStart files You must place all custom JumpStart installation files in the root (/) directory on the profile diskette. For example, the following command copies the contents of jumpstart_sample on the Solaris Software for x86 Platforms - 1 CD to the root (/) directory on a profile diskette that is named scrap:cp -r /media/cdrom/Solaris_11/Misc/jumpstart_sample/* /floppy/scrap Update the example JumpStart files on the profile diskette so that the files work in your environment. Ensure that root owns the JumpStart directory and that permissions are set to 755. Eject the diskette by clicking Eject Disk in the File Manager window or by typing eject floppy on the command line. In the Removable Media Manager dialog box, click OK. Manually eject the diskette. You have completed the creation of a profile diskette. Now you can update the rules file and create profiles on the profile diskette to perform custom JumpStart installations. To continue, go to Creating the rules File. The rules file is a text file that contains a rule for each group of systems on which you want to install the Solaris OS. Each rule distinguishes a group of systems that are based on one or more system attributes. Each rule also links each group to a profile. A profile is a text file that defines how the Solaris software is to be installed on each system in the group. For example, the following rule specifies that the JumpStart program use the information in the basic_prof profile to install any system with the sun4u platform group. karch sun4u - basic_prof -The rules file is used to create the rules.ok file, which is required for custom JumpStart installations.If you set up the JumpStart directory by using the procedures in Creating a Profile Diskette for Standalone Systems or Creating a Profile Server for Networked Systems, an example rules file is already located in the JumpStart directory. The sample rules file contains documentation and some example rules. If you use the sample rules file, ensure that you comment out the example rules you do not intend to use. The rules file must have the following attributes:The file must be assigned the name rules. The file must contain at least one rule. The rules file can contain any of the following:Commented textAny text that is included after the # symbol on a line is treated by JumpStart as commented text. If a line begins with the # symbol, the entire line is treated as a comment. One or more blank lines One or more multiline rulesTo continue a single rule onto a new line, include a backslash character (\) just before pressing Return. Use a text editor to create a text file that is named rules. Or, open the sample rules file in the JumpStart directory that you created. Add a rule in the rules file for each group of systems on which you want to install the Solaris software. For a list of rules file keywords and values, see Rule Keywords and Values.A rule within a rules file must adhere to the following syntax: !rule_keyword rule_value && !rule_keyword rule_value ... begin profile finish!A symbol that is used before a keyword to indicate negation. rule_keywordA predefined lexical unit or word that describes a general system attribute, such as host name, hostname, or memory size, memsize. rule_keyword is used with the rule value to match a system with the same attribute to a profile. For the list of rule keywords, see Rule Keywords and Values. rule_valueA value that provides the specific system attribute for the corresponding rule keyword. Rule values are described in Rule Keywords and Values. &&A symbol you must use to join rule keyword and rule value pairs in the same rule (a logical AND). During a custom JumpStart installation, a system must match every pair in the rule before the rule matches. beginThe name of an optional Bourne shell script that can be executed before the installation begins. If no begin script exists, you must type a minus sign (-) in this field. All begin scripts must be located in the JumpStart directory. Information about how to create begin scripts is presented in Creating Begin Scripts. profileThe name of a text file that defines how the Solaris software is to be installed on the system when a system matches the rule. The information in a profile consists of profile keywords and their corresponding profile values. All profiles must be located in the JumpStart directory.Optional ways to use the profile field are described in Using a Site-Specific Installation Program and Creating Derived Profiles With a Begin Script. finishThe name of an optional Bourne shell script that can be executed after the installation is completed. If no finish script exists, you must type a minus sign (-) in this field. All finish scripts must be located in the JumpStart directory. Information about how to create finish scripts is presented in Creating Finish Scripts. At the minimum, each rule must contain the following:A keyword, a value, and a corresponding profile A minus sign (-) in the begin and finish fields if no begin or finish scripts are specified Save the rules file in the JumpStart directory. Ensure that root owns the rules file and that the permissions are set to 644. The following example shows several example rules in a rules file. Each line has a rule keyword and a valid value for that keyword. The JumpStart program scans the rules file from top to bottom. When the JumpStart program matches a rule keyword and value with a known system, the JumpStart program installs the Solaris software that is specified by the profile that is listed in the profile field.For a complete list of rules file limitations, see Syntax of the rules File. # rule keywords and rule values begin script profile finish script # ----------------------------- ------------ -------- ------------- hostname eng-1 - basic_prof - network 192.168.255.255 && !model \ 'SUNW,Sun-Blade-100' - net_prof - model SUNW,SPARCstation-LX - lx_prof complete network 192.168.2.0 && karch i86pc setup x86_prof done memsize 64-128 && arch i386 - prog_prof - any - - generic_prof -The following list describes some of the keywords and values from this example.hostnameThe rule matches if the system's host name is eng-1. The basic_prof profile is used to install the Solaris software on the system that matches the rule. networkThe rule matches if the system is on subnet 192.168.255.255 and if the system is not a Sun Blade 100 (SUNW,Sun-Blade-100). The net_prof profile is used to install the Solaris software on systems that match this rule. This rule also provides an example of continuing a single rule onto a new line by using the backslash character (\). modelThe rule matches if the system is a SPARCstation LX. The lx_prof profile and the complete finish script are used to install the Solaris software on systems that match this rule. networkThe rule matches if the system is on subnet 192.168.2.0 and is an x86 based sun4u system. The setup begin script, the x864u_prof profile, and the done finish script are used to install the Solaris software on systems that match the rule. memsizeThe rule matches if the system has between 64 and 128 Mbytes of memory and is an x86 based system. The prog_prof profile is used to install the Solaris software on systems that match the rule. anyThe rule matches any system that did not match the previous rules. The generic_prof profile is used to install the Solaris software on systems that match the rule. If any is used, it should always be the last rule in the rules file. A profile is a text file that defines how to install the Solaris software on a system. A profile defines elements of the installation, for example, the software group to install. Every rule specifies a profile that defines how a system is to be installed. You can create different profiles for every rule or the same profile can be used in more than one rule. A profile consists of one or more profile keywords and their values. Each profile keyword is a command that controls one aspect of how the JumpStart program is to install the Solaris software on a system. For example, the following profile keyword and value specify that the JumpStart program install the system as a server:system_type serverSample profiles are already located in the JumpStart directory if you created the JumpStart directory by using either of these procedures:Creating a Profile Server for Networked Systems Creating a Profile Diskette for Standalone Systems A profile must contain the following: The install_type profile keyword as the first entry One keyword per line The root_device keyword if the systems that are being upgraded by the profile contain more than one root (/) file system that can be upgraded A profile can contain the following:Commented textAny text that is included after the # symbol on a line is treated by the JumpStart program as commented text. If a line begins with the # symbol, the entire line is treated as a comment. One or more blank lines Use a text editor to create a text file. Name the file descriptively. Or, open a sample profile in the JumpStart directory that you created.Ensure that the name of the profile reflects how you intend to use the profile to install the Solaris software on a system. For example, you might name the profiles basic_install, eng_profile, or user_profile. Add profile keywords and values to the profile.For a list of profile keywords and values, see Profile Keywords and Values.Profile keywords and their values are case sensitive. Save the profile in the JumpStart directory. Ensure that root owns the profile and that the permissions are set to 644. Test the profile (optional).Testing a Profile contains information about testing profiles. The following examples of profiles show how to use different profile keywords and profile values to control how the Solaris software is installed on a system. Profile Keywords and Values contains a description of profile keywords and values. # profile keywords profile values # ----------------- ----------------- install_type initial_install system_type standalone partitioning default filesys any 512 swap # specify size of /swap cluster SUNWCprog package SUNWman delete cluster SUNWCaccThe following list describes some of the keywords and values from this example.install_typeThe install_type keyword is required in every profile. system_typeThe system_type keyword defines that the system is to be installed as a standalone system. partitioningThe file system slices are determined by the software to be installed with the value default. The size of swap is set to 512 Mbytes and is installed on any disk, value any. clusterThe Developer Solaris Software Group, SUNWCprog, is installed on the system. packageIf the standard man pages are mounted from the file server, s_ref, on the network, the man page packages are not to be installed on the system. The packages that contain the System Accounting utilities are selected to be installed on the system. # profile keywords profile values # ----------------- ----------------- install_type initial_install system_type standalone partitioning default filesys any 512 swap # specify size of /swap cluster SUNWCprog cluster SUNWCacc package apache_server \ http://package.central/packages/apache timeout 5The following list describes some of the keywords and values from this example.install_typeThe install_type keyword is required in every profile. system_typeThe system_type keyword defines that the system is to be installed as a standalone system. partitioningThe file system slices are determined by the software to be installed with the value default. The size of swap is set to 512 Mbytes and is installed on any disk, value any. clusterThe Developer Solaris Software Group, SUNWCprog, is installed on the system. packageA third-party package is installed on the system located on an HTTP server. # profile keywords profile values # ---------------- ------------------- install_type initial_install system_type standalone partitioning explicit filesys c0t0d0s0 auto / filesys c0t3d0s1 auto swap filesys any auto usr cluster SUNWCallThe following list describes some of the keywords and values from this example.partitioningThe file system slices are determined by the filesys keywords, value explicit. The size of root (/) is based on the selected software, value auto, and is installed on c0t0d0s0. The size of swap is set to the necessary size and is installed on c0t3d0s1. usr is based on the selected software and the installation program determines where usr is installed, based on the value any. clusterThe Entire Solaris Software Group, SUNWCall, is installed on the system. # profile keywords profile values # ---------------- ------------------- install_type upgrade root_device c0t3d0s2 backup_media remote_filesystem timber:/export/scratch package SUNWbcp delete package SUNWxwman add cluster SUNWCacc add patch patch_list nfs://patch_master/Solaris_11/patches \ retry 5 locale deThe following list describes some of the keywords and values from this example.install_typeThe profile upgrades a system by reallocating disk space. In this example, disk space must be reallocated because some file systems on the system did not have enough space for the upgrade. root_deviceThe root file system on c0t3d0s2 is upgraded. backup_mediaA remote system that is named timber is to be used to back up data during the disk space reallocation. For more backup-media keyword values, see backup_media Profile Keyword. packageThe binary compatibility package, SUNWbcp, is not installed on the system after the upgrade. packageThe code ensures that the X Window System man pages and the System Accounting Utilities are to be installed if they are not already installed on the system. All packages already on the system are automatically upgraded. patchA list of patches that are installed with the upgrade. The patch list is located on an NFS server named patch_master under the directories Solaris_11/patches. In case of a mount failure, the NFS mount is tried five times. localeThe German localization packages are to be installed on the system. # profile keywords profile values # ---------------- ------------------- install_type upgrade root_device c0t3d0s2 backup_media remote_filesystem timber:/export/scratch layout_constraint c0t3d0s2 changeable 100 layout_constraint c0t3d0s4 changeable layout_constraint c0t3d0s5 movable package SUNWbcp delete package SUNWxwman add cluster SUNWCacc add locale deThe following list describes some of the keywords and values from this example.install_typeThe profile upgrades a system by reallocating disk space. In this example, disk space must be reallocated because some file systems on the system did not have enough space for the upgrade. root_deviceThe root file system on c0t3d0s2 is upgraded. backup_mediaA remote system that is named timber is to be used to back up data during the disk space reallocation. For more backup-media keyword values, see backup_media Profile Keyword. layout_constraintThe layout_constraint keywords designate that auto-layout can perform the following when auto-layout attempts to reallocate disk space for the upgrade. Change slices 2 and 4. The slices can be moved to another location and the size can be changed. Move slice 5. The slice can be moved to another location but its size cannot change. packageThe binary compatibility package, SUNWbcp, is not installed on the system after the upgrade. packageThe code ensures that the X Window System man pages and the System Accounting Utilities are to be installed if they are not already installed on the system. All packages already on the system are automatically upgraded. localeThe German localization packages are to be installed on the system. In the following example, the profile indicates that the custom JumpStart program retrieves the Solaris Flash archive from an HTTP server. # profile keywords profile values # ---------------- ------------------- install_type flash_install archive_location http://192.168.255.255/flasharchive/solarisarchive partitioning explicit filesys c0t1d0s0 4000 / filesys c0t1d0s1 512 swap filesys c0t1d0s7 free /export/homeThe following list describes some of the keywords and values from this example.install_typeThe profile installs a Solaris Flash archive on the clone system. All files are overwritten as in an initial installation. archive_locationThe Solaris Flash archive is retrieved from an HTTP server. partitioningThe file system slices are determined by the filesys keywords, value explicit. The size of root (/) is based on the size of the Solaris Flash archive. The root file system is installed on c0t1d0s0. The size of swap is set to the necessary size and is installed on c0t1d0s1. /export/home is based on the remaining disk space. /export/home is installed on c0t1d0s7. In the following example, the profile indicates that the custom JumpStart program retrieves the Solaris Flash archive from a secure HTTP server.# profile keywords profile values # ---------------- ------------------- install_type flash_install archive_location https://192.168.255.255/solarisupdate.flar partitioning explicit filesys c0t1d0s0 4000 / filesys c0t1d0s1 512 swap filesys c0t1d0s7 free /export/homeThe following list describes some of the keywords and values from this example.install_typeThe profile installs a Solaris Flash archive on the clone system. All files are overwritten as in an initial installation. archive_locationThe compressed Solaris Flash archive is retrieved from a secure HTTP server. partitioningThe file system slices are determined by the filesys keywords, value explicit. The size of root (/) is based on the size of the Solaris Flash archive. The size of swap is set to the necessary size and is installed on c0t1d0s1. /export/home is based on the remaining disk space. /export/home is installed on c0t1d0s7. In the following example, the profile indicates that the custom JumpStart program retrieves the Solaris Flash archive from an HTTP server. # profile keywords profile values # ---------------- ------------------- install_type flash_install archive_location http://192.168.255.255/flasharchive/solarisarchive partitioning explicit filesys c0t1d0s0 4000 / filesys c0t1d0s1 512 swap filesys c0t1d0s7 free /export/home package SUNWnew http://192.168.254.255/Solaris_11 timeout 5The following list describes some of the keywords and values from this example.install_typeThe profile installs a Solaris Flash archive on the clone system. All files are overwritten as in an initial installation. archive_locationThe Solaris Flash archive is retrieved from an HTTP server. partitioningThe file system slices are determined by the filesys keywords, value explicit. The size of root (/) is based on the size of the Solaris Flash archive. The root file system is installed on c0t1d0s0. The size of swap is set to the necessary size and is installed on c0t1d0s1. /export/home is based on the remaining disk space. /export/home is installed on c0t1d0s7. packageThe SUNWnew package is added from the Solaris_11 directory from the HTTP server 192.168.254.255. In the following example, the profile indicates that the custom JumpStart program retrieves the Solaris Flash archive from an NFS server. The flash_update keyword indicates that this is a differential archive. A differential archive installs only the differences between two system images.# profile keywords profile values # ---------------- ------------------- install_type flash_update archive_location nfs installserver:/export/solaris/flasharchive \ /solarisdiffarchive no_master_checkThe following list describes some of the keywords and values from this example.install_typeThe profile installs a Solaris Flash differential archive on the clone system. Only files that are specified by the archive are installed. archive_locationThe Solaris Flash archive is retrieved from an NFS server. no_master_checkThe clone system is not checked for a valid system image. A valid system image would have been built from the original master system. In the following example, the profile indicates that the custom JumpStart program creates an empty boot environment. An empty boot environment contains no file systems and no copy from the current boot environment occurs. The boot environment can be populated later with a Solaris Flash archive and then activated.# profile keywords profile values # ---------------- ------------------- install_type initial_install system_type standalone partitioning explicit filesys c0t0d0s0 auto / filesys c0t3d0s1 auto swap filesys any auto usr cluster SUNWCall bootenv createbe bename second_BE \ filesystem /:/dev/dsk/c0t1d0s0:ufs \ filesystem -:/dev/dsk/c0t1d0s0:swap \ filesystem /export:shared:ufsThe following list describes some of the keywords and values from this example.partitioningThe file system slices are determined by the filesys keywords, value explicit. The size of root (/) is based on the selected software, value auto, and is installed on c0t0d0s0. The size of swap is set to the necessary size and is installed on c0t3d0s1. usr is based on the selected software and the installation program determines where usr is installed, based on the value any. clusterThe Entire Solaris Software Group, SUNWCall, is installed on the system. bootenv createbeAn empty, inactive boot environment is set up on disk c0t1d0. File systems for root (/), swap, and /export are created, but left empty. This second boot environment can be installed with a Solaris Flash archive at a later time. The new boot environment can then be activated to become the current boot environment. For keyword values and background about using this keyword, see the following references:For descriptions of keyword values, see Profile Keywords and Values. For background about using Solaris Live Upgrade that creates, upgrades, and activates inactive boot environments, see Chapter 2, Solaris Live Upgrade (Overview), in Solaris Express Installation Guide: Solaris Live Upgrade and Upgrade Planning. For background about using a Solaris Flash archive, see Chapter 1, Solaris Flash (Overview), in Solaris Express Installation Guide: Solaris Flash Archives (Creation and Installation). In the following example, the profile indicates that the custom JumpStart program uses Solaris Volume Manager technology to create RAID-1 volumes (mirrors) for the root (/), swap, /usr and /export/home file systems. A Solaris Flash archive is installed on the boot environment.# profile keywords profile values # ---------------- ------------------- install_type flash_install arhcive_location nfs server:/export/home/export/flash.s10.SUNWCall partitioning explicit filesys mirror:d10 c0t0d0s0 c0t1d0s0 4096 / filesys mirror c0t0d0s1 2048 swap filesys mirror:d30 c0t0d0s3 c0t1d0s3 4096 /usr filesys mirror:d40 c0t0d0s4 c0t1d0s4 4096 /usr filesys mirror:d50 c0t0d0s5 c0t1d0s5 free /export/home metadb c0t1d0s7 size 8192 count 3The following list describes some of the keywords and values from this example.install_typeThe profile installs a Solaris Flash archive on the clone system. All files are overwritten as in an initial installation. archive_locationThe Solaris Flash archive is retrieved from an NFS server. partitioningThe file system slices are determined by the filesys keywords, value explicit. filesysThe root (/) file system is created and mirrored on the slices c0t0d0s0 and c0t1d0s0. The size of the root (/) file system is set to 4096 Mbytes. The RAID-1 volume that mirrors c0t0d0s0 and c0t1d0s0 is named d10. filesysThe swap file system is created and mirrored on the slice c0t0d0s1, and is sized at 2048 Mbytes. The custom JumpStart program assigns a name to the mirror. filesysThe /usr file system is created and mirrored on the slices c0t1d0s3 and c0t0d0s3. The size of the /usr file system is set to 4096 Mbytes. The RAID-1 volume is named d30. filesysThe /usr file system is created and mirrored on the slices c0t1d0s4 and c0t0d0s4. The size of the /usr file system is set to 4096 Mbytes. The RAID-1 volume is named d40. metadbThree state database replicas (metadbs) are installed on slice c0t1d0s7, and are sized at 8192 blocks (4 Mbytes). For overview information about how to create mirrored file systems during your installation, see Chapter 8, Creating RAID-1 Volumes (Mirrors) During Installation (Overview), in Solaris Express Installation Guide: Planning for Installation and Upgrade. For guidelines and requirements of creating mirrored file systems, see Chapter 9, Creating RAID-1 Volumes (Mirrors) During Installation (Planning), in Solaris Express Installation Guide: Planning for Installation and Upgrade. For descriptions of keyword values, see filesys Profile Keyword (Creating RAID-1 Volumes) and metadb Profile Keyword (Creating State Database Replicas). In the following example, the profile indicates that the custom JumpStart program uses Solaris Volume Manager technology to create a RAID-1 volume (mirror) for the root (/) file system.# profile keywords profile values # ---------------- ------------------- install_type initial_install cluster SUNWCXall filesys mirror:d30 c0t1d0s0 c0t0d0s0 / filesys c0t0d0s3 512 swap metadb c0t0d0s4 size 8192 count 4 metadb c0t1d0s4 size 8192 count 4 The following list describes some of the keywords and values from this example.clusterThe Entire Solaris Software Plus OEM Support software group, SUNWCXall, is installed on the system. filesysThe root (/) file system is created and mirrored on the slices c0t1d0s0 and c0t0d0s0. The RAID-1 volume that mirrors c0t1d0s0 and c0t0d0s0 is named d30. The custom JumpStart program assigns names to the two submirrors. filesysThe swap file system is created and mirrored on the slice c0t0d0s3, and is sized at 512 Mbytes. metadbFour state database replicas (metadbs) are installed on slice c0t0d0s4, and are sized at 8192 blocks (4 Mbytes). metadbFour state database replicas (metadbs) are installed on slice c0t1d0s4, and are sized at 8192 blocks (4 Mbytes). For overview information about how to create RAID-1 volumes during your installation, see Chapter 8, Creating RAID-1 Volumes (Mirrors) During Installation (Overview), in Solaris Express Installation Guide: Planning for Installation and Upgrade. For guidelines and requirements about creating RAID-1 volumes, see Chapter 9, Creating RAID-1 Volumes (Mirrors) During Installation (Planning), in Solaris Express Installation Guide: Planning for Installation and Upgrade. For descriptions of keyword values, see filesys Profile Keyword (Creating RAID-1 Volumes) and metadb Profile Keyword (Creating State Database Replicas). In the following example, the profile indicates that the custom JumpStart program uses Solaris Volume Manager technology to create RAID-1 volumes (mirrors) for the root (/), swap, and /usr file systems.# profile keywords profile values # ---------------- ------------------- install_type initial_install cluster SUNWCXall filesys mirror:d100 c0t1d0s0 c0t0d0s0 200 / filesys c0t1d0s5 500 /var filesys c0t0d0s5 500 filesys mirror c0t0d0s1 512 swap metadb c0t0d0s3 size 8192 count 5 filesys mirror c0t1d0s4 c0t0d0s4 2000 /usr filesys c0t1d0s7 free /export/home filesys c0t0d0s7 freeThe following list describes some of the keywords and values from this example.clusterThe Entire Solaris Software Plus OEM Support software group, SUNWCXall, is installed on the system. filesysThe root (/) file system is created and mirrored on the slices c0t1d0s0 and c0t0d0s0. The size of the root (/) file system is set to 200 Mbytes. The RAID-1 volume that mirrors c0t1d0s0 and c0t0d0s0 is named d100. filesysThe /var file system is installed on the slice c0t1d0s5 and is sized at 500 Mbytes. The root (/) file system is created and mirrored on the slices c0t1d0s0 and c0t0d0s0. The size of the root (/) file system is set to 200 Mbytes. The RAID-1 volume that mirrors c0t1d0s0 and c0t0d0s0 is named d100. filesysThe swap file system is created and mirrored on the slice c0t0d0s1, and is sized at 512 Mbytes. The custom JumpStart program assigns a name to the mirror. metadbFive state database replicas (metadbs) are installed on slice c0t0d0s3, and are sized at 8192 blocks (4 Mbytes). filesysThe /usr file system is created and mirrored on the slices c0t1d0s4 and c0t0d0s4. The size of the /usr file system is set to 2000 Mbytes. The custom JumpStart program assigns a name to the mirror. For overview information about how to create mirrored file systems during your installation, see Chapter 8, Creating RAID-1 Volumes (Mirrors) During Installation (Overview), in Solaris Express Installation Guide: Planning for Installation and Upgrade. For guidelines and requirements of creating mirrored file systems, see Chapter 9, Creating RAID-1 Volumes (Mirrors) During Installation (Planning), in Solaris Express Installation Guide: Planning for Installation and Upgrade. For descriptions of keyword values, see filesys Profile Keyword (Creating RAID-1 Volumes) and metadb Profile Keyword (Creating State Database Replicas). # profile keywords profile values # ---------------- ------------------- install_type initial_install system_type standalone fdisk c0t0d0 0x04 delete fdisk c0t0d0 solaris maxfree cluster SUNWCall cluster SUNWCacc deleteThe following list describes some of the keywords and values from this example.fdiskAll fdisk partitions of type DOSOS16 (04 hexadecimal) are deleted from the c0t0d0 disk. fdiskA Solaris fdisk partition is created on the largest contiguous free space on the c0t0d0 disk. clusterThe Entire Distribution software group, SUNWCall, is installed on the system. clusterThe system accounting utilities, SUNWCacc, are not to be installed on the system. After you create a profile, use the pfinstall1M command to test the profile. Test the profile before you use the profile to install or upgrade a system. Testing a profile is especially useful when you are creating upgrade profiles that reallocate disk space.By looking at the installation output that is generated by pfinstall, you can quickly determine if a profile works as you intended. For example, use the profile to determine if a system has enough disk space to upgrade to a new release of the Solaris software before you perform the upgrade on that system.pfinstall enables you to test a profile against the following:The system's disk configuration where pfinstall is being run. Other disk configurations. You use a disk configuration file that represents a structure of a disk, for example, a disk's bytes/sector, flags, and slices. Creating disk configuration files is described in Creating Disk Configuration Files and To Create a Disk Configuration File. You cannot use a disk configuration file to test a profile you intend to use to upgrade a system. Instead, you must test the profile against the system's actual disk configuration and the software that is currently installed on that system. To test a profile for a particular Solaris release successfully and accurately, you must test a profile within the Solaris environment of the same release. For example, if you want to test a Solaris initial installation profile, run the pfinstall command on a system that is running the Solaris OS.You need to create a temporary installation environment if you are testing a profile under one of the following conditions:You want to test a Solaris Express 5/07 upgrade profile on a system that is running a previous version of the Solaris software. You do not have a Solaris Express 5/07 system installed yet to test Solaris Express 5/07 initial installation profiles. Boot a system from an image of one of the following: For SPARC based systems:Solaris Operating System for SPARC Platforms DVD Solaris Software for SPARC Platforms - 1 CD For x86 based systems:Solaris Operating System for x86 Platforms DVD Solaris Software for x86 Platforms - 1 CD If you want to test an upgrade profile, boot the system that you are upgrading. Respond to the system identification questions. To exit from the installation program, type ! at the following prompt.The Solaris installation program will assist you in installing software for Solaris. <Press ENTER to continue> {"!" exits} Execute the pfinstall command from the shell. For details about using the pfinstall command, see Step 7 in To Test a Profile. If you are using the locale keyword, the pfinstall D command fails to test the profile. For a workaround, see the error message “could not select locale,” in the section, Upgrading the Solaris OS. Locate a system on which to test the profile that is the same type of platform, SPARC or x86, for which the profile was created.If you are testing an upgrade profile, you must test the profile on the actual system that you intend to upgrade. Use the following decision table to determine what to do next.Test Scenario Instructions Test an initial installation profile and have a system that is running the Solaris Express 5/07 software. Become superuser on the system and go to Step 5. Test an upgrade profile, or you do not have a system that is running Solaris Express 5/07 to test an initial installation profile. Create a temporary Solaris Express 5/07 environment to test the profile. For details, see To Create a Temporary Solaris Environment to Test a Profile. Then, go to Step 3. Create a temporary mount point.# mkdir /tmp/mnt Mount the directory that contains the profile or profiles that you want to test.Mount Scenario Typing Instructions Mount a remote NFS file system for systems on the network. mount -F nfs server_name:path /tmp/mnt SPARC: Mount a UFS-formatted diskette. mount -F ufs /dev/diskette /tmp/mnt Mount a PCFS-formatted diskette. mount -F pcfs /dev/diskette /tmp/mnt To test the profile with a specific system memory size, set SYS_MEMSIZE to the specific memory size in Mbytes.# SYS_MEMSIZE=memory_size # export SYS_MEMSIZE Did you mount a directory in Step 4? If yes, change the directory to /tmp/mnt.# cd /tmp/mnt If no, change the directory to where the profile is located, which is usually the JumpStart directory.# cd jumpstart_dir_path Test the profile with the pfinstall1M command.# /usr/sbin/install.d/pfinstall D:d disk_config_file c path profileYou must include the d or D option. If you do not include one of these options, pfinstall uses the profile you specify to install the Solaris software. All of the data on the system is overwritten. Dpfinstall uses the current system's disk configuration to test the profile. You must use the D option to test an upgrade profile. d disk_config_filepfinstall uses the disk configuration file, disk_config_file, to test the profile. If disk_config_file is not located in the directory where pfinstall is run, you must specify the path.For instructions about how to create a disk configuration file, see Creating Disk Configuration Files.You cannot use the d disk_config_file option with an upgrade profile, install_type upgrade. You must always test an upgrade profile against a system's disk configuration, that is, you must use the D option. c pathThe path to the Solaris software image. You use this option, for example, if the system is using removable media services to mount the Solaris Software - 1 CD for your platform.The c option is not required if you booted from a Solaris Operating System DVD or a Solaris Software - 1 CD image for your platform. The DVD or CD image is mounted on /media/cdrom as part of the booting process. profileThe name of the profile to test. If profile is not in the directory where pfinstall is being run, you must specify the path. The following example shows how to use pfinstall to test a profile that is named basic_prof. The profile is tested against the disk configuration on a system on which the Solaris Express 5/07 software is installed. The basic_prof profile is located in the /jumpstart directory, and the path to the Solaris Operating System DVD image is specified because removable media services are being used.# cd /jumpstart # /usr/sbin/install.d/pfinstall -D -c /media/cdrom/pathname basic_prof The following example shows how to use pfinstall to test the profile that is named basic_prof on a Solaris Express 5/07 system. The test is performed against the 535_test disk configuration file. The test checks for 64 Mbytes of system memory. This example uses a Solaris Software for SPARC Platforms - 1 CD or Solaris Software for x86 Platforms - 1 CD image that is located in the /export/install directory.# SYS_MEMSIZE=64 # export SYS_MEMSIZE # /usr/sbin/install.d/pfinstall -d 535_test -c /export/install basic_prof Before you can use a profile and rules file, you must run the check script to validate that the files are set up correctly. If all rules and profiles are correctly set up, the rules.ok file is created, which is required by the custom JumpStart installation software to match a system to a profile. Table 3–2 describes what the check script does. Stage Description 1 The rules file is checked for syntax.check verifies that the rule keywords are legitimate and that the begin, class, and finish fields are specified for each rule. The begin and finish fields can consist of a minus sign (-) instead of a file name. 2 If no errors are found in the rules file, each profile that is specified in the rules is checked for syntax. 3 If no errors are found, check creates the rules.ok file from the rules file, removes all comments and blank lines, retains all rules, and adds the following comment line at the end: # version=2 checksum=num Ensure that the check script is located in the JumpStart directory. The check script is in the Solaris_11/Misc/jumpstart_sample directory on the Solaris Operating System DVD or on the Solaris Software - 1 CD. Change the directory to the JumpStart directory. Run the check script to validate the rules file:$ ./check -p path -r file_namep pathValidates the rules by using the check script from the Solaris software image instead of the check script from the system you are using. path is the image on a local disk or a mounted Solaris Operating System DVD or a Solaris Software - 1 CD.Use this option to run the most recent version of check if your system is running a previous version of Solaris. r file_nameSpecifies a rules file other than the one that is named rules. Using this option, you can test the validity of a rule before you integrate the rule into the rules file. As the check script runs, the script reports the checking of the validity of the rules file and each profile. If no errors are encountered, the script reports the following information. The custom JumpStart configuration is ok Ensure that root owns the rules.ok file and that the permissions are set to 644. After you validate the rules file, you can learn more about optional custom JumpStart features in Chapter 4, Using Optional Custom JumpStart Features (Tasks). You can learn about performing custom JumpStart installations in Chapter 6, Performing a Custom JumpStart Installation (Tasks).