INSTALLATION / JUMPSTART
THREE INSTALLATION PHASES
System Configuration identifies system information, two methods to preconfigure this info
If not preconfigured, the sysidtool executes to prompt for info
(sysidtool has 5 programs: sysidnet, sysidnis, sysidsys, sysidroot & sysidpm)
Two methods to Preconfigure:
1. sysidcfg file create a sysidcfg file with the system config info, format: keyword=info
2. name service entries for the system is added to the NIS or NIS+ database
System Installation copies the software onto the system
Methods: SunInstall (interactive)
WebStart (interactive)
JumpStart
Custom JumpStart
Post-Installation any required updates to system software, patches installed, applications,
user accounts & environments, system security customizing
NETWORK INSTALLATION
(commands in this section are on the CD-ROM or boot server directory under Solaris_7/Tools)
Boot Server Provides the files needed for the client to boot via the network.
Must be on same subnet as the client.
setup_install_server –b pathname will copy the boot files to the boot server directory
Install Server Provides the files to the client for installation of the operating system via the network
Files are provided on either the CD-ROM or the server’s local disk.
setup_install_server pathname will copy the files to the install server directory
add_to_install_server pathname adds additional software to the install server dir.
modify_install_server enables WebStart install
Install Clients Client identification info is obtained from (in order until info is obtained):
(1st) sysidcfg file
(2nd) name service
(3rd) interactively during the installation.
add_install_client args client_name client_architecture
adds clients to the install server and/or boot server, updates /etc/bootparams file
-e install client’s ethernet address
-i install client’s IP address
-s install server name and path to distribution files, format host:pathname
-c JumpStart config server and path to config directory, format host:pathname
client_architecture information:
sun4c SCSI Sparc 1, 2, IPX, IPC
sun4m SCSI Sparc 4, 5, 10, 20, classic voyager
sun4u SCSI/PCI Ultra Port Architecture
rm_install_client client_name remove install client, updates /etc/bootparams file
TWO JUMPSTART METHODS:
1. JumpStart auto install of the operating system determined by a default profile for the
client system’s type architecture & disk size
software cannot be manually selected.
2. Custom JumpStart auto install of the operating system determined by a custom profile
rules contains the different classes of machines and is read sequentially
once a match is found the search ends
Fields of the rules file
keyword predefined keyword describing system attribute
match_value value to match the keyword
begin begin script filename
profile profile filename
finish finish script filename
Keywords Value
any matches any
arch system architecture type (sun4u, sun4m, sun4c)
disksize disk name
hostaddress IP address
hostname hostname
memsize physical memory
model platform name
Example:
match_key match_value begin profile finish
hostaddress 191.128.114.9 - ip_profile -
model ‘SUNW,Ultra-5_10’ - ultra_profile ultra_postinstall
any - - ; any_profile -
‘profile’ files define how to install Solaris 7 on systems using this profile file
uses keywords and values like the rules file
Keyword Value
boot_device partition to use as a boot device
cluster software group to install, add or delete
filesys pathname & mount point of a remote file system to mount
package software package to add or delete
root_device root device partition
rules.ok The check script verifies the syntax in the rules and ‘profile’ files. If there are no
syntax errors, the rules.ok file is created from the rules file. The rules.ok file is
read during automatic installation.
begin & finish begin script runs before the profile file (pre-install)
scripts finish script runs after the profile file (post-install)