Chapter 2 Issues

This chapter describes the known issues.

The known issues are the following:

• Unable to create base-only image of Solaris 8, Solaris 7, and Solaris 2.6 OS using es-imagetool and es-gui-imagetool. (6252625)

• Imagetool and agent-update do not work for Solaris 10.

• Agent-Update install client on Solaris 10 hangs (6216723). This is described below.

• Base-Only installation using agent-update fails to add essential patches (6219534). This is described below.

• Incremental upgrade of PRM to update 1b gives misleading message (6252406). This is described below.

• CD1 gets locked during server install using GUI installation utility (6219648). This is described below.

Agent-Update Install Client on Solaris 10 Hangs (6216723)

Agent-Update's install client does not use the -G option (global zone) for installing the bootstrap package SUNWessmu. On a Solaris 10 system with zones running, the install client hangs during the pkgadd of SUNWessmu, because the -G option is not used.

Workaround: None

Base-Only Installation Using Agent-Update Fails to Add Essential Patches (6219534)

If you create an agent-update image that included the base product and any add-on product, this information does not apply. This information applies when you use either es-imagetool or es-gui-imagetool to create an agent-update image of the base product only (that is, no add-ons in the image).

Workaround: There are two scenarios, depending on the operating system you are using.

To deploy Solaris 2.6 to Solaris 9 base agent images from a from a 3.5.1a server (Solaris 8 Sun Management Server with patch 118388-03, Solaris 9 or Solaris 10 Sun Management Server with patch 118389-03) using agent-update.bin or Job Manager, follow these steps:

1. Deploy the agent image on the target host.

2. Deploy the patch image on the target host.

To deploy Solaris 10 base agent only image from a Sun Management Center 3.5 Update 1a server (Solaris 8 Sun Management Server with patch 118388-03, Solaris 9 or Solaris 10 Sun Management Server with patch 118389-03) using agent-update.bin, follow these steps:

1. Pull the agent image using agent-update.bin and ignore the following message at the end of agent-update.bin:

   es-inst command will be timed out in 3600 seconds

   es-inst passed

   Doing setup of base product ...

   setup of base product will be timed out in 1800 seconds

   base setup failed

   install scripts failed

   Error: running InstallClient

   Error: running InstallClient with error code -1

2. Apply the patch for the base agent on Solaris 10 (patch 118389-03) located on the second CD at:

   <mount-point>/image/Patches/Essential/Solaris_9

3. Run es-setup and complete the agent installation.

Incremental Upgrade of PRM to Update 1b Gives Misleading Message (6252406)

During the upgrade of Performance Reporting Manager (PRM) add-on to the Sun Management Center 3.5 Update 1b patch, the console shows patchadd error message for 117438-04 patch. The installer tries to add this patch twice. Hence, the messages are misleading. Ignore the error messages.

Workaround: None

CD1 Gets Locked During Server Install Using GUI Installation Utility (6219648)

To work around this problem, you have two main choices.

Workaround: There are two scenarios, depending on your preference.

• Use the command-line installation utility (es-inst) for installing the server layer.

• Use the GUI-based installation utility (es-guiinst) with one of the following three options:

  1. Copy both disks (CD1 and CD2) onto a disk drive locally as explained below.

     CD1 must be copied to <target-directory>/disk1 and CD2 to <target-directory>/disk2.

  2. Load CD1 and CD2 in different CD drives and NFS mount them so that CD1 is mounted on the target host as <mount-directory>/disk1 and CD2 is mounted as <mount-directory>/disk2.

  3. Download the web image from http://www.sun.com onto a system, which has the structure as specified in option 1.

• After doing any of the above options, run es-guiinst from the disk1/sbin directory.