Sun Microsystems Logo
Products and Services
 
Support and Training
 
 

A  B  C  D  E  F  G  H  I  J  K  L  M  N  O  P  Q  R  S  T  U  V  W  X  Y  Z  
 
Maintenance Commandsslcreate(1M)


NAME

 slcreate - SMCT command to prepare the data for a generic flash archive.

SYNOPSIS

 slcreate -n swl-name -v swl-version [-f] [-c config-dir] [-l logfile] [-V verbosity-level] [-h]

DESCRIPTION

Do not use the SMCT tool with the current patch level of the Foundation Services product.

The slcreate command prepares the data needed to create a generic flash archive.

The slcreate command performs the following functions:

  • Copies the Foundation Services packages and any user application packages into the software repository.

  • Creates a software load in the software load repository. The Solaris JumpStart files are generated for master-eligible and dataless node groups.

    If the software load that is being created already exists, you are prompted to confirm that the current software load should be overwritten or that the operation should be cancelled. If slcreate is run with the -f option, this prompt does not appear.

The slcreate command is run once for each software load because all node groups are processed in one operation.

Data is created from information in several configuration files. Configure the following files before running the slcreate 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.

Optionally, configure the following files before running the slcreate command:

  • network.conf

    The network.conf file describes the network parameters for the target cluster. For more information see the network.conf(4) man page.

  • Solaris JumpStart profile file

    Each Solaris JumpStart profile file defines the set of Solaris operating environment packages to be installed on each master-eligible and dataless node group. There is one profile file for each master-eligible or dataless node group. A profile file, named profile.proto, is provided in the /opt/SUNWcgha/nhsmct/etc/jumpstart/Solaris_version directory. If you want to modify this file, copy this file to the SMCT_DEFAULT_CONFIG_DIR/jumpstart/Solaris_version directory with the file name profile.proto.node-group-name.. Alternatively, you can copy it to the config-dir/jumpstart/Solaris_version/profile.proto.node-group-name where config-dir is specified by the -c option, which is described in the following section.

  • 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.proto, is provided in the /opt/SUNWcgha/nhsmct/etc/jumpstart/ directory. If you want to modify this file, copy this file to the SMCT_DEFAULT_CONFIG_DIR/jumpstart/ directory with the file name sysidcfg.proto or sysidcfg.proto.node-group-name. Alternatively, you can copy it to config-dir/jumpstart/sysidcfg.proto or config-dir/jumpstart/sysidcfg.proto.node-group-name where config-dir is specified by the -c option, which is described in the following section.

  • Solaris JumpStart begin file

    There is one begin file for each master-eligible and dataless node group. A begin file template, named begin.proto, is provided in the /opt/SUNWcgha/nhsmct/etc/jumpstart/ directory. If you want to modify this file, copy this file to the SMCT_DEFAULT_CONFIG_DIR/jumpstart/ directory with the file name begin.proto or begin.proto.node-group-name. Alternatively, you can copy it to config-dir/jumpstart/begin.proto or config-dir/jumpstart/begin.proto.node-group-name where config-dir is specified by the -c option, which is described in the following section.

  • Software configuration files

    Each software configuration file defines additional software and patches that are to be installed for each node group. There may be a software configuration file for each node group. For more information on software configuration files, see the software.conf(4) man page.

OPTIONS

The options that you can use with the slcreate command are:

-n swl-name

Name of the software load to be created. This is an ASCII string.

-v swl-version

Version of the software load to be created. 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.

-f

Removes the software load identified by swl-name and swl-version if it already exists.

-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.

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPEATTRIBUTE VALUE
ArchitectureSPARC
AvailabilitySUNWnhsmc
Interface StabilityEvolving

SEE ALSO

cluster.conf(4), flconfig(1M), flcreate(1M), fldeploy(1M), flinstall(1M), machine.conf(4), nhsmctsetup(1M), network.conf(4), slconfig(1M), sldelete(1M), sldeploy(1M), slexport(1M), software.conf(4)


Netra HAS FS 2.1Go To TopLast Changed September 2004