sun.com | docs.sun.com | How To Buy | My Sun | Worldwide Sites |  |

| Previous Contents Index Next
1. Chapter 3 # Recovering From Installation Problems For information about how to resolve problems during installation of the Solaris operating system and the Foundation Services, see the following sections. These sections include information about how to resolve problems related to Solaris JumpStart™. Recovering From General Installation Problems Recovering From `nhinstall` Problems ## Recovering From General Installation Problems This section describes how to recover from an error that is not related to the `nhinstall` tool. ### Incorrect Software Is Installed on the Cluster Nodes If incorrect software is installed on the nodes when you use the `nhinstall` tool, perform the following procedure. #### To Investigate Why Incorrect Software Is Installed on the Cluster Nodes Search the console of the installation server for the IP address of the boot server.
       ok> boot net - install
3. The IP address of the boot server in this example is the class C address `10.101.1.253`. Alternatively, use the name of the boot server to find the boot server IP address. Find the IP address of your installation server. Compare the address of the boot server with that of the installation server. If the addresses are not the same, your node is being booted by the wrong machine. Perform the following steps: Access the console of the boot server. In the `/etc/ethers` file, delete the MAC address of any nodes in your cluster. In the `/etc/bootparams` file, delete the node parameters of any nodes in your cluster. Restart the installation. If you have not solved this problem, it is possibly because you have two installation servers for this cluster. Confirm the presence of a second installation server using the `/usr/sbin/bpgetfile` command on a machine running on the same local network as your installation server. If the problem persists, contact your customer support center. ## Recovering From `nhinstall` Problems This section describes how to recover from error scenarios that can occur during installation using the `nhinstall` tool. The `nhinstall` tool installs the Solaris operating system and the Foundation Services on a cluster. If the `nhinstall` tool encounters an error, it issues a message and stops. When the `nhinstall` tool encounters an error, it does not continue to search for other errors. You must fix the error and relaunch the `nhinstall` tool from the point at which it failed. If the `nhinstall` tool encounters another error, it stops again. ### The `nhinstall` Tool Stops During Installation If the `nhinstall` tool stops during the installation of a node, perform the following procedure. #### To Investigate Why the `nhinstall` Tool Stops During Installation Identify the problem by using the error message displayed on the installation server. Possible problems are: `local` command failure on the installation server `rsh` command failure due to a connection or permission problem `remote` command failure Correct the problem. If the `nhinstall` tool stops due a problem with Solaris JumpStart, see Solaris JumpStart Installation Fails During `nhinstall`Installation. Restart the `nhinstall` tool with the same options that you used to launch it the first time:
       # /opt/SUNWcgha/sbin/nhinstall -r config_file_directory -l logfile
1. 2. The `nhinstall` tool resumes from the point at which it stopped. If you have modified the `cluster_definition.conf` file to correct the error, the `nhinstall` tool displays a warning that the configuration has changed. If the change that you made to the file makes the cluster incoherent, you must reset the installation for a new installation. For information, see the Netra High Availability Suite Foundation Services 2.1 6/03 Custom Installation Guide. If the `nhinstall` tool stops again, repeat Step 1 through Step 3 until the tool completes successfully. If you cannot resolve this problem, contact your customer support center. ### Solaris JumpStart Installation Fails During `nhinstall` Installation If the Solaris JumpStart installation of a master-eligible node fails, perform the following procedure. #### To Investigate Why the JumpStart Fails During `nhinstall` Installation Confirm that the installation server and the first network interface of the master-eligible node are connected to the same switch. If they are, go to Step 2. If they are not, do the following: Configure your installation server as described in the Netra High Availability Suite Foundation Services 2.1 6/03 Hardware Guide. Restart the installation.
          # /opt/SUNWcgha/sbin/nhinstall -r config_file_directory -l logfile
2. 3. If the Solaris JumpStart software does not restart, delete the `/tmp/.install_client.lck` file. Confirm that a router is not connected between the installation server and the master-eligible node. If no router connects the installation server and the master-eligible node, go to Step 3. If a router connects the installation server and the master-eligible node, do the following: Remove the router. Reconfigure your hardware as described in the Netra High Availability Suite Foundation Services 2.1 6/03 Hardware Guide. Restart the installation:
          # /opt/SUNWcgha/sbin/nhinstall -r config_file_directory -l logfile
If the Solaris JumpStart software does not restart, delete the `/tmp/.install_client.lck` file. If you cannot resolve this problem, contact your customer support center.
Previous Contents Index Next

Copyright 1994-2004 Sun Microsystems