Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 10 1/13 Installation Guide: JumpStart Installations Oracle Solaris 10 1/13 Information Library |
1. Where to Find Oracle Solaris Installation Planning Information
3. Preparing JumpStart Installations (Tasks)
Task Map: Preparing JumpStart Installations
Creating a Profile Server for Networked Systems
How to Create a JumpStart Directory on a Server
Allowing All Systems Access to the Profile Server
Using a Wildcard Entry to Allow All Systems Access to the Profile Server
Creating a Profile Diskette for Stand-alone Systems
SPARC: How to Create a Profile Diskette
x86: How to Create a Profile Diskette With GRUB
How to Create a Temporary Oracle Solaris Environment to Test a Profile
How to Validate the rules File
4. Using Optional JumpStart Features (Tasks)
5. Creating Custom Rule and Probe Keywords (Tasks)
6. Performing a JumpStart Installation (Tasks)
7. Installing With JumpStart (Examples)
8. JumpStart Keyword Reference
A profile is a text file that defines how to install the Oracle 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 Oracle 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 server
Note - Sample profiles are already located in the JumpStart directory if you created the JumpStart directory by using either of these procedures:
A profile must contain the following:
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 text
Any 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
Name the profile to reflect how you intend to use the profile to install the Oracle Solaris software on a system. For example, you might name the profiles basic_install, eng_profile, or user_profile.
For a list of profile keywords and values, see Profile Keywords and Values.
Note - Profile keywords and their values are case sensitive.
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 Oracle Solaris software is installed on a system. Profile Keywords and Values contains a description of profile keywords and values.
Note - If you are installing an Oracle Solaris ZFS root pool, see Chapter 9, Installing a ZFS Root Pool With JumpStart for limitations and profile examples.
Example 3-2 Mounting Remote File Systems and Adding and Deleting Packages
# 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 SUNWCacc
Some of the keywords and values in this example are as follows:
The install_type keyword is required in every profile.
The system_type keyword defines that the system is to be installed as a stand-alone system.
The file system slices are determined by the software to be installed with the value default. The size of swap is set to 512 MB and is installed on any disk, value any.
The Developer Oracle Solaris Software Group, SUNWCprog, is installed on the system.
If 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.
Example 3-3 Mounting Remote File Systems and Adding a Third-Party Package
# 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 5
Some of the keywords and values in this example are as follows:
The install_type keyword is required in every profile.
The system_type keyword defines that the system is to be installed as a standalone system.
The file system slices are determined by the software to be installed with the value default. The size of swap is set to 512 MB and is installed on any disk, value any.
The Developer Oracle Solaris Software Group, SUNWCprog, is installed on the system.
A third-party package is installed on the system located on an HTTP server.
Example 3-4 Specifying Where to Install File Systems
# 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
Some of the keywords and values in this example are as follows:
The 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.
The Entire Oracle Solaris Software Group, SUNWCall, is installed on the system.
Example 3-5 Upgrading and Installing Patches
# 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_10/patches \ retry 5 locale de
Some of the keywords and values in this example are as follows:
The 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.
The root file system on c0t3d0s2 is upgraded.
A 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.
The binary compatibility package, SUNWbcp, is not installed on the system after the upgrade.
The 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.
A 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_10/patches. In case of a mount failure, the NFS mount is tried five times.
The German localization packages are to be installed on the system.
Example 3-6 Reallocating Disk Space for an Upgrade
# 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 de
Some of the keywords and values in this example are as follows:
The 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.
The root file system on c0t3d0s2 is upgraded.
A 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.
The 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.
The binary compatibility package, SUNWbcp, is not installed on the system after the upgrade.
The 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.
The German localization packages are to be installed on the system.
Example 3-7 Retrieving a Flash Archive From an HTTP Server
In the following example, the profile indicates that the JumpStart program retrieves the flash archive from an HTTP server. (Flash Archive is a feature of Oracle Solaris.)
# 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
Some of the keywords and values in this example are as follows:
The profile installs a flash archive on the clone system. All files are overwritten as in an initial installation.
The flash archive is retrieved from an HTTP server.
The file system slices are determined by the filesys keywords, value explicit. The size of root (/) is based on the size of the 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.
Example 3-8 Retrieving a Flash Archive From a Secure HTTP Server
In the following example, the profile indicates that the JumpStart program retrieves the 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/home
Some of the keywords and values in this example are as follows:
The profile installs a flash archive on the clone system. All files are overwritten as in an initial installation.
The compressed flash archive is retrieved from a secure HTTP server.
The file system slices are determined by the filesys keywords, value explicit. The size of root (/) is based on the size of the 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.
Example 3-9 Retrieving a Flash Archive and Installing a Third-Party Package
In the following example, the profile indicates that the JumpStart program retrieves the 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_10 timeout 5
Some of the keywords and values in this example are as follows:
The profile installs a flash archive on the clone system. All files are overwritten as in an initial installation.
The flash archive is retrieved from an HTTP server.
The file system slices are determined by the filesys keywords, value explicit. The size of root (/) is based on the size of the 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.
The SUNWnew package is added from the Solaris_10 directory from the HTTP server 192.168.254.255.
Example 3-10 Retrieving a Flash Archive Differential Archive From an NFS Server
In the following example, the profile indicates that the JumpStart program retrieves the 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_check
Some of the keywords and values in this example are as follows:
The profile installs a flash archive differential archive on the clone system. Only files that are specified by the archive are installed.
The flash archive is retrieved from an NFS server.
The clone system is not checked for a valid system image. A valid system image would have been built from the original master system.
Example 3-11 Creating an Empty Boot Environment
In the following example, the profile indicates that the 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 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:ufs
Some of the keywords and values in this example are as follows:
The 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.
The Entire Oracle Solaris Software Group, SUNWCall, is installed on the system.
An 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 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 the Live Upgrade, a feature of Oracle Solaris, that creates, upgrades, and activates inactive boot environments, see Chapter 2, Live Upgrade (Overview), in Oracle Solaris 10 1/13 Installation Guide: Live Upgrade and Upgrade Planning.
For background about using a flash archive, see Chapter 1, Flash Archive Overview, in Oracle Solaris 10 1/13 Installation Guide: Flash Archives (Creation and Installation).
Example 3-12 Creating RAID-1 Volumes When Installing a Flash Archive
In the following example, the profile indicates that the JumpStart program uses Solaris Volume Manager technology to create RAID-1 volumes (mirrors) for the root (/), swap, /usr and /export/home file systems. A 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 3
Some of the keywords and values in this example are as follows:
The profile installs a flash archive on the clone system. All files are overwritten as in an initial installation.
The flash archive is retrieved from an NFS server.
The file system slices are determined by the filesys keywords, value explicit.
The root (/) file system is created and mirrored on the slices c0t0d0s0 and c0t1d0s0. The size of the root (/) file system is set to 4096 MB. The RAID-1 volume that mirrors c0t0d0s0 and c0t1d0s0 is named d10.
The swap file system is created and mirrored on the slice c0t0d0s1, and is sized at 2048 MB. The JumpStart program assigns a name to the mirror.
The /usr file system is created and mirrored on the slices c0t1d0s3 and c0t0d0s3. The size of the /usr file system is set to 4096 MB. The RAID-1 volume is named d30.
The /usr file system is created and mirrored on the slices c0t1d0s4 and c0t0d0s4. The size of the /usr file system is set to 4096 MB. The RAID-1 volume is named d40.
Three state database replicas (metadbs) are installed on slice c0t1d0s7, and are sized at 8192 blocks (4 MB).
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 Oracle Solaris 10 1/13 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 Oracle Solaris 10 1/13 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).
Example 3-13 Creating a RAID-1 Volume to Mirror the Root File System
In the following example, the profile indicates that the 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
Some of the keywords and values in this example are as follows:
The Entire Oracle Solaris Software Plus OEM Support software group, SUNWCXall is installed on the system.
The 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 JumpStart program assigns names to the two submirrors.
The swap file system is created and mirrored on the slice c0t0d0s3, and is sized at 512 MB.
Four state database replicas (metadbs) are installed on slice c0t0d0s4, and are sized at 8192 blocks (4 MB).
Four state database replicas (metadbs) are installed on slice c0t1d0s4, and are sized at 8192 blocks (4 MB).
Example 3-14 Creating RAID-1 Volumes to Mirror Multiple File Systems
In the following example, the profile indicates that the 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 free
Some of the keywords and values from in this example are as follows:
The Entire Oracle Solaris Software Plus OEM Support software group, SUNWCXall is installed on the system.
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 MB. The RAID-1 volume that mirrors c0t1d0s0 and c0t0d0s0 is named d100.
The /var file system is installed on the slice c0t1d0s5 and is sized at 500 MB. 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 MB. The RAID-1 volume that mirrors c0t1d0s0 and c0t0d0s0 is named d100.
The swap file system is created and mirrored on the slice c0t0d0s1, and is sized at 512 MB. The JumpStart program assigns a name to the mirror.
Five state database replicas (metadbs) are installed on slice c0t0d0s3, and are sized at 8192 blocks (4 MB).
The /usr file system is created and mirrored on the slices c0t1d0s4 and c0t0d0s4. The size of the /usr file system is set to 2000 MB. The JumpStart program assigns a name to the mirror.
Example 3-15 x86: Using the fdisk Keyword
# profile keywords profile values # ---------------- ------------------- install_type initial_install system_type standalone fdisk c0t0d0 0x04 delete fdisk c0t0d0 solaris maxfree cluster SUNWCall cluster SUNWCacc delete
Some of the keywords and values in this example are as follows:
All fdisk partitions of type DOSOS16 (04 hexadecimal) are deleted from the c0t0d0 disk.
An Oracle Solaris fdisk partition is created on the largest contiguous free space on the c0t0d0 disk.
The Entire Distribution software group, SUNWCall, is installed on the system.
The system accounting utilities, SUNWCacc, are not to be installed on the system.
Example 3-16 Creating a JumpStart Profile for An Initial iSCSI Installation
install_type initial_install partitioning explicit filesys rootdisk.s4 5000 filesys rootdisk.s1 2048 iscsi_target_name iqn.1986-03.com.sun:02:358ddbf8-601a-e73a-df56-89 iscsi_target_ip 10.12.162.24 iscsi_target_lun 0 iscsi_target_port 3260 cluster SUNWCrnet
The following example shows a sample JumpStart profile for an upgrade installation.
Example 3-17 JumpStart Profile For An iSCSI Upgrade Installation
install_type upgrade iscsi_target_name iqn.1986-03.com.sun:02:358ddbf8-601a-e73a-df56-89 iscsi_target_ip 10.12.162.24 iscsi_target_lun 0 iscsi_target_port 3260 iscsi_target_slice 4
See iSCSI Profile Keyword for details about the keywords used in the JumpStart profile for iSCSI upgrade and installation.
Caution - The following keywords are used in the JumpStart profile to indicate where the locations of the directories such as the root directory, swap space, the /usr directory and so on have to be created.
Since the disk number is dynamically generated during an iSCSI installation, the user should not explicitly provide the disk nomenclature (cXtXdXsX) for the above keywords in the JumpStart profile during an iSCSI installation. |
Caution - When the iSCSI key-value information is provided in the profile, the boot_device key-value pair and root_device key-value pair should not be included in the profile. The root_device key-value pair is dynamically assigned by the pfinstall command based on the iSCSI target. |