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

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 Commands | flinstall(1M)

- NAME
- SYNOPSIS
- DESCRIPTION
- OPTIONS
- ATTRIBUTES
- SEE ALSO

## NAME

> flinstall - SMCT command to generate Solaris JumpStart environments for master-eligible and dataless node groups

## SYNOPSIS

> `flinstall -n swl-name -v swl-version -g node-group-name [-j jumpstart-dir] [-e export-dir] [-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 `flinstall` command generates a Solaris JumpStart environment for each master-eligible and dataless node group to be installed on the prototype machine. The `flinstall` command uses the data generated by the `slexport` command.

> The `flinstall` command must be run as a superuser.

> The following configuration files are used by `flinstall` to configure the network between the prototype machine and the installation server. They must be completed before running the `flinstall` command:

> - `install-server.conf`

>   For more information see the `install-server.conf`(4) man page.

> - `master-system.conf`

>   For more information see the `master-system.conf`(4) man page.

## OPTIONS

> The options that you can use with the `flinstall` command are:

> -n swl-name

>   Name of the software load to process. This is an ASCII string.

> -v swl-version

>   Version of the software load to process. This is an ASCII string.

> -g node-group-name

>   Name of the node group for which the Solaris JumpStart environment is created. An environment is created for each node of the node group. The node-group-name is an ASCII string defined in the file `cluster.conf`.

> -j jumpstart-dir

>   Directory where the Solaris JumpStart environment is to be created. This option overrides the Solaris JumpStart directory specified by the SMCT variable `SMCT_JUMPSTART_DIR`, which is defined in the `smct.env` file. For more information on the `smct.env` file, see the `nhsmctsetup`(1M) man page.

> -e export-dir

>   Directory to which the software load data will be exported. This option overrides the export directory specified by the SMCT variable `SMCT_EXPORT_DIR`, which is defined in the `smct.env` file. For more information on the `smct.env` file, see the `nhsmctsetup`(1M) man page.

> -c config-dir

>   Directory where the configuration files are located. This option overrides the configuration directories specified by the SMCT variables `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.

## ATTRIBUTES

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

> ATTRIBUTE TYPE | ATTRIBUTE VALUE
> --- | ---
> Architecture | SPARC
> Availability | SUNWnhsmc
> Interface Stability | Evolving

## SEE ALSO

> `flconfig`(1M), `flcreate`(1M), `fldeploy`(1M), `install-server.conf`(4), `master-system.conf`(4), `nhsmctsetup`(1M), `slconfig`(1M), `slcreate`(1M), `sldelete`(1M), `sldeploy`(1M), `slexport`(1M)

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.