test

Sun Management Center 3.5 Release Notes

Chapter 1 Installation Issues

This chapter describes problems that relate to the installation of the Sun Management 3.5 software and add-on packages that are an extension of this software. You can find the Sun Management Center 3.5 documentation on the Sun Management Center 3.5 Software 2 of 2 CD. The information included in these Release Notes supersedes the information in the Sun Management Center Release Notes on the Sun Management Center 3.5 Software 2 of 2 CD. The Sun Management Center 3.5 Release Notes can be found in the Sun Management Center 3.5 Software Collection on http://docs.sun.com.

The following installation bug descriptions have been added to this chapter since this document was published on the Sun Management Center 3.5 Software 2 of 2 CD.

Installation Bugs

Installation Guide Patch-Only Procedures Produce Extra-Large Image (4858591)

If the directory for the patch image is created at the root level, as described by the Sun Management Center 3.5 Installation and Configuration Guide, the image tool includes the Sun Management Center /sbin and /lib subdirectories in the patch-only image. The result is that a larger than necessary patch image is created. The /sbin and /lib directories are not needed for a patch-only image.

Workaround: To avoid this problem, follow these steps.

  1. Create the following directory structure on the machine:


    /disk2/image/Patches/Solaris_2.6
..                  /Solaris_7
..                  /Solaris_8
..                  /Solaris_9

  2. Download and uncompress the patch files.

  3. Place the patch in the appropriate Solaris directory.

  4. Run the image tool. When prompted for the installation files source directory, specify /disk2/image.

Start Script Might Display Could not start Grouping service or Could not start Platform Agent Error Message (4851517)

If Sun Management Center components are started on a heavily loaded machine, the following error message might be displayed:


Could not start Component

In addition, if a particular component process does not start within a specific amount of time, the start script might display the same error message, even if the component was successfully started.

This problem has been observed for both the Grouping service and the Platform Agent components.

The start script has the following actions:

A heavily loaded machine can delay the results of the status check, which results in an erroneous status check failure. The error occurs because the results were not received within x seconds.

Workaround: Complete the following workaround:

  1. Use the /usr/bin/ps -eaf | grep esd command to verify whether the following processes are running:

    • Agent

    • Topology service

    • Trap-handler service

    • Configuration service

    • Event-handler service

    • Metadata service

    • Platform Agent

    • Instances of Platform Agent

  2. Use the /usr/ucb/ps —wwxa | grep SunMCService command to verify whether the Grouping service is running.

  3. Use the /usr/ucb/ps —wwxa | grep java | grep ServerMain command to verify whether the Java server is running.

  4. Use the /usr/ucb/ps —wwxa | grep java | grep tomcat command to verify whether the Web server is running.

  5. Use the /usr/ucb/ps —wwxa | grep java | grep HWDS command to verify whether the the Hardware Service is running.

If a service is not running, reduce the machine load, and restart the Sun Management Center processes.

es-makeagent Command Does Not Work From CD Image (4863944)

The es-makeagent command will not run from the CD or a CD image. The command issues the following error message and then exits to the system prompt:


You have called es-makeagent from the cd image.
/var/run/tmp/SunMCInstall/sbin/es-makeagent: illegal option -- L

Workaround: Run the es-makeagent command from the machine on which you have installed the Sun Management Center server. Use the following command:


# /opt/SUNWsymon/sbin/es-makeagent

where /opt is the directory where Sun Management Center 3.5 was installed. If you installed Sun Management Center 3.5 in a different directory, substitute /opt with the name of the top-level directory where you installed Sun Management Center.

Bug That Requires a Patch Before Installing Sun Management Center 3.5 on the Solaris Platform

Upgrading or Uninstalling Sun Management Center 3.0 Server Fails if Sun Management Center Change Manager 1.0 Server Is Installed (4820069)

If you have the Sun Management Center 3.0 server and the Sun Management Center Change Manager 1.0 server installed on your system, you must apply a patch before you attempt either of the following operations:

Workaround: Before you begin the upgrade or uninstallation process, apply one of the following patches to the system that is running the Sun Management Center 3.0 server software:

You can download the patches from the SunSolveSM Web site at http://sunsolve.sun.com.

Localization Issue

Unable to Install Localized PDF Documentation on Solaris 2.6, Solaris 7, or Solaris 8 Operating Environment

The localized PDF documentation package names are longer than nine characters. If you are installing the localized collections on a system that is running the Solaris 2.6, Solaris 7, or Solaris 8 operating environment, you need to apply appropriate patches to support these longer package names.

Workaround: Follow these steps to install localized PDF documentation packages in the Solaris 7 or Solaris 8 operating environment:

Note –

No patches exist at the time of this release for Solaris 2.6 servers.

  1. Log in to the system that is running the Solaris 7 operating environment or the Solaris 8 operating environment.

  2. Go to the SunSolve program patch site at http://sunsolve.Sun.COM/pub-cgi/show.pl?target=patches/patch-access.

  3. In the Find Patch field, provide the appropriate patch IDs from Table 1–1 .

    Note –

    Check the SunSolve site to make sure that you are downloading the current version of the patch.

    Table 1–1 Solaris Documentation Server Patches

    Operating Environment 

    Patches to Apply 

    Solaris 7 operating environment 

    107332-02 (library) 

    107443-14 

    Solaris 8 operating environment 

    110380-03 (library) 

    110934-04 

  4. Click Download HTTP or Download FTP for each patch you want to download.

  5. Change to the directory with the library .zip patch package.

  6. Unzip the library patch package.


    % unzip library-patch-id.zip

  7. Become superuser.

  8. Apply the patch.


    # patchadd library-patch-id

  9. Repeat Steps 5 through 8 for the second patch you downloaded in Step 4.

  10. Install the Sun Management Center 3.5 localized PDF collection packages.

Localization Bugs That Occur During Installation

Windows 98 Platform: Localized Versions of Console, Hardware Diagnostic Suite, and Performance Reporting Manager Might Not Work if Installed in Default Location (4884908)

On the Microsoft Windows 98 platform, if Sun Management Center 3.5 has been installed in the default location, (C:\Program Files\SunMC), you might not be able to use localized versions of the Console, Performance Reporting Manager, or Hardware Diagnositc Suite.

This problem occurs because the length of the name for the default location exceeds the internal limitation allowable in the Microsoft Windows 98 environment.

Note –

This limitation does not occur if the C locale is the only version of the product that is installed.

The following error message is displayed:


Out of Environment Space

The report service is not available

Please make sure the Hardware Diagnostic Suite server is
running on the Sun Management Center server machine.

Workaround: During installation of localized versions of the software, specify a location name that is shorter in length, C:\smc or C:\sunmc, for example.

For more information on specifying an alternate installation location, see Step 6 of the procedure, “To Install Sun Management Center 3.5 on Microsoft Windows” in Sun Management Center 3.5 Installation and Configuration Guide.

Incorrect Message About SUNWescom Package in Localized Environments Is Displayed (4840461)

During installation of a localized environment, the system displays an incorrect error message. The following error message is displayed:


SUNWescom : package not found

This error message is displayed only briefly.

Note –

The message is not displayed during installation of the C locale.

Workaround: Ignore the error message. The SUNWescom package has been installed successfully. Product functionality has not been impaired.

Binary Code License and Supplemental Terms and Conditions for Some Asian Locales Are in English (4882094)

During installation, the Binary Code License (BCL) and Supplemental Terms and Conditions for the following Asian locales are in English:

Language 

Locale 

Japanese 

ja_JP.UTF-8

Simplified Chinese 

zh.UTF-8

Traditional Chinese 

zh_TW.UTF-8

zh_HK.UTF-8

Korean 

ko.UTF-8

The following Asian locales use localized BCL files and are in the appropriate languages.

Language 

Locale 

Japanese 

ja, ja_JP.PCK

Simplified Chinese 

zh, zh.GBK, zh_CN.GB18030

Traditional Chinese 

zh_TW, zh_TW.BIG5

zh_HK.BIG5HK

Korean 

ko

To read the BCLs in all supported languages, refer to the printed license that is included in the Sun Management Center 3.5 media kit.

Workaround: None.

Hardware Diagnostic Suite Console Unavailable in Simplified Chinese Language Locale on Windows 98 Platform (4883371)

On systems that are running Microsoft Windows 98 software in a Simplified Chinese language locale, the Hardware Diagnostic Suite console might not launch.

Workaround: Install the English-language version of the console when running Microsoft Windows 98.

es-makeagent Does Not Support Non–English Locales (4864504)

When an es-makeagent image is used to install an agent in a non-English locale, warning messages that certain locale package directories were not found are logged in the install log file. For example:


Unable to find package directory for SUNWjaesi

Agent installation images created by using the es-makeagent command contain only the English locale packages. The es-makeagent command does not add non-English locale packages in the agent installation image.

Workaround: To install agents in non-English locales, install the agent by using any of the following methods:

Installation Messages Not Displayed Completely on Localized Environment When Using es-guiinst (4841202)

When you use the es-guiinst command to install on Asian locales, installation messages on some of the screens are not completely displayed. This problem also occurs in the English locale when larger system font sizes are used.

Workaround: Manually size the screen to display the text or maximize the screen to display the text.

Using es-inst Command to Install Add-On Product From Sun Management Center 3.5 Installation 1 of 2 CD Fails to Install Non–English Packages (4862856)

Non-English locale packages are not installed when you use the es-inst command-line script to install an add-on product from the Sun Management Center 3.5 installation 1 of 2 CD. This problem occurs in the following instances:

The following error message is displayed:


All supported languages are installed.
Note –

This bug does not occur on agent-only machines.

Workaround: Install the add-on product from the Sun Management Center 3.5 Installation 2 of 2 CD. Follow these steps:

  1. Log in as superuser to the machine on which the Sun Management Center server and agent have been installed.

  2. Insert the Sun Management Center 3.5 installation 2 of 2 CD in the CD-ROM drive.

  3. Install the add-on using either the es-inst command–line script or the es-guiinst command:

    • To use the command line install es-inst, do the following:

      1. Type the following command:


        # /opt/SUNWsymon/sbin/es-inst -S /cdrom/cdrom0/image

        The installation process checks for available add-on products. When the check for add-on products finishes, add-on products that have not been installed are listed one at a time. You are asked whether you want to install the add-on product.

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

        When you have completed your selections, the add-on products you have selected are installed.

    • To use the graphical install es-guiinst, do the following:

      1. Type the following command:


        # /opt/SUNWsymon/sbin/es-guiinst

        The Welcome screen is displayed. Click Next. The Specify the Installation Files Source Directory screen is displayed. Make sure that you have inserted the installation 2 of 2 CD in your CD-ROM drive.

      2. When you are prompted to enter the source directory, type the following command:


        # /cdrom/cdrom0/image

      3. Click Next.

        The installation process checks for available add-on products. When the check for add-on products finishes, the Products Already Installed screen is displayed.

      4. Click Next.

        The Select Add-on Products screen is displayed. Add-on products that have not been installed are listed.

      5. Select the add-on products that you want to install. Click Next.

        The products you selected are installed.

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

  4. For setup procedures for each add-on product you have selected, refer to the add-on supplement that was provided with the Sun Management Center 3.5 release kit.

es-guiuninst Uninstalled Add-On Products Summary Panel in Non-English Locales Erroneously Displays Product Environment Component (4873795)

When you uninstall an add-on product using the es-guiuninst tool, a summary panel listing all the add-on components that were uninstalled is displayed. When you use this tool to uninstall add-on components in non-English locales, Product Environment is erroneously listed in the summary panel as one of the add-on components that was uninstalled.

Workaround: Ignore the Product Environment uninstalled message. The component was not uninstalled.

Disabled ASCII Characters Might Cause Installation to Not Continue (4765662)

If you use the es-guiinst command to display the window on another X11 display server, either by specifying the -display option or by setting the environment variable to DISPLAY, the installation might not continue.

This problem occurs because you are unable to type ASCII characters in text fields, and the ASCII characters are not displayed.

Workaround: When you encounter this problem, use the es-inst and es-setup commands to perform the installation and setup. Refer to the Sun Management Center 3.5 Installation and Configuration Guide for more information about using the es-inst and es-setup commands.

Localization Information That Pertains to Sun Management Center 3.5 Add-On Products

Supported Languages and Locales for Sun Management Center 3.5 Add-On Products.

The supported languages and locales for the following Sun Management Center 3.5 add-on products are listed in Table 1–2:

Table 1–2 Supported languages and Locales for Sun Management Center 3.5 Add-On Products

Languages 

Locales 

French 

fr

fr_ FR.ISO8859-15

Japanese 

ja

Korean 

ko

Simplified Chinese 

zh

Traditional Chinese 

zh_TW

Localization Bugs That Apply to Sun Fire 15K/12K Systems, Sun Fire 6800/4810/4800/3800 Systems, Starfire Servers, and Sun Enterprise 6500/5500/4500/3500 Systems

es-inst Install Script and Graphical User Interface Panels Display Inapplicable Add-On Products (4812402)

The es-inst CLI install script and the graphical user interface (GUI) panels for non-English locales display add-on products that are not applicable to running Sun Management Center 3.5 software on your system.

Workaround: Select only those add-on products that are applicable to running Sun Management Center 3.5 software on your system. Refer to the table of add-on products in your Sun Management Center 3.5 supplement for more information about which products apply to your system.

Incorrect Localization Add-On Packages Are Installed When Using Agent-Update (4865224)

Rather than installing only the packages that pertain to each add-on component, all the localization packages in an agent-update image are installed.

Workaround: Create an agent-update image for each add-on component and perform an Agent Update for each add-on component. Refer to the Agent Update section in your Sun Management Center 3.5 supplement for more information.

Sun Fire 15K/12K Systems Bug

Message Displayed by Sun Management Setup Wizard Might Be Truncated (4860962)

The following message that is displayed by the Sun Management Center Setup Wizard for a Sun FireTM 15K/12K system might be truncated after the word regenerated and before the word because:


The Sun Management Center security keys must be regenerated because
the platform agent port number has been changed.

Workaround: To view the entire message, refer to the preceding text.

Sun Fire Link Bugs

Sun Fire Link Remote Shared Memory (WRSM) Proxy Core Dumps if Patch Is Not Installed (4719746)

If the Remote Shared Memory (RSM) patch 109664-10 is not installed on your system, and you try to configure a two-node direct connect using Sun Management Center software, the WRSM proxy on the cluster node core dumps.

Workaround: Install on the system patch 109664–10.

Manage Extended Markup Language (XML) Configurations Option Produces an Invalid Error Message When Applying an XML File to a New Fabric (4855354)

You can use the Sun Management Center console's Manage XML Configurations option to open an XML file for editing. You can also apply any configuration information the file contains to an unconfigured fabric. The term unconfigured fabric refers to a fabric that has been created and started, but does not yet contain any member data, such as descriptions of compute nodes.

Note –

An XML file can be opened for editing without being associated with an unconfigured fabric. However, if the file will be used to configure a fabric, that fabric must first be created and started. See Document Affected: Appendix B, “Importing Preconfigured XML Files Using the Manage XML Configurations Option” in Sun Fire Link Fabric Administrator's Guide (4841740).

When you select the Manage XML Configuration option, two dialog windows might be displayed. If there is only one Configuration window, you can proceed with your configuration. If there are two dialog windows, the active window is labeled Error and the inactive window is labeled Configuration. The Error window displays the following message:


Getting FM Info Values

This message is generated because the newly created fabric name does not yet contain fabric data. Ignore this message and proceed with importing the XML configuration file.

Workaround: Complete the following steps to finish applying the fabric data contained in an XML file to an empty fabric:

  1. Press the OK button on the Error dialog window.

    This closes the Error window, making the Configuration window the active window.

  2. In the Look In field of the Configuration dialog window, enter the full path of the directory that contains the XML configuration file you want to import. Press Return.

    Displayed in the window is a list of the files that are contained in the specified directory.

  3. Select the XML configuration file that you want to import. The file name is displayed in the File Name field.

  4. Click the Open button to open the selected file.

    The contents of the selected file are displayed in the viewing area. If you want to change the file, you can edit the file here. If you want to use the contents to configure a fabric, proceed to Step 5.

    Note –

    You must press Return in Step 2 and then select the XML file of interest, as described in Step 3. Do not bypass the list that is displayed and manually enter the file name in the File Name field. The file will not open if you manually enter the file name.

  5. Click on the Configure button to apply the XML file contents to the fabric.

Bug That Applies to Sun Fire 15K/12K Systems and Sun Fire Link Systems

Removal of Sun Management Center 3.0 Software Also Removes SUNWwccmn Package (4824529)

The Sun Management Center es-uninst tool automatically removes the SUNWwccmn package from the system controller (SC) on Sun Fire 15K/12K systems. This package contains software that is required by the Sun Fire Link system software (wcapp). In a System Management Services (SMS) 1.3 environment, if the SUNWwccmn package is not present on the SC, the wcapp software cannot be restarted. As a result, SMS 1.3 will fail.

Workaround: If the SUNWwccmn package is removed from the SC, use the pkgadd command to reinstall the package on the SC.

The SUNWwccmn package is provided on the Sun Fire Link software distribution CD. Refer to the Sun Fire Link Software Installation Guide for more details.

Bug That Applies to Sun Fire 15K/12K Systems, Sun Fire 6800/4810/4800/3800 Systems, and Sun Enterprise 6500/5500/4500/3500 Systems

es-validate Command Indicates Domain Dynamic Reconfiguration Module Is Not Set Up After Update (4857280) (4858900)

During a regular setup, the setup script checks all the add-on software and runs the setup script, if needed. The Dynamic Reconfiguration (DR) module does not have a setup script. The module does not need to be set up. After the Agent Update, the es-validate script indicates that the DR module was not set up.

Note –

Bugs 4857280 and 4858900 affect all locales.

Workaround: When running the es-validate script, ignore the not set up state that is displayed for the DR module.