 |
|
|
NAME
sldeploy - SMCT command to generate
the Foundation Services and Solaris operating environment configuration files for a software load
SYNOPSIS
sldeploy -n swl-name -v swl-version [-c config-dir] [-l logfile] [-V verbosity-level] [-h]
Do not use the SMCT tool with the current patch level of the Foundation Services
product.
The sldeploy command generates the Foundation Services and Solaris operating environment
configuration files associated to a software load.
The configuration files generated for the Foundation Services are used to configure
services such as Reliable NFS and the Cluster Membership Manager (CMM). The sldeploy command also generates the nhfs.conf
file.
Configure the following files before running the sldeploy
command:
-
cluster.conf
The cluster.conf file contains a logical view of
the cluster in terms of nodes, node groups, and domains. For more information
see the cluster.conf(4) man page.
-
machine.conf
The machine.conf file describes the cluster in terms
of hardware elements, disk layout, and file system. For more information see
the machine.conf(4) man page.
-
network.conf
The network.conf file describes the network parameters
for the target cluster. For more information see the network.conf(4) man page.
Optionally, configure the following files before running the sldeploy command:
-
Solaris JumpStart sysidcfg file
The Solaris JumpStart system identification configuration file contains
information for the target cluster such as name service, timezone and superuser
password. There is one sysidcfg file for each master-eligible
and dataless node group. A sysidcfg file template, named sysidcfg.cluster, is provided in the /opt/SUNWcgha/nhsmct/etc/jumpstart directory. It must be copied to the SMCT_DEFAULT_CONFIG_DIR/jumpstart directory with the file name sysidcfg.cluster
or sysidcfg.cluster.node-group-name.
-
Solaris JumpStart begin file
There is one begin file for each master-eligible
and dataless node group. A begin file template, named begin.cluster, is provided in /opt/SUNWcgha/nhsmct/etc/jumpstart. If you want to modify this file, copy this file to the SMCT_DEFAULT_CONFIG_DIR/jumpstart directory with the file name begin.cluster or begin.cluster.node-group-name. Alternatively, you can copy this file to config-dir/jumpstart/begin.cluster or config-dir/jumpstart/begin.cluster.node-group-name where config-dir
is specified by the -c option, which is described in the following
section.
The options that you can use with the sldeploy command
are:
- -n swl-name
-
Name of the software load to be deployed. This is an ASCII
string.
- -v swl-version
-
Version of the software load to be deployed. This is an ASCII
string.
- -c config-dir
-
Directory where the configuration files are located. This
option overrides the configuration directory specified by the SMCT variable SMCT_DEFAULT_CONFIG_DIR, which is defined in the smct.env file. For more information on the smct.env
file, see the nhsmctsetup(1M) man page.
- -l log-file
-
Name of the file that is sent information and error messages.
By default these messages are displayed on the console.
- -V verbose-level
-
Verbosity level. Values are 1, 2, or 3, where 1 is minimal
traces and 3 is detailed information.
- -h
-
Displays help
information.
See attributes(5)
for descriptions of the following attributes:
ATTRIBUTE TYPE | ATTRIBUTE VALUE |
Architecture | SPARC |
Availability | SUNWnhsmc |
Interface Stability | Evolving |
cluster.conf(4), flconfig(1M), flcreate(1M), fldeploy(1M), flinstall(1M), machine.conf(4), network.conf(4), nhsmctsetup(1M), slconfig(1M), slcreate(1M), sldelete(1M), slexport(1M), nhfs.conf(4)
Netra HAS FS 2.1 | Go To Top | Last Changed September 2004 |
Company Info
|
Contact
|
Copyright 2004 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
|