In general, this is because the JumpStart client can't obtain RARP service from a boot server.

Check the following:1. cable or other physical connection problem? does the client use the right interface? (Check OBP NIC aliase, etc.)2. is in.rarpd daemon running on the boot server?3. does /etc/ethers and /etc/hosts or NIS have the correct entry for client's MAC,IP,hostname?

b. Resolving TFTP problemsIf the client shows the "Timeout waiting for ARP/RARP packet" ONLY once and stops,it indicates the JumpStart server may not be able to obtain TFTP services from a boot server.

Usually, this errory message indicates that there is no entry for the client in/tftpboot/ directory (inetboot.hex_ip).

If the client passes RARP and TFTP, but stops booting after displaying numeric value,such as 23e00, the client may not be able to obtain BOOTPARAMS information from boot server.

Solution:c1. Check if the boot server's /etc/bootparams file has an entry for the clientc2. Check if the daemon rpc.bootparamd is running on the server.If not,Re-run add_install_client script to add client in /etc/bootparams file and restartrpc.bootparams daemon.

Problems in the JumpStart client identification process usually relate to errors insysidcfg file (e.g. no id info) or from a name service. If client cannot obtain aresponse from a server for any identification item, the client interrupts the autoidentification process and asks from information.

check sysidcfg file if client stops and asks for any of the following info:IPv6 networkingnetmaskIP address of the default routersecuirty policyname servicetimezonesystem localetime server inforoot password

If the JumpStart server uses NIS for some of above info, please check NIS.

Resolving Name Service Problems

If you use a name service, and the JumpStart client interrupts the identification process to obtain identification items other than the following, check the corresponding map or table information in the name service, and correct the problem you find:

* Will the client implement IPv6 protocols?* What is the IP address of the default router?* What security policy will the client implement?* What is the root log in password?

The previous items can only be provided using the sysidcfg file.

You can use the sysidcfg file to provide information that a name service could otherwise provide. You must verify the content of the sysidcfg file or any information that it provides. Information provided in the sysidcfg file overrides information in name services.

Solution:verify /etc/dfs/dfstab on the boot has entries to share required directories;check /etc/bootparams file to ensure entry is correct for the client, path for root is right.check nfs is running on the installation server, if not manually start it.