C H A P T E R 2 |
For information about how to resolve problems during installation of the Solaris Operating System and the Netra HA Suite, see the following sections. These sections include information about how to resolve problems related to Solaris JumpStart.
This section describes how to recover from an error that is not related to the nhinstall tool.
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. For example, for a Solaris installation:
Beginning system identification... Searching for configuration file(s)... Using sysid configuration file 10.101.1.253:/export/nhjumpstart/101/10/sysidcfg Search complete. |
IP-Config: Got DHCP answer from 10.101.1.253, my address is \ 10.101.1.10 IP-Config: Complete: device=eth0, addr=10.101.1.10, mask=255.255.255.0, \ gw=10.101.1.253, host=cp3020-1, domain=, nis-domain=(none), bootserver=10.101.1.253, rootserver=10.101.1.253, \ rootpath=/dist/mvista/CGE_4.0/target_tdp<7>eth0: no IPv6 \ routers present |
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.
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:
If the boot server is running the Solaris OS, access the console of the wrong boot server as follows:
If the boot server is running Linux, access the console of the wrong boot server as follows:
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.
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 Netra HA Suite 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.
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.
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 |
# /opt/sun/sbin/nhinstall -r config_file_directory -l logfile |
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 3.0 1/08 Foundation Services Manual Installation Guide for the Solaris OS.
If the nhinstall tool stops again, repeat Step 1 through Step 6 until the tool completes successfully.
If you cannot resolve this problem, contact your customer support center.
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 4.
If they are not, do the following:
a. Configure your installation server as described in the Netra High Availability Suite 3.0 1/08 Foundation Services Getting Started Guide.
# /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.
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 7.
If a router connects the installation server and the master-eligible node, do the following:
b. Reconfigure your hardware as described in the Netra High Availability Suite 3.0 1/08 Foundation Services Getting Started Guide.
# /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.
Copyright © 2008, Sun Microsystems, Inc. All rights reserved.