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

| Previous Contents Index Next
2. ### Verifying That the Installation Server Directories Are Shared Before you boot the prototype machine, verify that the installation server directories are mounted on the prototype machine and the cluster. For more information, see To Mount the Installation Server Directories Onto the Prototype Machine and the Cluster. ## Booting the Prototype Machine With the Node Group Software This section describes how to install the node group software on the prototype machine by using the Solaris JumpStart environment and a boot net installation. The node group software is transferred to the prototype machine from the build server by using Solaris JumpStart. The Solaris operating system, the Foundation Services packages and any user applications are installed on the prototype machine. ### To Boot the Prototype Machine With the Node Group Software Log in to the prototype machine. At the `ok` prompt, boot the prototype machine:
       ok> boot net - install
3. The prototype machine performs a Solaris JumpStart from the build server. The prototype machine then installs the node group software, but does not start the Foundation Services. When the prototype machine has been installed with the node group software, a flash archive of the prototype system can be created. ## Verifying That the Node Group Software Has Successfully Installed To verify that the node group software has been successfully installed on the prototype machine, perform the following procedure: ### To Verify That the Node Group Software Has Been Successfully Installed on the Prototype Machine Log in to the prototype machine. Examine the Solaris JumpStart files `/var/sadm/system/logs/finish.log` and `/var/sadm/system/logs/install_log`. Ensure that these logs contain confirmation that the prototype machine was successfully installed with the node group software. Run the `nhadm` tool to check the installation.
       # nhadm check installation
2. ## Creating a Generic Flash Archive When the node group software has been installed on the prototype machine, use the `flcreate` command to create the flash archive. The flash archive is created on the build server using the system image from the prototype machine. The `flcreate` command creates a generic flash archive. The command is started on the build server but runs remotely on the prototype machine by way of a mounted directory. ### To Build a Generic Flash Archive by Using the `flcreate` Command Log in to the build server as superuser. Run the command `flcreate`:
       # flcreate -n SWL1 -v ha_v1 -g master_el -f FLASH_1
This example creates the generic flash archive in the directory smct-config-dir`/flash`. This is the default directory defined by the `SMCT_FLASH_DIR` environment variable. Run the `flcreate` command for each master-eligible node group and dataless node group because each node group is processed individually. Note - If an error occurs when `flcreate` is running, manually unmount the `/mnt/flash` directory from the prototype machine and run the `flcreate` command again. For more information on using the `flcreate` command, see the `flcreate`(1M) man page.
Previous Contents Index Next

Copyright 1994-2004 Sun Microsystems