Booting a System Over the Network

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

This error occurs when you have two or more servers on a network responding to an install client's boot request. The install client connects to the wrong boot server, and the installation hangs. The following specific reasons may cause this error: 

Reason 1: There may be /etc/bootparams files on different servers with an entry for this install client.

Solution for Reason 1: Make sure that servers on the network do not have multiple /etc/bootparams entries for the install client. If they do, remove duplicate client entries in the /etc/bootparams file on all install and boot servers except the one you want the install client to use.

Reason 2: There may be multiple /tftpboot or /rplboot directory entries for this install client.

Solution for Reason 2: Make sure that servers on the network do not have multiple /tftpboot or /rplboot directory entries for the install client. If they do, remove 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.

Reason 3: 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.

Solution for Reason 3: If there's a wildcard entry in the name service bootparams map or table (for example, * install_config=), delete it and add it to the /etc/bootparams file on the boot server.

No network boot server. Unable to install the system.
 See installation instructions.
 

SPARC based systems only. 

This error occurs on a system that you are attempting to install over the network. The system is not set up properly. 

Make sure you set up the system to install over the network (see "Setting Up Systems to Be Installed Over the Network").

prom_panic: Could not mount filesystem
 

SPARC based systems only. 

This error occurs when you are doing a network installation, but the boot software cannot locate the Solaris installation image (either the Solaris CD or a copy of the Solaris CD on the install server). 

Make sure that the installation software is mounted and shared.  

If installing from the install server's CD-ROM drive, make sure the Solaris CD is inserted in the CD-ROM drive, is mounted, and is shared in the /etc/dfs/dfstab file. If installing from a copy of the Solaris CD on the install server's disk, make sure the directory path to the copy is shared in the /etc/dfs/dfstab file.

Timeout waiting for ARP/RARP packet...
 

SPARC based systems only. 

The client is trying to boot over the network, but it cannot find a system that knows about it. 

Verify the system's host name is in the NIS or NIS+ name service. Also, verify the bootparams search order in the boot server's /etc/nsswitch.conf file.

For example, the following line in the /etc/nsswitch.conf file indicates the software will first look in the NIS maps for bootparams information. If not found there, software will look in the boot server's /etc/bootparams file.

bootparams: nis files

ip: joining multicasts failed on tr0 - will use link layer broadcasts for multicast
 

x86-based systems only. 

You will see this error message when you boot a system with a token ring card. Ethernet multicast and token ring multicast do not work the same way. The driver returns this error message to indicate that an invalid multicast address was given.

Ignore this error message. If multicast doesn't work, IP uses layer broadcasts instead and it won't cause the installation to fail. 

Requesting Internet address for Ethernet_Address
 

x86-based systems only. 

The client is trying to boot over the network, but it cannot find a system that knows about it.  

Verify the system's host name is in the NIS or NIS+ name service. If the system's host name is in the NIS or NIS+ name service, and the system continues to print this error message, try rebooting. 

RPC: Timed out
No bootparams (whoami) server responding; still trying...
 

x86-based systems only. 

The client is trying to boot over the network, but it cannot find a system with an entry in the /etc/bootparams file on the install server.

Use add_install_client on the install server. This will add the proper entry in the /etc/bootparams file, enabling the client to boot over the network.

Still trying to find a RPL server...
 

x86-based systems only. 

The system is trying to boot over the network, but the server is not set up to boot this system. 

On the install server, execute add_install_client for the system to be installed. The add_install_client command sets up an /rplboot directory, which contains the necessary network boot program.

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.

SPARC based systems only. 

After you set up an install server and configure the system to install over the network, the system still does not boot. 

Be sure the tftpd daemon is running on the install server. Type the following command and press Return:

# ps -ef | grep tftpd

If this command does not return a line indicating the tftpd daemon is running, edit the /etc/inetd.conf file and remove the comment (#) character from the following line:

# tftp dgram udp
wait root /usr/sbin/in.tftpd
in.tftpd -s /tftpboot

After making this change, try booting the system again. 

x86-based systems only. 

After setting up an install server and configuring the system to install over the network, the system still does not boot. 

Be sure the tftpd daemon is running on the install server. Type the following command and press Return:

# ps -ef | grep rpld

If this command does not return a line indicating the rpld daemon is running, execute the following command:

# /usr/sbin/rpld

After making this change, try booting the system again.