test

Sun Management Center 3.6.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

Start Script Might Display Error Messages (4851517)

Start script might display error messages like Could not start Grouping service or Could not start Platform Agent.

You might see these error messages when you run the es-guiinst command on the Sun Fire system controller or when the Sun Management Center components are started on a heavily loaded machine.

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 -ef | grep esd
    Note –

    (On Solaris 10) The command would be /usr/bin/ps -fz global | grep esd on a global zone and /usr/bin/ps -fe | grep esd on a non-global zone.

  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.

GUI-Based Incremental Installation Is Not Possible on Linux (6410179)

Workaround: Use CLI to perform incremental installation on Linux.

Uninstallation Hangs While Trying to Uninstall Agent and Base Add-ons Together in Solaris10 Update2 System

Workaround: Unload the Fault Manager Plug-in manually using the fmadm command before uninstalling the agent. The steps are as follows:

  1. Unload the libfmalm module by typing fmadm unload libfmalm.

  2. Uninstall the agent by typing es-uninst -X.

Installation Information That Applies to the Add-On Software for Sun Fire Entry-Level Midrange Systems

Installing Sun Management Center 3.6 Version 3 Add-On Software for Sun Fire Entry-Level Midrange Systems: Required for Netra 1290 Systems

If you are installing the add-on software for Sun Fire entry-level midrange systems, release 3.6 Version 3 is strongly recommended.

Note –

For support of Netra 1290 systems, release 3.6 Version 3 is required. Even if you have previously installed the release 3.6 Version 3 add-on software, you must install it again after installing the core 3.6.1 software.

ProcedureTo Install Sun Management Center 3.6 Version 3 Add-On Software

Steps

  1. When installing the Sun Management Center 3.6.1 software, do not install the Sun Fire Entry-Level System product.

  2. After you have installed the Sun Management Center 3.6.1 software, obtain the Sun Management Center 3.6 Version 3 add-on software.

    The add-on software packages are supplied in a zip file on the software download site at http://wwws.sun.com/software/download/index.html

    If you do not see the listing for Sun Management Center 3.6 Version 3 under New Downloads, use the A-Z Index of All Products to find the software.

    Refer to the Sun Management Center 3.6 Version 3 Add-On Software Release Notes for Sun Fire Entry-Level Midrange Systems for information about installing this release.

    The release notes document is available at http://docs.sun.com/

    Follow the instructions in the section “Updating From Sun Management Center 3.6 Software,” replacing references to the core Sun Management Center 3.6 software with “3.6.1.”

Localization Bugs That Occur During Installation

Advanced System Monitoring (ASM) Setup Messages Are Not Localized (6387101)

One of the localized packages of ASM (SUNW*am) is not installed on the server layer. Hence, you will see the setup messages only in English language.

String messages are displayed in English language in localized versions. The messages affected are in File Scanning, Fault Manager, HP JetDirect, IPv6 Instrumentation, LogView ACL, Print Spooler, Health Monitor, MIB-II Instrumentation, Service Management Facility, NFS File Systems, NFS Statistics, Process Monitoring, Kernel Reader, Solaris Process Details, Directory Resize Monitoring modules, and View Logs tab on the Java Console.

Workaround: Follow these steps:

  1. Become superuser by typing:

    # su -

  2. Change to the required directory.

    cd <imagedir>/disk2/image/SunOS/<arch>/Addons/AdvancedMonitoring/Common/Basic

  3. Add the SUNW*am package manually.

    # pkgadd -d <packagename>

    Packages for localized versions are SUNWfram (French), SUNWjaam (Japanese), SUNWkoam (Korean), SUNWcam (Simplified Chinese), and SUNWham (Traditional Chinese).

Note –

When you uninstall ASM, you need to remove these packages manually by executing the pkgrm command.

Software License Agreement and Supplemental Terms and Conditions for Some Asian Locales Are in English Language (4874523)

During installation, the Software License Agreement (SLA) and Supplemental Terms and Conditions for the following Asian locales are in English language:

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 SLA 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 SLAs in all supported languages, refer to the printed license that is included in the Sun Management Center 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.

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

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

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

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

Languages 

Locales 

French 

fr

fr_ FR.ISO8859-15

Japanese 

ja

Korean 

ko

Simplified Chinese 

zh

Traditional Chinese 

zh_TW

Bug That Apply to Solaris Container Manager

Installing Sun Web Console 2.2.3 Software

The Sun Web Console 2.2.3 software must be installed before installing Sun Management Center 3.6.1. The Sun Management Center graphical user interface (GUI) is browser based. To use the GUI, you must install the Sun Web Console 2.2.3 software on the Sun Management Center server layer. The Sun Web Console 2.2.3 software is included on the Sun Management Center 3.6.1 media and must be installed if you are running either the Solaris 8 or 9 Operating System.

By installing Sun Web Console 2.2.3 before installing Sun Management Center or Sun Management Center, you ensure the following:

If an earlier version of the Tomcat server is currently installed, you need first to remove the corresponding software package.

The Sun Web Console software depends on, at minimum J2SE 1.4.2 software, which is included. If you have an older version of J2SE, the installation script prompts you to update the J2SE software.

Note –

If you have a beta version of Sun Web Console 2.2.3 already installed, you must uninstall Sun Web Console 2.2.3 first. For more information, see To Uninstall Sun Web Console.

ProcedureTo Install Sun Web Console From the Media

Note –

You must install the Sun Web Console software only in the default location.

Steps

  1. Become superuser by typing:


    % su -

  2. If you have the Tomcat server already installed, check the version by typing:


    # pkginfo -l SUNWtcatu

    The version that is included with the Sun Web Console software is identified as 11.9.0,REV=2002.03.02.00.35.

  3. If your version starts with 11.8.0 or lower, remove the Tomcat server by typing: 


    # pkgrm SUNWtcatu

    The correct version is later installed as part of this procedure.

  4. Insert the Sun Management Center 3.6.1 Media

  5. Change directories to where the Sun Web Console software is located by typing:


    # cd <DiskMountDir>/image/SunOS/sparc/Lockhart2.2.3/sparc

  6. Set the JAVA_HOME variable. For example, in the C shell, type: 


    # setenv JAVA_HOME /usr/j2se/bin

  7. Install the software by typing:


    # ./setup

    • If the system has J2SE version 1.4.2 software installed, the installer automatically installs the Sun Web Console software. Wait until the installation is completed.

    • If the system has a J2SE version lower than 1.4.2 installed, J2SE version 1.4.2 software is automatically installed along with the Sun Web Console software. Wait until the installation is completed.

  8. At the end of installation, the following message is displayed: 


    Installation complete.
Server not started! No management applications registered

    This is a valid message.

  9. Enable the automatic startup of Sun Web Console at reboot by typing:


    # /usr/sbin/smcwebserver enable

  10. Continue with the installation of the Sun Management Center 3.6.1 software.

    For more information, see the following:

ProcedureTo Start Sun Web Console

After installation of all software is complete, you must start the Sun Web Console before you can use the Sun Management Center GUI.

Steps

  1. Start a browser.

  2. Go to the Sun Web Console https://host_machine_name:6789

    The Sun Web Console login page appears.

ProcedureTo Uninstall Sun Web Console

If you have an earlier version of Sun Web Console software on your system, you must uninstall Sun Web Console before installing the 2.2.3 version. If you want to remove the Sun Web Console software after removing the Sun Management Center from your system, you can also use this procedure.

Note –

Ensure that you are not in the /usr/lib/webconsole directory or its subdirectories when you run setup -u, or pkgrm fails.

Steps

  1. Become superuser by typing:

    % su -

  2. To remove the Sun Web Console software package, as superuser (su -) start the removal script by typing: 


    # /usr/lib/webconsole/setup -u

  3. When the script has finished, you are prompted to remove the Tomcat server and Java 1.4.2 software. To keep this software, answer “No” to the following questions:


    If you have other work that requires use of the 
Tomcat Servlet/JSP Container software, you may wish to 
not delete it from your machine.                

Do you want to delete it? [n]? n  

If you have other work that requires use of the 
Java 1.4.2 software, you may wish to not delete it 
from your machine.

Do you want to delete it? [n]? n