test

Sun Management Center 3.5 Installation and Configuration Guide

Creating Agent Installation and Update Images

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 two image tools 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 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. Conversely, you must copy or ftp 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 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.

To 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 in To Install Sun Management Center 3.5 on the Solaris Platform, Step 8.

  1. Log in as root on the Sun Management Center 3.5 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 3.5 source directory.

    The installation source default /cdrom/cdrom0/image is displayed.

    • If you are installing from CDs, insert Sun Management Center 3.5 CD 1 of 2 in the CD-ROM drive.

      When the CD-ROM drive LED turns off, press Return to accept the default /cdrom/cdrom0/image.

    • If you are installing from a Sun Management Center 3.5 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.. For example:


      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 3.5 disk1 and disk2 CD 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 Update Image Name screen appears. Go to Step 6.

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

    The target directory is the directory where the Sun Management Center 3.5 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.0 is installed in /opt/SUNWsymon on machine A.

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

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

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

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

    When you apply the Sun Management Center 3.5 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 3.5 agent is reinstalled and replaces the version 3.0 agent in directory /opt/SUNWsymon.

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

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

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

    • On machine E, the base agent is upgraded, with add-on packages, to version 3.5 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 Base-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 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.

    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.

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

To 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 in To Install Sun Management Center 3.5 on the Solaris Platform, Step 8.

  1. Log in as root on the Sun Management Center 3.5 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 3.5 source directory.

    • If you are installing from CDs, type the path to the Sun Management Center 3.5 installation CD 1 image directory. For example:


      Enter a valid source directory: /cdrom/cdrom0/image

    • If you are installing from a Sun Management Center 3.5 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 3.5 disk1 and disk2 CD 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 3.5 installation.

    The target directory is the directory where the Sun Management Center 3.5 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.0 is installed in /opt/SUNWsymon on machine A.

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

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

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

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

    When you apply the Sun Management Center 3.5 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 3.5 agent is reinstalled and replaces the version 3.0 agent in directory /opt/SUNWsymon.

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

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

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

    • On machine E, the base agent is upgraded, with add-on packages, to version 3.5 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, 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 Solaris versions for the target machines.

    The image tool creates images for all Solaris versions supported by Sun Management Center irrespective of the Solaris 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 Solaris versions.

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

    • Reply y if the target machines include all Solaris 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 Solaris versions.

      Each version of Solaris 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 Solaris_2.6 ? [y|n|q] n
Do you want to create images for Solaris_7 ? [y|n|q] n
Do you want to create images for Solaris_8 ? [y|n|q] y
Do you want to create images for Solaris_9 ? [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 3.5 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.

To Create a Patch-Only Image Using the Image Tools

Sun Management Center-specific patches are released periodically on the Sun Management Center website 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 3.5 server machine.

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

    Go 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_2.6 Solaris_7 Solaris_8 Solaris_9

    The directories must be created using the names shown.

  3. Determine which Sun Management Center patches are available for download.

    Open a browser and go to http://www.sun.com/sunmanagementcenter. Click the Patches and Support link.

    Review the list of available patches that is displayed at the bottom of the page. Print the page so that you can reference the patch numbers.

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

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

  6. Uncompress the patch files.

    Go 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 ssume 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 8 , or by using the command-line tool es-imagetool as described in Step 9.

  7. Move the download patch files to another directory.

    If desired, either move the compressed download patch files to another directory for safekeeping, or delete the compressed patch files.

  8. 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 in To Install Sun Management Center 3.5 on the Solaris Platform, Step 8.

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

  9. 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 in To Install Sun Management Center 3.5 on the Solaris Platform, Step 8.

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

To 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 in To Install Sun Management Center 3.5 on the Solaris Platform, Step 8.

  1. Log in as root.

  2. Place Sun Management Center 3.5 CD 1 of 2 in the CD-ROM drive.

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

    You are prompted for the installation source files directory.

  4. Type /cdrom/cdrom0/image.

    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.

    When es-makeagent completes copying files from Sun Management Center 3.5 installation CD 1 of 2, the CD is ejected, and you are prompted to insert the second CD or specify the source directory for disk 2.

    1. Remove the first Sun Management Center installation CD.

      Place the Sun Management Center 3.5 CD 2 of 2 in the CD-ROM drive, then close the drive.

    2. When the CD-ROM drive LED turns off, press Return.

      es-makeagent copies the remaining files from the CD.

      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 12 in To Create CD Images.

  6. Type the command eject to eject the CD.

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

    Note –

    The agent-only installation image also contains a tar file that you can 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 on the Solaris Platform Using es-inst.