test

Sun Management Center 3.5 Update 1a Release Notes

Chapter 1 Installation Issues

Issues include information that you should know about, such as prerequisites, tips, troubleshooting hints, and bugs. Bugs are a subset of issues. Bugs have tracking numbers shown in parentheses. For updates on bugs and for patches, see the SunSolveSM web site at http://sunsolve.sun.com.

Patches for Sun Management Center 3.5 Update 1a

These release notes apply to the following patches:

 

Solaris 2.6 

Solaris 7 

Solaris 8 

Solaris 9 

Solaris SPARC 

       

Core 

118386–03 

118387–03 

118388–03 

118389–03 

System Reliability Manager 

118836–01 

118837–01 

118838–01 

118839–01 

Performance Reporting Manager 

117436–02 

117437–02 

117438–02 

117439–02 

N1 GridTM Console - Container Manager

   

118728–01 

118729–01 

Hardware Diagnostics and Advanced System Monitoring 

   

118933–01 

118933–01 

Solaris x86 

       

Core 

     

117429–01 

System Reliability Manager 

     

118840–01 

Performance Reporting Manager 

     

118350–01 

N1 Grid - Console Container Manager 

     

118730–01 

Installation Issues

Solaris 2.6 and Solaris 7 Agent Installation from CD Fails

If you install the Sun Management Center 3.5 Update 1a CD image on a Solaris 2.6 or Solaris 7 agent, the installation fails because a decompression utility is missing.

Workaround: To get the decompression utility, follow these steps:

  1. Go to the web site http://sunfreeware.com.

  2. Click on the link for your operating system, either SPARC/Solaris 2.6 or SPARC/Solaris 7.

  3. Download the package bzip2-1.0.2 (SMCbzip2).

  4. Install the SMCbzip2 package:


    # pkgadd SMCbzip2

    The package is installed in /usr/local/bin directory.

  5. Create a soft link from /usr/bin/bzcat to /usr/local/bin/bzcat.


    # ln -s /usr/local/bin/bzcat /usr/bin/bzcat

  6. Install the Sun Management Center 3.5 Update 1a agent.

Solaris 10 Issues and Bugs

You can run Sun Management Center on systems running the Solaris 10 operating system. If you install and use the product on a system running Solaris 10, note the following:

patchadd in Solaris 10 Does Not Support Incremental Patching (6219176)

On Solaris 10 systems, installing a patch incrementally to a Sun Management Center layer (server, console, agent) or add-on works differently than on Solaris 9 and earlier systems.

On Solaris 9 and earlier systems, you can install a patch to the Sun Management Center console and then add the agent layer and apply the same patch. The patch installer knows which packages within the patch applied to which layer or add-on.

On Solaris 10 systems, if you install a patch to the Sun Management Center console and then add the agent layer and apply the same patch, the installer sees only that the patch was installed and exits.

Workaround: Remove the patch by using the patchrm command and then use the es-inst command to install the patch.

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)

Note –

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 3.5.1a server (Solaris 8 Sun Management Server with patch 118388-03, Solaris 9/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 3.5.1a server (Solaris 8 Sun Management Server with patch 118388-03, Solaris 9/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 id 118389-03) located on the second CD at:


    mount-point/image/Patches/Essential/Solaris_9

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

Core Product Only Install Fails to Install Essential Patch from Image Created by es-makeagent (6219541)

If you install the core product only (no add-ons), the installation fails to install the essential patch from the image created by es-makeagent.

Workaround: Apply the patch manually on the agent host. The patches for the core product are located on second CD at:


mount-point/image/Patches/Essential

CD 1 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.