To Configure the Solaris JumpStart sysidcfg.proto
File for the Prototype Machine
The system identification configuration file
contains information for the target cluster such as name service, timezone
and superuser password. Note that the Foundation Services default superuser password
is sunrules.
Log in to the build server.
Copy the sysidcfg.proto template from /opt/SUNWcgha/nhsmct/etc/jumpstart/ to one of the following directories:
Modify the file sysidcfg.proto to suit your local
environment. You can configure the following parameters:
system_locale
timezone
terminal
root_password
monitor
keyboard
display
pointer
Note - Although the template files for rules.proto
and finish.proto are provided, do not configure these
files. The template for the begin.proto file is supported
by the SMCT. If required, modify this file. For more information, see the
Solaris JumpStart documentation.
Creating the Software Load
This section describes how to create
the software load by using the slcreate command. The slcreate command does the following:
Compiles the cluster configuration files
Copies
the Foundation Services packages and any user applications into the software repository
Generates the Solaris JumpStart configuration files for master-eligible
node groups and dataless node groups
Creates a software load in the software load repository
To Create the Software Load by Using the slcreate
Command
Log in to the build server.
Run the command slcreate: $ slcreate -n SWL1 -v ha_v1
|
The slcreate command is run once for each software
load because all node groups are processed in one operation. If slcreate stops due to an error, you can run the command again.
The slcreate command automatically restarts from the stage
when the error occurred.
If a package in a software load already exists in the software repository,
it is not overwritten. Several versions of the same package can be stored
in the software repository.
After the slcreate command has been run, you must
restart the entire configuration process and deployment process to add or
remove user applications.
Note - To add user applications to your software load, declare them in
the software configuration files before you run slcreate.
Software configuration files are described in Creating a Software Configuration File for a Node Group.
The Solaris operating system can be modified according to the rules described in To Configure the Solaris JumpStart profile File
for the Prototype Machine.
For more information, see the slcreate(1M) man page.
Copying the Software Load to an Export Directory
When the slcreate command has been run successfully, use the slexport command to copy the software load into an export directory.
The export directory
is used by the flinstall and flcreate
commands to create the generic flash archives.
To Copy the Software Load to the Export Directory by Using the slexport Command
Log in to the build server.
Run the slexport command: $ slexport -n SWL1 -v ha_v1
|
This command exports data from the software load SWL1,
to the directory SMCT_EXPORT_DIR/SWL1@ha_v1.
The data is exported to the directory or in the directory specified
by the -e option.
If your installation server is a different machine than the build server,
use the remote option, -r, of the slexport
command. Then, copy the exported data to the installation server.
For more information, see the slexport(1M) man page.
Creating the Solaris JumpStart Environment for the Prototype Machine
When the software load has been copied to the export
directory, create the Solaris JumpStart environment for the prototype machine
by using the flinstall command.
The flinstall command generates a Solaris JumpStart
environment for each master-eligible node group and dataless node group to
be installed on the prototype machine. The command uses data from the export
directory.
Note - Make sure that you have performed the necessary steps to connect
the prototype machine to the build server. For more information, see the Netra High Availability Suite Foundation Services 2.1 6/03 Hardware Guide.
To Create the Solaris JumpStart Environment for the Prototype Machine
by Using the flinstall Command
Log in to the build server as superuser.
Run the command flinstall: # flinstall -n SWL1 -v ha_v1 -g master_el
|
The above example creates the Solaris JumpStart environment configuration
files in the directory SMCT_JUMPSTART_DIR/jumpstart:
Run the flinstall for each master-eligible node group
and dataless node group because each node group is processed individually.
For more information on using the flinstall command,
see the flinstall(1M) man page.
When the flinstall command has been run, the Solaris
JumpStart environment is created to enable the Solaris JumpStart mechanism
on the prototype machine.
|