These are some of the common installation problems and errors that users
face when using Solaris Jumpstart installation:

Q1:  How do I configure my Boot server if it is a NIS client and I wishes to
use 
sysidcfg file for my Jumpstart setup?

Q2:  Can I have all Configuration, Install and Boot server functions on a
single
host?

Q3:  After I have setup my Configuration/Install/Boot servers, I ran "boot net
- 
install" on the client and it gave me:
     No bootparam (whoami) server responding; still trying...
     RPC: Timed out.

Q4:  After I have setup my Configuration/Install/Boot servers, I ran "boot net
- 
install" on the client and it gave me:
     root directory: /cdrom/sol_7_sparc/s0/Solaris_2.7/Tools/Boot
     panic - boot: Could not mount filesystem.

Q5:  Half way through, during the installation of the client, it stopped and 
asked
for user input in one of its sysidtool or installtool dialog boxes.

A1:  To achieve that, we need to change /etc/nsswitch.conf to ensure that the 
server
searches for local files first before using NIS. i.e. change hosts, ethers and 
bootparams:
in the nsswitch.conf file to:
     hosts:      files nis 
     ethers:     files nis
     bootparams: files nis 
After which, we need to add to the /etc/hosts file with the IP address and 
hostname 
of the new client to be installed. We do not need to create or amend the 
/etc/ethers
and /etc/bootparams files. These files will be altered accordingly after we 
execute
the "add_install_client" command.

A2:  Yes.

A3:  The ethernet address of the client is not set correctly on the Boot
server.
Check that the /etc/ethers file on the Boot server has the correct ethernet 
address
of the client. If NIS is used for Jumpstart setup, make sure that the NIS
master
server executes "make" to rebuild the network NIS maps, after the /etc/ethers 
file 
is updated.

A4:  The filesystem with the installation directory on the Install server is
not 
shared. Also, make sure that, on the Configuration server, the directory with 
all 
the rule, classes and sysidcfg files, is shared.

A5:  It means that the class or sysidcfg file has not been set up correctly. 
Make 
sure that all the essential entries are included. Commonly omitted entries are:
"system_locale" and "timezone" for the sysidcfg file; and "locale" for the
class 
file.