![]() |
|||
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
| ||||||||||||||
Installing the Foundation ServicesAfter you have prepared the installation environment and installed and configured the nhinstall tool on the installation server, you are ready to install the software on the nodes of the cluster. The entire installation takes approximately one and a half hours.
|
# cd /opt/SUNWcgha/sbin # ./nhinstall -r config-file-directory -l logfile |
For details, see the nhinstall(1M) man page.
The nhinstall tool prepares the environment by using the Solaris JumpStart utility.
Note - If the Solaris JumpStart procedure stops, the utility might not restart. The cause can be the presence of the /tmp/.install_client.lck file, which prevents two Solaris JumpStart commands from being executed simultaneously. To restart the Solaris JumpStart, make sure that there are no other Solaris JumpStart processes running, and then delete this lock file.
After the Solaris JumpStart environment has been prepared, the following instructions are displayed by the nhinstall tool:
On the console of each master-eligible node: 1. Get the ok prompt. 2. At the prompt, type: ok> boot net - install Answer 'y' after the command has been entered on both master-eligible nodes: |
Follow these instructions by performing the procedures in the remainder of this section.
Go to the console window of the first master-eligible node.
The first master eligible-node is the first node defined in the cluster_definition.conf file with the NODE definition. In the example used in this document, the first master-eligible node is node10.
Get the ok prompt.
To get the telnet prompt, press Control-].
# Control-] |
To get the ok prompt, type send brk at the telnet prompt.
telnet> send brk Type 'go' to resume ok> |
Set the boot variables by using the setenv command at the ok prompt.
Configure the processors to use local Ethernet (MAC) addresses.
ok> setenv local-mac-address? true |
Configure the processors to retry booting when automatic boot fails.
ok> setenv auto-boot-retry? true |
Repeat Step 1 through Step 3 for the second master-eligible node.
The second master-eligible node is the second node defined with the NODE parameter in the cluster_definition.conf file. In the example used in this document, the second master-eligible node is node20.
Start the installation of the Solaris operating system on the first master-eligible node.
ok> boot net - install |
Where net is the device alias.
At the same time, start the installation of the Solaris operating system on the second master-eligible node.
ok> boot net - install |
After you type the command to boot the master-eligible nodes, type y at the nhinstall prompt in the installation server console.
Answer 'y' after the command has been entered on both master-eligible nodes: y |
The nhinstall tool checks the version of the Solaris operating system that has been installed. The nhinstall tool also checks whether the Foundation Services are already installed on the master-eligible nodes. If the Foundation Services is already installed, the nhinstall tool exits and displays an error message. The nhinstall tool then installs the Foundation Services on the nodes of the cluster.
The following instructions are displayed by the nhinstall tool in the console of the installation server:
Setup the eeprom boot parameters on your diskless nodes: At the prompt, type: ok> setenv local-mac-address? true ok> setenv auto-boot-retry? true ok> setenv boot-device net:dhcp,,,,,5 net2:dhcp,,,,,5 ok> setenv diag-switch? false You can now boot your diskless nodes. |
Configure the boot parameters for the diskless node. If you are installing more than one diskless node, repeat the following steps for each diskless node.
Get the ok prompt on the diskless node.
Execute these commands at the ok prompt on the diskless node.
ok> setenv local-mac-address? true ok> setenv auto-boot-retry? true ok> setenv boot-device net:dhcp,,,,,5 net2:dhcp,,,,,5 ok> setenv diag-switch? false |
Boot the diskless node.
ok> reset |
While you are booting the node, the following information is displayed by the nhinstall tool:
17:32:21 Waiting for the disks of the master-eligible nodes to synchronize. 17:32:21 - Partitions to be replicated: 17:32:22 . md/rdsk/d4 (2099 MB) 17:32:22 . md/rdsk/d3 (2099 MB) 0%....10%....20%....30%....40%....50%....60%....70%....80%....90%....100% 17:44:18 Your cluster is ready. |
When the cluster is first started, there is a period during which the master node and vice-master node synchronize their disks. This output describes the status of the initial synchronization of the disks of master node and the vice-master node. After the diskless node is rebooted and after the synchronization is complete, your cluster is ready.
Most warnings displayed by the nhinstall tool require no action. When the nhinstall tool is launched, the tool parses the configuration files and stops if the tool encounters errors in the files. After you correct the errors, you can continue the installation from the point at which the error occurred.
To restart the nhinstall tool, use the nhinstall command with the same options that you used to start the tool.
# cd /opt/SUNWcgha/sbin # ./nhinstall -r config_file_directory -l logfile |
If you modify the configuration files to correct an error, the nhinstall tool displays a warning that the configuration has changed. The nhinstall tool then prompts you to reset the installation. If you do not want to reset the installation, type no at the prompt.
![]() ![]() |