Jumpstart offers a way to install Solaris using network over multiple server with similar of different configurations.

Here is a step by Step howto guide to install Solaris over network .

1.0 Before you start
Pre Installation Checklist :
* The install server or boot server is in the same local network segment as client with network link up .
* NFS services are running On jumpstart server
* The tftp services are running . To start uncomment the tftp entry in /etc/inet/inetd.conf and restart the inet services
* The reverse address lookup daemon ,in.rarpd , is running .

2.0 Preparing for a jumpstart server

Create and share a directory to store and share install server data.

#mkdir /export/install

share it
#vi /etc/dfs/dfstab

add share -F nfs -o ro,anon=0 /export/install
to export file system for sharing.
Do a shareall so that the file system is now exported

2.1 Setting up an Install server

Mount Solaris cdrom

Follow the steps :
#cd /cdrom/cdrom0/s0/Solaris_2.7/Tools

#./setup_install_server /export/install

This will copy the cdrom contents in to the /export/install directory.

2.2 Setting up a boot server
For installing clients over different networks you need a boot server in the same subnet as client .
Boot server after booting the client hands over subsequent installation & configuration process to install server .

# ./setup_install_server -b /export/install sun4u

the above command installs software for booting the client.
You also have to do a add host and add_install_client in boot server, see adding clients . Rest of the configuration has to be done at install server.

2.3 Setting up configuration files

Make a jumpstart directory say /jumpstart
Copy sample jumpstart files from cd

#cp –r /cdrom/cdrom0/s0/Solaris_2.7/Misc/* /jumpstart

2.4 Making Rules

Edit the sample rules file as per your requirement

#vi /jumpstart/rules

Keywords their value and usage is described in rules file itself.
any minus sign (-) in rule value always matches for that keyword.

RULE_KEYWORD RULE_VALUE DESCRIPTIONS

domainname text system’s domain name
disksize text range system’s disk size
disk device name text disk size (MBytes range)
hostname text system’s host name
installed text text system’s installed ver. of Solaris disk device name (text)
OS release text
karch text system’s kernel architecture
memsize range system’s memory size (MBytes range)
model text’ system’s model number
network text system’s IP address
totaldisk range system’s total disk size (MBytes range)

The following rule set matches any machine and redirect the install request to a profile file called any_machine.

any – - any_machine -

more examples can be found in rules file.

2.5 Verifying rules

A script called check validates and generates a rules.ok file if syntax, keywords are in order.

#./check
Validating rules…
Validating profile any_machine…
rules ok.

The clients will read the rules.ok file for booting information

2.6 Creating Profiles

Profile is a text file which contains configuration information for the clients

A sample profile file called any_machine is already there . You can create your custom profile files through text editor and mention in rules file.

#vi any_machine
install_type initial_install
system_type server
partitioning explicit
filesys c0t0d0s0 500 /
filesys c0t0d0s1 1000 swap
filesys c0t0d0s3 1000 /usr
filesys c0t0d0s4 1000 /var
filesys c0t0d0s5 1000 /opt
cluster SUNWCall add

2.7 Sysidcfg file
Sysidcfg file keeps the various system information like locale time zone etc and supply it to the client at the booting time. In the absence of this the installation turns in to interactive mode to prompt you to supply the value for these variables

You have to create this file in text editor . A sample file would look like following

# vi sysidcfg
system_locale=en_US
install_locale=en_US
timeserver=localhost
timezone=US/Pacific
network_interface=hme0 {netmask=255.255.255.0}
name_service=NONE

2.8 Add a host entry
Edit the /etc/ethers file and put a host entry for your client ;ethernet address followed by host name.

On client ok>banner will give ethernet address

#vi /etc/ethers
8:00:50:44:88:12 mercury

2.9 Adding a Client
The clients are added using add_install_client command . You have to be in the Tools directory of Solaris CD or image as the programme looks for the presence of valid Boot image dir in the same directory.

#cd /export/install/Solaris_2.7/Tools
#./add_install_client -e 8:00:50:44:88:12 -s jupiter:/export/install -c jupiter:/jumpstart -p jupiter:/jumpstart mercury sun4u

-e specify the ethernet address of client -s option specify the location of boot image ( As given in setup_install_server)
-c option specify the jumpstart directory path.
-p option specify the sysidcfg file location
jupiter is your jumpstart server
mercury is jumpstart client to be installed.
sun4u is the architecture of client
You need to enter the client through above command at the boot server also

3.0 Starting The client Installation

at client use the following command

ok>boot net – install

the system will initialize and starts booting from network
and you will see these messages

System is coming up
checking rules file
using profile any _machine
selecting cluster SUNWCall
Preparing system to install software
setting up disk
creating and checking up file systems
installing packages

After completion it will reboot and ask the new root password and after that takes you to the
console prompt where you can login and do additional task you want to do.

4.0 Begin & Finish Scripts

These are the optional features of jumpstart .
A begin script is a shell script which is used to perform the task before Solaris OS is installed. These are specified in the rules file.

These can be used for creating dynamic derived profiles or backing up files before upgrading.

A finish script is used to perform the tasks after the OS is installed but before reboot.

These can be used to customize root environment , adding patches , files etc.

These scripts can not be checked by the check script so it must be accurate.

Out put of these scripts goes to /var/adm/begin.log and finish.log.

These should be owned by the root with permission 644

5.0 Trouble Shooting

The following are a few of the common errors encountered in jumpstart.

Error : unknown client “client host name”
Source : add_install_client
Cause : host name can’t be resolved . check host entry is there in /etc/ethers or in nis/nis+ maps .

File just loaded does not appear to be executable .
Source : Solaris booting process
Cause : Improper media . Make sure proper media is available through disk image or CD in the install server . Also see
that the rules point to valid media type.

Warning : getfile:RPC failed : error 5 (RPC timed out)
Source: Client boot requests
Cause : Muliple entries for a client in different servers. There should not be multiple entries in different install server’s /etc/bootparams , /tftpboot or /rplboot . These causes a hang situation when all of them try to answer.

No network boot server .Unable to install the system. See installation instructions
Source : Client boot request.
Cause : Installation is not proper. Check the boot server installation again for any error in command or file .

Timeout waiting for ARP/RARP packet …
Source : Client boot request .
Cause : No server is answering its request for booting .Probably they don’t know about this client . See the proper entries are there in /etc/bootparams or nis maps with proper entries in nsswitch.conf . add_install_client is responsible for adding client information in jumpstart server so check the command and its option.

The idea of this article is to introduce you with the procedure and sequence of event Solaris installation to build enough confidence to finish the installation on your own.

Table of contents
1. Before you begin
2. Getting Started
3. Starting the installation
4. OS distributions & disk configuration
5. After Installation
6. Next Steps

1. Before you begin
For Solaris installation on standalone Sun machine you need the following besides sun cpu :

A) Sun Monitor and Sun Keyboard
OR
For carrying the installation through the serial port A of Sun (ttya)
Dumb Terminal or PC with serial port communication software like HyperTerminal
AND
A null modem cable ( Pin 2 & 3 crossed 5 common ground in 9 Pin to 9 pin ; Pin 7 is common ground in 25 Pin connector ) connecting sun’s serial port A with PC serial port.

B) You will also require a IP address, netmask and a host name for your system.

2. Getting Started

Installation starts at OK> prompt & you can get to ok> using any of the following method :

A. by pressing Stop A key sequence on a Sun Keyboard.
B. typing #init 0 if your system boots up directly .
C. Pressing ctrl-break or shift-break on a pc keyboard if using pc as
console through serial port.
D. If auto-boot feature is enabled system directly boots up
and gives you a # prompt .You can disable auto-boot so next time it
stays at ok prompt for starting installation.
#/usr/platform/sun4u/bin/eeprom auto-boot?=false
reboot the system.

3. Starting the installation
Insert the installation media – OS CD in CD drive and type boot cdrom at ok> prompt .
Ok>boot cdrom

The first phase begins with system identification and gathers information about the system from the the user .System starts booting up and after initialization it asks for language and locale also terminal type in case of PC/terminal

Select your locale and DEC VT100 terminal type for terminal selection
Further installation through the terminal require response to the
selections through ESC and function keys and space bar which are
mentioned on the installation screen.

On the next screens, you are to identify the system as networked or non-networked, and set the default time zone and date/time. After this following host information is required :

A) A host name for the system
B) Whether the system is networked if yes you will have to
provide the IP address & netmask of this machine.

Next you will be asked to select the name services
Name services

[    ]                      NIS+
[    ]                      NIS
[    ]                      DNS
[X ]                        None

Select the service if you have complete details like domain names etc or select none to configure after installation.

You have to select a distribution type from among the choices choices

4. OS distribution & Disk configuration
After identification is complete the installation process proceeds on to the OS and disk configuration and need your input for these settings. Selection depends on role of your machine

Typical space requirement for Solaris 7 is given here.

[   ] Entire Distribution plus OEM support 64-bit 1242.00 MB (F4 to Customize
[X] Entire Distribution 64-bit .....…...….1215.00 MB
[   ] Developer System Support 64-bit.... 1154.00 MB
[   ] End User System Support 64-bit .….. 765.00 MB
[   ] Core System Support .............. .334.00 MB

* Entire distribution with OEM has all software with some third party software
* Entire distribution has all software without third party software .
* Developer system has run time libraries for C software etc.
* End user has X windows and CDE environment .
* Core system is without X windows softwares etc.

If you are not sure select entire distribution.

You will be presented with choice to select the boot disk among the disks present in the system ,unless you have reasons select the c0t0d0 at boot disk.

[ X ] c0t0d0 (17269 MB) boot disk 17269 MB

[ ] c0t1d0 (17269 MB) 17269 MB

overlap partition represents entire disk and is slice s2 of the disk.
If any of the disk contain a preexisting partition you will be given a choice to preserve the partition .
Next the current layout is given ( if existing ) and you are asked to select between Automatic and Custom layout of disk partitions.

* Automatic layout make a single partition of entire boot disk .
* Customize option gives and option to create the partitions and select the sizes .

Things to keep in mind while doing interactive or custom installation
- Additional space is required in /var & /home if server is to handle mail and printing as mail and print files are formed in /var & if the user home directories are to be located on /home partition

A sample partition table may look like following .

File system/Mount point Disk/Slice Size
---------------------------------------

/           c0t0d0s0       300 MB

swap        c0t0d0s1       2000 MB

overlap     c0t0d0s2       17269 MB

/usr        c0t0d0s3       2000 MB

/opt        c0t0d0s4       1000 MB

/var        c0t0d0s5       1000 MB

- The swap partition size depends on the size of RAM in the system if you are not sure of its size keep it double the RAM or more than RAM in the system.

- If you are not sure of individual partition sizes of / , /usr /opt & /var make one partition as / and keep its size sufficiently higher than the distribution size you have selected in earlier steps . Always keep in mind the future software that you might have to install like compilers applications etc and log files that will be generated and accumulate in /var directory or partition.

After you have specified the partition sizes it gives summary and error if any

Installation Option: Initial

Boot Device:            c0t0d0s0
Client Services:        None
Software: Solaris 2.7, Entire Distribution

File System and Disk Layout:
/          c0t0d0s0     300 MB
swap       c0t0d0s1     2000 MB
/usr       c0t0d0s3     2000 MB
/opt       c0t0d0s4     1000 MB
/var       c0t0d0s5     1000 MB

one more question is asked about rebooting

[X] Auto Reboot
[  ] Manual Reboot

Afterwards it starts configuring disk making partitions and installing software indicating the progress in a table .

MBytes Installed: 700.66

MBytes Remaining: 0.00

Installing:
|    |     |     |     |     |

0   20    40    60    80    100

After the installation is complete it customizes system files , devices ,logs , installs patches which are there in OS CD for that release. You can install recommended latest patches later

System then reboots or ask you to reboot depending upon the choice selected earlier .

5. After Installation
After rebooting it asks for new root passed and comes to console prompt where you can login as root install patches ,additional software , make user etc. etc.

Following are some of the booting issues ,error messages their meaning and possible solutions discussed in this article.

1) Booting in single user mode and mounting root disk
2) Making boot device alias
3) Timeout waiting for ARP/RARP packet”? error message
4) The file just loaded does not appear to be executable – error message
5) bootblk: can’t find the boot program – error message
6) boot: cannot open kernel/unix – error message
7) Error reading ELF header? – error message Cannot open /etc/path_to_inst error message
9) Can’t stat /dev/rdsk/c0t3d0s0 error message

1. Booting in single user mode and mounting root hard disk
Most important step in diagnosing the booting problems is booting the system in single user mode and examining the hard disk for possible errors & work out the corrective measure. Single user mode can be achieved by any of the following methods :-
ok> boot -s ;from root disk
ok> boot net -s ;from network

ok>boot cdrom -s ;from cdrom
Rebooting with command: cdrom -s
Configuring the /devices directory
Configuring the /dev directory |
INIT: SINGLE USER MODE
#
# fsck /dev/rdsk/c0t3d0s0
# mount /dev/dsk/c0t3d0s0 /mnt

Perform the required operation on mounted disk , now accessible through /mnt ,& unmount the hard disk after you are done ;
# umount /mnt
# reboot

2.Making boot device alias
In case system can not boot from primary disk and it is needed to make another boot disk to access the data , nvalias command is used .
nvalias command makes the device alias and assigns an alternate name to a physical disk. Physical address of target disk is required which can be had by show-disk command on ok>.

ok> nvalias disk7 /iommu@f,e0000000/sbus@f,e0001000/dma@3,81000/esp@3,80000/sd2,0
The new aliased disk can be named as boot disk or can be used for booting by refering its name .
ok> setenv boot-device disk7
ok>reset
or
ok> boot disk7

3. Timeout waiting for ARP/RARP packet ?
At ok> type printenv and look for these parameters .
boot-device disk
mfg-switch? false
diag-switch? false
if you see “boot-device net ” or true value for the other two parameter change it to the values above.
In case you wants to boot from network make sure your client is properly configured in boot server and network connections & configuration are proper.

4. The file just loaded does not appear to be executable
Boot block on the hard disk is corrupted .Boot the system in single user mode with cdrom and reinstall boot block .

#installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c0t3d0s0

5. bootblk: can’t find the boot program
boot block can not find the boot programe – ufsboot in Solaris .Either ufsboot is missing or corrupted . In such cases it can be restored from the cdrom after booting from cdrom & mounting the hard disk
# cp /platform/`uname -i`/ufsboot /mnt/platform/`uname -i`

6. boot: cannot open kernel/unix
Kernel directory or unix kernel file in this directory is not found .Probably deleted during fsck or deleted by mistake. Copy it from the cdrom or restore from the backup tape.
# cp /platform/`uname -i`/kernel/unix /mnt/platform/`uname -i`/kernel

7. Error reading ELF header ?
Kernel directory or unix kernel file in this directory is corrupted.Copy it from the cdrom or restore from the backup tape.
# cp /platform/`uname -i`/kernel/unix /mnt/platform/`uname -i`/kernel

8. Cannot open /etc/path_to_inst
System can not find the /etc/path_to_install file .It might be missing or corrupted and needs to be rebuild.
To rebuild this file boot the system with -ar option :
ok>boot -ar
Press enter to select default values for the questions asked during booting and select yes to rebuild /etc/path_to_install
The /etc/path_to_inst on your system does not exist or is empty. Do you want to rebuild this file [n]? y
system will continue booting after rebuilding the file.

9. Can’t stat /dev/rdsk/c0t3d0s0
When booted from cdrom and done fsck the root partition comes out to be fine but on booting from root disk this error occurs. The device name for / is missing from /dev/dsk directory and to resolve the issue /dev & /devices directories has to be restored from root backup tapes .

Accessing the openboot
Openboot console can be accessed by any of the following means . Be careful not to do this on a live system as you might end up in rebooting the server .

1. Rebooting a system , if auto-boot is not set to true rebooted system returns to OK> prompt which is openboot prompt

2. Pressing the keys L1 and A or STOP A , at the same time will bring you to the OpenBoot system. You will see the display
Type b (boot), c (continued), or n (new command mode)
>
Typing b boots the operating system . Typing c resumes the execution of a halted program. Typing n gets you to the Forth monitor, and the prompt will change to ok.

OpenBoot Parameters & commands

Following two tables gives a list of Openboot parameters & commands