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

File Formats | addon.conf(4)

- NAME
- SYNOPSIS
- DESCRIPTION
- EXAMPLES
- ATTRIBUTES
- SEE ALSO

## NAME

> addon.conf - `nhinstall` configuration file to install additional patches and packages

## SYNOPSIS

> `addon.conf`

## DESCRIPTION

> You can configure the `nhinstall` tool to install additional patches and packages by modifying the `addon.conf` file.

> It is not mandatory to configure this file. If this file is not configured or not present in the directory containing the configuration files, the `nhinstall` tool assumes there are no additional patches or packages to be installed. This file can be used to upgrade the Foundation Services at a later stage.

> The templates for the configuration files are contained in the `/opt/SUNWcgha/config.standard` directory with `.template` extensions. Templates for the `addon.conf` file are specific to the hardware platform type. Copy the necessary `addon.conf` template files to a local directory on the installation server as follows:

> >     # mkdir config-file-directory
> >     # export NHOME=/opt/SUNWcgha/config.standard
> >     # cp $NHOME/addon.conf.*.template config-file-directory

> Note – All the configuration files must be in the same local directory on the installation server.

> The `addon.conf` file format is ASCII. Comment lines begin with the comment mark (#). Parameters consist of a keyword followed by an equals (=) sign followed by the parameter value, of the form:

> >     Keyword=Value

> Within the Value, you can use a slash at the end of a line to indicate that the Value is continued on the following line. You can also add comments within a Value. For example:

> >     PATCH=123456-01 \ #This is the patch number
> >     NHAS -  S USR_SPECIFIC  Y Y \ #This is specific to Foundation Services

> Each additional patch or package to be installed must be specified in `addon.conf` by using the following parameters:

> >     PATCH=reference dir sub_dir phase scope men diskless [ - method ]

> >     PACKAGE=reference dir sub_dir phase scope men diskless

> reference

>   The patch number or the package name.

> dir

>   The directory exported from the installation server and mounted on remote nodes.

>   To install additional patches or packages from the Solaris distribution on the installation server after the Solaris operating system is installed on the nodes, specify the dir as `SOLARIS` and the phase as `S`. The additional patches or packages must be in the directory specified for `SOLARIS_DIR` in `env_installation.conf`.

>   To install additional Foundation Services patches or packages after the installation of the Foundation Services, specify the dir as `NHAS` and the phase as `F`. The additional patch or package must be in the directory specified for `NHAS2_PRODUCT_DIR` in `env_installation.conf`.

> sub_dir

>   The sub_dir directory is a subdirectory of dir containing the patches or packages. If there is no subdirectory and the package or patch is located in the exported directory, specify "-" for the sub_dir parameter.

>   If you define `NHAS` as the value for the dir parameter, the "-" takes one of the following values:

>   - `NetraHAS2.1/Packages` for a package

>   - `NetraHAS2.1/Patches` for a patch

>   If you define `SOLARIS` as the value for the dir parameter, the "-" takes one of the following values:

>   - `Solaris_x/Product` for a package

>   - `Solaris_x/Patches` for a patch

>   Where x is `8` or `9`, depending on the Solaris version installed.

> phase

>   Indicates the phase when the patch or package must be installed. The phases are:

>   `I`

>     The patch or package is installed during the installation of the Solaris operating system on the master-eligible nodes, and after the `smosservices add` command has run for diskless nodes.

>   `S`

>     The patch or package is installed after the Solaris operating system is installed on the master-eligible nodes, and after the `smdiskless add` command has run for diskless nodes.

>   `F`

>     The patch or package is installed after the Foundation Services are installed for both the master-eligible nodes and the diskless nodes.

> scope

>   Indicates where the package or patch will be installed.

>   `LOCAL`

>     Install the package or patch on the root partition of master-eligible node or the diskless node. For diskless nodes, the root partition is `/export/root/`diskless-node-name on the master node.

>   `USR_SPECIFIC`

>     Install the package or patch in the node's `/usr` directory. For diskless nodes, the `/usr` directory is the `/export/Solaris_x/usr_sparc_all` directory on the master-eligible node. The `basedir` is the default.

>   `USR_SOLARIS`

>     Install the package or patch in the node's `/usr` directory. For diskless nodes, the `/usr` directory is the `/export/Solaris_x` directory on the master-eligible node. The `basedir` is `/usr_sparc.all`.

>   `CLONE_OPT`

>     Install the package or patch in the clone area for diskless nodes. The `/usr` directory is `/export/root/clone/Solaris_x/sun4u`. The `basedir` is `/opt`.

>   `SHARED`

>     Install the package or patch in the shared package directory, that is, `/SUNWcgha/local/export/services`

>     If you specify `SHARED`, the package or patch cannot be installed after the Solaris installation on master-eligible nodes because the shared directory does not exist yet.

>   Note – The `USR_SPECIFIC`, `USR_SOLARIS`, and `CLONE_OPT` parameters are replaced by `LOCAL` if you are installing the software for a master-eligible node.
> men

>   Indicates if a patch or package is to be installed on the master-eligible nodes.

>   Options are `Y` or `N`.

>   This parameter is ignored if scope is set to `SHARED`.

> diskless

>   Indicates if a patch or package is to be installed for a diskless node.

>   Options are `Y` or `N`.

>   This parameter is ignored if scope is set to `SHARED`.

> method

>   Indicates the method used for patch installation. The method parameter is optional. If this parameter is not present, the default method of adding patches is either `patchadd` or `smosservice patch`. If the method parameter is present, the default method used depends on the value of the PATCH_WITH_SMOSSERVICE parameter. The possible methods of patch installation are as follows:

>   `DEFAULT`

>     Install patches using the default method

>   `STANDARD`

>     Install patches using `patchadd`

>   `SMOSSERVICE`

>     Install patches using `smosservice`. Note that you cannot use this method on Solaris 9.

>   `PATCH_WITH_PKGADD`

>     Install patch using `pkgadd`. This method is reserved for special patches.

## EXAMPLES

> This section provides examples of how to use the `addon.conf` file.

> Example 1. Sample addon.conf File

> > >     # A patch located on the standard NHAS distribution about
> > >     # packages located on /usr (installed after Solaris installation)
> > >     PATCH=123456-01   NHAS -  S USR_SPECIFIC  Y Y

> > >     # A patch about shared packages located on a user's directory
> > >     # and installed after the Foundation Services installation
> > >     PATCH=789012-03 /mydir nhas2/mypatchdir F SHARED

> > >     # A package located on the standard Solaris distribution and
> > >     # installed on the root file system only on the diskless nodes.
> > >     PACKAGE=SUNWkvm.u  SOLARIS - S LOCAL N Y

> > >     # A package located on a user's directory and installed
> > >     # only on the master-eligible nodes after the Solaris installation.
> > >     PACKAGE=SUNWsiox.u   /export  Solaris/package S LOCAL Y N

> Example 2. A `PATCH` entry that uses the dir and sub_dir values

> > >     PATCH=123456-01 /export patches/Nhas F LOCAL Y Y

> > Where:

> > - The patch 123456-01 is located at `/export/patches/Nhas`.

> > - The `/export` directory is the directory that will be shared.

> > The `nhinstall` tool executes the following commands:

> > - On the installation server:

> >   >     # share -F nfs /export

> > - On remote nodes:

> >   >     # mount server_ip:/export /mnt
> >   >     # patchadd -r /mnt/patches/Nhas 123456-01

> Example 3. Example 3

> > To export `/export/patches/Nhas`, the entry will be:

> > >     PATCH=123456-01 /export/patches/Nhas - S LOCAL Y Y

> > Where "`-`" means that the mount point is where the patch directory is located and there is no subdirectory.

## ATTRIBUTES

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

> ATTRIBUTE TYPE | ATTRIBUTE VALUE
> --- | ---
> Architecture | SPARC
> Availability | SUNWnhins

## SEE ALSO

> `env_installation.conf`(4), `cluster_definition.conf`(4), `nhinstall`(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.