Specific Installation Errors

Booting "81986E3F.PREP" from server <IP_address> <server_name> Read 156kbytes Trap Vector is 0x300 ...

Reason Error Occurred	How to Fix the Problem
You are using the wrong boot diskette.	Get the Solaris boot diskette that matches the version of the Solaris software that you are installing.
Error: Unknown client "host_name"
Reason Error Occurred	How to Fix the Problem
The host_name argument in the	Add the host host_name to the NIS or NIS+ name service. (Either update the

add_install_client command must NIS maps or populate the NIS+ tables.) Try executing the

be a host in the name service.	add_install_client command again.
le0: No carrier - transceiver cable problem
Reason Error Occurred	How to Fix the Problem
This system is not connected to the	If this is a non-networked system, ignore this message. If this is a networked
network.	system, make sure the Ethernet cabling is attached securely.

No response to BOOTP request. Load failed.

Reason Error Occurred	How to Fix the Problem
The in.dhcpd daemon on the server is	Use the Solstice Host Manager to reconfigure the client.

not running.

The file just loaded does not appear to be executable

Reason Error Occurred	How to Fix the Problem
This message cannot find the proper	Verify that you are using the correct boot command for your system. If
media for booting.	installing from a CD-ROM drive, make sure the Solaris CD is in the CD-ROM drive and that the CD-ROM drive is mounted.

WARNING: getfile: RPC failed: error 5 (RPC Timed out).

Reason Error Occurred........How to Fix the Problem

This error occurs when you have two or Examine the network setup:

more servers on a network responding to an install client's boot request. The install

· Ensure that servers on the network do not have multiple

client connects to the wrong boot server,	/etc/bootparams entries for the install client. If they do, remove
and the installation hangs. The following	duplicate client entries in the /etc/bootparams file on all install and
specific problems may cause this error:	boot servers except the one you want the install client to use.

• · There may be /etc/bootparams files · Ensure that servers on the network do not have multiple /tftpboot or

  on different servers with an entry for../rplboot directory entries for the install client. If they do, remove

  this install client............duplicate client entries from the /tftpboot or /rplboot directories on all install and boot servers except the one you want the install client to use.

• · There may be multiple /tftpboot or /rplpboot directory entries for this

  install client..............(for example, * install_config=), delete it and add it to the /etc/bootparams file on the boot server.

  · If there's a wildcard entry in the name servicebootparams map or table

• · There may be an install client entry in the /etc/bootparams file on a server and an entry in another /etc/bootparams file enabling all systems to access the profile server. Such an entry would look like this: * install_config=profile_server:path

A line like this in the NIS or NIS+ bootparams table would also cause this error.

General Installation Problems

Problem	How to Fix the Problem
The system boots over the network, but from a system other than the specified install server.	On the name server, update the /etc/bootparams entry for the system being installed. The entry should conform to the following syntax: install_system root=boot_server:path install=install_server:path Also, ensure there is only one bootparams entry on the subnet for the install client.
Problem	How to Fix the Problem
OpenWindows is not available to diskless and dataless clients.	The /usr/openwin may be on a separate, mounted file system. This directory is not automatically shared by admintool. The /usr/openwin file system must be manually added to the server's /etc/dfs/dfstab file and the file system must be shared. The entry looks like this: share -F nfs /usr/openwin Also, an explicit mount of the file system must be made in the client's /etc/vfstab file using the following: server_name:/usr/openwin - /usr/openwin nfs - yes -

Problem...............How to Fix the Problem

An installation using the upgrade option 1. Reboot the system from the Solaris CD or from the network.

fails for reasons beyond your control, 2. Choose the upgrade option for installation.

such as a power failure or a network...The Solaris installation program will determine if the system has been

connection failure. The system may be in partially upgraded and will continue the upgrade.

an unbootable state.