test

Sun Management Center 4.0 Installation and Configuration Guide

Chapter 6 Installing and Updating Agents and Installing on Microsoft Windows

This chapter provides the procedures for installing and updating agents.

This chapter discusses the following topics:

Caution – Caution –

Before you install Sun Management Center 4.0 using es-guiinst, ensure that you have completed all the tasks listed by Preinstallation Checklist.

Creating Agent Installation and Update Images

Agent-update images are supported on systems that have the Sun Management Center agent only installed. If you try to use agent-update images on systems where you have the Sun Management Center server or console or all three layers installed, the operation fails.Sun Management Center provides three tools to create agent-update images that can be used to install or simultaneously update Sun Management Center agents on multiple systems. The script and GUI image tool utilities also enable you to create patch-only update images that can be used to update multiple systems.

es-gui-imagetool and es-imagetool enable you to select specific Solaris and Linux operating environments and add-ons, resulting in a much smaller installation image than the image created by es-makeagent. Images created using the image tools are applied by using the Sun Management Center Java console Manage Jobs task, or by using the agent-update.bin executable file.

Note –

The Manage Jobs task enables you to apply the agent-update image to the target machines without performing any tasks on the target machines. Alternatively, you could copy or use FTP to copy the agent-update.bin executable file to each target machine, and then run the agent-update.bin on each target machine to apply the agent-update image.

The image type that you create depends on the following factors.

The Sun Management Center 4.0 can be installed on SPARC, x86, and on Linux systems.

The following procedures describe how to create agent-update images and patch-only update images using , es-gui-imagetool or es-imagetool, and how to create an agent-only image using es-makeagent.

ProcedureTo Create an Agent-Update Image Using es-gui-imagetool

es-gui-imagetool enables you to create agent-update images containing any one of the following items.

Note –

This procedure assumes that you installed Sun Management Center in the default directory /opt. If you installed Sun Management Center in a different directory, replace /opt with the name of the directory you specified.

  1. Log in as root on the Sun Management Center 4.0 server machine.

  2. Run the Sun Management Center GUI image tool by typing the following command: 


    # /opt/SUNWsymon/sbin/es-gui-imagetool

    The Welcome screen appears. Click Next. The Overview screen appears, listing the information that you might need to provide. Click Next.

    The Select Update-Image Components screen appears.

  3. Select the update-image components.

    Four choices are provided:

    • Base Agent Packages

    • Add-on Agent Packages

    • Base and Add-on Agent Packages

    • Base and Add-on Agent Patches Only

    Note –

    Any patches needed for a selected package are automatically included when you select the package. If you want to install base agent patches and add-on agent patches only, select Base and Add-on Agent Patches Only.

    Select the type of update-image that you want to create, and then click Next. The Specify the Installation Files Source Directory screen appears.

  4. Provide the name of a valid Sun Management Center 4.0 source directory.

    The installation source default /DiskMountDir/image is displayed.

    • If you are installing from DVDs, insert Sun Management Center 4.0 DVD in the DVD drive.

      Enter a valid source directory: /DiskMountDir//disk1/image

    • If you are installing from a Sun Management Center 4.0 installation image on disk, either click Browse to navigate to the Sun Management Center installation disk1/image directory, or type the path to the disk1/image directory in the Source Directory field. 


      Source Directory: /net/machine/installdir/disk1/image

      where machine is the machine on which you created the installation image, and installdir is the directory containing the Sun Management Center 4.0 disk1 and disk2 images. See Determining the Installation Source for further information about installation images.

    Click Next.

    • If you selected Base Agent Packages, or selected Base and Add-on Agent Packages, the Specify the Destination Directory screen appears. Go to Step 5.

    • If you selected Add-on Agent Packages or Base and Add-on Agent Patches Only, the Sun Management Center Update Image Name screen appears. Go to Step 6.

  5. Provide the target directory for Sun Management Center 4.0 installation.

    The target directory is the directory where the Sun Management Center 4.0 SUNWsymon directory is created if it does not already exist.

    • If an agent is not installed, then the new agent is installed in the directory you specify.

    • If an older version of an agent is already installed in a different directory, then the new agent is installed in the directory you specify.

    • If the same version of an agent is already installed in a different directory and the update you are applying contains additional components such as add-ons, the agent is updated in the existing directory.

    The following scenario provides an example.

    Assume you have created a base and add-on agent packages update image, and you have specified /opt as the target directory. Also, assume that you want to apply the update image to five different machines in the following states:

    • Sun Management Center 3.6.1 is installed in /opt/SUNWsymon on machine A.

    • Sun Management Center 3.6.1 is installed in /export/home/opt/SUNWsymon on machine B.

    • No Sun Management Center components are installed on machine C.

    • The Sun Management Center 4.0 base agent only is installed in /opt/SUNWsymon on machine D.

    • The Sun Management Center 4.0 base agent only is installed in /export/home/opt/SUNWsymon on machine E.

    When you apply the Sun Management Center 4.0 base and add-on agent packages update image to the five machines, each machine is updated as follows.

    • On machine A, the Sun Management Center 4.0 agent is reinstalled and replaces the version 3.6.1 agent in directory /opt/SUNWsymon.

    • On machine B, the Sun Management Center 4.0 agent is installed in directory /opt/SUNWsymon.

    • On machine C, the Sun Management Center 4.0 agent is installed in directory /opt/SUNWsymon.

    • On machine D, the base agent is upgraded, with add-on packages, to version 4.0 in directory /opt/SUNWsymon.

    • On machine E, the base agent is upgraded, with add-on packages, to version 4.0 in directory /export/home/opt/SUNWsymon.

    Click Next. The Sun Management Center Update-Image Name screen appears.

  6. Provide a name for the agent update-image.

    Type a name for the update-image that reflects the update-image type, for example SPARC-Base-agents, x86-Base-agents, Linux agents add-ons or config-readers.

    The update-image is created in /var/opt/SUNWsymon/agentupdate/update-image-name where update-image-name is the name that you provide.

    Click Next. The OS Selection screen appears.

  7. Select the platform (Solaris or Linux) versions that the target machines are running.

    The image tool will create images for all platform versions supported by Sun Management Center irrespective of the version of the machine on which the tool is running. You have a choice of selecting any of the platform versions, or all.

    Caution – Caution –

    If you omit a platform version when you create an agent-update image, application of the update-image to the machine whose platform version is omitted will fail.

    Click Next. The Checking for Available Products screen appears.

    • If you selected Base Agent Packages, or Base and Add-on Agent Packages, the image tool verifies that all components of the base layer are available in the image source you specified.

      When image source verification completes, the SNMP Port Assignment screen appears. Go to Step 11.

    • If you selected Add-on Packages, the Select Add-ons for Package and Patch Updates screen appears. Go to Step 8.

    • If you selected Base and Add-on Agent Patches, the Select Patches screen appears. Go to Step 9.

  8. Select Add-ons.

    Select the products that you want to add to the agent update-image, and then click Next.

    The image tool checks whether setup responses are needed by any of the add-on products you selected for inclusion in the update-image. Go to Step 10.

    • If the selected add-on products do not require setup responses, the SNMP Port Assignment screen appears. Go to Step 11.

    • If any selected add-on product requires setup responses, the Add-on Setup screen appears.

  9. Select patches.

    You can select all patches, or you can select individual patches.

    When you have finished selecting patches, click Next. The Confirmation screen appears. Step 12.

  10. Provide add-on setup responses.

    You are prompted to click Next to answer the setup questions for the selected add-on products. Click Next.

    A terminal window appears, and the image tool process steps through each add-on product that you selected for agent update, and prompts you for the responses needed by each product. Refer to the documentation that is provided with each add-on for further information.

    When you finish providing responses, the SNMP Port Assignment screen appears.

  11. Specify an SNMP port for the Sun Management Center agent.

    In most cases, port 161 is the default port assigned to and used by the SNMP daemon. However, other processes or daemons could be using port 161. Several third-party replacements and enhancements for the SNMP daemon exist, and could be installed on your system. The Sun Management Center agent is one such daemon. Also keep in mind that a port number other than 161 could have been specified during Sun Management Center setup on each target machine.

    See To Determine Whether a Port Is Used for procedures on how to determine if a port is unused.

    Caution – Caution –

    If you select port 161, you must stop and disable any process that uses port 161 on each target machine before you can restart the agent on each machine. Stopping and disabling the SNMP daemon on each machine is not a guarantee that you have stopped the actual process using port 161. To determine which daemon process uses port 161 requires you to manually review all /etc/rcN and /etc/rcN.d files, where N is 0 through 6 and S. When you have identified the file that defines the process using port 161, you can disable the process by renaming the file. For example, 


    /etc/rc3.d# mv S76snmpdx s76snmpdx

    You must disable any daemon that uses port 161 on each target machine.

    • To use port 161 on each target machine, select Use Port 161, and then click Next. The Stop and Disable SNMP Daemon screen appears.

    • To assign a different port number, select Use A Different Port Number.

      Type the port number in the Port ID field and then click Next.

      When the agent-update image is applied on the target client, the update process checks whether an agent is already installed.

      • If an agent was previously installed and configured, the update process uses the original port assignment. For example, if the previous agent uses port 2261, then the update process assigns port 2261 to the updated agent.

      • If an agent is not installed and port 161 is not in use, the update process assigns port 161 to the agent .

      • If an agent is not installed and port 161 is in use, the update process assigns the port you specified to the agent .

    The image tool process now checks for sufficient disk space.

    • If there is not enough space to create the image, you are notified. The amount of free space that is needed is listed. Click Cancel to exit the update-image tool. You must increase the amount of free space by the amount listed before you can create an update-image.

    • If there is enough disk space, the Confirmation screen is displayed.

  12. Confirm the update-image selections.

    A list of the components that you selected for inclusion in the agent update-image is displayed.

    • If the list is not correct, click Back repeatedly to return to either the Select Add-ons for Package and Patch Updates screen, or to the Select Update-Image Components screen. When the appropriate screen is displayed, select the products that you want to add to the update-image and confirm your new selections.

    • If the list is correct, click Next.

      The image tool creates the agent update-image in the directory /var/opt/SUNWsymon/agentupdate using the file name you specified in Step 6.

    You are notified when the update image has been created. Click Finish to return to the system prompt.

    You can check the update image creation status by viewing the log file /var/opt/SUNWsymon/install/es-gui-imagetool_host-name.date-and-time-string.process-id where:

    • host-name is the name of the Sun Management Center 4.0 server that you used to create the update image.

    • date-and-time-string is the year, date, and time the image was created.

    • process-id is the process ID of the imagetool session that created the agent-update image.

  13. Apply the agent-update image.

    You can now apply the update-image to the target machines.

ProcedureTo Create an Agent-Update Image Using es-imagetool

es-imagetool enables you to create agent-update images containing any one of the following.

Note –

This procedure assumes that you installed Sun Management Center in the default directory /opt. If you installed Sun Management Center in a different directory, replace /opt with the name of the directory you specified.

  1. Log in as root on the Sun Management Center 4.0 server machine.

  2. Run the Sun Management Center command-line image tool by typing the following command: 


    # /opt/SUNWsymon/sbin/es-imagetool

  3. Select the components to update.

    You are prompted to select the components that you want to add to the update-image, for example:


    Select the components you want to add to the update-image.

Do you want to upgrade components of Base Agent? [y|n|q] y
Do you want to install/upgrade components of Addons? [y|n|q] y

    Type y to add the component to the update-image, or type n to exclude the component from the update-image.

    You are prompted for a valid source directory.

  4. Provide the name of a valid Sun Management Center 4.0 source directory.

    • If you are installing from DVDs, type the path to the Sun Management Center 4.0 installation image directory. For example:


      Enter a valid source directory: /DiskMountDir/image

    • If you are installing from a Sun Management Center 4.0 installation image on disk, type the path to the image disk1/image directory. For example:


      Enter a valid source directory: /net/machine/installdir/disk1/image

      where machine is the machine on which you created the installation image, and installdir is the directory containing the Sun Management Center 4.0 disk1 and disk2 images. See Determining the Installation Source for further information about installation images.

      • If you replied y to the prompt Do you want to upgrade components of the Base Agent?, you are prompted for the installation target directory. Go to Step 5.

      • If you replied n to the prompt Do you want to upgrade components of the Base Agent?, and replied y to the prompt Do you want to install/upgrade components of Addons?, you are prompted for the installation target directory. Go to Step 6.

  5. Provide the name of the target directory for Sun Management Center 4.0 installation.

    The target directory is the directory where the Sun Management Center 4.0 SUNWsymon directory is created if it does not already exist.

    • If an agent is not installed, then the new agent is installed in the directory you specify.

    • If an older version of an agent is already installed in a different directory, then the new agent is installed in the directory you specify.

    • If the same version of an agent is already installed in a different directory, and the update you are applying contains new software, the agent is updated in the existing directory.

    The following scenario provides an example:

    Assume that you have created a Base and Add-on Agent Packages update image, and that you have specified /opt as the target directory. Also, assume that you want to apply the update image to five different machines in the following states:

    • Sun Management Center 3.6.1 is installed in /opt/SUNWsymon on machine A.

    • Sun Management Center 3.6.1 is installed in /export/home/opt/SUNWsymon on machine B.

    • No Sun Management Center components are installed on machine C.

    • The Sun Management Center 4.0 base agent only is installed in /opt/SUNWsymon on machine D.

    • The Sun Management Center 4.0 base agent only is installed in /export/home/opt/SUNWsymon on machine E.

    When you apply the Sun Management Center 4.0 Base and Add-on Agent Packages update image to the five machines, each machine is updated as follows.

    • On machine A, the Sun Management Center 4.0 agent is reinstalled and replaces the version 3.6.1 agent in directory /opt/SUNWsymon.

    • On machine B, the Sun Management Center 4.0 agent is installed in directory /opt/SUNWsymon.

    • On machine C, the Sun Management Center 4.0 agent is installed in directory /opt/SUNWsymon.

    • On machine D, the base agent is upgraded, with add-on packages, to version 4.0 in directory /opt/SUNWsymon.

    • On machine E, the base agent is upgraded, with add-on packages, to version 4.0 in directory /export/home/opt/SUNWsymon.

    You are prompted for a name for the agent update image.

  6. Provide a name for the agent update-image.

    Provide a name for the update-image that reflects the update-image type, for example Ultra60agent, SPARC-baseagent, x86–baseagent, or Linux agent and then press Return.

    The update-image is created in /var/opt/SUNWsymon/agentupdate/update-image-name, where update-image-name is the name that you provide.

    You are then prompted to choose the platform (Solaris or Linux) versions for the target machines.

    The image tool creates images for all platform versions supported by Sun Management Center irrespective of the platform version on the machine on which the tool is running. You have a choice of selecting any Solaris version or all versions.

  7. Select the platforms that the target machines are running.

    The supported versions are listed, and you are asked whether you want to select all versions.

    • Reply y if the target machines include all Solaris and Linux versions.

      The image tool process checks for available add-on products. Go to Step 8.

    • Reply n if the target machines do not include all versions.

      Each version of Solaris and Linux is listed, and you are asked whether you want to create an image for that version. Reply y or n as appropriate for the target machines. For example:


      Do you want to select ALL OS versions ? [y|n|q] n
Do you want to create images for sparc-sun-Solaris_8 ?   [y|n|q] y
Do you want to create images for sparc-sun-Solaris_9 ?   [y|n|q] n
Do you want to create images for sparc-sun-Solaris_10 ?  [y|n|q] y
Do you want to create images for i386-sun-Solaris_9 ?    [y|n|q] n
Do you want to create images for i386-sun-Solaris_10 ?   [y|n|q] y
Do you want to create images for i686-sun-Linux_2.6 ?    [y|n|q] n
      Caution – Caution –

      If you omit a Solaris version when you create an agent-update image, application of the update-image to the machine whose Solaris version is omitted will fail.

    • If you selected only Upgrade Components of Base Agent in Step 3, go to Step 9.

    • If you selected Install/upgrade Components of Addons in Step 3, the image tool process checks the add-on products and lists the products for which an agent update is available. Go to Step 8.

  8. Select the agent add-on products that you want to upgrade.

    The available add-on products are listed, and you are then sequentially asked whether you want to install each add-on product. Reply y to add the add-on software to the update-image, or reply n to exclude the add-on software from the image.

    When you finish selecting the add-on products to upgrade, you are prompted for the Sun Management Center agent port.

  9. Specify a port for the Sun Management Center agent.

    In most cases, port 161 is the default port assigned to and used by the SNMP daemon. However, other processes or daemons could be using port 161. Several third-party replacements and enhancements for the SNMP daemon exist, and could be installed on your system. The Sun Management Center agent is such a daemon. A different port number could have been specified during Sun Management Center on each target machine.

    Caution – Caution –

    If you select port 161, you must stop and disable any process that uses port 161 on each target machine before you can restart the agent on each machine. Stopping and disabling the SNMP daemon on each machine is not a guarantee that you have stopped the actual process using port 161. Determining the actual daemon process that uses port 161 requires you to manually review all /etc/rcN and /etc/rcN.d files, where N is 0 through 6 and S. When you have identified the file that defines the process using port 161, you can disable the process by renaming the file. For example, 


    /etc/rc3.d# mv S76snmpdx s76snmpdx

    You must disable the daemon that uses port 161 on each target machine.

    Press Return to use port 161 on each target machine, or type a different port number.

    • If you selected only Upgrade Components of Base Agent in Step 3, the image tool process checks for sufficient disk space. If there is enough space, the agent update-image is created.

      If there is not enough space to create the image, you are notified. The amount of free space that is needed is displayed. The image tool exits. You must increase the amount of free space by the amount listed before you can create an update-image.

    • If you selected install/upgrade components of Addons in Step 3, the image tool process checks whether setup responses are needed by any of the add-on products that you selected for inclusion in the update-image.

      If any selected product requires setup responses, the image tool process steps through each add-on product that you selected for update, and prompts you for the responses needed by each product. Refer to the documentation that is provided with each add-on for further information.

      When add-on product setup response collection is completed, the image tool checks disk space. If there is enough space, the agent update-image is created.

      If there is not enough space to create the image, you are notified. The amount of free space that is needed is displayed. The image tool exits. You must increase the amount of free space by the amount listed before you can create an update-image.

    You are notified when the update-image has been created. You can check the update image creation status by viewing the log file /var/opt/SUNWsymon/install/es-imagetool_host-name.date-and-time-string.process-id where:

    • host-name is the name of the Sun Management Center 4.0 server that you used to create the update image.

    • date-and-time-string is the year, date, and time that the image was created.

    • process-id is the process ID of the imagetool session that created the agent-update image.

    You can now apply the image to the target machines.

ProcedureTo Create a Patch-Only Image Using the Image Tools

Sun Management Center-specific patches are released periodically on the Sun Management Center web site at http://www.sun.com/sunmanagementcenter. Sun Management Center enables you to create a patch-only image, and then apply the patch-only image to multiple agent machines.

  1. Log in as root on the Sun Management Center 4.0 server machine.

  2. Create a directory in which to download the Sun Management Center patches.

    Change to the directory you just created. Create directories for each Solaris operating environment version for which you want to download patches.

    For example, assume you created the directory /sunmcpatches. Furthermore, assume you plan to create patch-only update images for each supported Solaris version. You would create the directories as follows.


    # mkdir /sunmcpatches
# cd /sunmcpatches
/sunmcpatches# mkdir Solaris_8 Solaris_9

    The directories must be created using the names shown.

  3. Log on to SunSolve.

    Click the Login button to display the login screen, and then enter your SunSolve ID and password.

    If you do not have a SunSolve ID, click the Register button to obtain a SunSolve ID.

  4. Download the patches for each Solaris version.

    Click the patch number corresponding to the Solaris version.

    The SunSolve Online Web page is displayed.

    1. Type the number of the patch you want to view, and then click Find Patch.

      A description of the patch is displayed.

      Make note of the supported Solaris versions. If the patch applies to more than one Solaris version, you must download the patch file for each Solaris version.

    2. Click either the HTTP or FTP download link to download the patch.

      The Save As panel appears.

      Save the patch file to the applicable Solaris version directory you created in Step 2.

      For example, assume patch 111222-33 is applicable to Solaris version 8 and Solaris version 9. Assume that you also created the subdirectories Solaris_8 and Solaris_9 within the root directory sunmcpatches. You would then download the patch file to both /sunmcpatches/Solaris_8 and /sunmcpatches/Solaris_9.

    If you want to download more patches, click Back to return to the SunSolve Online Web page. Repeat the previous two steps to download each patch you have selected.

    When you have completed downloading patches, go to the next step.

  5. Uncompress the patch files.

    Change to each directory where you downloaded the patch files and uncompress the files.

    For example, assume you downloaded the patch file for patch 111222–33 and patch 111222–34 to /sunmcpatches/Solaris_8. Also assume that the patch file for patch file 111222–33 is 111222–33.tar.Z, and the patch file for 111222–34 is 111222–34.zip. You would then uncompress the patch files as follows:


    /sunmcpatches # cd Solaris_8
/sunmcpatches/Solaris_8 # ls
111222-33.tar.Z        111222-34.zip
/sunmcpatches/Solaris_8 # zcat 111222-33.tar.Z | tar xvf -
x 111222-33, 0 bytes, 0 tape blocks
x 111222-33/installpatch, 119239 bytes, 233 tape blocks
   .
   .
   .
x 111222-33/README.111222-33, 136444 bytes, 267 tape blocks
/sunmcpatches/Solaris_8 # unzip 111222-34.zip
Archive: 111222-34.zip
   creating: 111222-34/
..inflating: 111222-34/prepatch
   .
   .
   .
  inflating: 111222-34/README.111222-34
/sunmcpatches/Solaris_8 # ls -p
111222-33/     111222-33.tar.Z.....111222-34/     111222-34.zip

    You can create the patch-only image using either the graphical tool es-gui-imagetool as described next in Step 7 , or by using the command-line tool es-imagetool as described in Step 8.

  6. Move the download patch files to another directory.

    Either move the compressed download patch files to another directory for safekeeping, or delete the compressed patch files.

  7. Create the patch-only image file using es-gui-imagetool.

    Note –

    The following steps assume that you installed Sun Management Center in the default directory /opt. If you installed Sun Management Center in a different directory, replace /opt with the name of the directory you specified.

    1. Type the command /opt/SUNWsymon/sbin/es-gui-imagetool.

      The Welcome screen appears. Click Next. The Overview screen appears. Click Next.

      The Select Update-Image Options screen appears.

    2. Select Base and Add-on Agent Patches Only.

      Click Next.

      The Specify the Installation Files Source Directory screen appears.

    3. Specify the patch file source directory.

      Type the name of the patch directory you created in Step 2, or Click Browse to navigate to and select the directory.

      Click Next. The Update Image Name screen appears.

    4. Provide a name for the patch-only image.

      Type a name for the patch-only image that reflects the image type, for example base-and-addon-patches.

      The image is created in /var/opt/SUNWsymon/agentupdate/update-image-name where update-image-name is the name that you provide.

      Click Next. The OS Selection screen appears.

    5. Select the Solaris versions that the target machines are running.

      The image tool will create images for all Solaris versions supported by Sun Management Center irrespective of the version of the machine on which the tool is running. You have a choice of selecting any of the Solaris versions, or all versions.

      Caution – Caution –

      If you omit a Solaris version when you create a patch-only image, application of the patches to the machine whose Solaris version is omitted will fail.

      Click Next. The Checking for Patches screen appears. When the image tool has completed checking for patches, the Select Patches screen appears.

    6. Select the patches you want to add to the patch-only update image.

      You can select all patches, or you can select individual patches.

      When you have finished selecting patches, click Next. The image tool checks for disk space.

      • If there is not enough space to create the image, you are notified. The amount of free space that is needed is listed. Click Cancel to exit the image tool. You must increase the amount of free space by the amount listed before you can create a patch-only image.

      • If there is enough disk space, the Confirmation screen is displayed.

    7. Confirm Update-Image Selections

      A list of the patches and the Solaris versions that you selected for the patch-only image is displayed.

      • If the list is not correct, click Back twice to return to the Solaris version selection screen, or click Back once to return to the Select Patches screen. Select the Solaris versions and patches that you want to add to the patch-only image and confirm your new selections.

      • If the list is correct, click Next.

        The image tool creates the patch-only image in the directory /var/opt/SUNWsymon/agentupdate using the file name you specified in Step d.

      You are notified when the update image has been created. Click Close to return to the system prompt.

      You can check the update image creation status by viewing the log file /var/opt/SUNWsymon/install/es-gui-imagetool_host-name.date-and-time-string.process-id where:

      • host-name is the name of the Sun Management Center 4.0 server that you used to create the update image.

      • date-and-time-string is the year, date, and time the image was created.

      • process-id is the process ID of the imagetool session that created the agent-update image.

    8. Apply the patch-only image.

      You can now apply the image to the target machines.

  8. Create the patch-only image file using es-imagetool.

    Note –

    The following steps assume that you installed Sun Management Center in the default directory /opt. If you installed Sun Management Center in a different directory, replace /opt with the name of the directory you specified.

    1. Type the command /opt/SUNWsymon/sbin/es-imagetool.

      You are asked whether you want to upgrade components of the Base agent. Type n and press Return.

      You are asked whether you want to install or upgrade components of add-ons. Type n and press Return.

      You are asked whether you want to install patches. Type y and press Return.

      You are prompted for the patch-only source directory.

    2. Specify the patch file source directory.

      Type the name of the patch directory you created in Step 2, and then press Return.

      You are prompted to provide a name for the patch-only image.

    3. Provide a name for the patch-only image.

      Type a name for the patch-only image that reflects the image type, for example base-and-addon-patches.

      The image is created in /var/opt/SUNWsymon/agentupdate/update-image-name where update-image-name is the name that you provide.

      Press Return. The supported Solaris versions are listed.

    4. Select the Solaris versions that the target machines are running.

      The image tool will create images for all Solaris versions supported by Sun Management Center irrespective of the version of the machine on which the tool is running. You have a choice of selecting any Solaris version, or all versions.

      Caution – Caution –

      If you omit a Solaris version when you create an patch-only image, application of the patches to the machine whose Solaris version is omitted will fail.

      • To select all Solaris versions, type y.

      • To select only specific Solaris versions, type n.

        You are prompted to select each Solaris version sequentially. Type y to select a Solaris version, or type n to exclude the Solaris version from the image.

      Press Return. The image tool lists the patches that are available for selection.

    5. Select the patches that you want to add to the patch-only update image.

      You are prompted to select each patch.

      Type y to select a patch for inclusion in the patch-only image, or type n to exclude the patch from the image.

      When you have completed selecting patches, press Return. The image tool checks for disk space.

      • If there is not enough space to create the image, you are notified. The amount of free space that is needed is listed. Type q to exit the image tool. You must increase the amount of free space by the amount listed before you can create a patch-only image.

      • If there is enough disk space, the patch-only image is created in the directory /var/opt/SUNWsymon/agentupdate using the file name that you specified in Step c.

      You can check the update image creation status by viewing the log file /var/opt/SUNWsymon/install/es-imagetool_host-name.date-and-time-string.process-id where:

      • host-name is the name of the Sun Management Center 4.0 server that you used to create the update image.

      • date-and-time-string is the year, date, and time the image was created.

      • process-id is the process ID of the imagetool session that created the agent-update image.

    6. Apply the patch-only image.

      You can now apply the image to the target machines.

ProcedureTo Create an Agent-Only Installation Image Using es-makeagent

Note –

This procedure assumes that you installed Sun Management Center in the default directory /opt. If you installed Sun Management Center in a different directory, replace /opt with the name of the directory you specified.

  1. Log in as root.

  2. Place Sun Management Center 4.0 DVD in the DVD drive.

  3. Type the command /opt/SUNWsymon/sbin/es-makeagent.

    You are prompted for the installation source files directory.

  4. Type the source directory:


    (SPARC) /DiskMountDir/image/SunOS/sparc
    		 

    (x86) /DiskMountDir/image/SunOS/i386
    		 

    (Linux) /DiskMountDir/image/Linux

    You are asked for a target directory in which to create the agent-only installation image.

  5. Type the name of the target directory.

    If the directory does not exist, you are asked whether you want to create it. Type y to create the directory, or type n or q to exit to the system prompt.

    The directory you specify must have write permission for root.

    For example:


    # enter the target directory: /es-makeagent-image
Directory /es-makeagent-image does not exist
Do you want to create it (y|n|q) y

    The es-makeagent script creates the subdirectories disk1 and disk2 in the directory you specified, and then copies the files required to the subdirectories.

    1. Remove the Sun Management Center 4.0 DVD.

    2. Press Return.

      es-makeagent copies the remaining files from the DVD.

      You are informed that the agent-only product is available in the directory you specified. The command required to install the agent on the local machine is also displayed.

    Tip –

    Mount the target directory using NFS, so that the directory is accessible by other machines on your network. See Step 8 in To Create DVD Images.

  6. Type the command eject to eject the DVD.

    You can now install the Sun Management Center 4.0 agent using any of the following methods.

    Note –

    The agent-only installation image also contains a tar file that you can copy using ftp to other agent machines and uncompress on each agent machine to create an installation image. The uncompressed installation image directory contains the subdirectories disk1 and disk2. To install from the uncompressed image on each agent machine, change directory to the disk1/sbin directory, and use the es-inst command as described in Installing Sun Management Center Using es-inst.

Applying Agent Installation, Update, and Patch-Only Images

The following procedures describe how to install or update agents from agent-update images using the Manage Jobs task, and the agent-update.bin executable file, and how to install agent-only installation images using the es-inst -a command.

Note –

If you want to use the JumpStart software to install the Solaris operating environment and the agent, see Installing Agents Using JumpStart.

ProcedureTo Install Agents From an Agent-Update Image Using the Manage Jobs Task

If you want to upgrade Sun Management Center 3.6.1 agents, apply the agent-update image by using the agent-update.bin executable file as described in To Install or Update Agents From an Agent-Update Image Using agent-update.bin. The Manage Jobs task is used to upgrade existing Sun Management Center 4.0 agents.

  1. Create an agent-update image using either of the image tools.

  2. Start the Sun Management Center console, and then log in to the console as an authorized Sun Management Center user.

    See To Start the Console on the Solaris Platform.

  3. Choose Tools -> Manage Jobs.

    The Manage Jobs window is displayed.

    The Manage Jobs window enables you to propagate your agents on multiple hosts simultaneously. For further details on the Manage Jobs feature, refer to the Sun Management Center 3.6.1 User’s Guide.

  4. Create a multiple-agent upgrade task.

    Note –

    Make sure the Sun Management Center agent is installed and running on the target hosts.

    1. Select target hosts for upgrades, and then create a group.

    2. Create a task of type Agent Update

      Select an appropriate image name for the upgrade operation. This name should be the name of an image you created using either the es-imagetool or the es-gui-imagetool.

      For detailed instructions, see To Create an Agent Update Task in Sun Management Center 3.6.1 User’s Guide

    The status displayed in the Job Manager window only shows the success or failure of the entire job. The job is marked Failed if the upgrade fails on a single agent in the entire group, even though the rest of the agent upgrades succeeded. Click View Log next to the Job list to check the status of individual upgrades.

    To view the intermediate upgrade status while the job is in progress, click View Logs tab, and then click InstallServer.log.

ProcedureTo Install or Update Agents From an Agent-Update Image Using agent-update.bin

The space requirements on the target machine /tmp directory are as follows depending on the contents of the update-image:

If you use a seed-file to specify the security seed and SNMP community string automatically, the seed-file must have the following format:


ES_SECURITY_SEED=seed 
ES_SNMPV1_STRING=string

where seed and string are the actual seed and community string specified when the Sun Management Center server was installed. If you do not specify a value for ES_SNMPV1_STRING, the default SNMP value is used. In this case, the file will be:


ES_SECURITY_SEED=seed
ES_SNMPV1_STRING=string

  1. Log in as root on the Sun Management Center server machine.

  2. Create an agent-update image using either of the image tools.

  3. Download the relevant agent-update.bin file from the Sun Management Center server to each target machine's root directory.

    • (SPARC) /opt/SUNWsymon/base/bin/sparc-sun-solaris/agent-update.bin

    • (x86) /opt/SUNWsymon/base/bin/i386-sun-solaris/agent-update.bin

    • (Linux)/opt/SUNWsymon/base/bin/i686-sun-Linux/agent-update.bin

    If you installed Sun Management Center in a different directory than /opt, replace the /optwith installdir in the paths mentioned, where installdir is the directory you specified. This step must be performed for each target machine.

    When you have finished downloading the file agent-update.bin to each target machine, you must log in to each target machine and perform the following four steps on each machine.

  4. Log in as root on the target machine.

  5. Change to the directory where you downloaded agent-update.bin.

  6. Type this command:


    ./agent-update.bin -s server -r http-port -p image-name [-f seed-file]

    where

    • server is the server that you logged into in Step 1

    • http-port is the Sun Management Center Web server port.

    • image-name is the name of the agent-only image you created in Step 2

    • seed-file is a file containing the security seed and SNMP community string. By using this option, you can make agent installation automatic after running the command. The seed-file must be owned by root and have read/write permissions for root only as a security precaution. If the file does not meet these requirements, the script exits.

    For example, assume that the Sun Management Center server name is Production1 and that the Web server port is 8080. Also, assume that the agent-update image name is sparc-baseagent. You would then type:


    # ./agent-update.bin -s Production1 -r 8080 -p sparc-baseagent

  7. Provide the security seed and the SNMPv1 community string.

    The agent-update process prompts you for the security seed and the SNMPv1 community string.

    • The security seed must be the same seed that you provided when you set up the Sun Management Center server and agent.

      Type the security seed password that you provided in Step b, Setting Up Sun Management Center. Type the password again to confirm the password.

    • The SNMPv1 community string must be the same community string you provided when you set up the Sun Management Center server and agent.

      If you specified a custom community string, make sure that you type the same community string that you provided in Setting Up Sun Management Center, Step c. If you used the default community string of public, press Return.

    The update process applies the update to the machine without prompting for further information.

    When the update process completes, check the update status by viewing the log file /var/opt/SUNWsymon/log/agent-update.log on the target machine.

ProcedureTo Install Agents From an Agent-Only Installation Image Using es-inst -a

  1. Create an agent-only installation image as directed in To Create an Agent-Only Installation Image Using es-makeagent.

  2. Log in as root on the machine where you want to install the agent.

  3. Go to the agent-only install image disk1/sbin directory.

    For example, if you created the agent-only image in the /export/agentsource directory on a machine that is named appserver, you would type:


    # cd /net/appserver/export/agentsource/disk1/sbin

  4. Type the command ./es-inst -a to install the Sun Management Center agent.

    You are prompted for the target directory

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

    The install process checks for any applicable add-ons.

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

    The install process lists each add-on product, and asks whether you want to install the product.

    Note –

    Only the agent component of a selected add-on is installed.

    Type y to select the product for installation, or type n if you do not want to install the product.

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

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

  7. Review your selections.

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

    The install process checks disk space.

  8. Check disk space.

    The installation process checks whether there is enough disk space to install the agent and the agent component of any add-on that you selected.

    • If there is enough disk space, the agent is installed. You are asked whether you want to run setup. Go to Step 10.

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

  9. 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 agent is installed. You are asked whether you want to run setup.

  10. Decide whether to set up the agent.

    To set up Sun Management Center agent and any add-on products that you selected, type y. Follow the instructions in To Set Up Sun Management Center.

    If you chose to run setup later, you must set up the agent on the machine before you can run the agent. Use either es-guisetup or es-setup to set up the agent.

Installing Agents Using JumpStart

This section describes how to configure and use a Solaris JumpStart server to install and set up the Sun Management Center 4.0 base agent, and the Solaris version 8 or version 9 operating environment, on a large number of systems.

JumpStart Concepts

The JumpStart software enables you to automatically install or upgrade the Solaris operating environment on several systems, and to perform pre-install and post-install tasks that can include installation and setup of additional software such as Sun Management Center.

The Solaris JumpStart software is a client-server application that consists of the following components:

You also need a separate machine, referred to as the prototype machine, on which to generate the Sun Management Center install and setup response files required by the JumpStart finish script.

For detailed information about the JumpStart software, see Solaris 9 9/04 Installation Guide.

System Services Needed

The JumpStart software requires the following system services.

Table 6–1 System Services Required for the JumpStart Software

Service 

Used for 

Network File System (NFS) daemons mountd and nfsd

Sharing the Solaris operating system image files 

rarp

IP address discovery 

bootp

Host definition and location of shared file systems 

tftp

Transfer of the Solaris initial boot kernel from the boot server to the install client 

JumpStart Process Overview

Deployment of the Sun Management Center 4.0 base agent is performed by the JumpStart finish script, which is run on the install clients. After JumpStart installs the specified Solaris operating environment, the JumpStart finish script installs the base agent on the install client based on the contents of the Sun Management Center install response file.

The finish script also prepares the install client to set up the base agent after the install client reboots, based on the contents of the Sun Management Center setup response file.

The Sun Management Center response files are generated during the Sun Management Center 4.0 command-line installation and setup process on a separate or prototype system. The response files are then copied to the JumpStart profile directory. If needed, you can manually create the install and setup response files directly in the JumpStart profile directory.

JumpStart mounts the install client's file systems on the /a partition. The JumpStart finish script then installs the Sun Management Center base agent by running the Sun Management Center command es-inst -R /a -T /a/target-directory, where target-directory is the name of the directory on the install client in which the agent is installed. For information about the es-inst command and parameters, see es-inst Options

The finish script also creates an rc3.d file that runs after the install client reboots. The rc3.d file sets up the Sun Management Center base agent using the setup response file. When the base agent is set up, the rc3.d file is deleted. Output from the finish script is stored in /var/sadm/system/logs/finish.log.

Security Considerations for Finish Scripts

During Sun Management Center setup, you provided a password to generate the security key, and you provided an SNMP community string. To ensure security, the security key and community string are not stored in the Sun Management Center setup response file.

To successfully install and set up the Sun Management Center base agent on an install client, you must provide the same password that was used to generate the security key in Setting Up Sun Management Center, Step b. You must also provide the same SNMP community string that you specified in Setting Up Sun Management Center, Step c. This can be performed using either of the following two methods.

Examples of JumpStart finish scripts for both methods are provided in To Create the JumpStart Finish Script.

JumpStart Configuration and Use

The following list summarizes the major steps required to set up the JumpStart software and install the Solaris operating environment, and the Sun Management Center base agent, on one or more install clients.

When all of the above steps have been completed, you can use the JumpStart server to perform a fresh Solaris operating environment and Sun Management Center base agent install on one or more install clients.

The procedures in this section assume the following situation:

ProcedureTo Create the JumpStart Install Server and Profile Directory

  1. Create the JumpStart install server and Solaris operating environment image.

    1. Log in as root on the machine you want to use as the JumpStart install server.

    2. Insert the Solaris installation CD 1 of 2 in your CD-ROM drive.

    3. Go to the Tools directory on the CD.


      # cd /DiskMountDir/Solaris_2.8/Tools

    4. Create the Solaris operating environment installation image.

      Type the command ./setup_install_server /install-server-directory, where install-server-directory is the directory that is to be used to serve the install images. For example:


       
# ./setup_install_server /export/home/JumpStart/Solaris_9 
Verifying target directory... 
Calculating the required disk space for the Solaris_9 product
Copying the CD image to disk...
Install Server setup complete

    5. Optional: Add the Solaris operating environment supplemental products to the JumpStart install server.

      Insert the Solaris installation CD 2 of 2 in your CD-ROM drive, and go to the Tools directory on the CD.

      Type the command ./add_to_install_server /install-server-directory, where install-server-directory is the directory that is to be used to serve the install images. For example:


      # cd /DiskMountDir/s0/Solaris_9/Tools
# ./add_to_install_server /export/home/JumpStart/Solaris_9

  2. Create the JumpStart profile directory on the server.


    # mkdir /export/home/JumpStart/jumpstart

  3. Insert the Solaris installation CD 1 of 2 in your CD-ROM drive.

  4. Copy the JumpStart samples from the CD directory Solaris_2.8/Misc/jumpstart_sample to the JumpStart profile directory /export/home/JumpStart/jumpstart. For example:


    # cd /DiskMountDir/s0/Solaris_2.8/Misc
# cp -r jumpstart_sample/* /export/home/JumpStart/jumpstart

  5. Stop the Network File System daemon mountd.


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

  6. Make the JumpStart directory NFS-shared.

    The JumpStart directory must be NFS-shared so that the install clients can access the files on the JumpStart server. Add the following line to the /etc/dfs/dfstab file, then save and close the file.

    share -F nfs -o ro,anon=0 /export/home/JumpStart

  7. Start the Network File System daemon mountd.


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

ProcedureTo Create the Base Agent Image on the JumpStart Install Server

  1. Log in as root on the machine where you created the JumpStart install server.

  2. Insert the Sun Management Center 4.0 DVD in your DVD drive.

    Change to the directory /DiskMountDir/sbin.

  3. Type the command ./es-makeagent to create the Sun Management Center base agent image.

    You are prompted for the installation files source directory, and for the agent image target directory.

    (SPARC) The source directory is /DiskMountDir/disk1/image/sunOS/sparc.

    (x86) The source directory is /DiskMountDir/disk1/image/sunOS/i386

    (Linux) The source directory is /DiskMountDir/disk1/image/Linux

    The target directory is the directory on the JumpStart install server where the agent image is to be created, for example, /export/home/JumpStart/AgentImage.

    Note –

    If the target directory that you specify does not exist, you are asked whether you want to create the directory. Type y to create the directory.

    Example:


    # ./es-makeagent
Installation files source directory: /DiskMountDir/image
Please enter the target directory: /export/home/JumpStart/AgentImage
    Note –

    The image creation process can take over half an hour to complete.

  4. Exclude add-on agents.

    If you do not want to include the add-on agent components, rename the agent-image Addons directory.


    # cd /export/home/JumpStart/AgentImage/disk1/image
# ls -p
Addons/     PE/         Patches/    Webserver/  db/
# mv Addons Addons-temp

ProcedureTo Generate the Sun Management Center 4.0 Install and Setup Response Files

  1. Select a machine on which to install and set up the Sun Management Center base agent, and log in as root.

    This is the prototype machine.

    Tip –

    Select a machine on which Sun Management Center has not been installed. If such a machine is not available, uninstall the Sun Management Center software from the prototype machine as directed by the installation manual for the Sun Management Center software. Do not save the configuration data from the previous version of Sun Management Center.

  2. Insert the Sun Management Center 4.0 DVD in your DVD drive.

    Change to the directory /DiskMountDir/sbin.

  3. Create a directory on the machine in which to store the Sun Management Center install and setup response files.

    For example:


    # mkdir /response-files

  4. Generate the Sun Management Center Install Response file.

    To generate the install response file, you must install the base agent using the command format ./es-inst -C /response-file-dir/install-response-file.cfg where:

    • response-file-dir is the directory that you created in which to store the response files

    • install-response-file is the name of the response file

    For example: 


    # ./es-inst -C /response-files/install.cfg

    You are prompted for the directory in which to install Sun Management Center.

    1. Provide the name of the directory in which to install Sun Management Center

      You are prompted for the target directory. 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. 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.

      You are prompted to select the Sun Management Center components that you want to install.

    2. Select only the agent component.

      Type n when prompted to install the server component.

      Type y when prompted to install the agent component.

      Type n when prompted to install the console component.


      3 component(s) are available for your selection:
  Do you want to install the Server component (y|n|q) n
  Do you want to install the Agent component (y|n|q) y
  Do you want to install the Console component (y|n|q) n

      The install process checks for add-on components, and then prompts you to select add-ons.

    3. Do not select any add-on components for installation.

      Type n when prompted to select each add-on.


      Select the products you want to install:
    Advanced System Monitoring (y|n|q) n
    Service Availability Manager (y|n|q) n
    Performance Reporting Manager (y|n|q) n
    Sun Fire Platform Administration (y|n|q) n
    System Reliability Manager (y|n|q) n
    Workgroup Server (y|n|q) n

      You are asked whether you want to proceed. Type y to continue.

    4. Check disk space.

      The installation process checks whether there is enough disk space to install the Sun Management Center base agent.

      • If there is enough disk space, the base agent is installed.

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

        Tip –

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

      When the agent installation completes, you are asked whether you want to run setup.

      Caution – Caution –

      Do not run setup. Type n to exit. Running setup from within the install process will not create the Sun Management Center setup response file needed by the JumpStart finish script.

  5. Go to the directory /opt/SUNWsymon/sbin.

    If you installed Sun Management Center in a different location, go to the /install-dir/SUNWsymon/sbin directory, where install-dir is the directory you specified in Step 4.

  6. Generate the Sun Management Center 4.0 setup response file.

    To generate the Sun Management Center setup response file, you must set up the base agent using the command format ./es-setup -C /response-file-dir/setup-response-file.cfg where:

    • response-file-dir is the directory that you created in which to store the response files

    • setup-response-file is the name of the response file

    For example: 


    # ./es-setup -C /response-files/setup.cfg

    You are prompted to provide a seed for security key generation,

    1. Generate the security keys.

      An encrypted security key is needed for communications between all Sun Management Center processes. The key is generated based on the password seed that you provide. The seed must be between one and eight characters long, and contain no spaces. Entries that are greater than eight characters are truncated to eight characters.

      Caution – Caution –

      You must ensure that you use the same security seed for all the machines that you install in a single server context.

      Type the same password seed that you provided during Sun Management Center server setup in Step b in Setting Up Sun Management Center.

      Type the password seed again when prompted.

      Note –

      To ensure security, the password seed that you provide is not stored in the Sun Management Center setup response file. You can either hard-code the password seed in the JumpStart finish script, or configure the finish script so that the install client prompts for the password seed when the finish script runs on the install client. Both methods of specifying the password seed are provided in To Create the JumpStart Finish Script.

      You are prompted for the SNMPv1 community string.

    2. Specify the SNMPv1 community security string.

      An SNMPv1 community string is required for security, and by default is set to public. For additional security, a customized string can be specified.

      Caution – Caution –

      You must ensure that you use the same SNMPv1 community string on all the machines that you install in a single server context.

      Provide the same community string that you provided during Sun Management Center server setup in Step c in Setting Up Sun Management Center.

      • If you used the default community string of public, press Return when prompted to submit the SNMPv1 community string.

      • If you specified a custom community text string, type the same community string that you provided during Sun Management Center server setup.

      Note –

      To ensure security, the community string that you provide is not stored in the Sun Management Center setup response file. You can either hard-code the community string in the JumpStart finish script, or configure the finish script so that the install client prompts for the community string when the finish script runs on the install client. Both methods of specifying the community string are provided in To Create the JumpStart Finish Script.

      You are prompted for the Sun Management Center server host name.

    3. Specify the Sun Management Center server host name.

      Type the name of the machine on which the Sun Management Center server was installed.

      The setup process checks whether the SNMP port is in use.

      • If SNMP port 161 is not in use, you are asked whether you want to start the Sun Management Center agent. Go to Step e.

      • If SNMP port 161 is in use, you are prompted to assign an SNMP port number.

    4. Resolve the SNMP port conflict.

      Type the same port number that you provided during Sun Management Center server setup in Step f in Setting Up Sun Management Center.

    5. Start the Sun Management Center agent.

      Caution – Caution –

      If your network uses Network Address Translation (NAT), type n to exit setup without starting Sun Management Center. Use the es-config command-line utility described in To Enable NAT Support to configure the machine for NAT before you start Sun Management Center.

  7. Copy the install and setup response files to the JumpStart profile server.

    As an example in the previous steps, the Sun Management Center install response file install.cfg was created on the prototype machine in the directory /response-files. The Sun Management Center setup response file setup.cfg was also created on the prototype machine in the directory /response-files.

    Assume that your JumpStart profile server is named bootserver01, and the JumpStart profile directory on machine bootserver01 is /export/home/JumpStart/jumpstart. Also assume that you have enabled write-access to the JumpStart profile directory from the prototype machine. You would then copy the response files from the prototype machine to the JumpStart profiles directory on the JumpStart machine. For example:


    # cd /response-files
# cp install.cfg /net/bootserver01/export/home/JumpStart/jumpstart
# cp setup.cfg /net/bootserver01/export/home/JumpStart/jumpstart

  8. Log in as root on the machine where you created the JumpStart profile directory.

  9. Go to the JumpStart profile directory that you created in Step 2, in To Create the JumpStart Install Server and Profile Directory.

  10. Edit the Sun Management Center install response file.

    You must edit the install response file so that it can be used by JumpStart. The install response file is the file name you specified in Step 4. Make the following changes to the install response file:

    • Change the SOURCE_DIRECTORY value to /a/mnt/disk1/image. The /a/mnt/disk1/image corresponds to the $MNTDIR value specified in the JumpStart finish script.

    • Change the TARGET_DIRECTORY value to /a/target_directory, where target_directory is the directory on each install client where the Sun Management Center base agent is to be installed.

    • Change the value of the SETUP_NOW parameter to zero. Setting the value of the SETUP_NOW parameter to zero ensures that the Sun Management Center setup does not automatically run on each install client when the Sun Management Center base agent has been installed.

    The following sample shows a basic Sun Management Center install response file after edits have been completed.

    SUNMC_VERSION=4.0
ENVIRONMENT=1
SOURCE_DIRECTORY=/a/mnt/disk1/image
TARGET_DIRECTORY=/a/opt
OSVERS=8
PRTOUT= Sun Microsystems sun4u PCI (UltraSPARC-II 450MHz)
LAYER.SERVER=0
LAYER.AGENT=1
LAYER.CONSOLE=0
SETUP_NOW=0

    The value of the PRTOUT parameter is not important because the base agent is platform independent. However, JumpStart requires this parameter to be present. Do not delete the PRTOUT parameter.

  11. Edit the Sun Management Center setup response file.

    You must edit the setup response file so that it can be used by JumpStart. The setup response file is the file name that you specified in Step 6. Make the following changes to the setup response file if needed:

    • Make sure that the server name specified by the SUNMC_SERVER parameter is the name of the Sun Management Center 4.0 server machine.

    • Make sure that the value of the START_SUNMC parameter is set to 1 (one). Setting the value of the START_SUNMC parameter to 1 ensures that the Sun Management Center base agent is started after it has been set up.

    • Make sure that the agent_OPTIONAL_PORT parameter is present, and that the assigned value is either a valid port number, or the text string DEFAULT.

    • Make sure that all of the parameters in the sample setup response file shown below are present.

    The following examples show a Sun Management Center setup response file before and after JumpStart edits have been applied. In both examples, bootserver01 is the name of the Sun Management Center server machine.

Example 6–1 Setup Response File Before JumpStart Edits Are Applied

SUNMC_SERVER=bootserver01
agent_OPTIONAL_PORT=1161
START_SUNMC=1
Example 6–2 Setup Response File After JumpStart Edits Are Applied

DISABLE_SNMPDX_DAEMON=1
STOP_SNMPDX=1
SUNMC_SERVER=bootserver01
agent_OPTIONAL_PORT=1161
START_SUNMC=1

In this example, the line DISABLE_SNMPDX_DAEMON=1 disables the SNMP daemon. The line STOP_SNMPDX=1 stops the SNMP daemon. The line SUNMC_SERVER=bootserver01 specifies that the base agent Sun Management Center server host is the machine named bootserver01. The line agent_OPTIONAL_PORT=1161 assigns port 1161 to the agent. The line START_SUNMC=1 starts the base agent when base agent setup is complete.

ProcedureTo Create the JumpStart Profiles

  1. Log in as root on the machine where you created the JumpStart profile directory.

  2. Go to the JumpStart profile directory that you created in Step 2, in To Create the JumpStart Install Server and Profile Directory.

  3. Create a JumpStart profile for each type of install client on which you will install the Sun Management Center base agent.

    You can create a JumpStart profile either by copying an appropriate sample profile from the samples in the directory, or by using the following example as a template. Save each JumpStart profile that you create in the JumpStart profile server directory, and record the name of each profile you create.

    Caution – Caution –

    Do not use a sample profile as the actual profile. Edit the profile to meet the JumpStart requirements, as described in “Creating a Profile” in Solaris 9 9/04 Installation Guide.

    The following examples show sample JumpStart profiles. The first example shows a profile that is used for a fresh Solaris operating environment install. The second example shows a profile that is used for Solaris operating environment upgrade.

Example 6–3 Sample JumpStart Profile: Fresh Solaris Operating Environment Install

#
# all_9000_t0+swap
#
install_type    initial_install
system_type     standalone
partitioning    explicit
#
filesys         c0t0d0s1        2024    swap
filesys         c0t0d0s0        6120    /
filesys         c0t0d0s7        free    /export/home
#
cluster         SUNWCall 
package         SUNWabe             delete
cluster         SUNWCapache         delete
cluster         SUNWCdhcp           delete
cluster         SUNWClux            delete
cluster         SUNWCfct            delete
cluster         SUNWCnet            delete
package         NSCPcom             delete
Example 6–4 Sample JumpStart Profile: Upgrade Solaris Operating Environment Install

install_type    upgrade

ProcedureTo Create the JumpStart Finish Script

  1. Log in as root on the machine where you created the JumpStart profile directory.

  2. Go to the JumpStart profile directory that you created in Step 2, in To Create the JumpStart Install Server and Profile Directory.

  3. Create the JumpStart finish script.

    Review Security Considerations for Finish Scripts. Then, depending on your security requirements, use either of the following sample finish scripts as a guideline to create the finish script in the JumpStart profile directory.

    The first example shows a finish script in which the password seed and community string are hard coded. The second example shows a finish script that will prompt for the password seed and community string.

    Save your finish script with the sh extension, for example, base_agent_finish.sh.

Example 6–5 Sample Finish Script: Security Password Seed and Community String Hard Coded

#!/bin/sh
#
# Program type      : Unix bourne shell script
# Description       : Standard finish script for installing and 
#                     setting up Sun Management Center core agent
#
#
#
ROOTDIR=${ROOTDIR:-/a}               # Root directory for new OS
MNTDIR=${ROOTDIR}/mnt
LOGDIR=${ROOTDIR}/var/tmp/sunmcfinish
SI_CONFIG_DIR=${SI_CONFIG_DIR:-/export/home/JumpStart/jumpstart}
INSTALL_RESP=${SI_CONFIG_DIR}/install.cfg
SETUP_RESP=${SI_CONFIG_DIR}/setup.cfg
#
#
# Begin Main Program
#
#
umask 022
mkdir -p $LOGDIR
#
# Copy the install and setup response file to target system
#
cp ${INSTALL_RESP} $LOGDIR
cp ${SETUP_RESP} $LOGDIR
#
# mount Sun Management Center image
#
mount -F nfs bootserver01:/export/home/JumpStart/AgentImage $MNTDIR
[ $? -ne 0 ] && exit 1
# 
# run es-inst with -a -R -T and -A options
# skip the next line for Flash Archive based deployment
# Do not use the -T option if you have specified the TARGET_DIRECTORY 
# tag in install.cfg
#
${MNTDIR}/disk1/sbin/es-inst -a -R /a -T /a/opt -A ${LOGDIR}/install.cfg
#
# Clean up any rc script with the same name if present
#
test -f ${ROOTDIR}/etc/rc3.d/S80SunMCJumpStart && \
rm -f ${ROOTDIR}/etc/rc3.d/S80SunMCJumpStart
rm -f /etc/init.d/SunMCJumpStart
#
# Place rc script in rc3.d and init.d to do setup
# Remember to access es-setup based on the target directory location
#
echo "Creating rc script..."
cat > ${ROOTDIR}/etc/rc3.d/S80SunMCJumpStart << EOF
#!/sbin/sh
#
rm /etc/rc3.d/S80SunMCJumpStart /etc/init.d/SunMCJumpStart
SECURITY_SEED=abc123
SNMPV1_STRING=private
export SECURITY_SEED SNMPV1_STRING
/opt/SUNWsymon/sbin/es-setup -e -A /var/tmp/sunmcfinish/setup.cfg
EOF
cp ${ROOTDIR}/etc/rc3.d/S80SunMCJumpStart \
     ${ROOTDIR}/etc/init.d/SunMCJumpStart
exit 0
Example 6–6 Sample Finish Script: Prompt for Security Password Seed and Community

#!/bin/sh
#
# Program type      : Unix bourne shell script
# Description       : Standard finish script for installing and 
#                     setting up Sun Management Center core agent
#
#
#
ROOTDIR=${ROOTDIR:-/a}               # Root directory for new OS
MNTDIR=${ROOTDIR}/mnt
LOGDIR=${ROOTDIR}/var/tmp/sunmcfinish
SI_CONFIG_DIR=${SI_CONFIG_DIR:-/export/home/JumpStart/jumpstart}
INSTALL_RESP=${SI_CONFIG_DIR}/install.cfg
SETUP_RESP=${SI_CONFIG_DIR}/setup.cfg
#
#
# Begin Main Program
#
#
umask 022
mkdir -p $LOGDIR
#
# Copy the install and setup response file to target system
#
cp ${INSTALL_RESP} $LOGDIR
cp ${SETUP_RESP} $LOGDIR
#
# mount Sun Management Center image
#
mount -F nfs bootserver01:/export/home/JumpStart/AgentImage $MNTDIR
[ $? -ne 0 ] && exit 1
#
# Read secure inputs from user who invoked boot net - install
#
echo "Enter Security seed:"
read SECURITY_SEED
echo "Enter SNMP string:"
read SNMPV1_STRING
#
# run es-inst with -a -R -T and -A options
# skip the next line for Flash Archive based deployment
# Do not use the -T option if you have specified the TARGET_DIRECTORY 
# tag in install.cfg
#
${MNTDIR}/disk1/sbin/es-inst -a -R /a -T /a/opt -A ${LOGDIR}/install.cfg
#
# create a temporary es-setup script to use the secure information 
# read earlier
# Remember to access es-setup based on the target directory location 
#
FILE2=/a/opt/SUNWsymon/sbin/es-setup
FILE=/a/opt/SUNWsymon/sbin/es-setup.jumpstart
mv $FILE2 $FILE
count=`wc -l $FILE`
count=`echo $count | cut -d' ' -f1`
ncount=$count
count_enter=`expr $ncount - 3`
while [ $ncount -gt 0 ] ; do
   k=`tail -$ncount $FILE | head -1`
   if [ $ncount -eq $count_enter ]
   then
       echo $k >> $FILE2
       echo "SECURITY_SEED=$SECURITY_SEED" >> $FILE2
       echo "SNMPV1_STRING=$SNMPV1_STRING" >> $FILE2
   else
       echo $k >> $FILE2
   fi
   ncount=`expr $ncount - 1`
done
chmod +x $FILE2
#
# Clean up any rc script with the same name if present
#
test -f ${ROOTDIR}/etc/rc3.d/S80SunMCJumpStart && \
rm  -f ${ROOTDIR}/etc/rc3.d/S80SunMCJumpStart \
rm -f /etc/init.d/SunMCJumpStart
#
# Place rc script in rc3.d and init.d to do setup and cleanup 
# Remember to access es-setup based on the target directory location
# 
echo "Creating rc script..."
cat > ${ROOTDIR}/etc/rc3.d/S80SunMCJumpStart << EOF
#!/sbin/sh
#
rm /etc/rc3.d/S80SunMCJumpStart /etc/init.d/SunMCJumpStart
/opt/SUNWsymon/sbin/es-setup -e -A /var/tmp/sunmcfinish/setup.cfg
mv /opt/SUNWsymon/sbin/es-setup.jumpstart /opt/SUNWsymon/sbin/es-setup
EOF
cp ${ROOTDIR}/etc/rc3.d/S80SunMCJumpStart \
   ${ROOTDIR}/etc/init.d/SunMCJumpStart
exit 0

ProcedureTo Create the JumpStart Rules File

  1. Log in as root on the machine where you created the JumpStart profile directory.

  2. Go to the JumpStart profile directory that you created in Step 2, in To Create the JumpStart Install Server and Profile Directory.

  3. Create the JumpStart rules file.

    Use the following example rules file as a template, and create the rules file in the JumpStart profile directory.

Example 6–7 Sample Rules File

#
# rule keywords and rule values   begin script   profile    finish  script 
# ------------------------------  ------------   -------    --------------
  
# This rule matches one system: 
#
hostname bootserver01            -         basic_prof  base_agent_finish.sh 
 
 
# This is a complex rule:
#
network 192.43.34.0 && ! model \ 
 SUNW,SPARCstation-20                 -         net_prof         - 
 
 
# This rule applies to all 
# SUNW,SPARCstation-LX:
#
model SUNW,SPARCstation-LX            -         lx_prof     complete.sh
 
 
# Another complex rule:
#
network 193.144.2.0 && karch i86pc   init.sh    IA_prof     done.sh
 
#
# You can use system attributes like RAM size and architecture to 
# classify targets:
#
memsize 16-32 && arch i386           -          prog_prof        -
 
 
# rules are matched top-down. If nothing matches, this rule will apply:
#
any                  -               -         generic_prof     -

ProcedureTo Validate Your JumpStart Files

  1. Log in as root on the machine where you created the JumpStart profile directory.

  2. Go to the JumpStart profile directory that you created in Step 2, in To Create the JumpStart Install Server and Profile Directory.

  3. Type ./check to validate your JumpStart files.


    # ./check  
Validating rules... 
Validating profile basic_prof... 
Validating profile net_prof... 
Validating profile lx_prof... 
Validating profile IA_prof... 
Validating profile prog_prof... 
Validating profile any_machine... 
The custom JumpStart configuration is ok. 
# cat rules.ok 
hostname bootserver01          -         basic_prof      base_agent_finish.sh 
network 192.43.34.0 && ! model \ 
 SUNW,SPARCstation-20                    -         net_prof        - 
model SUNW,SPARCstation-LX             -         lx_prof         complete.sh
network 193.144.2.0 && karch i86pc       init.sh   IA_prof         done.sh
memsize 16-32 && arch i386               -         prog_prof       -      
any -                                    -         generic_prof    -

ProcedureTo Add Install Client Information to the JumpStart Server

  1. Log in as root on the JumpStart server.

  2. Insert the Solaris installation CD 1 of 2 in your CD-ROM drive.

    Go to the Tools directory on the CD.


    # cd /DiskMountDir/s0/Solaris_2.8/Tools

  3. Determine the system identification information for each install client.

    The JumpStart server requires the following information about each install client.

    • Name

    • Ethernet address

    • IP address

    • Architecture

    Log on to each install client, and use the arp and uname commands as follows to display the install client's Ethernet address, IP address, name, and architecture. 


    > arp clienthost
clienthost (111.222.123.124) at 8:0:80:e4:23:eb permanent published
> uname -a
SunOS clienthost 5.9 Generic_112233-01 sun4u sparc SUNW

    In the above example, the clienthost install client Ethernet address is 8:0:80:e4:23:eb, the IP address is 111.222.123.124, and the architecture is sun4u.

  4. Add the system identification information for each install client to the JumpStart server.

    The add_install_client command is used to add the install client information to the JumpStart server as follows: 


    add_install_client \
-c JumpStart_profile_server:path_to_configuration_directory \
-s JumpStart_install_server:path_to_operating_environment_image \
-p JumpStart_profile_server:path_to_SYSIDCFG_file \
-e install_client_ethernet_address \
-i install_client_IP_address \
install_client_name install_client_architecture

    For example, assume your systems are configured as follows.

    • Machine bootserver01 is your JumpStart boot server, profile server, and install server.

    • The JumpStart configuration directory on bootserver01 is /export/home/JumpStart/jumpstart.

    • The JumpStart operating environment image directory on bootserver01 is /export/home/JumpStart/Solaris_9.

    • The system identification configuration file sysidcfg is located in the JumpStart configuration directory /export/home/JumpStart/jumpstart.

    • The install client Ethernet address is 8:0:80:e4:23:eb, and the IP address is 111.111.123.124.

    • The install client's name is clienthost, and the install client's architecture is sun4u.

    You would then add the install client clienthost using the add_install_client command as follows.


    # ./add_install_client -c bootserver01:/export/home/JumpStart/jumpstart \
  -s bootserver01:/export/home/JumpStart/Solaris_9 \
  -p bootserver01:/export/home/JumpStart/jumpstart \
-e 8:0:80:e4:23:eb -i 111.111.123.124 \
  clienthost sun4u 
  Adding Ethernet number for clienthost to /etc/ethers
  making /tftpboot
  enabling tftp in /etc/inetd.conf
  starting rarpd
  starting bootparamd
  updating /etc/bootparams
  copying inetboot to /tftpboot

    When you have finished adding install client system information to the JumpStart server, you can then use JumpStart to install the Solaris operating environment and the Sun Management Center base agent as described in the next step.

    For further information about the add_install_client command and options, see the man page add_install_client(1m).

  5. Boot each install client.

    1. Logon as root on the client machine in single-user mode.

    2. At the ok prompt, type the command boot net - install.

      For example:


      {2} ok boot net - install

      The client system boots from the JumpStart server. JumpStart installs the Solaris operating environment specified by the JumpStart profile assigned to the install client by the applicable rule in the rules file. When the operating environment has been installed, the Sun Management Center 4.0 base agent is installed. The install client then reboots.

      When the install client reboot completes, the Sun Management Center base agent is set up according to the specifications of the finish script assigned to the install client by the applicable rule in the rules file. If you hard coded the security password seed and the SNMP community string in the finish script, base agent setup is automatic. If you chose not to hard code the password seed and community string in the finish script, you must respond to the base agent setup prompts on each install client to complete base agent setup.

Configuring Server and Agent on Multi-IP Machines

This section describes how to configure the Sun Management Center 4.0 server and agent on multi-IP machines.

Server Configuration

When installed on a system with multiple IP interfaces, the Sun Management Center 4.0 server is configured, by default, to support all agents on all of the IP interfaces.

The esmultiip command enables you to list, remove, or add an IP interface. The syntax of the esmultiip command is as follows:

esmultiip [-lh] | [ < -a | -d > Host-IP ]

The following table describes the esmultiip command parameters.

Table 6–2 esmultiip options

Option 

Modifying Options 

Definition 

 

 

Enable the multi-IP feature on the Sun Management Center server if more than one IP interface is present. 

-h

 

List the options for esmultiip

-l

 

List all of the active IP interfaces of the Sun Management Center server 

-a

Host-IP

Add the host name corresponding to the IP address Host-IP to the list of active server IP interfaces

-d

Host_IP

Remove the host name corresponding to the IP address Host-IP from the list of active server IP interfaces

Note –

The following procedures assume that the Sun Management Center server has been installed on the multi-IP machine in the directory /opt. If you installed the agent in a different directory, replace /opt with the name of the directory that you specified.

ProcedureTo Add an IP Interface to the Sun Management Center Server

  1. Log in as root on the server multi-IP machine.

  2. List the current Sun Management Center active IP interfaces.

    Type the command /opt/SUNWsymon/sbin/esmultiip -l. For example:


    # /opt/SUNWsymon/sbin/esmultiip -l
Multi IP configured with active interfaces "10.1.2.111"

  3. List all IP interfaces on the machine.

    Type the command ifconfig -a. For example:


    # ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000 
hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 10.1.2.111 netmask ffffff00 broadcast 10.1.2.255
        ether 8:0:20:a8:7a:c9 
hme1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
        inet 129.1.2.222 netmask ffffff00 broadcast 129.199.199.255
        ether 8:0:20:a8:7a:c9

    As shown by the above examples, only IP interface hme0 at IP address 10.1.2.111 is being used by the Sun Management Center server.

  4. Add an IP interface.

    Assume that you want to add the IP interface hme1 at IP address 129.1.2.222. You would then type the command /opt/SUNWsymon/sbin/esmultiip -a 129.1.2.222.

    The IP interface is added to the list of active Sun Management Center server interfaces.

ProcedureTo Remove an IP Interface From the Sun Management Center Server

  1. Log in as root on the server multi-IP machine.

  2. List the current Sun Management Center active IP interfaces.

    Type the command /opt/SUNWsymon/sbin/esmultiip -l. For example:


    # /opt/SUNWsymon/sbin/esmultiip -l
Multi IP configured with active interfaces "10.1.2.111 129.1.2.222"

  3. Remove an IP interface.

    Assume that you want to remove the IP interface hme1 at IP address 129.1.2.222. You would then type the command /opt/SUNWsymon/sbin/esmultiip -d 129.1.2.222.

    The IP interface is removed from the list of active Sun Management Center server interfaces.

Agent Configuration

If the Sun Management Center 4.0 agent is configured to use one IP interface on a multi-IP machine, and another IP interface is configured for use by the server, then the Sun Management Center agent on the multi-IP machine cannot communicate with the Sun Management Center server.

The agent must be reconfigured to use the same IP interface as the server

Note –

The following procedure assumes that only the Sun Management Center agent has been installed on the multi-IP machine in the directory /opt. If you installed the agent in a different directory, replace /opt with the name of the directory that you specified.

ProcedureTo Configure the Sun Management Center Agent on a Multi-IP Machine

  1. Log in as root on the multi-IP agent machine.

  2. Determine which IP address the agent is using.

    Type the command uname -n to display the machine name. 


    # uname -n
u60-01

    The agent is configured to run on the IP address corresponding to the machine name reported by uname -n. In this example, the agent is configured to run on the IP interface assigned to machine name u60–01.

  3. Determine the IP interface addresses.

    Type the command cat /etc/hosts to display the machine name assigned to each IP interface.

    For example:


    # uname -n
u60-01
# cat /etc/hosts
127.0.0.1       localhost
10.1.2.111      u60-01      loghost
10.2.3.222      u60-01-ip2

    In the above examples, uname-n showed u60–01, and u60–01 is assigned to the IP interface 10.1.2.111.

    If you want to configure the Sun Management Center agent to run on a different IP interface, reassign the agent to use the required IP interface as described in the following steps.

  4. Stop the agent if it is running.

    Type the command /opt/SUNWsymon/sbin/es-stop -A.

    All Sun Management Center processes are stopped.

  5. Change the machine name to the name assigned to the appropriate interface.

    Assume that the agent uses IP interface 10.1.2.111, which is named u60–01. Also assume you want to reassign the agent to use IP interface 10.2.3.222, which is named u60–01-ip2.

    You would then reassign to agent to IP interface 10.2.3.222 by typing the command uname -S u60–01–ip2.

  6. Set up the agent.

    You must set up the agent again to enable the agent to use the new IP interface assignment.

    Type the command /opt/SUNWsymon/sbin/es-setup -F.

    You are prompted for the security key seed.

    1. Specify the Sun Management Center security key.

      Type the same security seed password that you provided during Sun Management Center setup in Setting Up Sun Management Center, Step b. Type the password again to confirm.

      You are prompted for the SNMPv1 community string.

    2. Specify the SNMPv1 community string.

      Type the same community string that you provided during Sun Management Center setup in Setting Up Sun Management Center, Step c. If you used the default value public, press Return.

      You are informed that server-host-name appears to be configured as your Sun Management Center server, where server-host-name is the name of the machine where the server was installed.

      • If the displayed server name is correct, type y.

      • If the displayed server name is not correct, type n. You are prompted to provide the Sun Management Center host name.

        Type the name of the machine where the server is installed.

      The agent is set up to use the new IP address.

      Note –

      If you installed any add-on agent components, you might be asked to set up the add-on components as well.

    Agent configuration is now complete, and you can restart the agent.

  7. Restart the agent.

    Type the command /opt/SUNWsymon/sbin/es-start -A.

Installing Sun Management Center 4.0 on Microsoft Windows

Only the Sun Management Center console and the console components of some add-ons can be installed on Microsoft Windows. The Microsoft Windows machine must be accessible by your Solaris or UNIX network, and must have access to your network for the console to work.

Caution – Caution –

Before you install Sun Management Center 4.0 on any Microsoft Windows platform, make sure that you have set the Java environment variables and path as described in Java Environment Variables and Path. Installation will fail if JDK 1.5 or higher version is not installed and configured.

ProcedureTo Install Sun Management Center 4.0 on Microsoft Windows

  1. Log in as administrator, or as a user with administrator privileges.

  2. Run Windows Explorer.

  3. Review the README file.

    If you are installing from the DVD, insert Sun Management Center 4.0 DVD in the DVD drive, and then use Windows Explorer to navigate to and open /install/windows_install_readme.txt.

    If you are installing from the Sun Management Center image, use Windows Explorer to navigate to and open /net/machine-name/imagedir /disk1/install/windows_install_readme.txt.

  4. Use the Windows Explorer to navigate to /install/install.bat and double-click the icon.

  5. The Welcome window appears.

    Ensure that you have the information listed, and then click Next.

    The Specify the Installation Destination Directory window appears.

  6. Specify the installation directory.

    You are prompted for the directory in which to install Sun Management Center. The default location is C:\Program Files\SUNWsymon. The Sun Management Center 4.0 console can be installed in any location on your system where the minimum required disk space is available.

    Click Next to accept the default of C:\Program Files\SUNWsymon, or browse to a directory name, select the directory, and then click Next.

    • If the directory exists, the Select Add-on Products window appears.

    • If the directory does not exist, you are informed that the directory does not exist, and asked Create it now?.

      Click Create. The window closes.

      Click Next in the Specify the Installation Destination Directory window.

      The Select Add-on Products window appears.

  7. Select the add-ons that you want to install, and then click Next.

    The Disk Space Check window appears.

    • If there is enough free disk space to install Sun Management Center, the Confirmation window appears.

    • If there is not enough free disk space, you are prompted to specify a different directory, or to browse to and select a different directory.

      The disk space check is run again. If the directory does not have enough space, you are again prompted to specify a directory that contains enough free space. If the directory that you specified has sufficient space, the Confirmation window appears.

  8. Confirm installation selections.

    A list of your selections is displayed.

    • Confirm the selections. If the list is correct, click Next to start installation of Sun Management Center.

    • If the list is not correct, click Back to return to the Select Add-on Products window to select the products that you want to install.

    The installation in progress screen appears.

  9. Complete the installation process.

    When the installation process completes, a list of installed products is displayed. Click Close.

See Also

This concludes the Microsoft Windows installation process. Setup and configuration is not required for the Sun Management Center console on Microsoft Windows systems. You can now run the Sun Management Center console as directed by To Start the Console on Microsoft Windows.