test

Sun Management Center 4.0 Installation and Configuration Guide

Installing Sun Management Center Using es-inst

This section describes how to install the product on Solaris and Linux systems using the es-inst script. During installation, you may install the console, server, and agent layers either separately or in combination. You may also choose specific add-on products for the features that you want to install. When the install process is completed, the setup script es-setup is run, enabling you to set up the base and add-on components.

Note –

On Linux, agent and console layers can be installed. Remote installation is not possible using es-inst.

es-inst Options

The syntax for the es-inst command is:

es-inst [-S dir][-T dir][-R dir][-C file][-A file][avh]

The following table describes the es-inst parameters.

Table B–2 es-inst Options

Option 

Modifying Options 

Description 

-A

filename

Perform an automated installation using the specified configuration file filename. This option is ignored if —C is also used.

-C

filename

Specify a file in which to store the configuration details entered during installation and setup. The file can be used for subsequent automated installation. 

-R

/path/remote-machine

Install Sun Management Center on a remote machine that is network file system read/write accessible from the root login account on the local machine.

See Installing on a Remote Machine.

-S

directory

Specify the source directory. 

-T

directory

Specify the target directory. 

-a

 

Perform an agent-only product installation. See To Install or Update Agents From an Agent-Update Image Using agent-update.bin.

-h

 

List the es-inst options.

-v

 

Perform an installation using verbose full log mode. 

Hands-Free Installation

Sun Management Center 4.0 supports hands-free, also known as Boom, installation. In a hands-free installation, the installer does not prompt you for any inputs while installing the product. You can install both the server and agent components using the es-inst -B command. Two response files, default-agent-install.ascii and default-server-install.ascii, contain the default parameter values that are required for a hands-free installation. The default-agent-install.ascii file has default values for an agent installation and the default-server-install.ascii file has default values for a server installation.

Assuming that you are installing Sun Management Center from a media image directory on your network, the response files are located in the /net/machine/disk1/sbin directory. You can make a copy of the response files and modify the parameter values, if required. To run the hands-free installation, do the following:

  1. Log in as root.

  2. Run the command

    es-inst -B filename

where

For example, es-inst -B default-agent-install.ascii

Note –

Hands-free installation is supported only on the Solaris platform.

Installing on a Local Machine

This installation procedure assumes you are installing Sun Management Center from a image directory on your network. See Creating Installation DVD Images for further information. This procedure also assumes that you have not specified any of the es-inst parameters.

ProcedureTo Install Using es-inst

  1. Log in as root on the machine where you want to install Sun Management Center.

  2. In the /etc/nsswitch.conf file, ensure that the group entry has files as the first token.


    group: files nis

  3. Go to the Sun Management Center installation disk 1 sbin directory.

    • If you are installing from disk, and then go to the /DiskMountDir/sbin directory.

      During the installation process, you might be prompted to change the disks depending on your selections.

    • If you are installing from a image, go to the /image-dir/disk1/sbin directory, where image-dir is the directory either where you copied the installation images, or where you downloaded and untarred the installation image from the Web.

  4. Run the es-inst installation script:


    #./es-inst

    • If a prior version of Sun Management Center is not installed on the system, you are prompted for the target directory. Go to Step 7.

    • If a prior version of Sun Management Center is installed on the system, you are asked whether you want to uninstall the previous Sun Management Center version.

  5. Uninstall the previous version.

    You are asked whether you want to uninstall the previous version. You cannot install Sun Management Center 4.0 until the previous version is uninstalled.

    • Type n or q if you do not want to uninstall the previous version. You are returned to the system prompt.

    • Type y to uninstall the previous version.

      You are asked whether you want to migrate the data from the previous installation of Sun Management Center.

  6. Migrate previous version data.

    The administrative domain configuration data, custom alarm settings, and scripts from your previous installation of Sun Management Center can be saved and applied to the new installation of Sun Management Center 4.0. The data is located in /var/opt/SUNWsymon.

    • Type y to save and migrate the data from the previous version of Sun Management Center.

      The installation process stops any Sun Management Center processes that are running. The data is saved to /var/opt/SUNWsymon.bak.

    • Type n to discard all data from the previous version of Sun Management Center.

      The installation script warns you to move any custom scripts that you want to save.

      Caution – Caution –

      If you have custom scripts stored in any directory under /var/opt/SUNWsymon that you want to use in Sun Management Center 4.0, move them to an alternate location before going to Step 5.

    The installation process then runs the previous Sun Management Center version's es-uninst script to uninstall the previous version.

    Note –

    The uninstall process can take anywhere from a few minutes to half an hour, depending on the products and add-ons installed in the previous version.

    During the uninstall process, you might see messages that state package removal failed. You can ignore these messages. Any package that is not removed at first is removed later by the uninstall process.

    When the uninstall process completes, you are prompted for the directory in which to install Sun Management Center.

  7. Type the name of the directory in which to install Sun Management Center

    The default location is /opt.

    Sun Management Center software can be installed in any location on your system where the minimum required disk space is available. Press Return to accept the default location /opt or, if you want to install to a directory other than /opt, type the directory name.

    Tip –

    The command df -ak lists the used space and free space for each file system on the machine.

  8. Select the Sun Management Center component layers that you want to install.

    You are asked to reply y or n to each layer. For example:


        Select the Sun Management Center Architectural Component Layers:
    3 Layer(s) are available for your selection:
    Do you want to install Server Layer Components ? [y|n|q]  y 
        The Server Layer has been selected for install.
        The Sun Management Center Agent will be installed automatically.
    Do you want to install Console Layer Components ? [y|n|q]  y
    Note –

    If you select Server, Agent is automatically selected.

    • If you selected Server, or selected Server, Agent, and Console, the Server Layer Binary Code License is displayed. Go to Step 9.

    • If you selected Console, or Agent and Console, the Select Language Support message appears. Go to Step 10.

    • If you selected Agent only, the Select Add-on Products message appears. Go to Step 11.

  9. Review the Server Layer Binary Code License.

    Read the Server Layer Binary Code License carefully. To continue the installation, you must agree to the terms of the license.

    Type y to agree to the license and continue, or type n to exit the installation.

    • If a valid JDK version is not installed, you are informed which version is needed. The installation process then exits to the system prompt.

    • If you accept the license, the installation process checks for a valid JDK version. If a valid JDK version is installed, you are prompted to select additional language support.

    Note –

    The Sun Management Center Web server and online help are installed with the server layer.

  10. If you want to install the product in additional languages, select the appropriate languages.

    • If you want to install additional language support, type y.

      You are asked to reply y or n to each language.

    • If you do not want to install additional language support, type n.

    When you have completed language selection, the install process checks for add-on products.

  11. Select the Sun Management Center add-on products.

    The install process lists each add-on product, and asks if you want to install the product. Type y to select the product for installation, or type n if you do not want to install the product.

    • Some add-ons are platform-specific. For information about each add-on, refer to the platform supplements provided with the Sun Management Center release kit, and to the Sun Management Center Web site at http://www.sun.com/solaris/sunmanagementcenter/.

    • Some add-ons have optional components. If optional add-on components are available, the components are listed sequentially. Type y to select the optional component for installation, or type n if you do not want to install the optional component.

    If you did not select any add-on products, you are asked whether you want to proceed. Type y to continue. The install process checks disk space. Go to Step 14.

    If you selected any add-ons, your selections are listed.

  12. Review your selections.

    Type y to continue, or type n to repeat the selection process.

    • If you selected only the agent, or agent and console during component selection, and selected any add-on products, the installation process checks disk space. Go to Step 14.

    • If you selected the server during component selection, and selected any of the following add-on products, the Add-on Products Binary Code License is displayed. Go to Step 13.

      • Advanced System Monitoring

      • Performance Reporting Manager

      • Service Availability Manager

      • Solaris Container Manager

      • System Reliability Manager

    • If you did not select any of the above add-on products but did select other add-on products, the installation process checks disk space. Go to Step 14.

  13. Review the Add-on Products Binary License.

    Read the Add-on Products Binary Code License carefully. To continue the installation, you must agree to the terms of the license.

    Type y to agree to the license or n to exit the installation.

    If you typed y to agree to the license and did not select additional add-on components, the installation process checks disk space.

  14. Check disk space.

    The installation process checks whether there is enough disk space to install the products that you selected.

    • If there is enough disk space, the products that you selected are installed.

      Note –

      The installation process can take from a few minutes to half an hour or more, depending on the products selected.

      When the installation process completes, a list of installed products is displayed. You are asked whether you want to set up the Sun Management Center components. Go to Step 16.

    • If there is not enough disk space, you are asked to provide an alternate file system. The amount of space available and the amount of space that is needed are displayed.

  15. Provide the name of an alternate file system with enough disk space.

    At the prompt requesting a different file system, type the name of a file system and directory that has enough free space.

    Tip –

    In a terminal window on the machine where you are installing Sun Management Center, type df -ak to list the amount of used and free space for each file system on the machine.

    The installation process checks disk space again. If there is enough disk space, the products that you selected are installed.

    Note –

    The installation process can take from a few minutes to half an hour or more, depending on the products selected.

    When the installation process completes, a list of installed products is displayed. You are asked whether you want to set up the Sun Management Center components.

  16. Decide whether to set up the installed products.

    Type y to set up Sun Management Center and any add-on products that you selected, or type n to exit and run setup later.

    Caution – Caution –

    If you have used es-inst to install only add-on products, type n to exit the installation and setup process. You must set up the add-on products as described by To Set Up an Add-on Product Using es-setup. Otherwise, you will overwrite your security keys, and will then have to set up all of the agents on all of your machines for the agents to work properly.

Installing on a Remote Machine

This section provides the procedure for installing Sun Management Center 4.0 on a Network File System accessible (NFS-mounted) remote machine using the es-inst command. The procedure assumes that you are installing Sun Management Center from a image directory on your network. See Creating Installation DVD Images for further information.

To install Sun Management Center on a remote machine, you have to prepare the remote machine before you install the software. Also, if the local machine is running Solaris 8 software, you must install a patch as described in To Install Patches for pkgadd.

The following machine names are used as examples in the procedures in this section:

Note –

Remote installation is not supported if the remote machine is a Solaris 10 machine.

ProcedureTo Install Patches for pkgadd

If the local machine is running Solaris 8 software, a patch for pkgadd specific to the operating system version must be installed on the local machine. You must install this patch before you can use the local machine to install Sun Management Center 4.0 on the remote machine.

If the local machine is running the Solaris 9 release, you do not need to install any patches. Go to To Prepare the Remote Machine.

  1. Log in as root on the local machine.

  2. Ensure that the OS patch level is current.

    To determine whether the patch is already installed, use the command showrev -p | grep patchnum, where patchnum is the required OS patch as follows:

    • Solaris 8 release: 110934

    For example, if the local machine is running Solaris 8 release, you would type:


    admin-host# showrev -p | grep 110934
admin-host#

    In the above example, the patch is not installed. The patch must be downloaded and installed as directed by Step 3.

    If the patch is installed, a listing similar to the following is displayed.


    admin-host# showrev -p | grep 110934
admin-host# Patch: 110934-13 Obsoletes: Requires: Incompatibles: 
Packages: pkgtrans, pkgadd, pkgchk

    If the patch that is required by the local machine Solaris version is installed, go to To Prepare the Remote Machine.

  3. Install the OS patch if needed.

    1. Download the required patch from http://www.sunsolve.sun.com.

    2. Untar and then unzip the downloaded patch archive file.

    3. Install the patch using the patchadd command.

ProcedureTo Prepare the Remote Machine

  1. Log in as root on the remote machine.

  2. Create the Sun Management Center database access group and user account.

    1. Use the groupadd command to create the access group smcdbg. 


      remote# /usr/sbin/groupadd smcdbg

    2. Create the directory /var/opt/SUNWsymon.

      This directory is where the database user account will be located.


      remote# mkdir -p /var/opt/SUNWsymon

    3. Use the useradd command to create the database user account smcdbu, and then add the user account to the group smcdbg. 


      remote# /usr/sbin/useradd \
...-d /var/opt/SUNWsymon/smcdbu \
   -m -g smcdbg -s /bin/sh smcdbu

  3. Stop the Network File System daemon mountd. 


    remote# /etc/init.d/nfs.server stop

  4. Edit the /etc/dfs/dfstab file on the remote host.

    Add the following line:

    share —F nfs —o rw=admin-host,root=admin-host /

    where admin-host is the name of the machine from which you will install Sun Management Center onto the remote host.

    For example, if the remote host name is remote-server, and the name of the machine you will use to install Sun Management Center on remote-server is adminserver, then the entry in the remote-server /etc/dfs/dfstab file would be:

    share —F nfs —o rw=adminserver,root=adminserver

    This entry in the remote machine's dfstab file gives remote read and write permission only to the root user account logged on to the machine adminserver.

  5. Save and close /etc/dfs/dfstab.

  6. Start the Network File System daemon mountd. 


    remote# /etc/init.d/nfs.server start

  7. Determine the Solaris version running on the remote machine. 


    remote# /usr/bin/uname -r

    When you install Sun Management Center on the remote host, the es-inst script will prompt you for the Solaris version running on the remote host.

  8. Determine the remote host machine type.

    When you install Sun Management Center on the remote host, the es-inst script will prompt you for the remote machine type.

    The information required by es-inst for the remote host machine is generated by the command:


    remote# /usr/platform/platform/sbin/prtdiag | /usr/bin/head -1 \
      | /usr/bin/cut -f2 -d:

    where platform is the output of the command uname -i.

    For example:


    remote# /usr/bin/uname -i
SUNW,Ultra
remote# /usr/platform/SUNW,Ultra/sbin/prtdiag 
  | /usr/bin/head -1 | /usr/bin/cut -f2 -d:
Sun Microsystems  sun4u Sun Ultra UPA/PCI (UltraSPARC-IIi 333 MHz)
    Tip –

    Copy the remote host machine-type information to a temporary file on the local host. You can then paste the information when es-inst prompts you for the remote host machine type.

  9. Log off the remote machine.

    You can now install Sun Management Center on the remote host as described by the next procedure.

ProcedureTo Install Sun Management Center on the Remote Machine

  1. Log in as root on the local machine.

  2. Change to the Sun Management Center installation disk 1 sbin directory.

    • If you are installing from disk, then Change to the /cDiskMountDir/sbin directory.

      During the installation process, you might be prompted to change the disks depending on your selections.

    • If you are installing from a image, Change to the /image-dir/disk1/sbin directory, where image-dir is the directory either where you copied the installation images, or where you downloaded the installation image from the Web.

  3. Run the es-inst installation script, and specify the remote host machine using the -R path/remote parameter.


    #./es-inst -R path/remote

    where path/remote is the full path to the remote machine. For example, if the remote host path and name is /net/remote-server, you would type:


    local-machine# ./es-inst -R /net/remote-server

    You are prompted for the Solaris version running on the remote machine.

  4. Type the Solaris version running on the remote machine.

    See To Prepare the Remote Machine, Step 7.

    You are prompted for the remote host machine type.

  5. Provide the remote host machine type.

    Type the machine type string that you generated in To Prepare the Remote Machine, Step 8. Alternately, if you copied the generated text to a file on the local host, you can paste the machine-type string in answer to the prompt.

    Note –

    The steps that are required to complete installation of Sun Management Center on a remote host are the same steps that are required for the default Sun Management Center install.

  6. Complete the installation.

    • If a prior version of Sun Management Center is installed on the system, you are asked whether you want to migrate the data from the previous Sun Management Center version. Go to To Install Using es-inst, Step 6.

    • If a prior version of Sun Management Center is not installed on the system, you are prompted for the target directory. Go to To Install Using es-inst, Step 7.

    Note –

    Remote installation on to a Solaris 10 system is supported only from another Solaris 10 system.