test

Sun Management Center 3.5 Update 1 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.

Installation Bugs

Cannot Install Sun Management Center 3.5 Update 1 on Windows 98 Platform from CD-ROM (5035612)

When you install Sun Management Center 3.5 Update 1 on the Windows 98 platform, you receive an error message that it cannot find localization files. On Windows 98 the SYSTEMDRIVE variable needs to be set in the autoexec.bat file for the value of this variable to be accessible on the MS-DOS prompt. For Sun Management Center 3.5, the installer used to assume C: would be the default Microsoft Windows installation directory and drive. But on machines where the system drive is something other than C:, the installer fails.

To eliminate this issue, the installers were enhanced to detect the Microsoft Windows installation drive and proceed with this drive instead of assuming C: drive as the installation directory and drive. On other Microsoft Windows operating systems, the default installation drive and directory are available at the MS-DOS prompt. But for Windows 98 the default drive is not defined.

Workaround: You have several options:

Using the JumpStart Script from Previous Sun Management Center Releases Fails to Install the x86 Agent and Shows an XML Library Message (5030308)

Using the JumpStartTM script from previous Sun Management Center releases fails to install the x86 agent and produces an XML library message. Because of differences between SPARC and x86 architecture, you might see these messages: 


WARNING: Cannot determine the hostname on /a using default registry name
Registry_localhost .xml SML shared object library not accessible

Workaround: None.

es-inst -R Command With Documentation Fails When SUNWsdocs Does Not Exist on Remote Host (5025112 )

If the remote server does not have the documentation package SUNWsdocs, installing the Sun Management Center 3.5 Update 1 server layer on a remote machine might fail.

The command es-inst —R /net/remote_server fails when you add the documentation package SUNWpsmd. Because the package SUNWpsmd depends on SUNWsdocs, if SUNWsdocs is missing, the installation exits.

Workaround: Make sure the remote server has the SUNWsdocs package installed before installing the Sun Management Center 3.5 Update 1 documentation.

Installation From CD or CD Image Requires Full Path for es-inst script (4975862)

When you install Sun Management Center 3.5 or Sun Management Center 3.5 Update 1, you must give the full path for the es-inst script. Running the es-inst script from the /cd-image-dir/disk1/sbin directory or /cdrom/cdrom0/sbin directory does not work. If you change the directory to /cdrom/cdrom0/sbin and give the complete path, the script does not work. Your working directory should not be /cdrom/cdrom0/sbin.

Workaround: If you are installing from the CD, change to the root directory (/) and type the full path: 


# cd /
# /cdrom/cdrom0/sbin/es-inst
If you are installing from the CD image, change to the root directory and type the full path:

# cd /
# /cd-image-dir/disk1/sbin/es-inst

Start Script Might Display Error Messages: Could not start Grouping service or Could not start Platform Agent (4851517, 5016981)

You might see these error messages when you run the es-guiinst command on the Sun Fire 15K system controller or when the 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 does 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 n seconds.

Workaround: Complete the following workaround:

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

    Type the following command:


    /usr/bin/ps -eaf | grep esd

  2. To verify whether the Grouping service is running, type the following command:


    /usr/ucb/ps —wwxa | grep SunMCService

  3. To verify whether the Java server is running, use the following command:


    /usr/ucb/ps —wwxa | grep java | grep ServerMain

  4. To verify whether the web server is running, type the following command:


    /usr/ucb/ps —wwxa | grep java | grep tomcat

  5. To verify whether the Hardware Service is running, type the following command:


    /usr/ucb/ps —wwxa | grep java | grep HWDS

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

Bugs That Require a Patch Before Installing Sun Management Center 3.5 Update 1 on the Solaris Platform

Performance Reporting Manager Database Setup Fails During Upgrade to Sun Management Center 3.5 Update 1 (4974121)

When you upgrade from Sun Management Center 3.5 to Sun Management Center 3.5 Update 1, the setup for the Performance Reporting Manager database fails and you might see the following error messages: 


No such file or directory Unable to fix permissions for export files 
Aborting Performance Reporting Manager database setup 
performing a (shutdown immediate)...... 
Database setup failed: db-setup.sh failed 
A problem occurred with Performance Reporting Manager setup. 
Do you want to continue (y|n|q)

Workaround: Apply the following Sun Management Center 3.5 patch before performing an upgrade:

System Availability Manager Data Not Imported During Upgrade to Sun Management Center 3.5 Update 1 (5011762)

If you have System Availability Manager data to import when you upgrade from Sun Management Center 3.5 to Sun Management Center 3.5 Update 1, you might receive the error message: 


Couldn't find SAM data (Modules, rows, scheduler, alarm data)

Workaround: If you use the System Availability Manager add-on, apply the following patch to Sun Management Center 3.5 before upgrading to Sun Management Center 3.5 Update 1.

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:

Localization Bugs That Occur During Installation

When Using GUI (es-guiinst) to Install Sun Management Center 3.5 Update 1 in French, Japanese, and Korean Locales, CD Does Not Eject (5054110)

If you use the GUI installer for Sun Management Center 3.5 Update 1 (es-guiinst), the Sun Management Center 3.5 Update 1 Software CD 1 of 2 does not eject.

Workaround: You have several options:

Also, if you are doing multiple installations of the software, copy the CD image onto your hard disk drive and then install from the CD image.

Localized Documents Missing and Link to Localized Document Missing from CD (5054094 )

The following localized documents are missing from the Sun Management Center 3.5 Update 1 Software CDs:

The list of Traditional Chinese HTML documentation is missing a link for the following file: Sun Management Center Hardware Diagnostic Suite 2.0 User's Guide (817-3047).

Workaround: To access these documents, go to http://docs.sun.com and choose the appropriate localized collections from the Sun Management Center 3.5 Update 1 Software collection.

If You Install Documentation During Installation, Localization Documentation Packages Not Installed (5049698)

If you install documentation during installation, the following localized packages are not installed:

Workaround: Use pkgadd to install the localized documentation packages. For more information, see “Installation Overview” Chapter.

During Installation Question on Migration of Service Availability Manager Data Is Not Translated (5032183)

If you chose a language other than English during installation, the following question is not translated:


Do you want to migrate the Service Availability Manager data (y|n|q)

If you answer this question incorrectly, you could lose your Service Availability Manager data.

Workaround: Make sure you understand this question before answering. For a translation of this question, see the localized version of these release notes.

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 (4874523)

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-8zh_CN.UTF-8, zh.GBK, zh_CN.GBK, zh_CN.GB18030

Traditional Chinese 

zh_TW.UTF-8

Korean 

ko.UTF-8ko_KR.UTF-8

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

Language 

Locale 

Japanese 

ja, ja_JP.PCK, ja_JP.EUC

Simplified Chinese 

zh, zh_CN.EUC

Traditional Chinese 

zh_TW, zh_TW.BIG5,

zh_TW.EUC

Korean 

ko, ko_KR.EUC

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

Workaround: None.

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.

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.

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

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

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

Table 1–1 Supported languages and Locales for Sun Management Center 3.5 Update 1 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 High-End (15K/12K) Systems, Sun Fire Midrange Systems, Starfire Servers, and Sun Enterprise 6500/5500/4500/3500 Systems

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 Update 1 add-on supplement for more information.

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 patch 109664–10 on the system.

Manage Extensible 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 that 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 is used to configure a fabric, that fabric must first be created and started.

When you select the Manage XML Configuration option, two windows might be displayed. If only one Configuration window appears, you can proceed with your configuration. If two windows appear, 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: For the Solaris 8 release, apply patch 114995–01.

Bug That Applies to Sun Fire High-End (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 on Sun FireTM High-End (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 system controller, the wcapp software cannot be restarted. As a result, SMS 1.3 fails.

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

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

Bug That Applies to Sun Fire High-End (15K/12K) Systems, Sun Fire Midrange Systems, and Sun Enterprise 6500/5500/4500/3500 Systems

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

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

Note –

This bug affects all locales.

Workaround: Ignore this message displayed for the DR module.